Merged roms possible solution
Posted: Mon Apr 14, 2008 9:09 pm
Hi Eric!
This feedback will help when users do merged romset fusion. A user had that problem and I'd like to present it to you.
Ussually we find the classical add:
SAME FILE, DIFFERENT CRC:
xxx (12345678)
xxx (90abcdef)
It means that RC wil read only the first one or even to DELETE the file - in my oppinion I DON'T WANT IT!
A boring solution that I've done for months is to rename files whose have that problem. IE: Neogeo games:
217-p1.bin (5a5s8e1b)
217-p1.bin (78aab741)
The first one os ok, but the other is needed because IS MERGED, SO I RENAME IT:
217-p1.bin (5a5s8e1b)
217--p1.bin (78aab741)
And holy solution. Even if RC says that the romfile is wrong, it must read it properly due to CRC and SHA id number.
Could your RC read the CRC and rename files IF NECCESARY IN MERGED ROMSETS? It works for me, even if the games are marked in yellow and the file says "wrong name". If I fix it... the rom goes to red instead to green.
See you!
This feedback will help when users do merged romset fusion. A user had that problem and I'd like to present it to you.
Ussually we find the classical add:
SAME FILE, DIFFERENT CRC:
xxx (12345678)
xxx (90abcdef)
It means that RC wil read only the first one or even to DELETE the file - in my oppinion I DON'T WANT IT!
A boring solution that I've done for months is to rename files whose have that problem. IE: Neogeo games:
217-p1.bin (5a5s8e1b)
217-p1.bin (78aab741)
The first one os ok, but the other is needed because IS MERGED, SO I RENAME IT:
217-p1.bin (5a5s8e1b)
217--p1.bin (78aab741)
And holy solution. Even if RC says that the romfile is wrong, it must read it properly due to CRC and SHA id number.
Could your RC read the CRC and rename files IF NECCESARY IN MERGED ROMSETS? It works for me, even if the games are marked in yellow and the file says "wrong name". If I fix it... the rom goes to red instead to green.
See you!