Geri
Experienced Member
- Joined
- Apr 24, 2019
- Messages
- 147
after googling a bit, your problem has something to do with the error correction algorithm in windows 7
on the cd there is an error correction byte after every few bytes, and usually a large chunk of error correction after every 2048 bytes again.
maybe this will be wrong what i am writing here: the DOS cd rom drivers will not implement any error correction, they will rely on the cd/dvd drives firmware to do it for you, and the DOS drivers (and probably early windows drivers, and every naive implementation) will also rely on the firmware as the drivers will PROBABLY use the legacy commands to get the data.
newer windows and linux will probably read the raw data and do the error correction itself, which in your case, fails.
its hard to decide if your discs are damaged but your drives mistakenly think the data is correct, OR the error correction in the windows is buggy.. maybe windows does not really tries to restore the information based on the checksum information, just throws an error if there are too much errors.
on the cd there is an error correction byte after every few bytes, and usually a large chunk of error correction after every 2048 bytes again.
maybe this will be wrong what i am writing here: the DOS cd rom drivers will not implement any error correction, they will rely on the cd/dvd drives firmware to do it for you, and the DOS drivers (and probably early windows drivers, and every naive implementation) will also rely on the firmware as the drivers will PROBABLY use the legacy commands to get the data.
newer windows and linux will probably read the raw data and do the error correction itself, which in your case, fails.
its hard to decide if your discs are damaged but your drives mistakenly think the data is correct, OR the error correction in the windows is buggy.. maybe windows does not really tries to restore the information based on the checksum information, just throws an error if there are too much errors.