Re: 2 Gig Print Spooler process
- From: "Andrew Morton" <akm@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Jul 2006 10:28:13 +0100
Scott M wrote:
The Printimage function gets called 500 times for tiffs that have
about 10 - 30 pages in each. I haven't installed the service on any
other machines to see if it will konk out the server there, either.
I really stinks to have to restart the spooler and to restart the
machine after only printing 100 tiffs.
And as far as other software, Jeff. What do you suggest? This is
a server side process for a production orientated environment so I
can't have much downtime.
"Andrew Morton" wrote
Could you monitor the size of the spooler directory and wait for it
to go down a bit before adding more print jobs to it?
Scott M wrote:
It doesn't go down...
What, not even after the images have been printed? I'm suggesting that
rather than try to sent umpteen gigabytes all in one go, you give the
printer (and print spooler) a chance to catch up/breathe. And avoid filling
up the disk the spool folder resides on.
...even after the service that spools the images is
restarted.
The print spooler service should not delete the files in the spool folder
just because it's been restarted.
The spool folder location is in the registry at
HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Print\Printers\DefaultSpoolDirectory
(and other locations; I can't remember which one to set to change it).
Andrew
.
- References:
- 2 Gig Print Spooler process
- From: Scott M
- RE: 2 Gig Print Spooler process
- From: "Jeffrey Tan[MSFT]"
- Re: 2 Gig Print Spooler process
- From: Scott M
- Re: 2 Gig Print Spooler process
- From: Andrew Morton
- Re: 2 Gig Print Spooler process
- From: Scott M
- 2 Gig Print Spooler process
- Prev by Date: Programming the sound control on XP
- Next by Date: Re: silly, probably meaninigless question
- Previous by thread: Re: 2 Gig Print Spooler process
- Next by thread: Re: 2 Gig Print Spooler process
- Index(es):
Relevant Pages
|
