Xref: utzoo comp.lang.postscript:2967 comp.windows.ms:993 comp.sys.dec:1888
Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!ucsd!ucbvax!bloom-beacon!eru!luth!sunic!tut!santra!mjolner!jnp
From: jnp@mjolner.tele.nokia.fi (J|rgen N|rgaard)
Newsgroups: comp.lang.postscript,comp.windows.ms,comp.sys.dec
Subject: Re: Hung DEC Scriptprinter
Message-ID: 
Date: 1 Oct 89 12:43:23 GMT
References: <2034@leah.Albany.Edu>
Sender: news@mjolner.tele.nokia.fi
Organization: Nokia Telecommunications Oy, Espoo, Finland
Lines: 26
In-reply-to: rds95@leah.Albany.Edu's message of 19 Sep 89 18:36:45 GMT


(Our configuration:
	DEC ScriptPrinter (LN03R) connected to UNIXes and VAXes
	through a LAT (?) - something that can be used for printer-
	connections.
	Gating from UNIXes goes via a DECStation)

I've experienced something similar:

	When printing certain types of files the printer
	dies with 'ioerror' (the exact position in the file can be moved
	by inserting/removing comments) or 'syntaxerror' (at places
	where there (verifiable) are no syntax-errors (looks like
	a part of the input "disappears" so that f.ex. strings are
	seen as commands). If the file is split into smaller parts
	they *always* print; the split is purely textual, so eventuel
	PostScript errors would not go away.

	Both the printer and the server (this LAT thing) claim to be
	using XON/XOFF, no parity and same number of databits.

--
--                                                                           --
| Regards, J|rgen N|rgaard ('|' is '\o{}' in \LaTeX{})                        |
|    e-mail: jnp@tele.nokia.fi or pedersen%tnclus.dnet@tele.nokia.fi          |
--                telephone: <..>-358-0-511-5671                             --