I have a rather simple VB5 program to backup new/modified files to a CD. It
dawned on me the other day that I have no way of knowing if the CD is any
good. So I wrote some code to read every file from start to end and report
any errors. It almost works. When the CD driver gets a read error it tries
to read the record about 50 times or so. Finally it displays a window saying
it couldn't read and then goes on to the next record where it does its retry
trick again. During this time the program is not notified about the error
and the program can not be terminated due to an outstanding IO.
Is there any way of reading and error checking that bypasses the driver?
--
Rick Hughes Salem, SC
rbhughes @ Bellsouth.net
dawned on me the other day that I have no way of knowing if the CD is any
good. So I wrote some code to read every file from start to end and report
any errors. It almost works. When the CD driver gets a read error it tries
to read the record about 50 times or so. Finally it displays a window saying
it couldn't read and then goes on to the next record where it does its retry
trick again. During this time the program is not notified about the error
and the program can not be terminated due to an outstanding IO.
Is there any way of reading and error checking that bypasses the driver?
--
Rick Hughes Salem, SC
rbhughes @ Bellsouth.net