That's what I was thinking. Thanks Roman!


> > Are you sure that sfrushrk is a clone of sfrush? Emuloader doesn't report it
> as
> > a clone (of course there could be an error in mame or emuloader).
>
> OOps...looked at it again...it's not a clone...and ClrMamePro imports it
> correctly...as a single set and not as a clone
>
> > I am using merged sets. If I copy the contents of sfrushrk.zip into
> sfrush.zip
> > and run the scanner I get no errors (including no error about the lack of the
> > sfrushrk.chd file).
>
> There is no sfrushrk.chd file currently. ClrMamePro won't include it from mame's
> -listinfo since it doesn't have a sha1/md5 yet.
>
> > When I go to the command line and run "mame sfrushrk" I get an error that it
> > cannot find the roms that were in sfrushrk.zip and the sfrushrk.chd.
>
> well..because it's not a clone...
>
> > is not reporting the lack of the sfrushrk.chd file in either case.
>
> because it didn't include it since it's not valid
>
>
> Now to your original problem: Since sfrushrk doesn't include a chd (in the
> database), creating a folder for the future chd will cause the message you've
> seen. You have a zip and a folder for a set..which is normally wrong....only
> exception are sets with chdfiles...but since sfrushrk isn't one currently, the
> message is correct.
>
> Roman Scherzer
> ClrMamePro
>