Register - Login
Views: 99388911
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 07:40:53 AM
Jul - The Cutting Room Floor - General information about the GB/GBC Codebreaker New poll - New thread - New reply
Next newer thread | Next older thread
nensondubois
seek help please
Level: 49


Posts: 491/551
EXP: 852703
For next: 31180

Since: 05-30-10


Since last post: 7.8 years
Last activity: 7.8 years
Posted on 09-23-13 11:37:12 PM (last edited by nensondubois at 12-11-13 01:26:51 AM) Link | Quote
Added more information thanks to further testing and Andrew_Rae: Revised 1 time:

Information about the GB/GBC Codebreaker is sparse at best. I had to purchase one because I really wanted one to be able to use Game Genie codes easily with the SGB, and to possibly dump the ROM image. If this doesn't belong elsewhere, please move it away.

Here are some facts about the unit:

Description: The device is black, bulky and contains an obvious cartridge insert adapter facing the player. There is a hint of a sturdy build. The unit is assumed to have been dropped several times by the previous owner. The pin connector build is of high quality compared to the cheap Gameshark pins the easily bend over time. There is a battery compartment for rumble support (seriously, why).

*Game codes are stored via flash chip. the size is unknown, estimated to be 256kb. Supports for one "real-time" savestate exist, and one battery backup SRAM save file, which can be replaced or swapped in from memory is also present. SRAM from the currently inserted cartridge can be formatted as well.

*Supports patching of ROM addresses (or decrypted Game Genie codes). Compare values can indeed be entered. The patch code format is as follows:
B = Bank Value (ROM bank destination for patch codes. This is the bank value for the code itself, not the compare value.)
A = Address (RAM or ROM)
V = Value

BBAAAAVV (or colloquially XXYYYYZZ)

*Game Genie (ROM patch) codes can be entered comprising a total of 17 active codes. Can be combined in conjunction with RAM lock-in value codes.
*Gameshark support for 17 codes can be applied.

*Cheat search with built in button-trainer also exists for finding new cheats.

*Slow motion that fools vertical synch can be found with up to four slow speeds; setting 4 is the fastest. Anti-flickering can be used to prevent screen flickering if slow-motion is used. I have only three games and the the anti-flickering works.

*Rumble settings can be set to in-game, rhythm or off. Probably the least impressive aspect of the unit.Very useless.

*10 new pages containing an unknown amount of code storage (unless you erase an already existing page). It is also unknown how many codes can be stored per page.

*Built in quick access to entering Gamemshark and patch codes can also be entered. These cannot be saved.

*built in memory editor/viewer

*GBC menus

*Games are detected based on internal ROM name. While you can mix and match codes from different games, you can't rename game page titles, which can be annoying.

*There doesn't appear to be any glitches causing code lists to be erased or any bricking (from testing a reasonable amount)

*code list has to organised every time you make changes to a game page or code list. This takes about 10-15 seconds.

Unknown:

*SGB custom menu palette?

*How long the rumble battery lasts

Status: Undumped. PM me if you can dump the unit.
omega59
Member
Level: 29


Posts: 147/184
EXP: 144356
For next: 3529

Since: 02-25-13


Since last post: 6.5 years
Last activity: 5.0 years
Posted on 09-24-13 03:41:52 AM Link | Quote
It's quite interesting, but I believe it should go in the "ROM Hacking" section. TCRF is about games after all.
Sik

Level: 23


Posts: 62/107
EXP: 64770
For next: 2953

Since: 12-07-12


Since last post: 3.3 years
Last activity: 1.2 years
Posted on 09-24-13 03:45:32 AM Link | Quote
*cough*

That said, there's nothing unused here so it probably won't get an article. But it's undumped, so I guess the whole point is to dump it to see if there's anything hidden inside (which indeed would pertain TCRF).
Tamkis
Member
Level: 27


Posts: 58/148
EXP: 109441
For next: 6718

Since: 03-12-12


Since last post: 3.2 years
Last activity: 3.1 years
Posted on 09-24-13 04:17:54 AM Link | Quote
How would one go best about dumping a cheat device anyhow? Using yet another cheat device to dump it in a redundant fashion ? Do you have an N64, a 64Drive flashcart, and a N64 Transfer Pak? If so, the dumper's best bet would be to use the agbd gameboy dumper.

