Cyclic redundancy errors ~ recovery?

[JacobM5727]

win xp
any cd drive

i get cyclic redundancy errors trying to transfer from cd to hard drive, on anything ive burned at 52x

nero can make images of the "damaged" cds, but it takes hours, in some cases, many hours.. i have a ton of stuff i need to get back

is there any faster way? im trying iso buster now, but it seems to be having problems with making working files, trying to make an image now to see if that will work

or is there a way to disable that cyclic error check?

thanks for any tips

[poopeyhed2]

CRC errors usually occur from 2 things 1) usually a game that hasn't been copied correctly and that causes it or 2) which sounds like your case is when a CD becomes very scratched and problems arise like this.

But since you burned it at 52x it could be the problem because you burned it on cheap media. I suggest trying a different reader and hopefully you'll have better luck. Another feature is to use one of Nero's utilities to make the reader clock down to say 2x and see if you can recover the data. Otherwise, you could spend $50 and see if Arrowkey CD/DVD Diagnostic could help you, which Maximum PC reviewed in the March 2004 issue. Website to check out is www.arrowkey.com

[JacobM5727]

the cds arent scratched, and none of them are games, just data

the media was memorex, which ive had good experience with otherwise

i could try nero at 2x, but when it is making the image it gets down to like .8x, and stuff like that anyway

its not worth $50, since i have other people who could probably get the files for me, but its still a huge hassle

thanks for the advice

[Jack Hannibal]

Out of curiousity, can these CDs be copied on another system without getting the cyclic redundancy errors? You might be able to make a replacement copy that way.

[poopeyhed2]

Perhaps a different reader will read it better. I know Plextor, Asus, and Lite On optical drives are one of the better drives out.

[Peter M]

If the CDRW drive fscked it up while writing, your data is gone. Next time, use Verify After Write ...