new value: This cart, like any of the 32MB games using this PCB, has up to four bytes written incorrectly by most dumpers, starting at 0x1FFFF00, as this area mapped to save-chip functions, but on the chip match the 0xFF or 0x00 padding around them. As of 2024 this is corrected on the Sanni OSCR's latest build.

     old value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF02 are mapped to save-chip functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build.

     new value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF02 are mapped to save-chip functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build.

     old value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF01 are mapped to SRAM functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build.

     new value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF01 are mapped to SRAM functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build.

     old value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF01 are mapped to SRAM functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build

     new value: This cart, like any of the 32MB games using this PCB, has two bytes written incorrectly by most dumpers. 0x1FFFF00 and 0x1FFFF01 are mapped to SRAM functions, but are located within FF padding and on the chip are simply FF padding like that around them. As of 2024 this is corrected on the Sanni OSCR's latest build

     new value: Games

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, as is much of the rom after the differences, but there's no record of a revision being produced. Oddly, closer match to the EU version than a proper dump (possible hack/proto?)

     old value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, as is much of the rom after the differences, but there's no record of a revision being produced. Oddly, closer match to the EU version than a proper dum (possible hack/proto?)

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, as is much of the rom after the differences, but there's no record of a revision being produced. Oddly, closer match to the EU version than a proper dum (possible hack/proto?)

     old value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, as is much of the rom after the differences, but there's no record of a revision being produced.

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, as is much of the rom after the differences, but there's no record of a revision being produced.

     old value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, and there's no record of a revision being produced.

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different for a large chunk. However, the header and first small bit are the same, and there's no record of a revision being produced.

     old value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different. However, the header and first small bit are the same, and there's no record of a revision being produced.

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different. However, the header and first small bit are the same, and there's no record of a revision being produced.

     old value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different. However, the header is the same, and there's no record of a revision.

     new value: Doesn't match proper dump at all. On a diff, changes seem interwoven throughout the rom, with over half different. However, the header is the same, and there's no record of a revision.

     new value: Bad

     new value: 1

     old value: 0