Roman,

First of all, thank you again for a program that is an absolute necessity for a MAME fan like myself. I only started using it about a year ago, and WOW was I foolish for not starting sooner.

I have an easy question regarding CHDs. If ClrMame reports that a CHD is OK, is there a reason for me to run a program like 'Quick Par' to re-verify ? I am sure that it is not necessary, but would like to hear it from you.

Thanks again for such a great program.

Old Wolf
Austin, Texas

> I have an easy question regarding CHDs. If ClrMame reports that a CHD is OK, is
> there a reason for me to run a program like 'Quick Par' to re-verify ? I am
> sure that it is not necessary, but would like to hear it from you.


Well...depends. Scanner->Checksums got 2 settings for chdfiles. One is the simple sha1/md5 check in the header, the other one is the full integrity check. As long as you only enable the header check, you can't be sure that the image is 100% ok, since this check ony looks if the diskimage is available, correctly named and got the correct md5/sha1 stored in its header.

If you enable the full integrity check (which takes a while...) ClrMamePro will check each block of the chd (mainly the same as a hdcomp/chdman -verify). If that tests succeeds, the chd is ok and doesn't need any other tests.

Roman Scherzer
ClrMamePro

> > I have an easy question regarding CHDs. If ClrMame reports that a CHD is OK,
> is
> > there a reason for me to run a program like 'Quick Par' to re-verify ? I am
> > sure that it is not necessary, but would like to hear it from you.
>
>
> Well...depends. Scanner->Checksums got 2 settings for chdfiles. One is the
> simple sha1/md5 check in the header, the other one is the full integrity check.
> As long as you only enable the header check, you can't be sure that the image is
> 100% ok, since this check ony looks if the diskimage is available, correctly
> named and got the correct md5/sha1 stored in its header.
>
> If you enable the full integrity check (which takes a while...) ClrMamePro will
> check each block of the chd (mainly the same as a hdcomp/chdman -verify). If
> that tests succeeds, the chd is ok and doesn't need any other tests.
>
> Roman Scherzer
> ClrMamePro
>