The biggest problem that I see here is that Bob
wants to be able to use
this OS on systems that have as little as 16k words but still use LARGE
modern drives. I'm not sure that's practicle without a lot of wasting a lot
of drive space. But I frankly don't think wastage is a problem. There's
simply not a lot of software for this OS and I don't think we'd ever use
more than a tiny fraction of the drive. Therefore my vote ould be for
program size, speed and drive space effientcy in that order.
So what about the archiving file system I outlined? Files are stored
contiguously, and if you want to append to a file, it's copied to the end of
the used space, given a new time stamp, and it goes from there?
-spc (And if you don't want to set aside a fix amount for the master
directory, have the directory at one end of the drive, and pull
the free space from the other end, where they would meet in
the middle ... )