Xref: utzoo comp.sys.next:12854 comp.sys.hp:7708 comp.lang.postscript:7595
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!linac!midway!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.sys.next,comp.sys.hp,comp.lang.postscript
Subject: Re: HP LJ III dying under NeXTStep 2.0
Message-ID: <1991Feb15.171041.3582@chinet.chi.il.us>
Date: 15 Feb 91 17:10:41 GMT
References: <1991Feb15.031524.3210@wam.umd.edu>
Distribution: usa
Organization: Chinet - Chicago Public Access UNIX
Lines: 27

In article <1991Feb15.031524.3210@wam.umd.edu> mikec@wam.umd.edu (Michael D. Callaghan) writes:

>Ever since I upgraded my NeXTCube 030 to NeXTStep 2.0, my HP
>Laserjet III PostScript doesn't work right.

>I am constantly getting I/O Config errors when printing Complex PostScript
>files. If I try to reset the printer, I proceed to get PS Error 18, which
>says a non-postscript operator has been used. 

If the postscript generates any output back to the sending tty, it is
important to have the spooler port configured properly to handle it.

I had a problem with more or less random timeouts and hangups which
turned out to be caused by the print spooler enabling reverse xon/xoff
flow control on the line (i.e the computer could send the printer an
xoff for flow control on messages coming back).  Nothing on the
computer was ever reading from the printer, so after a printout or
two that generated output (usually psroff), the computer would send
an xoff and the printer would sit waiting to be able to finish sending
back its message.

Another posting recently pointed out a similar but more drastic problem
when character echoing is enabled on the line.  That could be your
trouble as well.

Les Mikesell
  les@chinet.chi.il.us