• Subject: Re: TCP/IP Printing, # of Copies
  • From: Gary Feinstein <gfeinste@xxxxxxxxxxxxxxxxxxx>
  • Date: Mon, 04 May 1998 09:26:12 -0400
  • Organization: Planet Hollywood International Inc.

DAsmussen wrote:
> It is my understanding that the only way to cirmcumvent the PAGERANGE and
> COPIES function loss inherent with LPD/LPR (after all, an inherently
> _SUPERIOR_ machine wouldn't actually _POLL_ a device to see what it's
> capabilities were and adjust its data stream accordingly, now _WOULD_ it ;-)?)
> is to create a "dummy" OUTQ and point it at the TCP/IP remote writer in
> question.  Send output to the queue rather than the writer, and PAGERANGE and
> COPIES should work again.
I changed the Destination parameter to 'XAIX XAUTOQ' to get the copies
functionality.  You may need a PTF to get this working though...don't
remember.  I don't think the double queueing technique will work by
> Be forewarned -- this method, while sound, utilizes even more system resources
> than "Host Print Transform" from what I've heard.  Be sure and have your
> spooling subsystem split out into a different memory pool with a high enough
> activity level if you're going to use it.  Hey!  What am I _SAYING_????!!!!
> That little miracle called QPFRADJ can do this _FOR_ you, can't it?  Everyone
> _SAYS_ you don't _NEED_ to understand Work Management anymore ;-)!
I am running approx 120 IP writers.  There has to be a better way to
manage all of these printers.  Anyone using WinAppc from Synapse? 
> Regards!
> Dean Asmussen
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].