Redownloaded some sets over and over wondering what the heck was wrong with all my crc32/size mismatches, then checked out the sources and noted that MAME is now putting in identically named but different crc32 roms in parent/clone sets. In other words, rendering merged sets completely obsolete and unusable. No warning for ClrMame or that I can find.

When on earth did this happen and WHY wreak something that has worked for YEARS?

Edit: See that many people having this problem, also that ClrMAME is supposed to remove the parent/clone relationship for these but doesn't do so for me (and I looked in Options...).

Anyway, I suppose it's time to go to split merged... I sure hope it works, and I don't have to go to full merged which would be a goddamn disaster.

Identical named but different hash-valued roms are in MAME since its beginning.
If such a thing occurs within a parent/clone relationship, clrmamepro tells you while parsing the datfile/mame.exe.

You go the option to either: split up parent/clone relationship for the sets in question, or force clrmamepro to work in split mode.

Again..this is nothing new...it's a common MAME behaviour.


Roman Scherzer

http://mametesters.org/mantis/view.php?id=2165

Go w/ split merge, I gave in after years too.

> Redownloaded some sets over and over wondering what the heck was wrong with all
> my crc32/size mismatches, then checked out the sources and noted that MAME is

--
john iv
http://mame32qa.classicgaming.gamespy.com/

unfortunately the mantis thread is closed...otherwise I could tell Robbert that he's wrong. It's not a cmpro behaviour since cmpro handles it correct.


Roman Scherzer

> Identical named but different hash-valued roms are in MAME since its beginning.
> If such a thing occurs within a parent/clone relationship, clrmamepro tells you
> while parsing the datfile/mame.exe.
>
> You go the option to either: split up parent/clone relationship for the sets in
> question, or force clrmamepro to work in split mode.

Hrm, I think for some reason ClrMame stopped doing this, as I had "Hide All" on - when you put on "Show Common" and select "Yes to All" for this does it remember you wanted to do that if you set it back to "Hide All"?

Why it broke so many of my sets is that it probably tried to merge them back into the same file, and didn't backup the file it replaced (or did so once, and then overwrote it on the next backup for identically named file).

> Hrm, I think for some reason ClrMame stopped doing this, as I had "Hide All" on

If Hide all is on, it automatically splits up the parent/clone relationship.


> Why it broke so many of my sets is that it probably tried to merge them back
> into the same file, and didn't backup the file it

Nope. All files are backuped before they get replaced. So most likely you only have to run a rebuild on the backup folder to readd them.


Roman Scherzer

> > Hrm, I think for some reason ClrMame stopped doing this, as I had "Hide All"
> on
>
> If Hide all is on, it automatically splits up the parent/clone relationship.

I assure you it wasn't doing this for some reason. I had to put it back on Hide Common. I've been using it for lots and lots of versions and never had this problem before, hence my stupid thread. It just kept rebuilding those Freeze sets to the parent.

>
> > Why it broke so many of my sets is that it probably tried to merge them back
> > into the same file, and didn't backup the file it
>
> Nope. All files are backuped before they get replaced. So most likely you only
> have to run a rebuild on the backup folder to readd them.

I had to download a bunch. If a destination file/zip exists in the backup folder already, what does ClrMame do?

> If Hide all is on, it automatically splits up the parent/clone relationship.

Just changed to Hide All and ran a scan, and it's bitching and dozens of wrongly merged sets... maybe something broken in last version?

> Just changed to Hide All and ran a scan, and it's bitching and dozens of wrongly
> merged sets... maybe something broken in last version?


right....hide common doesn't set the option correctly in all cases. Will be fixed in next version.


Roman Scherzer

> I had to download a bunch. If a destination file/zip exists in the backup folder
> already, what does ClrMame do?

It adds a _1, _2 etc...nothing gets overwritten. You should add them back with the rebuilder, not fix-missing


Roman Scherzer