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.