drm@noaacrd.colorado.edu (Donald Mock) (03/19/90)
Here's the problem: I'm using Sun's Transcript software with a QMS-PS810
laser printer attached to /dev/ttyb on a Sun 4/280 running SunOS 4.0.3
with all the relevant bug fixes. Users are complaining that it takes too
long to print 1MB postscript plot files. So I figure, "Why not use the
ALM-2 parallel port, since the QMS-PS810 also has a parallel port?" It
should be faster than 9600 baud, right? After connecting the thing up, I
can do a 'cat ps_file > /dev/mcpp0' where ps_file is a postscript file.
It comes out fast and correct. But I cannot get Transcript to do anything
with it through 'lpd'. I've tried numerous variations on the
/etc/printcap file with no success. Does anyone have any insight into
this problem? Can it be done? Is it just a matter of making the correct
printcap entry or must the Transcript package be modified as well? Thanks
in advance.
EXAMPLE PRINTCAP:
lw|lp|ps|postscript|PostScript:\
:lp=/dev/mcpp0:sd=/usr/spool/lw:\
:lf=/usr/spool/lw/lw-log:af=/usr/adm/lw.acct:\
:rw:mx#0:sf:sb:\
:if=/usr/tran/sparc/lib/psif:\
:of=/usr/tran/sparc/lib/psof:gf=/usr/tran/sparc/lib/psgf:\
:nf=/usr/tran/sparc/lib/psnf:tf=/usr/tran/sparc/lib/pstf:\
:rf=/usr/tran/sparc/lib/psrf:vf=/usr/tran/sparc/lib/psvf:\
:cf=/usr/tran/sparc/lib/pscf:df=/usr/tran/sparc/lib/psdf:graham@relay.eu.net (Graham Underwood) (03/21/90)
In article <5875@brazos.Rice.edu> you write: >X-Sun-Spots-Digest: Volume 9, Issue 83, message 11 >Here's the problem: I'm using Sun's Transcript software with a QMS-PS810 >laser printer attached to /dev/ttyb on a Sun 4/280 running SunOS 4.0.3 >with all the relevant bug fixes. Users are complaining that it takes too >long to print 1MB postscript plot files. So I figure, "Why not use the >ALM-2 parallel port, since the QMS-PS810 also has a parallel port?" I dont know much about transcript, but I have some experience of writing print filters for postscript printers. The problem could well be caused by the different behaviour of the printer on RS232 and parallel. On RS232 you can send ^T and the printer will respond with a status message in the form `%%[ status: busy ]%%'. The filters can therefore parse these and print out useful messages on the console like `paper out'. On parallel there is no such feature. If transcript is written assuming RS232 behaviour you are in trouble. What I did was disable all ^Ting if the interface was parallel and it works fine, only you dont get any status messages back - and yes it is faster. Doesn't help you much for transcript though. An alternative approach is to connect via RS232 AND parallel and use the RS232 for the ^Ts - again not much help for transcript. If you want an unbiased opinion, the best solution would be to buy some decent printer software ! If you want a really unbiased opinion ask one of our sales staff. Graham graham@advent.co.uk ..!ukc!advsys!graham