🚀 go-pugleaf

Mike Richter (mrichter@mindspring.com) wrote:
: Not to belabor the point over so many ng's:
: 
: The problem is not in the TOC itself but in the way information is
: accessed. A CD-ROM is read through MS extensions as though it were a
: 650-MB HD in FAT16. I do not know whether the slack space is actually
: recorded as zeroes - but I suspect that it is from some very rough tests
: I ran.
: 
: Your assertions are logical, but I do not believe that MS employed such
: logic in designing MSCDEX.
MSCDEX has no relevance in this issue, although the recording software
does...  I refuse to believe that the ISO 9660 standard was designed to
allow for the limitations of one particular piece of software that would
be used to read it.

The issue is NOT how the data is accessed - it is entirely about how it
is stored on the CD.

I have a strong feeling that MSCDEX doesn't even try to emulate a HD with
a FAT.  There is really no need for it to do so, since it works on the
same level as networking software where it provides only file level
access.  Try to chkdsk a CD - if your theory was true it should run and
then show some statistics - instead it returns "Cannot CHKDSK a network
drive."

Regards,
Mark Griffiths.