radardoug Posted June 9, 2010 Posted June 9, 2010 Hi, I was trying to write a disc image file to a USB drive. I selected what I wanted to write and all was going fine, until the program encountered a CRC error when trying to read a file. At this point it aborted. The program is smart enough to go past system files that are being used, prompting the user. Why does it not treat any damaged files it finds the same? After all, one file with a CRC problem is no biggie, and as long as it is mentioned in the log, the user can repair/copy it later, rather than stopping the whole file write. Otherwise the user would need to be able to guarantee no errors on the drive, and after all that is why we are trying to burn backups! And with Windows producing surplus files faster than rats have babies, it makes life too difficult.
mmalves Posted June 9, 2010 Posted June 9, 2010 ImgBurn isn't a full fledged backup tool and, as such, it doesn't try to overcome file read errors. And why is this posted in the Bugs section if it's more of a suggestion than anything else?
LIGHTNING UK! Posted June 9, 2010 Posted June 9, 2010 Indeed, invest in something like r-studio if you're trying to recover files/as much as you can from dead hdds, they're not my problem. Hell, you could even run chkdsk with the /f and /r switches.
Recommended Posts