barrett@jhunix.HCF.JHU.EDU (Dan Barrett) (08/12/89)
Our LN03R Scriptprinter has had a major problem since we bought it
over a year ago. I'd like to find out if the problem has been fixed yet.
If we send it a Postscript file that has EVEN ONE line that is
greater than 80 characters long, the entire file will not print. Break the
long line into 2 shorter lines, and the file prints fine. Needless to say,
this is not really standard Postscript behavior. :-) The printer spits
back error messages about an "Unknown Command," followed by garbage.
When we contacted DEC about this last year, their only response was
"Huh? You're kidding!" And we said, "We've printed the files on an Apple
Laserwriter with no problems." They said those famous words, "We'll get back
to you." They never did.
The printer is connected to a DECserver 200 via LAT. We send the
files from a VAX 8530 running ULTRIX 2.0. The printcap entry is pretty
standard:
ln03r|lnps|ps|ln03R postscript printer on a DECserver 200:\
:br#9600:\
:ts=CS2ATS:\
:lp=/dev/tty14:\
:df=/usr/local/bin/dvi2psfilter:\
:of=/usr/lib/lpf:\
:sh:\
:op=PORT_2:\
:sd=/usr/spool/ln03r:\
:lf=/usr/spool/ln03r/messages:
We send the files to the printer with the command: lpr -Pps filename.
Any ideas or news about this problem? Is it even remotely possible
that the problem is caused by lpr or another part of the printing software?
Dan
//////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| Dan Barrett, Systems Administrator -- barrett@cs.jhu.edu (128.220.13.4) |
| Dept. of Computer Science, Johns Hopkins University, Baltimore, MD 21218 |
| E-mail addresses: ARPANET: barrett@cs.jhu.edu |
| BITNET: ins_adjb@jhuvms.bitnet |
| UUCP: ins_adjb@jhunix.UUCP noog |
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/////////////////////////////////////grr@cbmvax.UUCP (George Robbins) (08/12/89)
In article <2282@jhunix.HCF.JHU.EDU> barrett@jhunix.HCF.JHU.EDU (Dan Barrett) writes: > > If we send it a Postscript file that has EVEN ONE line that is > greater than 80 characters long... > > Any ideas or news about this problem? Is it even remotely possible > that the problem is caused by lpr or another part of the printing software? It's possible the standard filter is doing a line wrap or truncation for you. Unplug the LN03 and plug the cable into a VT100 or other printer that can do 132 columns, and observe the "printout". If this is the problem, use lpf for the "output filter", so you will get the nice header pages, and /bin/cat for the "accounting filter" so your text won't get diddled. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)