wow, first I wanna thank you all for replying!
The text file, you mentioned, is great. Very useful info. Thank you for this!
Maybe you have to do "better things" than testing track modes.
Girl-friends can be a very time-intensive "hobby" .
You wrote, that reading the data disc as audio won't give better results or even exacter results.
But as I wrote before, I created a data-disc, which contained actually audio-data. Because the audio sector uses the full size of a raw main-channel (2352 bytes/sector), my created DATA MODE1/2352 Track containes ALL the audio data.
An if I read the CD as audio again (CDRWIN / sector reading), I get the TRUE audio data. NO interpolation errors occur, the resulting wave file is the SAME (except the introduced offset, of course)!!!
I tried reading the CD sectors as Mode1/2352 (as reported from the CD-TOC) with CDRWIN / sector reading. Then the whole CD is interpreted as Data, and of course, the audio doesn't give ANY sense as MODE1, because the EDC/ECC infos are completely wrong. So I end up with garbage data. Proof enough, that only AUDIO reading will give you the true bytes !?
I wanted to try out the alternate read method of BlindRead.
The problem is, that BlindRead doesn't have the option to read single sectors, only. It wants to read the TOC of the disc first, which is complete junk, of course. So you can't read the disc with BR, even if you own a UltraPlex :-[.
I had the idea to write a new CD, on which the first track is normal (any files on your hdd, etc.), and only the second track would be the strange audio/data track, so BlindRead could recognize the CD properly. Nice try !
The first track is read properly, of course, but as soon as BlindRead reaches the 2nd Track, it stops reading from the CD and filles up the whole track with garbage, even in the "nibble" reading mode :-[.
Again, I had no chance to test this reading method.
But one thing is certain:
If you read a SafeDisc protected CD with BlindRead / audio mode, you won't get the sectors filled up with 55 as explained in the text file. Instead maybe you will get the true bytes. I can't test this because the sectors are still "bad", otherwise the copy wouldn't run as the original game CD, obviously.
This brings us to the final topic:
I don't think, that Macrovision can "enhance" their SafeDisc sheme, to check if the "bad" sector is bad because only the checksum is wrong or if the sector is bad because Olli filled it up with 55 bytes.
The general problem is:
The original game should run in MOST drives, not only on high-end drives, like Plextor (just kidding!).
You can't expect from a CD-ROM drive that is discerns if a sector is generated or originally pressed.