Home Page Forums MAME MAME Mess vs. ClrMame

I was always wondering why the ClrMame Output of Mess is going absolutely berzerk. You get lots of messages telling you that this set has no parent and other stuff. I was under the impression that mess uses the same system mame uses for system definitions.
So can someone shed some light on this ?
What is needed to fix this ? I'm willing to take a look at it, if you can give me some pointers. :shiver:
I also noticed that for some recently added msx2 and msx2p clones you have lots of differently named files with the same CRC.
Is this intentional and if so, what's the reason for it ?

Cheers

I would recommend using advancescan over clrmame.

ClrMamePro only moans about database issues. Like:

- when a set doesn't have roms at all (like a2600); clrmamepro will not import it then
- when a parent set is missing for a clone; clrmamepro will remove the parent/clone relationship then and keep the clone as a unique (parent) set
- countless other issues (bad hashvalues, incomplete database output, etc...)

MESS uses a lot of fake clones, too (100% identical sets within a parent/clone relationship). ClrMamePro is strict here...Since I don't like 0 byte sized sets and the number of sets should match the number mentioned in mess, you have to keep the sets doubled or simply use full merged sets.

All the prompts which appear while importing mess' database can of course be hidden. Use the appropiate option of Settings->Database errors.

Since I'm not a messdev, I can't tell you why there are sets listed as clones with non-existing parents...