> From [EMAIL PROTECTED] Wed Nov 21 08:06:22 2001
> Date: Wed, 21 Nov 2001 10:10:06 -0500
> From: Rajeev Agrawala <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: LPRng: spooling to windows lpd
>
> As per windows FAQ, if you wish to spool to windows lpd serv
hi,
multiple possibilities:
on the command line:'lpr -Fl -P or lpr -l -P
in the printcap: 'default_format=l' (or 'global' in
the lpd.conf file with the same entry)
(this works only on the client, the machine that creates the controlfile)
do the translation for
It is a NT 4.0 machine. For that particular machine, I also applied the
same fix that you have mentioned (enabled SimulatePassThrough
). But for a change Microsoft mentioned compliance to RFC :), and I was
wondering if LPRng lpd server can send the codes as per RFC1179 and send
the 'l' control
you didn't mention if this was 2000. On NT4, the following helped me.
SYMPTOMS
When a formatted job prints from a line printer remote (LPR) client to a
Windows NT computer that is running the Line Printing Demon (LPD) services,
PCL or PostScript codes are printed instead of a properly
As per windows FAQ, if you wish to spool to windows lpd server "l"
cahracter must be passed to windows lpd for passing the job directly to
printer. Following is the text from Microsoft site
"The Windows NT LPD Service follows the RFC1179 specification. This
states that the LPR client must tell
