Re: Postscript agony....

Article View: comp.lang.postscript

Article #661

Back to comp.lang.postscript Previous Next

#661

From: Caleb Hess
Date: Thu, 06 Jul 1989 15:14

4 lines
743 bytes

We've had similar problems in the past that were traced to parity or bits/char
settings.  The end-of-file character is ^D, but if parity or bit count is
wrong, it won't be recognized by the printer and will produce yet another
error message.

Technical Details

Message-ID: <22976@iuvax.cs.indiana.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!hess

References: <73@mara.cognet.ucla.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!hess
From: hess@iuvax.cs.indiana.edu (Caleb Hess)
Newsgroups: comp.lang.postscript
Subject: Re: Postscript agony....
Summary: parity, bits/char?
Keywords: noprinting laserwriterII unix serial port
Message-ID: <22976@iuvax.cs.indiana.edu>
Date: 6 Jul 89 15:14:13 GMT
References: <73@mara.cognet.ucla.edu>
Reply-To: hess@iuvax.cs.indiana.edu (Caleb Hess)
Distribution: na
Organization: Indiana University, Bloomington
Lines: 4

Reply to Parent Message