Many thanks for all the prompt replies. My question regarded the
optimum setup of a HP laserjet 6MP under Solaris 2.6 (see the original
question below).
The solution I used was to set up a separate printer queue for the
windows machines which accepts only 'simple' jobs. Therefore, when it
treats the postscript prepended with printer control as 'simple', it
sends it to the printer rather than attempting to convert it to
postscript again. Thanks to Brooke King and Anthony Worrall for that
suggestion. Other suggestions included telling the windows machine
that the printer was a basic postscript printer (thanks Danny
Johnson).
Thanks also to
Dave Foster
Vladimir
Charlie Mengler
Chad Price
Mark Ashley
Roger Fujii
Here was my original query:
> Hello - I've been banging my head against lpadmin for ages and have to
> admit defeat. Any help is gratefully received.
>
> I have a Laserjet 6MP connected to the parallel port on my Ultra 30
> running Solaris 2.6. I have installed all the recommended patches
> (including 105741 to fix the /etc/ecpp0 device).
>
> The configure script in /etc/lp/printers/laserjet/ is as follows:
>
> Banner: on
> Content types: simple,postscript
> Device: /dev/ecpp0
> Interface: /usr/lib/lp/model/standard
> Printer type: PS
> Modules:
> Options:
>
> Since I've had the printer I've not been able to print plain ASCII
> files properly. If I do 'lpr testfile.txt' the printer light flashes
> for a few seconds and then stops. Its only when the next file is
> printed that the first file comes out of the printer and even then I
> get the staircase effect. Postscript files print fine however, and
> other machines running IRIX, Windows 95 or linux can print postscript
> to the printer.
>
> Finally I got fed up with the ASCII problem so I tried
>
> lpadmin -p laserjet -I postscript
>
> and hey presto, 'lpr testfile.txt' works fine and so does postscript
> printing. What's happening is that any text file is being converted
> (with postprint.fd I suppose) to postscript now. This is reasonable
> but now the Windows 95 machine can't print. When it does, You get the
> raw postscript text, preceeded by some printer control codes. The
> first few lines are:
>
> %-12345X@PJL JOB
> %PJL SET ECONMODE = OFF
> %PJL SET RESOLUTION = 600
> %PJL ENTER LANGUAGE = POSTSCRIPT
> %!PS-Adobe-3.0
> %%Title: Untitled - Notepad
> ...
>
> I think that before I restricted the printer to postscript input, the
> program that Solaris uses to decide if a printer job is postscript or
> not decided that this was 'simple' (because it doesn't start with
> %!PS) and so sent the file directly to the printer with the correct
> results. Now, since it knows the printer doesn't allow 'simple', it
> sends it through postprint. I've looked at sunsolve and followed its
> suggestion to modify the printer settings on Windows 95 to 'optimise
> for portability' but that has no effect.
>
> I've experimented setting the device type with
>
> lpadmin -p laserjet -T hp
> lpadmin -p laserjet -T hplaser
> lpadmin -p laserjet -T hplaserjet
>
> but there seems to be no effect.
>
> Does anyone know how to make the printer work with ascii and
> postscript files from the local machine and also work with files from
> Windows 95?
>
> Many thanks for any help!
-- | Chris Murphy: Department of Mechanical Engineering, | | University of Bath, Claverton Down, Bath BA2 7AY, UK | | TEL : +44 1225 826826 ext 5558 FAX : +44 1225 826928 | | MAIL: C.M.Murphy@bath.ac.uk URL: http://www.bath.ac.uk/ |
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:14 CDT