How to access HP printer print jobs waiting

Question

How to access HP printer print jobs waiting

I have different models of HP printers at 2 work sites, no network connection between them 40 miles apart. There is a button in the dialog box that says open print que, but when I click it, nothting happens. How do I get to the print que to delete jobs that I mistakenly assigned to the printer at the other site? OS 10.7.2

I downloaded the latest HP drivers from the APP store. still cannot get to the que to delete jobs before they start printing.

MacBook, Mac OS X (10.4.11)

Posted on Dec 8, 2011 2:28 PM

Reply

Answer 1

sdpitbull

Level 3

965 points

Dec 8, 2011 2:34 PM in response to jamesfrombryan

Did you try System Preferences > Print & Scan

Select the printer and click Open Print Queue...

Then you should see this:

Jobs on hold should be listed. You can click on one and click the red slash/delete to remove it.

Oh you say they are at 2 sites but not network connected? How are you printing to the remote one?

You may need HP software directly from HP to do what you want. I know my other HP will let you get into the printer itself and delete jobs.

Or am I not understanding this at all? 🙂

Reply

Answer 2

Dec 8, 2011 2:57 PM in response to sdpitbull

I tried going to system preferences , then print and scan, and I get the first dialog box, but when I click on "open print queue" nothing happens.

When I click on the options and supplies button, that works, It even gives me a name for the print queue, but when I search for that name I get no results.

My problem is that when I am at site A and close down for the day, go to site B, create a new document I just hit the command p return to print before I remember I should have selected a new printer. I often print again - this time remembering to select the correct printer from the list so I don't need to print again at site A. So the job sits in the queue for the printer at Site A, and when I return to site A and plug the printer in, it just starts printing.

I went to the HP web site and they just refer you to the Apple site.

The printers I am using are old and I doubt HP is writing drivers for them any more. This just began when I updated to a new MacBookPro and jumped from system 10.4 to 10.7 The old drivers were from HP.

I just may be out of luck.

Reply

Answer 3

sdpitbull

Level 3

965 points

Dec 8, 2011 3:15 PM in response to jamesfrombryan

I'm going to rephrase so I understand you correctly. Hope you don't mind.

At Site A working, close down for day. (At this point the default printer is probably the Site A printer.)

Go to Site B and hit Command-P and forget to change to the Site B printer. Job is sent to a queue for the "A" printer.

The key phrase you said is "when I plug the printer in". When you are at Site B you are not connected to Site A and cannot see the Site A printer - you have no physical connection to it nor a wireless one but I would think it would still be writing the job to a local queue for the Site A priner on your machine.

Weird that you say going into the site A print driver will not let you into a queue. When you check on the Site A printer while at Site B - do you even get the Print Queue... button at all? I would think you should always be able to see the Queue screen, even if it is an empty one. The job has to be in queue somewhere because, as you say, if you go back to Site A and plug in the job will start printing.

You may have to go down to a system level on this one. I would suggest you look up CUPS - that is the printer engine under all the pretty dialog boxes - and see if that leads anywhere. You may also want to see if there is a printer forum or check in on the OS X forums.

Sorry I couldn't be of more help. Strange.

Reply

Answer 4

Dec 8, 2011 6:31 PM in response to sdpitbull

Yes, you got it. It seems that once a job goes in the queue, the only way to get ot out is to let it print. Thanks for trying to help

Reply

Answer 5

sdpitbull

Level 3

965 points

Dec 8, 2011 7:05 PM in response to jamesfrombryan

The job has to be going to a queue because you say it prints when connected at Site A. Strange it is not showing in the queue. Something to do with CUPS is going to be your answer.

Reply