Hello, On 07/12/2014 06:33 PM, Tom Ehlert wrote: > it's not terribly difficult either. however nobody will program this > either :<
My understanding was that the OP was willing to do some work in this area :) > *every* sane program used BIOS interrupts to communicate to the > printer, which could be redirected by > > NET USE LPT2 \\server\printername > http://support.microsoft.com/kb/245017 I don't know about the "historic" aspect, but from my purely practical point of view, I did used a 'lpt2file' program a few years ago with some DOS word processors, spreadsheets, and graphic programs, and it worked every time - so I assume that indeed all these applications were behaving "nicely" (ie. use the BIOS to command the printer). > there's just a teeny weeny little problem remaining: DOS programs > don't understand the HP JetDirect printer language. > If you want more then plain ASCII (exciting stuff like bold, smaller font,...) > this is a problem. This surprises me a little bit. I know next to nothing about printer internals, but I always thought that JetDirect is just a smart name for "send raw printer commands over TCP". I used JetDirect along the past decade on many printers of different vendors, and always used the native printer's driver (PCL, PostScript, etc). At no point I ever noticed anything about a "JetDirect" protocol.. That's why I am almost sure that if one sends raw Postscript to a laser printer over port 9100, it will actually work. Mateusz ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
