--- In os2user{at}yahoogroups.com, Phil Astley  wrote:
> ...
> So now now I can't print at all - which is a little inconvenient. I 
> understand the answer is probably to use TCP/IP printing with lpr or 
> lpd or some combination of these things.

FWIW, do a "tcphelp lrpmon" and get more hints.  

You need to read the individual printer docs to know what its internal
print queue name is,  Sometimes it might be called something simple
like "printer", or "printq", but it can vary
drastically.  You have to
read the individual printer docs to find out.  Or even you could set
it up to indirectly point to a Winders box that itself points to the
printer.  Enough flexibility to really confuse a person.

You could start off by issuing a simple command such as:
'start /C "Print Monitor for xxxx" /MIN lprmon -b -s 192.168.xxx.xxx
-p printq lpt3' and then when you don't need that monitor anymore,
just close it from the task list.  Naturally -s xxx can be the
hostname or the TCP/IP address.  -p yyyy where yyyy is the name you
found from the internal printer documents.  And lpt# is what ever free
port you like...lpt1, lpt2, lpt3, etc.  You aren't accessing a real
hardware printer port, just a logical one.  Then, assuming you have a
printer that understands straight text, then from older apps or
command lines, you just print to that port. i.e. 'type config.sys
>lpt3:' Many printers sense the data stream coming in and
automatically interpret it "correctly" for basic text.

Next, define a logical printer in your printers folder so you can tie
it to a print driver, such as postscript, for more features.  and set
that print object's output port to the lpt# that you have monitored. 
If you have more than one printer that takes a common print driver
(such as multiple postscript printers), you can create one printer
object in generic terms such as "Global Printer" always tied to
postscript and perhaps LPT3, then by just varying the lprmon options
monitoring LPT3, you can route the output to any postscript printer
via the -s and -p options on the appropriate lprmon task that you
start.  And if you need to reroute, just kill the task and start a new
lprmon as needed.

Need to find out what's queue'd up in the remote printer queue?  look
at the 'tcphelp lpq'.  For example, 'lpq -l -p pppppp -s aaaaaa'

And if you are still confused, ignore me.  It sounds complicated, but
really isn't once you understand the basics.

Al H





 
Yahoo! Groups Links

 To visit your group on the web, go to:
    http://groups.yahoo.com/group/os2user/

 To unsubscribe from this group, send an email to:
    os2user-unsubscribe{at}yahoogroups.com

 Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 




---