> > same files as the ones I already had, Mame32 now audits them without error.
>
> Most likely an internal datastructure error in the chds.
>
> Using clrmamepro's checksum->chd unpack and check sha1/md5 option should have
> listed the chd as bad too.
>
>
> Roman Scherzer
>
I'm doing this as I type this reply. Will let you know how I get on.