richmilne
5th December 2002, 04:05 PM
Dear Mickael,
Maybe it is just my setup, Windows XP and a 16x Burn-proof burner, but on several CDs it will thrash for 2-3 minutes, and in the worst case, more than 5 minutes, verifying one file before it produces an error message "A Verification Error was detected in File:" Couldn't this be done a little more quickly? And then I sometimes get an "Error 52 Bad filenamenumber, Location:ArchiveCreator.clsFileVerifier.Verifyfile , Line 72" and the only useful option is to abort. At which point the program bales out. and I need to follow your advice and restart and go directly to Burn again, removing the disks that have already been created. But this means I don't know what other errors there might have been on the disk that caused the error message.
Is anyone else having problems in the verify cycle?
Sincerely,
Rich Milne
Maybe it is just my setup, Windows XP and a 16x Burn-proof burner, but on several CDs it will thrash for 2-3 minutes, and in the worst case, more than 5 minutes, verifying one file before it produces an error message "A Verification Error was detected in File:" Couldn't this be done a little more quickly? And then I sometimes get an "Error 52 Bad filenamenumber, Location:ArchiveCreator.clsFileVerifier.Verifyfile , Line 72" and the only useful option is to abort. At which point the program bales out. and I need to follow your advice and restart and go directly to Burn again, removing the disks that have already been created. But this means I don't know what other errors there might have been on the disk that caused the error message.
Is anyone else having problems in the verify cycle?
Sincerely,
Rich Milne