This finishes off the back side of disk 1 except for the TOC which hasn't been
cleaned up yet in the least. The TOC itself is not useful to us as is because
we don't yet have any hyperlinks. That'll be the next step--but we'll clean it
up in preparation of that anyway.
Mostly just dot commands here as this entire chapter is a formatted reverse
engineering of the DOS 3.3 RWTS. Which is an amazingly useful resource, but not
one I'm doing anything with at this stage. :)
Chapter 8 is basically as big as the rest of the book combined. Before
searching for bitrot, let's make that a little easier on me in terms of typing
filenames.
Fixing the bitrot in chapter 4 after moving it meant looking at the OCR'd text
on archive.org, which is not good. Here's how not good it was:
> A tiL. (be it APPLESOFT, INTEGER, BINARY. or TEXT type) con,i a t a of one
> or more sectors containing data. Since the •• ctor i, the smallest unit of
> allocatable space on a di s kette, a file will use up at least one sector even
> if it i a Ie •• than 256 bytes long; the remainder of the sector is w • • ted.
> ThuB , a file containing 400 characters (or bytes) of data will occupy one
> entire sector and 144 bytes of another with 112 bytes wasted . Knowing these
> facts, one would expect to be able to use up to 16 times 35 times 256 or
> 143,360 bytes of space on a diskette for files. Actually, the largest file
> that can be stored is about 126,000 bytes long. The reason for this is that
> some of the sectors on the di a kette .uat be used for what is called
> ·ove[head- .
>
> <Figure 4.1>
>
> Overhead sectors contain the iMage of DOS which is 10ad •• 1 when booting the
> diskette, a list of the nallles and loes,lollll of the files on the diskette,
> and an accounting of the sectors which are free for use with new files or
> expon.lu". of existing files. An example of the way DOS uses lectDr. ,.
> given in Pigure 4 . 1 .
Yeah.... You see why I was so excited by the source text? :)
PIEWriter dot codes are case-insensitive, and I've deciphered that .pp is a
paragraph break. Replace those with blank lines. The NUL at EOF was escaped,
but it can be simply deleted. Did so.
