home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!hellgate.utah.edu!cc.usu.edu!kaos.declab.usu.edu!hal
- Newsgroups: comp.unix.ultrix
- Subject: Re: Printcap entry for Serial Laserwriter needed.
- Message-ID: <1992Aug31.084821.58518@cc.usu.edu>
- From: hal@kaos.declab.usu.edu (000200 Lynch)
- Date: 31 Aug 92 08:48:20 MDT
- Reply-To: hal@kaos.declab.usu.edu (000200 Lynch)
- Sender: hal@kaos (000200 Lynch)
- References: <1992Aug29.000257.2853@uws.EDU.AU>
- Distribution: world
- Organization: Utah State University
- Keywords: printcap Laserwriter serial
- Nntp-Posting-Host: kaos.declab.usu.edu
- Lines: 24
-
- I suspect that your printcap entry is _not_ the problem. I am assuming
- a direct connection to the laserwriter and not through lat. We experienced
- lost jobs also. We put a data line monitor on the line and discovered
- that all jobs were being sent to the printer. The problem is this:
- The laserwriter was getting a buffer full and xoffing the decstation.
- The decstation didn't stop.
- The laserwriter xoffed again.
- The decstation still didn't stop.
- The laserwriter choked on the job, barfed it into the bit bucket then
- reset itself at the beginning of the next job.
- Small jobs may make it through but large ones probably won't.
- The decstation finally responded to xoff but many times it was too late.
- The data line monitor showed that the decstation would take anywhere from 2
- to over 100 hundred characters to respond to an xoff. The laserwrite and many
- other printer can't handle that. We solved the problem by putting the
- printer on a lat. That introduced a whole new set of problems but that is
- another story.
-
- BTW we are using a decstation 5000/200.
-
- --
- Hal Lynch
- Internet: Hal@cache.declab.usu.edu
- DECnet: USU::HAL
-