Hi Paul, Sorry, I don’t have any ideas on how to help improve your networking issues at this time.
But… Isn’t LOGGER neat? Here are a couple things you may find interesting… Most of the command line options (like Print & Information) can be abbreviated to a single character… For example, “logger p >my log.txt” It is amazing how much color logging can be squeezed into 256KB. It supports up to 63Mb, imagine how much it could record. Recording in MONO instead of COLOR will roughly double the capacity. But, it won’t look as pretty when simply viewing the log. Although not good for the mailing list, logger includes a LOG2HTML program. When recording in color, this looks really good for web pages and is very easy to edit the output. Generally, “logger message” is intended to write to the log from a batch without displaying anything on the screen. No problem using it as you have. Although simply using REM would work for the same purpose. :-) Speaking of writing to the log, included with logger are some simple demo programs (compiled+sources) for the various API functions. LOG-CLR - Turn off logging and clear the log. LOG-OFF - Simply turn off logging. LOG-ON - Simply turn on logging. LOG-STAT - Display the current status of logging (size/color/enabled). LOG-MSG - Send a message to the log. Using Red text if color is enabled. LOG-RIO - Redirect Standard I/O to the log. Using Purple text. LOG-SHOW - Display the Log text. Finally, if you do not have a Menu setup in the FDCONFIG.SYS file, then the screen won’t clear. Then like with the JEMM messages, LOGGER should be able to back-capture the Kernel messages as well. :-) Jerome _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
