dodecahedron wrote:obviously, but what i had meant was - any more detail?
how many files mismatched etc?
it's a data CD, yes?
how many and what kind of files?
It (they; I tried several) was a Data CD with 1 file made by Acronis True Image.
Such as: Interum 9-1.tib = a 645 meg backup segment.
Acronis will make it in one file like on a Hard disk or it will make pieces any size you specify.
Or, it will burn them right onto the CD.
I was makeing segments on the Hard drive so I could restore from there and also burn them to CDs.
So, when burning one of these puppies it would go to the very end and then give an error. I used list.exe (old dos prg) and looked at the end of the file and saw the output from fc.exe which shows the bytes. They were the same but the file copied back off of the CD-rom had 9 extra bytes on the end, which I believe is padding and the problem.
roxio's verify, and cdcheck would just error. All cdcheck would say was compare mismatch and only by being in dos with fc.exe could I see the error. That Beyond Compare I think showed it too.
By turning on fc.exe's binary switch '/b' it said the files were the same.
Also comp.exe would say they were ok too. I figure those likely read up to the end of file marker and stopped there instead of reading to the end of the file on disk.
Just guessing there.
But anyway it was just one big file that I was burning and testing.
Both comp.exe and fc.exe /b work.
If I can get a success message I feel very comfortable.
I see it as easily possible to have a file checker error saying files don't match when they actally do.
However, I find it practically impossible to believe that pair of unmatching files could be shown as matching.