hi,
thanks for your help, I have been thinking about somethinge like that. But
I ran these printers for some years with a bunch of shell scripts as
a filter without any problems, so I thought there might be something in
the IFHP filter that triggers this stuff. I'm also worried a bit because
the number of default copies is written in the flashrom of the printer and
I experienced that after a certain number of write accesses the flashrom
breaks and is not writeable anymore.
Thank you for the piece of postscript anyway, I will put it in the filter and then
just let them run as long as
they work ;-)
By the way my shell-script filters are heavily using the hpnp commandline
tool but it seems to have disappeared from the HP website, they probably
think that webjetadmin is a replacement (?)
thank you very much !!!
take care
~christoph
On Fri, 2 Nov 2001, Jim Easton wrote:
> christoph beyer wrote:
> > but I actually mean something different: after a while the default
> > number of copies entry in the internal printer menu is set to e.g. 13
> > copies, which automatically results in 13 copies of every job you send.
> > This is probably done by some pjl string but I don't know which one and
> > where it comes from....
>
> I can suggest where it might be coming from:
>
> The number of copies can be set by the postscript file. Likely
> a user has asked for 13 copies. Naturally the postscript
> doesn't set it back and that leaves the printer with /NumCopies
> set.
>
> If LPRng doesn't have a option with which you can force, or at
> least default, the number of copies to 1 you could send it the
> following postscript file.
>
> %!
> << /NumCopies 1 >> setpagedevice
>
> As an interesting note: years ago our administrator decreed that
> multiple copies were not allowed because photocopying was cheaper.
> (In fact it was - by quite a bit) Since this didn't cut no ice
> with the users I ended up putting a catch in the filter which
> forbad the setting of /NumCopies - complaints predictable.
>
> This did not however prevent some enterprising sole (sic.) from
> setting the console to multiple copies. Of course he didn't
> set it back - they never do - and after that we got several
> copies of every job. :-( So I added a default of one. That
> worked just fine until one day people were telling me that
> one of our printers was printing two copies of the banner -
> I had forgotten to default the banner too - sigh.
>
> Jim
>
>
> -----------------------------------------------------------------------------
> 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.
> -----------------------------------------------------------------------------
>
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
