> > > Random crc32 errors are a sign for a hardware issue. Usually caused by bad
> > RAM,
> > > bad RAM timing (overclocked systems), bad IDE cables, buggy VIA chipsets,
> > > corrupt harddisk.
> >
> > I don't believe this qualifies as "random" crc32 errors. One program (yours)
> > reports no CRC32 errors, another (CRCheck32) reports errors in almost every
> > file.
> >
> > The files work fine in MAME with no problems.
>
>
> If ClrMamePro shows no errors as you now say, you're ok. I wouldn't trust any
> other progs.
>

Thanks for your help.

Yeah, I set CLRMamePro to unzip and CRC32 check each file. No errors reported. I have far more trust in your program.

I find it odd that CRCheck32 (http://www.breezin.net/sdetails.php?SID=2) finds problems with most, but not all of my files. Even if they are computing the CRC check incorrectly, wouldn't it be an all or nothing kind of thing? The CRC algorithm is pretty straightforward.

-------------------------------------------------
if you take cranberries and stew them like applesauce, they taste much more like prunes than rhubarb does