|
CiroConsentino |
|
Frontend freak!
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 6211
|
|
Loc: Alien from Terra Prime... and Brazil
|
|
|
|
Send PM
|
|
Re: Emu Loader frontend and MAME sets with CRC32 collisions (different files, same CRC32)
09/02/16 07:59 PM
|
|
|
>> no need to do this for all sets...just the affected ones....
yes, I already wrote a small function to check for duplicate CRC32 in a set.
I will make EL unzip ROMs directly into RAM (using a TMemoryStream class). This will take a hell of a time to process. The good thing is it will not unzip to the hard drive...
One thing I noticed, lots of games have duplicate ROMs with same name, same CRC32 and same SHA-1... why ? One example is indytemp (Indiana Jones and the Temple of Doom (set 1)).
Others like hcastle (Haunted Castle (version M)) have ROMs with different names but same CRC32 and SHA-1 checksums. This game, I tried deleting duplicate ROMs from the hcastle.zip and MAME loaded the game without a problem. MAME didn't report missing files.
(rom name="768c13.j21" size="256" crc="f5de80cb" sha1="e8cc3e14a5d23b25fb7bf790e64786c6aa2df8b7" region="proms" offset="0")
(rom name="768c11.i4" size="256" crc="f5de80cb" sha1="e8cc3e14a5d23b25fb7bf790e64786c6aa2df8b7" region="proms" offset="200")
My frontend doesn't parse SHA-1 info from -listxml output. Do you know of a game that 2 ROMs have same CRC32 but different SHA-1 ? I can modify my frontend to find that out, but it will take days since my free time is almost none.
Ciro Alfredo Consentino
home: http://emuloader.mameworld.info
e-mail: [email protected]
Edited by CiroConsentino (09/02/16 08:00 PM)
|
|
Index 
Flat 
Re: Emu Loader frontend and MAME sets with CRC32 collisions (different files, same CRC32)
Reply
