On 7/17/2014 1:49 PM, Jim Michaels wrote: > for the network stufff, I was thinking of opening a socket and just dumping > the printer data from stdin or from a file depnding on commandline options. > it' > s the easiest way to go. sockets is probably about 10-20 lines of code I > think. > google sockets example (or look in the source code of the telnet program in > wattcp). > then it's not > > > DHCP printers are another thing altogether. they do exist, they seem to be > the consumer printers like officejets and like printers that have wifi or > ethernet. they default to DHCP, but can be manually config'd for static > (works better I think with static, just make sure ip is outside of DHCP > range). > > not sure how to handle usb printers at this point. I know they are packet > driven. usb.org has the specs. usb 2.0 uses 8b/10b but usb 3.0 uses 128b/132b > encoding. >
You are aware that netcat already exists and has the capabilities that you wrote about - the ability to open a socket to the printer and send data from stdin or a file. (See my email to this list dated July 12th.) Mike ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
