> the area51 issue.
>
> in u8u9 we got a new area51.chd file. the old one became area51a.chd. That's
> ok....but:
> the clone a51r3k uses the name of the new file but the sha1/md5 values of the
> old one....great stuff....and you'll end up with a chd-clone-in-clone issue...
>
> Mamedevs know about that issue...and will probably fix it till next mame
> release.

I don't have area51a.chd...and CMP 3.31 says I'm not missing it. That's not right, is it? Or related to the above?