Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!ukma!nrl-cmf!ames!ucbcad!zen!ucbvax!NASAGISS.BITNET!CLDLV
From: CLDLV@NASAGISS.BITNET (Dimitri Vulis)
Newsgroups: comp.laser-printers
Subject: LaserWriter losing characters
Message-ID: <8711242104.AA22617@brillig.umd.edu>
Date: Sat, 14-Nov-87 12:01:51 EST
Article-I.D.: brillig.8711242104.AA22617
Posted: Sat Nov 14 12:01:51 1987
Date-Received: Sat, 28-Nov-87 11:06:47 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: laser-lovers@brillig.umd.edu

>From: mcvax!minster.york.ac.uk!john@uunet.uu.net
>Date:       30 Oct 1987 13:38:13 GMT
>
>My department has an Apple LaserWriter Plus connected to the serial
>output of a Sun 3/280 fileserver. ...
> ... the silos of the Sun serial port are emptied so quickly
>that one character pulse train immediately follows the preceding
>one, and that overrun errors occur in the UART of the LaserWriter's
>RIP.

Our department (my school, CUNY, not here) has a SunWriter (identical
to Apple LaserWriter) that used to be connected to a Sun (now it's on
a PS/2 model 60). When you drive it at 9600 bps, every 10 chars or so
it sends you a xoff and then you have to wait till it send you a xon.
Since you did not explicitly say that your driver waits for xoff/xon,
I presume that your problem MAY lie there. Most modern (post-1970)
software expects the adressee to do its own buffering.
----> Adobe stinks.
                                           DV
P.S. Your other printer sure sounds nice.