|
> 3.31a (05-05-2004)
>
> removed: chdfile clone-of-clone support. since mame doesn't support it, cmpro
> doesn't support it. Live with it. double area51 for 82 or keep it in a pure
> rompath, or put it in the parentset...mame supports all of that
> fixed: fastscan tempfile creation fails when datfileheader description/name
> tags contains |/\, etc....illegal filename-characters
> misc: fixdatfiles don't include chds anymore
> misc: changed profiler's datfile listing/parsing order... maybe a
> small speed increase if you're using a lot dats
>
>
> Roman Scherzer
> ClrMamePro
Ok, I admit it, I don't understand all of the options for the new area51 sets.
area51 = parent set
area51a = cloneset of area51
a51r3k = cloneset of area51 that uses area51a.chd of area51a.
clone-of-clone is not supported therefore to make the above work in MAME/ClrMamePro we have the following options:
1. Place a copy of area51a.chd in the a51r3k folder - only downside is the extra 530MB of space used.
2. Place area51a.chd in the parent set area51 folder alongside area51.chd. Then both area51a and a51r3k will pick up area51a.chd out of the parent folder. This sound like a sensible compromise.
3. Keep area51a.chd in a pure rompath - is this like placing area51a.chd in the roms directory? The only downside here is that it becomes unclear which romset(s) that file belongs to.
I'm hoping someone can confirm the above points or clarify my misunderstanding.
|