Pics of unit for the tcrf wiki page, please.

____________________
"For he who serves his fellows, is of all his fellows, greatest"
--- Urner E. Goodman
ICEknight
Member
Level: 26


Posts: 46/135
EXP: 97120
For next: 5155

Since: 10-25-11


Since last post: 4.1 years
Last activity: 3.9 years
Posted on 09-26-13 12:45:23 PM (last edited by ICEknight at 09-26-13 12:45:36 PM) Link | Quote
If it's undumped, I'm sure that somebody at the MESS forums will be interested in getting the data out of its ROM chips and attempting to emulate it.
KingMike
Member
Level: 16


Posts: 4/50
EXP: 20222
For next: 34

Since: 05-09-13


Since last post: 37 days
Last activity: 4 days
Posted on 09-29-13 02:53:16 PM Link | Quote
I had wondered if it would have been possible for someone to write a GB dumper that could work with only a Transfer Pak and a N64 controller USB adapter.

I'd guess if it was, someone would've done it by now?
omega59
Member
Level: 29


Posts: 148/184
EXP: 144356
For next: 3529

Since: 02-25-13


Since last post: 6.5 years
Last activity: 5.0 years
Posted on 09-29-13 03:47:52 PM Link | Quote
Originally posted by KingMike
I had wondered if it would have been possible for someone to write a GB dumper that could work with only a Transfer Pak and a N64 controller USB adapter.

I'd guess if it was, someone would've done it by now?

Nope, not really likely that would be possible. With a customly programmed transfer pack maybe, but it'd be better to just make a USB drive to put the cartridge into.
nensondubois
seek help please
Level: 49


Posts: 496/551
EXP: 852703
For next: 31180

Since: 05-30-10


Since last post: 7.8 years
Last activity: 7.8 years
Posted on 10-08-13 01:50:42 AM Link | Quote
Updated OP with some more information:

Originally posted by Sik
*cough*

That said, there's nothing unused here so it probably won't get an article. But it's undumped, so I guess the whole point is to dump it to see if there's anything hidden inside (which indeed would pertain TCRF).


That is one reason; ROM image preservation's sake is the second. Maybe someone can program a few EPROMS and a sturdy connector to create their own Codebreaker hash project.

____________________
Youtube.com/user/nensondubois
Keitaro

Fire Snake
LOVELY ARRANGEMENT. VOLCANO BAKEMEAT
Level: 70


Posts: 1179/1191
EXP: 2898914
For next: 116897

Since: 09-09-08

From: California

Since last post: 4.1 years
Last activity: 3.8 years
Posted on 10-09-13 09:29:22 AM Link | Quote
Originally posted by omega59
Originally posted by KingMike
I had wondered if it would have been possible for someone to write a GB dumper that could work with only a Transfer Pak and a N64 controller USB adapter.

I'd guess if it was, someone would've done it by now?

Nope, not really likely that would be possible. With a customly programmed transfer pack maybe, but it'd be better to just make a USB drive to put the cartridge into.


Why not? The transfer pack is literally just a GameBoy cartridge connection attached via ribbon cable to a circuit board which interfaces the accessory port of the N64 controller. It has full SRAM read/write capabilities, so it would stand to reason that any other functionality cartridge interfacing would entail should also work. It would just be a matter of creating something software side to actually do anything useful, I would imagine.
omega59
Member
Level: 29


Posts: 150/184
EXP: 144356
For next: 3529

Since: 02-25-13


Since last post: 6.5 years
Last activity: 5.0 years
Posted on 10-10-13 01:18:07 AM Link | Quote
Originally posted by Keitaro
Originally posted by omega59
Originally posted by KingMike
I had wondered if it would have been possible for someone to write a GB dumper that could work with only a Transfer Pak and a N64 controller USB adapter.

I'd guess if it was, someone would've done it by now?

Nope, not really likely that would be possible. With a customly programmed transfer pack maybe, but it'd be better to just make a USB drive to put the cartridge into.


