> Romname (Country) [folder: errorset - parent: parentset - size: xxmb]
> wrong merged ROM set: C:\Emulation\MAME\errorset (merge to: parentset)

well..it means exactly what it lists. You use full-merged sets and got a clone set 'errorset' (zip file or subfolder) which isn't merged correctly to its parent.

Usually turning on unneeded + fixuneeded will automatically move it to the belonging parent set. That's just one method to fix that. Merger, Rebuilder can fix that, too.



Roman Scherzer

> > > > Romname (Country) [folder: errorset - parent: parentset - size: xxmb]
> > > > wrong merged ROM set: C:\Emulation\MAME\errorset (merge to: parentset)
> > >
> > > well..it means exactly what it lists. You use full-merged sets and got a
> clone
> > > set 'errorset' (zip file or subfolder) which isn't merged correctly to its
> > > parent.
> > >
> > > Usually turning on unneeded + fixuneeded will automatically move it to the
> > > belonging parent set. That's just one method to fix that. Merger, Rebuilder
> > can
> > > fix that, too.
> > >
> > >
> > >
> > > Roman Scherzer
> > >
> >
> >
> > Hmmm... that's strange because I don't use fully merged sets I use the "Split
> > Sets" option. And the unneeded "fix" checkbox is definitely checked when I
> scan.
> >
> > Thanks for the help though. I will play around and see what I can figure out.
> >
>
> Ok, well I looked into this a bit further...
>
> Both the zipped up romsets and the extracted files are identical on CRC32, MD5
> and SHA1 hash values, so I would venture to guess that it is safe to say that
> the two romsets are infact identical.
>
> When I remove the "clone" romset from my rom dir and scan with clrmame there are
> no errors, and there are no romsets listed as missing either.
>
> So have I gotten a hold of a bad romset here? Because I was under the impression
> that clrmame would delete these files since they are unneeded. Any insight would
> be appreciated.
>



The "merge to parent set" should only appear if you're using full merged mode and got a cloneset/folder in your rompaths. On the other side "move to parent/clone" rommessage appear if sets are mixed up (cloneroms in parentset and viceversa). I will do some tests on your reported setup. If you can repeat it somehow, let me know the exact steps.



Roman Scherzer

> Ok, to make this simpler I created a new profile, put only the two roms in
> question into a folder, and unchecked the scan for missing files (so I wouldn't
> get all the messages about missing roms).
>
> I set up the profile using the EXE from MAME .104u8, and the problem also
> happened when I used .104u7. I am using clrmame 2.85c and my options are set up
> as follows:
>
> http://img.photobucket.com/albums/v21/dcm386/scan_set.gif
>
> All settings besides ROM path were not touched.
>
> running the scan gives these results:
> Cannon Dancer (Japan) [folder: candance - parent: osman - size: 13mb]
> wrong merged ROM set: C:\test\candance (merge to: osman)
> wrong placed file: C:\test\candance\mcf-00.9a (move to parent: osman)
> wrong placed file: C:\test\candance\mcf-01.13a (move to parent: osman)
> wrong placed file: C:\test\candance\mcf-02.14a (move to parent: osman)
> wrong placed file: C:\test\candance\mcf-03.14d (move to parent: osman)
> wrong placed file: C:\test\candance\mcf-04.14h (move to parent: osman)
> wrong placed file: C:\test\candance\mcf-05.12f (move to parent: osman)
> wrong placed file: C:\test\candance\sa00-0.1e (move to parent: osman)
> wrong placed file: C:\test\candance\sa01-0.13h (move to parent: osman)
>
> HTH
>



well...these 'wrong placed' messages are normal and are correct. "candance" is a 'fake clone' i.e. it's a 100% identical set to its parent. So in this case it doesn't play a role if you use full or splitmerged sets. In this case it
's because of the chosen 'fake-clone' behaviour.

There is a setting in the profiler options window how they should be handled ("don't create dummy clones"). The default behaviour is that you don't need them (so you only got the parent set, in this case "osman". The other behaviour is that you need them.

So I assume all your messages belong to such fake clones. There are a handful fake clonesets (natodef/natodefa, osman/candance, jdredd/jdreddb and some others).

Turning on fix-unneeded should remove them for you automatically.

Maybe I should replace "wrong merged set" to "unneeded fake clone" or something. Although it IS a wrong merged event....well..time will tell how I name it 8)


Roman Scherzer