So what does clrmame do during a rebuild if you are missing the chd in your rompath but it's in one of your rebuild path. Where does clrmame put it on rebuild?

> > Yeah, see the mametesters board Aaron never knew why it worked w/ them
> > freestanding and just plugged another hole so we're back to having them in
> > \setname\*.chd. I manually did it anyhow although you may want to consider it
> > an option going forward as people might want to rebuild that way. :) *shrug*.
> >
> > > > With 105u1 Aaron is going to be enforcing a certain CHD hierarchy, that of
> > > > putting the CHDs in subdirectories named for the gamename.
> > > >
> > > > Is there a way for clrmame to automatically rebuild to this structure
> style
> > > from
> > > > a single directory currently containing all the CHDs freestanding?
> > >
> > >
> > > Hmm...that's new to me. The main storing method: rompath\setname\file
> 1...file
> > n
> > > (no matter if it's for roms or chds) is in MAME since its beginning. CHDs
> were
> > > stored always that way...so nothing really has changed. Some other guy added
> > > support for keeping them in pure romfolders later on...never liked it but I
> > > added support for this, too.
> > >
> > > Since I am on holiday currently I can check that first when I'm back next
> > week.
> > > Currently there's no automatic move-to-subfolder procedure in cmpro for
> > > chds....maybe because I always stored them the correct way 8)
> > >
> >
> >
> > --
> > john iv
> > http://www.classicgaming.com/mame32qa
> >
>
>
>
> never liked the unofficial way either.....I guess I add a switch for allowing it
> or not.....it slows down the scanner anyway 8)
>
>
> Roman Scherzer
>


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