: We have a HP9000 at work and users are connecting to HP
: from local PCs. We have some printer connected to HP but
: i am having problem to print from HP to local (Directly
: connected to PCs).
: Note: We are using PROCOMM PLUS 2.0 and 3.0 to connect
: to HP9000. i'll appreciate you advise.
I used to do local (PC) print with Procomm 2.4.2, Procomm Plus 1.x, and
PC-Kermit by using vt100 (actually vt102) terminal emulation to connect
the PC to the Unix system, and using vt102's local-print commands.
I don't know if this will work with newer versions of Procomm.
Also the network I used was a switched-RS 232 network,
and I don't whether more modern LANs would introduce additional problems.
Now that I've given my disclaimers, let me describe what I used to do:
The vt102 had a serial printer port. The command
ESC [ ? 5 i printed incoming data and echoed it on the screen
ESC [ 5 i printed incoming data without screen echo
ESC [ 4 i turned off the vt102 printer port.
Either of the first two commands turned on the printer, which would print
all data received by the terminal until the third command was received.
On the Unix end, I had a shell script called wpr (workstation print)
whose usage was: wpr file-name.
After checking to see if $1 was a valid file, wpr did the following:
echo \033\133\065\151 # Octal for ESC [ 5 i (vt102 print on)
echo \014 # Form feed
echo \033\133\064\151 # Octal for ESC [ 4 i (vt102 print off)
That's all there was to it. The script could easily be enhanced to reveive
redirected or piped input, or to handle more than one file at a time.
You may also need to fiddle with enclosing the backslash-octal strings in
quote marks on some versions of sh or ksh.
I hope this is of help.