Quote:
|
... It takes a very long time to read certain parts of the CD, and its scratchless
|
M$ Office CDs don't use bad sectors as a protection - nor any sort of protection as far as I know - so yes, U've surely encountered "real" read errors when making the dump, although there may not be serious scratches on the CD. Check its surface: is it perfectly smooth and CLEAN?
I strongly suggest U run Nero
CDspeed's scandisc test (tick the 'surface scan' box only): what R the results? I bet there will be a few yellow, or even red squares on the graph...
Quote:
...
I still don't understand how software can ehnance CD-RWs ability to READ the same thing. Same mods, same CD-RW - should be read the same way with any type of software...
|
They don't "enhance" reader's ability to read it (this would sound like sorcery more like
) : they just tell the reader how to handle what it is reading. For bad sectors for example, ordinary software corrects any read error when making the image, thus taking away eventual 'bad sector' protection. RAW-reading software performs extra operations to tell the difference between real errors and C2 read errors (provided the drive's chipset & firmware allows that!!! - which is the case for most modern readers/burners) and when it finds a C2 error it generates a fake read error in the image (discdump can even copy C2 error as is).
Quote:
...
I made many copies of music CDs (recent ones) - never takes a long time to read and write...
|
Big surprise
EFM encoding applies to
data CDs only, not analog audio ones. There is no error-correction (which obviously is crucial for a data CD) when it comes to an audio disk. Makes sense, too. Therefore, there is no such thing as "bad sectors" (or C2 read errors) protection for audio CDs. Which is why audio CDs - non-scratched ones at least
- take much less time to read, even protected ones that use illegal track lengths or invalid TOCs, which can somewhat slow down the dumping process, but never near to the extent that C2 errors can.
semper idem, sed aliter