SWANGER@AUDUCVAX.BITNET (06/03/88)
I have a DEC LN03R Scriptprinter (Postscript) that I have not been able to get
to work properly with a VAX (actually, I have two of these printers and each
has the same symptoms, so I don't think it's the printer, although anything is
possible). I have tried using this printer with both an 11/785 and an 8200
with little success. I have installed the DEC LN03R Scriptprinter software
version 1.0 on each VAX.
When I print small text files (3 blocks or less), they print with no problem.
But when I print large text files, part of the file prints and the rest is
lost. If I use a print/notify command, I eventually get an %LPS-I-IOERROR
message, followed by various messages telling me that one of the postscript
commands was unrecognized and that the rest of the job will be flushed. I
interpret these messages to mean that proper XON/XOFF communications between
the VAX and the LN03R aren't taking place, the printer's buffer becomes full,
some of the postscript commands from the VAX are lost, and the rest of the
postscript stream from the VAX becomes meaningless to the LN03R (of course, I
could be wrong).
I have the switches on the back of the printer set to: 4800 baud, XON/XOFF
enabled and 8 bits. I have two generic queues, one for text and one for
postscript code. I have named these queues TEXT and POST. The queue these
generic queues point to is named LN03R. The settings for these queues are:
Printer queue LN03R, on TXC0:, mounted form LPS$LN03R$FORM (stock=DEFAULT)
/BASE_PRIORITY=4 /DEFAULT=(FORM=LPS$LN03R$FORM (stock=DEFAULT))
/LIBRARY=LPS$LN03R$DEVCTL /OWNER=[SYSTEM] /PROCESSOR=LPS$LN03R$SMB
/PROTECTION=(S:E,O:D,G:R,W:W) /SCHEDULE=(NOSIZE) /SEPARATE=(FLAG,
RESET=(LPS$$EOJ),TRAILER)
Generic printer queue POST
/GENERIC=(LN03R) /OWNER=[SYSTEM] /PROTECTION=(S:E,O:D,G:R,W:W)
/SCHEDULE=(NOSIZE)
Generic printer queue TEXT
/GENERIC=(LN03R) /OWNER=[SYSTEM] /PROTECTION=(S:E,O:D,G:R,W:W)
As you can see, queue LN03R points to prot TXC0: (the printer is connected
directly to port TXC0:). The settings for device TXC0: are:
Terminal: _TXC0: Device_Type: Unknown Owner: SYMBIONT_0013
Username: SYSTEM
Input: 4800 LFfill: 0 Width: 80 Parity: None
Output: 4800 CRfill: 0 Page: 24
Terminal Characteristics:
Passall No Echo Type_ahead No Escape
Hostsync TTsync Lowercase Tab
No Wrap Scope No Remote No Eightbit
No Broadcast No Readsync No Form Fulldup
No Modem No Local_echo No Autobaud No Hangup
No Brdcstmbx No DMA Altypeahd Set_speed
No Line Editing Overstrike editing No Fallback No Dialup
Secure server No Disconnect Pasthru No Syspassword
No SIXEL Graphics No Soft Characters No Printer Port Numeric Keypad
No ANSI_CRT No Regis No Block_mode No Advanced_video
No Edit_mode No DEC_CRT No DEC_CRT2 No DEC_CRT3
Device spooled to _DUA0:
Does anyone have ANY idea why this printer isn't working correctly? I should
add that this printer works perfectly with an IBM PC with several software
packages (all with postscript printer drivers, of course). I am able to print
reasonably large documents (30-40k) with no problem from a PC.
I have the feeling that my VAX to LN03R problem is something simple that I have
overlooked. If anyone out there has any suggestions/help/ideas/solutions,
please send them to me.
Thanks for the help!
David Swanger
Academic Computing Services
Auburn University, AL 36849-5345
205-826-4813
SWANGER@AUDUCVAX <--- (Bitnet address)kenw%noah.arc.CDN@ean.ubc.ca (Ken Wallewein) (06/07/88)
> I >interpret these messages to mean that proper XON/XOFF communications between >the VAX and the LN03R aren't taking place, the printer's buffer becomes full, >some of the postscript commands from the VAX are lost, and the rest of the >postscript stream from the VAX becomes meaningless to the LN03R (of course, I >could be wrong). Me too. >Terminal Characteristics: > Passall No Echo Type_ahead No Escape I think I see the problem. Try using /PASTHRU rather than /PASSALL. They're the same, except that /PASSALL ignores _everything_, including XOFF/XON... and /PASTHRU doesn't. Wouldn't it be nice if these were properly documented? It's worth a shot, anyway. /kenw
SWANGER@AUDUCVAX.BITNET (06/09/88)
I would like to thank everyone who responded to my question about LN03R to VAX communications. In case anyone has the same problem, the terminal line used by the LN03R must be set to /NOPASSALL for flow control to work correctly. David Swanger Academic Computing Services Auburn University, AL 36849 205-826-4813 SWANGER@AUDUCVAX <--- Bitnet Address