dodecahedron wrote:you also said you had problems with CDCheck.
can you elaborate?
CDCheck has worked very well for me.
I used cdcheck many times and was fairly pleased but then I started having nothing but failures.
Finally I tried the fc and it failed too and finally I found out about the binary switch for fc and then at that time (like 6 months ago) found out about comp.exe.
I had burns where cdcheck failed and when I ran comp.exe on the files they passed.
I then encountered a message thread or a web page (I forget) that described the problem with padding being added during a burn; I assume for the purpose of filling out a block. This padding would actually have no affect when using the copied (burned) file, but when checking it there would be an error.
I guess using the binary switch '/b' with fc, or just using comp.exe remedies this situation and only the file is checked; with padding or without.
I've even used comp.exe with .iso's and .nrg's (nero) by using nero's drive image to mount an image. I then used comp.exe and sometimes 'fc /b' to compare the files in the image drive with those on a burned disk and had success.
As I told a friend locally; I can see the data on a burned disk actually matching the source data on a hard disk and yet wrongly failing the test, but, if two such data sets pass a compare I believe it would be astronomical difficult for them to actually be different. It would be so incredibly difficult to pass the test and be different.
Your 13 hours ahead of me. That should be about 10 til 2pm now.