Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[newuzer]

Hi Roman,

When loading the attached datfile in clrmamepro 4.050, it shows a datfile problem for all of the entries with "merge=" in them.
It appears to be (or looks like) the entry where the merge= is pointing at a "rom name" that is not in the datfile.
In this case:
<rom name="roland-r01891445-823.ic7" size="16777216" crc="2cfe5aa2" sha1="68655acdea37bfa73a30db64807902f525bf2215" merge="roland-r01891445-823.ic53" />
If you change it to "merge=roland-r01891445-823.ic7" the problem is gone, for all the entries with merge=.

Why is CMP having a datfile problem loading this datfile?
Why is it showing a datfile problem for all of the merge= entries in the datfile?
Why not just the problem entry?

What is tripping this datfile problem in CMP?
In other words, what are the rules regarding the "merge=" entries?

With kind regards,
NU.

[Roman]

Your datfile does not have any parent/clone relationships at all.
Merge attributes indicate which roms of a clone are shared with the parent.

No relationships -> no merge attributes

[newuzer]

Yeah, I know it has no parent-clone information.
It's an update ROMs datfile, a delta.
But why is it giving a datfile problem for -all- merge= entries, if just one can't be matched?

I can uncheck the "Parse ROM 'merge' Tags" in the options, but I have never ran into this and never needed to and do not know the consequences for the end result.
If it just a reference for MAME itself, I couldn't care less and uncheck it.
I just don't know the consequences when I use a full datfile in regard to naming of ROMs.

What does CMP do with the merge= information?

edit: after unchecking the "Parse ROM 'merge' Tags" in the options and doing a scan with the full MAME 0.289 ROMs (merged) datfile on the existing set, there are no changes.
My guess is that the merge= information is only used, when you use the raw -listxml with CMP to build a merged set?

Regards, NU.

[Roman]

well, clrmamepro only warns about "Wrong merge tag ' merge xyz...'" which is completely right since the merge attribute in your dat is simply wrong, obsolete (as mentioned, no parent/clone relationsships, no merge attributes) and so it gets removed. It detects all kind of syntactical wrong things in dats..that's one of them
If you don't want to see such warnings during dat parsing you can simply turn them off in Profiler->Options->DatFile Errors->Hide Common

..or you simply use clrmame.

[newuzer]

..or you simply use clrmame.

As soon as there is a Linux version available 

Thanks!
NU.

[Roman]

clrmame runs much better in a Linux wine environment than clrmamepro....