> If your network attached printer is listening on TCP/IP port 9100 ("HP
> JetDirect" protocol) and your DOS program can generate something the
> printer can understand, then do the following:
>
> - Print your printer output to a file
> - Send the file to the printer using this command:
>
> nc -target <printer address> 9100 -bin < <filename>
>
> Substitute <printer address> with the IP address of your printer and
> <filename> with the filename your program generated when you said "print
> to file". For example, on my printer:
>
> nc -target 192.168.2.20 9100 -bin < testfile.txt
>
> Will print testfile.txt over the network to the printer. (testfile.txt
> gets redirected on stdin to netcat.)
>
>
> Here is the fine print:
>
> Most new network attached printers will listen on port 9100. Yours
> might not. If it does nothing then it might be listening on the Unix
> LPD port (515) or the IPP port (631). Just try it, nothing bad will
> happen.
>
> Your DOS program has to generate output that your printer understands.
> That is usually some form of PCL output. Some printers can take raw
> ASCII text, some more expensive printers can do PostScript, and some
> cheap and nasty printers require Windows and can't do anything by
> themselves. If you have a printer that does not do ASCII, PostScript,
> or PCL and requires a Windows machine to do anything, it won't work for
> you.
>
>
>
> Mike
Very interesting. I suggest you make a FreeDOS Wiki page from this
information.
Georg
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
