View Single Post
  #7  
Old March 9th 10, 07:57 PM posted to microsoft.public.windowsxp.print_fax
Paul Baker [MVP, Windows Desktop Experience]
external usenet poster
 
Posts: 12
Default Print Job will not delete

John,

That's what I do, but I did not think to delete those files. If I don't, are
they just harmless orphaned files?

What is causing the delay? Is it waiting on a third party component?

Paul

"John John - MVP" wrote in message
...
Michael Dobony wrote:
Ok, why does it take forever to delete a print job? The printer ran out
of
black ink and I canceled and deleted the job. An hour later the job was
still deleting. This seems to be a common problem with all versions of
Windows. It also prevents one from getting on with other print jobs.


It's always been like that on NT versions. Stop the Spooler service and
then delete the files in the %Systemroot%\system32\spool\PRINTERS folder
and then restart the Spooler service again. From the Command Prompt:

net stop spooler
del /q %SystemRoot%\system32\spool\printers\*.*
net start spooler

MVP Pegasus has often posted this little batch file where he has added a
ping command to delay the batch commands to allow more time for the
spooler service to stop and start. You can use this batch file to do the
job for you:

@echo off
echo.
echo Purging the print queue . . .
net stop Spooler
echo Deleting all print jobs . . .
ping localhost -n 4 nul
del /q %SystemRoot%\system32\spool\printers\*.*
net start Spooler
echo Done!
ping localhost -n 4 nul

John



Ads