Print

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

[gh0stp1rate]

I have a complete 0.139u1 merged set with the only issue (or non-issue depending on the person) are 155+ version 4 CHD's which clrmamepro shows them mismatched which should be version 5. I used the mame64-0139u1.exe from which I downloaded from Arcade Database to merge and check a 0.139 set I downloaded from Internet Archive, which i had to find missing CHD's, ROM's and Samples to complete.

If I uncheck "List CHD version mismatches during scan" in Settings>Compressor>CHDMan the set is complete. But is there a way to update the CHD version with CHDMan? Because when I use pS CHDManFE to update them, clrmamepro will see them as unneeded and asks if I would like to remove them, but when I do, then they show up as missing in the scan results.

I also found a batch script over on Arcade Controls forums which is supposed to update the CHD, but after trying it out the version isn't changed at all and CHDMan basically just repacks it.

[Roman]

If I'm not mistaken a current MAME chdman has no update function anymore and I doubt that all old chdfiles can be simply updated.
Since all chds are 'available' for the current MAME version (which is .257) you shouldn't have a problem finding them.

[gh0stp1rate]

I also have a complete merged 0.257 set as well. But when I transferred the CHD's in question over to my 0.139u1 set, clrmamepro still sees them as mismatched versions. But no issues when I scan my current set, which I found weird, which is why I was asking if there was a way to update them.

[Roman]

I think there was a time where chds were simply redumped / reencoded with chdman instead of just being updated to a newer chdman version. For example to include some more metadata.....but hey...that was years ago...can't really remember.

[gh0stp1rate]

Would it be possible to get a version of clrmamepro that was around when 0.139 was released in August 2010? I would like to see if the mismatched version issue will come up with it.

EDIT: v3.135c?

[Roman]

Your problem is not related to cmpro. It's a question of old chds which can't be converted via chdman to match the current ones. You need to find the old chds or the new chds depending on which MAME version you want to check.