Can't kill a print job

[Stephen Ford]

XP Pro + SP2 + HP Deskjet 840C

I think this is the first print job that's gone wrong since upgrading from
Win98se. I can't stop a detailed graphics job from printing.

I suspect there is so much in the XP's buffer that cancelling the job and
switching the printer on and off to trash the printer's buffer still results
in masses of junk output.

If I want to stop a job in an emegency I cancel the job and sometimes, it
depends, remove the paper from the printer and switch the printer off and on
maybe feeding one page through until the junk stops printing.

It was taking so long presumably because of the big graphics job that I
decided to restart XP...

.... lo and behold, the print job restarted as if I'd not tried to stop it at
all. It's like Glen Close in Fatal Attraction - the bi*tch wouln't die ...
:-}

Regards
Stephen Ford

 

[Bobby]

After canceling the job, stop the printer spooler service and restart it.

 

[Pegasus \(MVP\)]

XP Pro + SP2 + HP Deskjet 840C

I think this is the first print job that's gone wrong since upgrading from
Win98se. I can't stop a detailed graphics job from printing.

I suspect there is so much in the XP's buffer that cancelling the job and
switching the printer on and off to trash the printer's buffer still results
in masses of junk output.

If I want to stop a job in an emegency I cancel the job and sometimes, it
depends, remove the paper from the printer and switch the printer off and on
maybe feeding one page through until the junk stops printing.

It was taking so long presumably because of the big graphics job that I
decided to restart XP...

... lo and behold, the print job restarted as if I'd not tried to stop it at
all. It's like Glen Close in Fatal Attraction - the bi*tch wouln't die ...
:-}

Regards
Stephen Ford

Paste the following lines into a batch file, then create a shortcut
to invoke the batch file. The method is simple, brutal and usually
very effective.

@echo off
net stop "print spooler"
del /q "%SystemRoot%\system32\spool\PRINTERS\*.*"
net start "print spooler"
ping localhost -n 5 > nul

 

[Jim Macklin]

Open printer properties and purge the documents in the
buffer.


--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.
some support
http://www.usdoj.gov/olc/secondamendment2.htm



message | XP Pro + SP2 + HP Deskjet 840C
|
| I think this is the first print job that's gone wrong
since upgrading from
| Win98se. I can't stop a detailed graphics job from
printing.
|
| I suspect there is so much in the XP's buffer that
cancelling the job and
| switching the printer on and off to trash the printer's
buffer still results
| in masses of junk output.
|
| If I want to stop a job in an emegency I cancel the job
and sometimes, it
| depends, remove the paper from the printer and switch the
printer off and on
| maybe feeding one page through until the junk stops
printing.
|
| It was taking so long presumably because of the big
graphics job that I
| decided to restart XP...
|
| ... lo and behold, the print job restarted as if I'd not
tried to stop it at
| all. It's like Glen Close in Fatal Attraction - the bi*tch
wouln't die ...
| :-}
|
| Regards
| Stephen Ford
|
|

 

[Pegasus \(MVP\)]

Your method works in theory. In practice there can be
extremely long delays, even hours, until the jobs get
purged.

 

[Jim Macklin]

Gee, it only takes a few seconds on my computer, I have an
HP 3820 and it has a pause print and a "cancel all" command.
Some printers say purge, but why would it take hours to run?


--
The people think the Constitution protects their rights;
But government sees it as an obstacle to be overcome.
some support
http://www.usdoj.gov/olc/secondamendment2.htm



| Your method works in theory. In practice there can be
| extremely long delays, even hours, until the jobs get
| purged.
|
|
in message
| | > Open printer properties and purge the documents in the
| > buffer.
| >
| >
| > --
| > The people think the Constitution protects their rights;
| > But government sees it as an obstacle to be overcome.
| > some support
| > http://www.usdoj.gov/olc/secondamendment2.htm
| >
| >
| >
in
| > message | > | XP Pro + SP2 + HP Deskjet 840C
| > |
| > | I think this is the first print job that's gone wrong
| > since upgrading from
| > | Win98se. I can't stop a detailed graphics job from
| > printing.
| > |
| > | I suspect there is so much in the XP's buffer that
| > cancelling the job and
| > | switching the printer on and off to trash the
printer's
| > buffer still results
| > | in masses of junk output.
| > |
| > | If I want to stop a job in an emegency I cancel the
job
| > and sometimes, it
| > | depends, remove the paper from the printer and switch
the
| > printer off and on
| > | maybe feeding one page through until the junk stops
| > printing.
| > |
| > | It was taking so long presumably because of the big
| > graphics job that I
| > | decided to restart XP...
| > |
| > | ... lo and behold, the print job restarted as if I'd
not
| > tried to stop it at
| > | all. It's like Glen Close in Fatal Attraction - the
bi*tch
| > wouln't die ...
| > | :-}
| > |
| > | Regards
| > | Stephen Ford
| > |
| > |
| >
| >
|
|

 

