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

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

..or you simply use clrmame.

As soon as there is a Linux version available 

Thanks!
NU.

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.

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.

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

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.

Ah you mean the www profiler and its required xml file on the server....

clrmame doesn't even have a profiler (yet), not to mention a www profiler. While I really work hard (*cough*, *cough*, *cough*) on the profiler part, there are no plans yet for www profiler things...but time will tell. For now, you don't have to care about any

Thank you...
On the XML file, though... I'm talking about the one I keep on my website, so that if clrmame has the option turned on to ping this XML and see if a DAT file has been updated, it gets a notification.
See attached pic for my most recent version.

(Also... I remember having a conversation with you, about how I had this setup wrong at one point... I don't remember if I fixed it... please let me know that part also).

Regarding the screensize, you're right Header part in dir2dat is not fully visible unless you resizing the window.
You can resize the window at each border and there are draggeable parts above the log part and left of the tree output and yeah, you're right, I should make them a bit more visible for the user.

"Allowed" XML formats are mainly what MAME offers
- standard format as used by MAME's -listxml
- software list hash files as in MAME's hash folder
- software list collection output as used by MAME's -listsoftware

additionally, it also allows XML files using "game" instead of "machine" elements. So e.g. all the progetto snap dats work....

Hi, Roman... been a while... looks like if I have questions, I'll have to ask them here now...

I just downloaded the current version of clrmame, as I'm about to get things up and running again... I have a note and a question:

- In the UI, on the Dir2Dat tab, in the Header section... that section is not expanded 100% when you first run the software... Homepage, URL, and Comment are hidden on first run, and there is no scrollbar to move the list down...
- I played with the window a bit, and found a spot where I could drag that section bigger, but then, I still can't expand all three options, until I actually make the full window itself bigger... then I can go back and see the whole section...

Is that by design (e.g. to keep the UI small at first launch)?
Window size is saved after first run, so no issues after that... just wasn't sure if you were aware of that or not.

XML Question:

- I didn't notice any notes in the online readme file (tbh... I didn't read the "whole" thing)... is the XML file I keep on my site still the same format as before?
  - Since this is now just "clrmame", the first level tag would now be that, instead of "clrmamepro"?  Then second level is "datfile", and third level are the options shown in the Header section of Dir2Dat?