> > > > 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