stupid question

Ben Scott dragonhawk at gmail.com
Fri Jun 2 16:42:01 EDT 2006


On 6/2/06, Jerry Feldman <gaf at blu.org> wrote:
> Solution 1 for Windows (this is true).
> 1. Turn off printer.
> 2. Try to delete from the queue.
> 3. Windows does not delete it from the queue and may hang or simply lock up
> the queue.

4. Obtain a command prompt with admin privilages on the computer
hosting the spool queue.  This might mean using "MSTSC" to access a
server, "RUNAS" to obtain a privilaged command prompt on the local
machine, or just doing Start, Run, "CMD", OK.
5. NET STOP SPOOLER
6. NET START SPOOLER
7. See if that fixed the queue.  If so, stop.  If not, continue.
8. NET STOP SPOOLER
9. CD C:\%SystemRoot%\SYSTEM32\SPOOL\PRINTERS
10. DEL *.*
11. NET START SPOOLER

  Determining which of these is "easier" is left as an exercise to the reader.

-- Ben



More information about the gnhlug-discuss mailing list