> I suggested the shelling technique for somebody who wants to experiment > with hooking the BIOS interrupts but is not ready to tackle the TSR > portion. right; also much easier to debug (as you already pointed out)
> "Too big" depends on the program being used; there are many > programs that will still load and run even with another 64K missing from > RAM. Let's leave that question to the person who decides to tackle the > project, eh? right. if this program ever materializes, and is written in C, I offer my help to make it a TSR with the least possible footprint. > My Brother laser printer (HL 5370DW) which emulates Epson FX codes, PCL > and PostScript just printed a PostScript copy of my 2002 family > christmas letter from DOSBox using the following command: > nc -target 192.168.2.20 9100 -bin < \xmas.ps > Lots of fonts and formatting, an embedded image or two, etc. in a 3MB > file. You are limited to what the printer understands, but I think I've > demonstrated that you can safely send ASCII, PCL, PostScript, or > whatever your printer supports. you are probably right. even in the dark ages before Windows 1995, many (at least some) programs existed that could talk PostScript and PCL. Tom ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
