CRC calculated wrong for one ROM

[Yago Méndez Vidal]

tl;dr

The ROM for Sega Master System [BIOS] Hang-On (USA, Europe) (v3.4) gets its CRC calculated wrong.

#Explanation While everthing works perfectly for any ROM I've tested, one is not working properly. I've created a database from No-Intro Sega Master System DAT file; here's the part where its defined:

    <game name="[BIOS] Hang-On (USA, Europe) (v3.4)">
        <description>[BIOS] Hang-On (USA, Europe) (v3.4)</description>
        <rom name="[BIOS] Hang-On (USA, Europe) (v3.4).sms" size="131072" crc="8EDF7AC6" md5="5CD8F62CD8786AF0226E6D2248279338" sha1="51FD6D7990F62CD9D18C9ECFC62ED7936169107E" status="verified"/>
    </game>

Romcenter lists the ROM requiring a Crc/SHA-1 of "8edf7ac6" as in the DAT.

I checked the sums for the ROM dumped by SMS Power:

$ ls -go "[BIOS] Hang-On (USA, Europe) (v3.4).sms"
-rwx------+ 1 131072 sep.  4  2000 '[BIOS] Hang-On (USA, Europe) (v3.4).sms'

$ crc32 "[BIOS] Hang-On (USA, Europe) (v3.4).sms"
8edf7ac6

$ sha1sum "[BIOS] Hang-On (USA, Europe) (v3.4).sms"
51fd6d7990f62cd9d18c9ecfc62ed7936169107e *[BIOS] Hang-On (USA, Europe) (v3.4).sms

Strangely enough, when loaded into Romcenter, that file appears with a Crc/SHA-1 of "161fbfcf" and a Real format of ".gg".

Being one single ROM failing, I've been thinking it's a mistake on my side, but I'm unable to figure out what's happening and all points to something now working ok in the application.

[Eric Bole-Feysot]

Hi The datafile specifies to romcenter to use the sms plugin. With this plugin, romcenter analyses the rom structure and skip any non relevent data to calculate the crc. Then it suggests an extension which matches the file structure.

But in your case, this rom is not a 'real' rom, it is a bios. These roms will be handled correctly in the next verison.

[Yago Méndez Vidal]

Thanks for your answer.

I get what you mean and understand it, but this issue went a bit further today: I did a Reload of the folder with the ROMs and one game that initially was accepted, Sonic Spinball (Europe, Brazil), now appears as unknown. The checksums are OK manually but Romcenter again calculates it wrong, and in this case it's a regular game (not a BIOS) and recognizes a .sms format.

Just telling for adding more information to the issue, I'll check in the next release. Thanks.

[Yago Méndez Vidal]

Iv've tried the RomCenter plug in ther module with the sms.dll plugin for that last ROM I commented and I'm getting a different checksum in the application than in the test module.

Again, this project is fantastic, thanks, I'm just trying to add feedback for fixes.

[Eric Bole-Feysot]

Removing milestone: 4.0 (automated comment)

[Jason Siebert]

I am having this same issue now with the exact same rom with the latest 4.1.1 Romcenter. All details listed in the original issue are pertinent to what I’m experiencing. The hash it looks for is 8edf7ac6 but when romcenter calculates the hash for the file I have it has 161fbfcf. I verified the hash of my file to be 8edf7ac6. Should I open another issue?