EMULAB Forum

clrmamepro [English] => clrmame Discussion => Topic started by: yerduaz on 27 September 2014, 08:21

Title: Problem with parent - clone dat file
Post by: yerduaz on 27 September 2014, 08:21

Hi Roman,

It seems there is a problem with parent - clone relationship in this dat file:
rom Great Golf (Japan) is parent
rom Great Golf (Korea) is clone of Great Golf (Japan)
rom Great Golf (World) is parent
rom Great Golf (World) (Beta) is clone of Great Golf (World)

When scanning with clrmame (4.015), it creates a container "Great Golf" (without country) and adds then removes some roms from this container. This behaviour repeats by every scan.

Can you plesae take a look at this ?

Title: Re: Problem with parent - clone dat file
Post by: Roman on 27 September 2014, 18:46

Your datfile is special. It uses release/language settings and so it uses the release name in full merge mode (and you can select prefered languages etc...). So this is a wanted behaviour.

Title: Re: Problem with parent - clone dat file
Post by: yerduaz on 29 September 2014, 16:45

Thanks for your answer.

For info, this dat file is coming directly from the DoM of No-Intro (as P/Clone XML with "Default parent if there is no p/c info").

I agree with you that this dat file is "special" but it is not wrong either as it respects the xml/dat file format and keywords.
What I don't understand is why clrmame can't scan properly these roms with such dat file: either the release/region is disregarded (in this case, 2 sets containing 2 roms should be created) or the release/region is considered and one only set containing the 4 roms is created. Instead of this, every scan leads to unsuccessful results with wrong placed roms and "Great Golf (World) (Beta)" removed. It seems that the code is struggling with contradictoy instructions on how to handle this special case...

Title: Re: Problem with parent - clone dat file
Post by: Roman on 29 September 2014, 18:18

The problem is because you end up with 2 identically named parent sets which is a not allowed state.....based on the fact that the sets share the same release name ("Great Golf") over different parent/clone relations.

If they all (would be a  cloneof="Great Golf (Japan)" you won't run into issues.

So...a datfile issue...
however I should think about a check which warns you if you end up with double set names if you're using "release/language" dats

Title: Re: Problem with parent - clone dat file
Post by: yerduaz on 29 September 2014, 19:32

Thanks for the explaination.

Such a warning would be nice indeed.