Romcenter

Hi,

I have a small collection of ROMs which are so far stored in SPLIT mode.
Due to the fact that I wanted to reduce the disk space used I tried to MERGE them.
Problem: each and every DAT I either create or download from Logiqx shows some inconsistencies which result in deletion of specific roms.

How can this be solved?

Thanks in advance
Davy

Which version of romcenter are you using ?

I tried it with
2.71 and
3.0 alpha6

Can you post an example: datafile or mame version and a game where some roms are deleted during a split-merge conversion ?

OK I just generated a new DAT using RC2.71 and latest DATutil 2.32 for MAME 1.21.

One of the inconsistent examples is:

Game punchout, rom chp1-c.8l (a4003adc)
Game punchout, rom chp1-c.8l (1d595ce2)

Another one is:

Game rastan, rom b04-40.20 (0930d4b3)
Game rastan, rom b04-40.20 (6bcf70dc)

Hope this helps.

BTW, I just imported the same DAT with clrmamepro and there were no such errors reported (but I really like RC much much more ....)

Cheers
--davy

Ok, this is a mame problem.
Same rom name, but different crc. This is not a problem in split mode, but a collision appears in merge mode.

The best solution, I think, will be to keep a clone file with duplicated roms.
For example, punchout in merge mode will be:
punchout.zip with rom chp1-c.8l (1d595ce2) and all other roms
punchita.zip with rom chp1-c.8l (a4003adc) and only other dup roms.

If you have another idea...

I suggest a possibility for this problem....even RC 3.0 final could include this option:

When we find merged romsets, allow romcenter to rename the file - Remember that emus read CRC and SHA before the filename!

For example a neogeo game:

271-m1decrypted.bin (original file)
271-m1decrypted.bin (the other one with different CRC and SHA)

It could help to keep both files if RC could do this:

217-m1decrypted.bin (Original File)
217--m1decrypted.bin (CRC & SHA different)

In this way we can keep both files WHITHOUT DELETING ONE OF THEM!

Eric: Could you do something to avoid deleting romfiles with same name with different crc and sha? That's my suggestion.

This case is handled in rc3 and different roms with same name should not be deleted. Tell me if they are.
Roms in this case are left in their clone file (in merge mode).