This is *way* overdue. My apologies to the list and
especially to those that responded so quickly to my posting.
======
Original question:
> I have an Apple Laserwriter 16/600PS printer sitting on a TCP/IP network
> with two Solaris boxes. There are also printers directly connected to each of the
> Sun's. Printing to either of the directly connected printers is no problem from
> either host. The problem is printing to the network printer. I can only get
> postscript out of the Laserwriter. Under BSD printing the printer detected content
> type based on the remote printer name flag (rp) in the printcap file. i.e.
>
> bdips|LaserWriter 16/1600PS :\
> :lp=:\
> :rm=libps1600.biotech.ufl.edu:\
> :rp=raw:\
> :sd=/var/spool/lpd/bdi_PS:\
> :lf=/var/spool/lpd/printerlog:
> :mx#0:
>
> < ... other stuff deleted ... >
Well I was close - I just couldn;t quite grab the brass ring. The answer is that
you can tell this particular printer which of its internal print queues to use
by specifying the printer name as the queue name. (Which, had I read and
UNDERSTOOD the original printcap entry would have been obvious). Here's the
exact sequence of commands I used:
lpsystem -t bsd -p libps1600.biotech.ufl.edu
lpadmin -p bdips -s libps1600.biotech.ufl.edu\!raw
enable bdips
accept bdips
The ascii queue was set up the same except bdips was changed to bdi and
raw was changed to text. This duplicates the rp=raw, rp=text bits
from the SunOS style printcap entry.
Thanks to:
John Justin Hough <john@oncology.uthscsa.edu>
Mike Youngberg <mikey@synacom.com>
"Mark.Phillips@UniSA.Edu.Au" <itumrp@lux.levels.unisa.edu.au>
Glenn.Satchell@Uniq.com.au (Glenn Satchell - Uniq Professional Services)
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:14 CDT