On Tue, 9 Jul 1996, I wrote:
> I have a DEClaser 5100 printer attached to a LAT terminal server. The
> current printcap for this printer is
>
> lp2|2|laser:\
> :ct=LAT:\
> :if=/usr/lbin/ln09of:\
> :lf=/var/adm/lperr:\
> :lp=/dev/lat/622:\
> :mc#20:\
> :mx#0:\
> :of=/usr/lbin/ln09of:\
> :pl#66:\
> :pw#80:\
> :rw:\
> :sd=/var/spool/lpd2:\
> :sh:\
> :xf=/usr/lbin/xf:
> lp3|3|ps:\
> :ct=LAT:\
> :lf=/var/adm/lperr:\
> :lp=/dev/lat/622:\
> :mx#0:\
> :pl#66:\
> :pw#132:\
> :sd=/var/spool/lpd3:\
> :sh:\
>
> This is running OK, except for two problems:
>
> 1) I wanna set up the text incarnation to print two pages of text on the
> same sheet. I think this can be achieved by some sort of pr command plus
> lpr parameters. Any help?
>
> 2) I am using Samba to share the printers with the local network PCs.
> Unfortunately the Windows postcript driver generates a ^D at de beginning
> an at the end of each job, causing a postscript interpreter error. I
> realy do not know whi this kind of error does not appear when I have the
> printer hardwired to the PC's paralel port :-(. My initial idea was to
> write a small C program to act as a filter and remove the ^D, but I was
> wondering about the possibility off do this by means of some printcap
> magic. What do you suggest?
=====
From: "Daniel S. Notov" <danno_at_large.com>
--8<--
Look for a copy of nenscript. This filter will convert text to poscript,
and has the ability to print 2-up (2-col, landscape). A great paper saver.
--8<--
Did you try sending to the device LPT#.DOS?
sometimes the windows driver acts differently when a job is sent to the
pseudo-file device.
=====
I installed nenscript from my Sunsite mirror CD. It is running very well.
=====
=====
From: Walter Alpuin <WalterA_at_bufalo.coasin.com.uy>
--8<--
No me queda claro donde esta el problema.
Pero como primer pregunta es si probaste definirla con filtros
transparentes para usar los drivers de windows
--8<--
Yes, but ^D was the culprit, not the filters.
I tried even without filters...
=====
=====
From: Grant Ward <gaward_at_cssip.edu.au>
From: Rene.Landert_at_gd.srg-ssr.ch
(same suggestion)
-----
You can tell MS-Windows to not put a ^D at the beginning of the print
job. The Unix print filter will interpret the ^D as the end-of-file
character and so stops immediatly processing the print job.
To suppres the ^D edit the file c:\windows\win.ini at each PC using the
network printer.
Search for the section for the appropriate network printer, i.e. a line
with
[PostScript,LPT1]
add the following line to the section:
CtrlD=0
-----
I did this, but Windows - that stupid thing - is yet putting ^D at
beginning an end of each job...
I will try with another PostScript printer driver (perhaps DEC's).
=====
Thanks to all.
-----
Carlos A M dos Santos - Analista de Sistemas
Universidade Federal de Pelotas - Centro de Pesquisas Meteorologicas
Pelotas, RS, Brasil - e-mail: ufpelrm_at_eu.ansp.br
Received on Thu Jul 11 1996 - 20:20:58 NZST