![]() ![]() ![]() When comparing that GS*.z64 to the Read Cartridge GPERROR.z64, they do differ after even truncating my 4.2MB GPERROR.z64 to 262144 bytes. It ended up not corrupting the Gameshark or SD card, and no new image was written to it. At this point, I waited a few seconds for any sync needed, and then just shut off the power, careful to not press the buttons. If I, instead, choose the Flash Gameshark option, it immediately saves a backup of the current Gameshark ROM as GS.z64 in a Gameshark directory. This is the first string in my GPERROR ROM: Running the GNU/Linux command "strings" on it, reveals where the title comes from. If I dump it anyway, I get a CRC ERROR (the gameshark's own unchanging checksum is always used), but if I choose to ignore that, and read the ROM in the GPERROR directory (GPERROR.Z64) it exists probably as it should (although I'm not sure which size ROM to specify when reading it). It's just telling us that the cartridge is unknown due to no match in the n64.txt file database, which seems understandable to me if each inserted cartridge generates new boot code, while the checksum is always falsified by the gameshark, it would never match when compared to the actual data. The reason for the error seems to be that the header is patched by the game inserted into the gameshark, by the gameshark itself: ![]() The detected title in my case is: CMUSHROOMNU184 (ID:2 99) I too have the Pro v3.2 (not reflashed, as in your case), and mine gives a similar error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |