Hi everybody, as mentioned, I plan to get rid of the old MS DOS 4.01 handbooks, but before, I have copied the pages about drivparm and driver sys. Apparently, the config sys command and device driver simply serve to override (or provide) the drive type and geometry data which you would normally get from the BIOS, unless it is 100 years old. The difference between command and driver is that the latter can handle parameters for drives which would not exist at all according to the BIOS while the former just changes parameters of already existing BIOS diskette (or tape, in theory) drives. I think we could add some extra power to our config sys processing to turn BOTH into built-in config sys commands and become a little bit more complete as MS DOS replacement. However, has ANYBODY ever felt the need for either of the two?? My guess is that you would need a very old or very broken BIOS or very non-standard hardware to have any advantages from the feature. Given that 22DISK proudly lists 100 (in registered version > 400) CP/M formats it can read, I can imagine that DRIVPARM and DRIVER actually were useful in the 1980s, but would anybody like something like that today for their hobby or museum hardware? Thoughts please :-) Regards, Eric PS: I also looked at the manual item about FASTOPEN - it works only for harddisks and caches directory entries in one or optionally two ways, but I fail to understand the optional one. The idea seems to be that opening x:\a\b\c\d\e\f\g.txt needs many harddisk seeks for finding all the directories in the chain, so FASTOPEN caches them. _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
