Hi Linda,

Thank you for your advice. I tried the printing=bsd 
but that didn't do the trick. Hmmmmm, if I just use 
that without any print declaractions (i.e.: print command=,
lpq command=,lprm command=), it won't work. I guess 
that's to be expected, samba has no clue where the 
lprng files are ;)

A brief check through the archives said that long ago (yep, 
back in 2000) multiple print jobs weren't printed because
of the initial copy being deleted. lpd_bounce was the
solution back then, I think that caused it to pre-process 
through the filter and create multiple copies. Maybe that's 
the solution now? Tried both below in the /etc/printcap but 
still no multiple copies.
:lpd_bounce:\
:lpd_bounce=true:\

Cheers.

Mike Samuel

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]
Sent: May 10, 2002 11:27 AM

Hi,
I am using samba and have no problem printing mutiple pages from
windows so I checked out my smb.conf file and I still have 
printing=bsd eventhough I am using lprng you might give it a try.
(Personally LPRng has caused me alot of headaches with the upgrade
from 6.2 to 7.2, I noticed 7.3 is using CUPS and am considering
giving it a try)
                 Linda Hanigan

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to