Why not? The transfer pack is literally just a GameBoy cartridge connection attached via ribbon cable to a circuit board which interfaces the accessory port of the N64 controller. It has full SRAM read/write capabilities, so it would stand to reason that any other functionality cartridge interfacing would entail should also work. It would just be a matter of creating something software side to actually do anything useful, I would imagine.

Fair enough. Sounds more reasonable to me now.
Next newer thread | Next older thread
Jul - The Cutting Room Floor - General information about the GB/GBC Codebreaker New poll - New thread - New reply


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

33 database queries, 2 query cache hits.
Query execution time:  0.097309 seconds
Script execution time:  0.013764 seconds
Total render time:  0.111073 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 301 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 219 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 228 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 230 column 9 - Warning: missing <tr>
line 248 column 13 - Warning: missing <tr>
line 249 column 102 - Warning: unescaped & or unknown entity "&postid"
line 254 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 256 column 9 - Warning: missing <tr>
line 274 column 13 - Warning: missing <tr>
line 275 column 102 - Warning: unescaped & or unknown entity "&postid"
line 282 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 284 column 9 - Warning: missing <tr>
line 302 column 13 - Warning: missing <tr>
line 303 column 102 - Warning: unescaped & or unknown entity "&postid"
line 311 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 313 column 9 - Warning: missing <tr>
line 331 column 13 - Warning: missing <tr>
line 332 column 102 - Warning: unescaped & or unknown entity "&postid"
line 334 column 185 - Warning: unescaped & or unknown entity "&Board"
line 337 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 339 column 9 - Warning: missing <tr>
line 357 column 13 - Warning: missing <tr>
line 358 column 102 - Warning: unescaped & or unknown entity "&postid"
line 365 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 367 column 9 - Warning: missing <tr>
line 385 column 13 - Warning: missing <tr>
line 386 column 102 - Warning: unescaped & or unknown entity "&postid"
line 394 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 396 column 9 - Warning: missing <tr>
line 414 column 13 - Warning: missing <tr>
line 415 column 102 - Warning: unescaped & or unknown entity "&postid"
line 426 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 428 column 9 - Warning: missing <tr>
line 446 column 13 - Warning: missing <tr>
line 447 column 102 - Warning: unescaped & or unknown entity "&postid"
line 457 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 459 column 9 - Warning: missing <tr>
line 477 column 13 - Warning: missing <tr>
line 478 column 102 - Warning: unescaped & or unknown entity "&postid"
line 489 column 17 - Warning: missing <tr>
line 489 column 17 - Warning: discarding unexpected <table>
line 492 column 35 - Warning: missing <tr>
line 492 column 50 - Warning: missing </font> before </td>
line 492 column 91 - Warning: missing </font> before </table>
line 494 column 35 - Warning: missing <tr>
line 494 column 50 - Warning: missing </font> before </td>
line 495 column 37 - Warning: unescaped & or unknown entity "&id"
line 494 column 219 - Warning: missing </font> before </table>
line 496 column 17 - Warning: discarding unexpected </textarea>
line 496 column 28 - Warning: discarding unexpected </form>
line 496 column 35 - Warning: discarding unexpected </embed>
line 496 column 43 - Warning: discarding unexpected </noembed>
line 496 column 53 - Warning: discarding unexpected </noscript>
line 496 column 64 - Warning: discarding unexpected </noembed>
line 496 column 74 - Warning: discarding unexpected </embed>
line 496 column 82 - Warning: discarding unexpected </table>
line 496 column 90 - Warning: discarding unexpected </table>
line 498 column 9 - Warning: missing </font> before <table>
line 510 column 25 - Warning: discarding unexpected </font>
line 519 column 57 - Warning: discarding unexpected </font>
line 497 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 22 - Warning: <img> lacks "alt" attribute
line 161 column 63 - Warning: <img> lacks "alt" attribute
line 161 column 112 - Warning: <img> lacks "alt" attribute
line 161 column 162 - Warning: <img> lacks "alt" attribute
line 162 column 11 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 176 column 92 - Warning: <font> attribute "color" had invalid value "7C60B0" and has been replaced
line 233 column 22 - Warning: <img> lacks "alt" attribute
line 233 column 63 - Warning: <img> lacks "alt" attribute
line 233 column 112 - Warning: <img> lacks "alt" attribute
line 233 column 162 - Warning: <img> lacks "alt" attribute
line 244 column 15 - Warning: <img> lacks "alt" attribute
line 259 column 22 - Warning: <img> lacks "alt" attribute
line 259 column 63 - Warning: <img> lacks "alt" attribute
line 259 column 112 - Warning: <img> lacks "alt" attribute
line 259 column 162 - Warning: <img> lacks "alt" attribute
line 270 column 15 - Warning: <img> lacks "alt" attribute
line 287 column 22 - Warning: <img> lacks "alt" attribute
line 287 column 63 - Warning: <img> lacks "alt" attribute
line 287 column 112 - Warning: <img> lacks "alt" attribute
line 287 column 162 - Warning: <img> lacks "alt" attribute
line 298 column 15 - Warning: <img> lacks "alt" attribute
line 305 column 198 - Warning: <img> proprietary attribute value "absmiddle"
line 305 column 198 - Warning: <img> lacks "alt" attribute
line 316 column 22 - Warning: <img> lacks "alt" attribute
line 316 column 63 - Warning: <img> lacks "alt" attribute
line 316 column 112 - Warning: <img> lacks "alt" attribute
line 316 column 162 - Warning: <img> lacks "alt" attribute
line 327 column 15 - Warning: <img> lacks "alt" attribute
line 331 column 92 - Warning: <font> attribute "color" had invalid value "7C60B0" and has been replaced
line 342 column 22 - Warning: <img> lacks "alt" attribute
line 342 column 63 - Warning: <img> lacks "alt" attribute
line 342 column 112 - Warning: <img> lacks "alt" attribute
line 342 column 161 - Warning: <img> lacks "alt" attribute
line 353 column 15 - Warning: <img> lacks "alt" attribute
line 370 column 22 - Warning: <img> lacks "alt" attribute
line 370 column 63 - Warning: <img> lacks "alt" attribute
line 370 column 112 - Warning: <img> lacks "alt" attribute
line 370 column 162 - Warning: <img> lacks "alt" attribute
line 381 column 15 - Warning: <img> lacks "alt" attribute
line 399 column 22 - Warning: <img> lacks "alt" attribute
line 399 column 63 - Warning: <img> lacks "alt" attribute
line 399 column 112 - Warning: <img> lacks "alt" attribute
line 399 column 162 - Warning: <img> lacks "alt" attribute
line 400 column 11 - Warning: <img> lacks "alt" attribute
line 410 column 15 - Warning: <img> lacks "alt" attribute
line 430 column 11 - Warning: <img> lacks "alt" attribute
line 431 column 22 - Warning: <img> lacks "alt" attribute
line 431 column 63 - Warning: <img> lacks "alt" attribute
line 431 column 112 - Warning: <img> lacks "alt" attribute
line 431 column 162 - Warning: <img> lacks "alt" attribute
line 442 column 15 - Warning: <img> lacks "alt" attribute
line 462 column 22 - Warning: <img> lacks "alt" attribute
line 462 column 63 - Warning: <img> lacks "alt" attribute
line 462 column 112 - Warning: <img> lacks "alt" attribute
line 462 column 162 - Warning: <img> lacks "alt" attribute
line 473 column 15 - Warning: <img> lacks "alt" attribute
line 495 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 495 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 495 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 504 column 25 - Warning: <img> lacks "alt" attribute
line 509 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 489 column 17 - Warning: trimming empty <tr>
line 492 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 249 column 27 - Warning: <nobr> is not approved by W3C
line 275 column 27 - Warning: <nobr> is not approved by W3C
line 303 column 27 - Warning: <nobr> is not approved by W3C
line 332 column 27 - Warning: <nobr> is not approved by W3C
line 358 column 27 - Warning: <nobr> is not approved by W3C
line 386 column 27 - Warning: <nobr> is not approved by W3C
line 415 column 27 - Warning: <nobr> is not approved by W3C
line 447 column 27 - Warning: <nobr> is not approved by W3C
line 478 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 163 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md