Right... I'm sitting down and designing the BDOS for all of my future projects... it'll be PD too, so it should provide a nice little core for people to use (though I won't be releasing the source -- so that if updates need to happen, people won't have splattered their code with undocumented routines).
Basically, what kind of hooks do you want in the system? I'd be interesting to hear what kind of stuff, say, Linux has wrt disk access, etc etc... On another note, I talked to Nev Young at the show on Sunday... unfortunately, while it seems that his DOS is coming along nicely, he's done something rather silly with regards to the directory structure... It's all one block. Each file has a 2-byte directory-tag associated with it, set to -1 for an erased file... It's rather like MasterDOS... Unfortunately, if you have, say, 64k files on a disk, and you want to read the one at the end of the directory, it'll have to go through 65534 other files before it finds yours -- even if you use subdirectories. :( I think I've found a better way... I may limit filenames to 64 characters though :) (at the start of any directory branch on my DOS, you'll have a "." file... in this file, the current path, and linking information is stored... not sure about space allocation yet -- anybody got any ideas?) Anyway... back to the plot, Si Cooke
