Bad checksum error snes9x rom corruptor4/11/2024 ![]() Is that a cartridge of yours, Cody? Can you tell us anything about its origin, when/why it started glitching, etc? Qyzbud wrote:That first video is one of Cody's, so he might be able to help explain a bit of what's going on. So either (A) the cart has bit-rot which makes some of the code on the ROM bad, which then potentially corrupts both RAM and SRAM or (B) someone managed to screw up the cart by pulling it out while the console is on - which could probably do anything to it or (C) somebody tried a fatal game glitch and corrupted the SRAM to the point of no return.Īnd by the way, DKC3's SRAM saves have a checksum, so aside from ROM bit-rot, DKC3 is resistant to save errors. ![]() The SRAM becomes scrambled to the point of no return, and the only way to "fix" a bad SRAM save is for the SRAM backup battery to go dead (battery going dead also means you won't be able to actually save the game, it won't retain any save data without the battery's power).ĮDIT: You could replace the battery, if that's even do-able in the first place, but you'd need a Gamebit to get into the cart. but only if the game saves out direct pointers to code routines or locations of critical game resources organized somewhere in ROM memory if that corrupts, the entire cart could be "permanently" screwed up (because the bad save data cannot load properly, the game crashes almost immediately).ĭKC2 has the fatal Castle Crush glitch, which I suspect does something like this. This in turn can also corrupt values in the SNES RAM memory, and from there it's anyone's guess.Īnd yes, it is possible for the game to be messed up by a bad save. I suspect that the cartridge has bit-rot, making some of the code go wonky. Notice that the 904 bananas does not change when bananas are collected.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |