Nil said:
That ought to work...
That may work, but it shouldn't be necessary. The Print Spooler
Service should be set to Automatic in Services.msc. If it is set that
way, but you keep finding it in a stopped condition after rebooting
the computer, something is wrong - the service is crashing for some
reason. The real problem needs to be addressed. The event log should
provide some clues.
Right. Here's a batch file (PURGE.BAT) to dump the contents of the spool
file.
@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
I use this when everything is so hoplessly FUBARed, it's just easier to
start over than to try and cancel 100 jobs in the print queue.