> For fun, I decided to implement a single binary compiler directive. > When enabled, it generates a single COM that acts as both the driver > and interface program. But, I am unsure if I will use that or the > dual (SYS+COM) build for the 1.0 release.
FWIW, in my TSRs I don't try to create a SYS program at all but just stick with COM. At least in later versions of DOS, you can install TSRs with the INSTALL= option in CONFIG.SYS. So, you don't actually need a SYS (or dual-mode) program to install something in CONFIG.SYS instead of AUTOEXEC.BAT. TSRs have so many advantages over device drivers (particularly in their ability to be uninstalled and reconfigured) that I don't see a real need for device drivers. Exceptions would be if you're using an older version of DOS (before the INSTALL= functionality was added to CONFIG.SYS which in MS-DOS was version 4.0) or you need the device driver to be installed really early in the boot process (which I think may be the case for your logger program). Unlike AUTOEXEC.BAT, CONFIG.SYS has a prioritization of which commands get processed first so the order of installation is not necessarily the same as the order things are listed in CONFIG.SYS. I'm not sure exactly where in the prioritization the INSTALL= lines are processed compared to the DEVICE= lines. _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