[R. McCarty]

Sometimes you can go directly to the Spooling folder and remove
the jobs from there:
C:\Windows\System32\Spool\Printers
On my system I redirect my "Spooling" folder to a scratch disk
where I keep all my Temp/workspace stuff. MS has an article on
how to redirect it here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;308666&sd=tech

 

[Steve N.]

Paste the following lines into a batch file, then create a shortcut
to invoke the batch file. The method is simple, brutal and usually
very effective.

@echo off
net stop "print spooler"
del /q "%SystemRoot%\system32\spool\PRINTERS\*.*"
net start "print spooler"
ping localhost -n 5 > nul

What is the ping line for?

Steve

 

[Bob I]

A 4 second delay is what it is for. The question is why is there a 4
second delay?

 

[Pegasus \(MVP\)]

What is the ping line for?

Steve

It gives the user 5 seconds of viewing time, to see the
result of the job. Sometimes the print spooler service
cannot be stopped - this is a simple way of making
the user aware of this.

 

[Pegasus \(MVP\)]

If I knew the answer to your question then I would not
use my little purge tool. The problem usually occurs when
there is something wrong with the printer, e.g. an invalid
printer port (e.g. USB instead of LPT1, or an invalid
network printer).

 

[Bobby]

Yes, I have seen it take an hour/s depending on the job sent.

 

[Stephen Ford]

Funny you should say this because my print job just disappeared of it's own
volition ... well after I'd done everything I could think off..

Regards
Stephen Ford

 

[Stephen Ford]

Pegasus

I like the look of this. Thanks.

@echo off
net stop "print spooler"
del /q "%SystemRoot%\system32\spool\PRINTERS\*.*"
net start "print spooler"
ping localhost -n 5 > nul

Stephen

 

[Pegasus \(MVP\)]

Actually, about 5 seconds . . .

A 4 second delay is what it is for. The question is why is there a 4
second delay?

 

[Steve N.]

It gives the user 5 seconds of viewing time, to see the
result of the job. Sometimes the print spooler service
cannot be stopped - this is a simple way of making
the user aware of this.

I knew it would cause a delay, just didn't know why. Thanks for the
explanation.

Steve

 

[Steve N.]

Yes, I have seen it take an hour/s depending on the job sent.

I have seen it still "cancelling" for over a day in some cases. That's
when I go into Safe Mode and delete the damn printer.

Steve

 

[Steve N.]

If I knew the answer to your question then I would not
use my little purge tool. The problem usually occurs when
there is something wrong with the printer, e.g. an invalid
printer port (e.g. USB instead of LPT1, or an invalid
network printer).

Also corrupted job, data or printer driver.

Steve

 

[HeyBub]

Gee, it only takes a few seconds on my computer, I have an
HP 3820 and it has a pause print and a "cancel all" command.
Some printers say purge, but why would it take hours to run?

Because the son-of-a-bitch deletes the first byte in the queue and shuffles
the remaining 30 million bytes up by one. Then it deletes another byte.

I don't know the ACTUAL reason, but the above theory matches the symptoms.

On a fast printer, you're better off letting the damn thing print 100 pages
of trash than to purge the job.

 

[Torgeir Bakken \(MVP\)]

Actually, about 5 seconds . . .

Hi,

Actually, the "formula" commonly used in the scripting groups and
command line/batch groups, is that the number behind -n is number
of seconds to pause + 1, so "-n 5" would be closer to 4 seconds than
5 seconds.

Using the VBScript below (using -n 5), I get results from 4.2 to 4.5
seconds.

'--------------------8<----------------------
Set oShell = CreateObject("WScript.Shell")

iStartTime = Timer
oShell.Run "ping.exe localhost -n 5", 0, True
iEndTime = Timer
WScript.Echo iEndTime - iStartTime

'--------------------8<----------------------