Xref: utzoo comp.sys.next:13061 comp.lang.postscript:7645
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!midway!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.sys.next,comp.lang.postscript
Subject: Re: HP LJ III dying under NeXTStep 2.0
Message-ID: <1991Feb19.162937.11725@chinet.chi.il.us>
Date: 19 Feb 91 16:29:37 GMT
References: <1991Feb15.031524.3210@wam.umd.edu> <1991Feb15.171041.3582@chinet.chi.il.us> <1363@ecicrl.ocunix.on.ca>
Distribution: na
Organization: Chinet - Chicago Public Access UNIX
Lines: 27

In article <1363@ecicrl.ocunix.on.ca> clewis@ferret.ocunix.on.ca (Chris Lewis) writes:
>>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
>			   ---------------
>(mine or Adobe's?  By default, psroff emits a fair bit of stuff back
>up the line unless you define NOCHATTER, and anything wrong with handshaking
>will show up quickly)

Yours (thanks - I finally have nice looking man page printouts for the
things I've picked up from the net).

>Many people using Postscript printers are unaware of the fact that Postscript
>prints error messages and so-on "back up the line".

I knew about it but it still took a bit of time to figure out what was
happening since the printer usually would print the first psroff job
with no problem, then hang up even if the same thing was sent again.
Our other postscript-generating programs didn't have the same problem,
and when I ran a daemon program to log the printer's output, the
problem wouldn't happen.

Les Mikesell
  les@chinet.chi.il.us