said:
>but repeating
>say stream('\pipe\lpd1','c','open ready') returns NOTREADY:231
I assume the above is a typo, but I can duplicate your results here. Now
that you made me think about it, it's obvious why it should fail. You
don't know how to talk to lprportd. There must be a defined interface
between the printer object LPD port driver and lprportd. Otherwise, how
would the paramters be passed? Since I'm pretty sure you don't know this
interface, you are not going to be able to use it.
Use lprmon to connect to the print server and write the the redirected lpt
port. Something like:
lprmon -b -p lp0 -s 192.168.0.x lpt2
should get you connected. Then just write to lpt2 from REXX. I recall
mumbling something about doing it this way at the meeting.
FWIW, the error messages say nothing about printer errors. They
reflecting your script's inability to talk correctly to the pipe.
Steven
--
---------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.31a #10183 Warp4/FP15/14.085_W4
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
---------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".
For problems, contact the list owner at
"rollin@scoug.com".
=====================================================
>> Next Message >>
Return to [ 26 |
July |
2002 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
