Hi Jim, > On Nov 29, 2024, at 7:24 PM, Jim Hall via Freedos-devel > <freedos-devel@lists.sourceforge.net> wrote: > > [..] > D:\SRC\MAKE-0.0>WCC -q getopt~1.c > > [no messages] > > D:\SRC\MAKE-0.0>WCC -q make.c > [.. couldn't copy/paste all of the output from QEMU..] > make.c(606): Error! E1063: Missing operand > make.c(606): Warning! W111: Meaningless use of an expression > [..]
Sometimes we forget we have solutions for such things already. The LOGGER device driver is installed with full. However, like many device drivers it is not loaded at startup with the default FDCONFIG.SYS or FDAUTO.BAT files. But, that is not a problem. It is fairly easy to load after boot. DEVLOAD /H C:\FREEDOS\BIN\LOGGER.COM 256 mono xms That will load the driver high (if possible) and allocate 256 kilobyte of XMS memory for simple text logging. It will also automatically start logging console text. The total number of pages will vary based on content. But, that amount of memory will provide at least 128 screens worth of mono text before older messages get discarded. You could then run your build batch file and not worry about pausing or trying to capture text. Afterwards, you can simply run: logger print >result.txt As a general rule, when the driver is loaded, using the command line interface program (logger.com) will turn off logging. This is usually because the user is likely done logging things. However, more importantly to prevent confusion or a possible infinite capture loop. To turn back on simply run: logger on Clear the current log contents: logger clear Personally, I just always boot with it loading. It has no noticeable affect on performance. However, I usually give it more memory and enable color logging. Then, I use the log2html tool to dump full color text to an easily edited awesome looking html file that is great for web pages and such things. It even supports various text modes like 40x25, 132x50 and VESA text modes. Logger also includes documentation and some examples for interacting with the driver’s API. Those get installed into the DEVEL\LOGGER subdirectory. All in assembly but could be easily converted to C, Pascal or language of choice. Some the examples even show how the log can be appended without displaying text. ;^) Jerome _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
