|
|
Re: Emu Loader frontend and MAME sets with CRC32 collisions (different files, same CRC32)
09/02/16 09:55 PM
|
|
|
double entries like in indytemp hmmm...no idea..haven't looked at the mamesource if they are listed twice accidently (unless they are really mirrored on the original board for whatever reason)
different names/same checksums...pretty common....especially within parent/clone relationsships...since MAME wants to use the actual IC naming of the board it can happen that they are named differently
same names/differnt checksums within a parent/clone relationship...yeah great...can happen, too for obvious reasons, you only run into issues if you want to fully merge the sets (you need a way to avoid overwriting)
crc32 collisions (same crc32, different sha1) within a set can be found in .177 in naomigd (bios) set with the checksum a738ea1c
|
|
Index 
Flat 
Re: Emu Loader frontend and MAME sets with CRC32 collisions (different files, same CRC32)
Reply
