|
> > > Does anyone know how to fix this: > > > > > > [img]http://www.mightymo.net/Misc/gauntd24.png[/img] > > > > > > > > > Yes. Move the file to the parent set and remove the subfolder. Rom-wise, > gaunt24 > > is 100% identical ('fake clone') to its parent gauntdl, so a set split-merge > > isn't needed. You can change the fake-clone behaviour in profiler->options. > Same > > for chdfiles. No real clone, no real chdsubfolder.... > > > > Although I thought I changed that behaviour in one of the last releases, so > that > > -even in split-merged mode- you can store chds of fake-clones in a subfolder. > I > > will recheck that later at home. > > > > > > Roman Scherzer > > > > > OK I'm a little confused. Basically what you're saying is to make a copy of > gauntdl.chd in the \gauntdl directory and name it gauntd24.chd? And which option > in the profiler are you referring to? >
Nope. First of all....there are several 'fake clones' in MAME. A 'fake clone' is a clone set which is 100% identical to its parent. natodefa/natodef for example. You can chose how such sets should be treated in cmpro. For this there's an option in profiler->options->don't create dummy clones. If this option is enabled (which is the default state), you don't need the fake clone sets, otherwise you do need them.
Some fake clone sets do differ in the used chd file. gauntd24 is one of them. The romset is 100% identical to its parent, the chd isn't. The used mergemode you selected in cmpro's scanner is also used for chds, so if you e.g. use fullmerged sets, you need to put the chds together in the parentset.
Now the interesting part is coming: For the fake clone, you don't need a cloneset, and so you don't need a subfolder for the chd. You should put the gauntd24.chd in the folder where the parent chd is stored. You don't have to double anything. Move the chd and remove the clone-chd subfolder.
Now the more interesting part comes: Well...as far as I remember, I changed that behaviour for fake clones, meaning that you can keep a clone chd of a fake clone in a setsubfolder named after the clone. So, if you got the latest cmpro version (3.87a) you shouldn't even see that message. I will recheck that at home.
So for now: Move the gauntd24.chd to the rompath subfolder gauntdl where the gauntdl.chd is and remove any empty rompath subfolder called gauntd24.chd. For the romset, you can remove the romset gauntd24 since it's 100% identical to its clone gauntdl.
 Roman Scherzer
|