LPR Printer Queue Name

Hello,
I have A dozens of LPR Printers in my organization.
When I create a Printer in Policies, It doesn't accept the the Underscore sign in the queue name (Marketing_Printer).
I don't want to change the queue name, is there a solution for that?
I have ZENworks 11.3
Thanks
YAron

Thanks for your reply.
Yes I think so, but mannual of router has not even indicated about that. It says that IP of print server is 192.168.1.254. It doesn't say that it's IP of the router. Even in router's cutomized settings it refers to it as print server's IP. And it is preassigned.
thanks again. i hope you'll try to find a solution.
jurry

Similar Messages

  • How to change the print queue name with Lexmark printer?

    Is it at all possible to change the print queue name from Lexmark_3500_4500_Series, to something shorter? I try to link printouts from an old Sun Unix system, thru my iMac to the Lexmark X4580 multifunction printer. However, the Sun/Unix will not accept this long print queue name...

    Apologies, I misread. The only way I know of changing the Print Queue Name is by readding the printer.
     > System Preferences > Print & Scan > Add
    Choose your printer, make sure you change the print queue name to something different (equates to the Printer Name).
    When you need to print, simply select the printer you just added.
    Once your happy it works, delete the old printer from the list in Print & Scan.
    Morgan

  • Lpr printing from linux

    We currently have Linux based applications that we would like print jobs be directed to windows print server. Our current server is windows 2012R2 with LPD services enabled. Does anyone have any type of documentation on how this could be achieved via LPR
    Thanks in advance.
    Rene

    the syntax of the lpr usage will depend upon the OS where you are running lpr, or however you might setup the remote print queue connection.
    an example of how you can use the Windows lpr.exe utility, is here:
    http://technet.microsoft.com/en-us/library/afc8790b-8b52-45c4-acdf-be0ffa9da534
    LPR is fairly basic, at its simplest, all the client needs to know, is the printserver hostname, and printer (queue) name.
    Create a Windows printer (queue), and test it locally from the WS2012 machine to ensure it works.
    if your WS2012 machine is named "server01", and the printer (queue) on that machine is named "printer01", those are the arguments you need to supply to your Linux clients. Depending upon the nature of the print jobs, you may need to specify other arguments,
    e.g. PDL or banners, etc
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • 'Unshare' 100+ dead print queues

    Hi there
    I have been tasked with removing inactive/dead print queues from our print servers (Server 2008 R2). I have been pinging all IPs for the past month to get an idea of what is dead and what isn't. Before I delete the queues, I would want to 'unshare' them
    first (untick the tick box) for 100+ queues. I am a complete PowerShell novice so I would appreciate it if someone could give me any code that they have used in the past, where I can just reference a list of print queue names I have in a text file and
    it unshares them in a batch process.
    Thanks in advance!

    $_.Comment = "$($_.Comment) - marked to unshare"
    I hope this post has helped!

  • How to keep file name in print queue when printing crystal report

    We are using VB .Net 2003 + Crystal Report 2008 SP2 up to Fix Pack 2.6
    When the VB program spools crystal report files to print queue, the print queue only shows "Crystal Report" for each document.  How to keep the original file name?  In the past when we were using Crystal Report 11, the original file name can be shown in the print queue.
    Please help because it's so important for operation to see which report is failed in printing when reports are printed in batch.
    Thanks

    Hello,
    Set the PrintOption.JobTitle value for the print job. Here's C# code on how to:
                   System.Drawing.Printing.PrintDocument pDoc = new System.Drawing.Printing.PrintDocument();
                CrystalDecisions.ReportAppServer.Controllers.PrintReportOptions rasPROpts = new CrystalDecisions.ReportAppServer.Controllers.PrintReportOptionsClass();
                CrystalDecisions.ReportAppServer.ReportDefModel.PrintOptions newOpts = new PrintOptionsClass();
                   pDoc.PrinterSettings.PrinterName = cboCurrentPrinters.Text;          
                   rasPROpts.PrinterName = cboCurrentPrinters.Text;               
                   rasPROpts.PaperSize = (CrPaperSizeEnum)
                        pDoc.PrinterSettings.PaperSizes[cboCurrentPaperSizes.SelectedIndex].Kind;
                // this sets the name of the print job
                rasPROpts.JobTitle = "MYPrintJob";
                   rptClientDoc.PrintOutputController.PrintReport(rasPROpts);
                   MessageBox.Show("Printing report.", "RAS", MessageBoxButtons.OK,MessageBoxIcon.Information );
    Thank you
    Don

  • How to set  the CR print job name that displayed in Printer job queue?

    As following image shows, when I press the Print button in Crystal Report Preview GUI,
    a print job is sent to Windows Printer Spool.
    [Windows Printer queue dialog snapshot|http://www.box.net/shared/96vq4qa2mp]
    The "Document Name" in the dialog is like "Crystal Reports - temp_214d9d11-a73f-4872-81f6-b8a63bf0a6b9.rpt".
    I want to know which property of Crystal Reports can be used to set the print job name to a more meaningful one.
    Edited by: Xiaobing Sun on Apr 2, 2009 5:08 AM

    The solution in this thread is for VS .NET as this is the forum for CR in .NET.
    With Foxpro, I suspect you want to create a new thread in the SAP Crystal Reports - Legacy SDKs forum.
    Make sure you specify the exact version of CR used.
    - Ludek

  • Printing w/Leopard & AD-based Windows Print Queues:

    For those interested, I have written an overview of printing in Leopard 10.5.0 to Windows print servers (published queues Active Directory). Your mileage may vary. This document contains the good the bad and the ugly.
    Objective:
    Get Leopard based Macs to print to AD published SMB print queues hosted on Windows 2003 print servers. Sounds easy, huh?
    Overview:
    Print Servers:
    Windows 2003 print servers.
    Printers:
    All the printers in my test were all new HP network b/w printers or network MFP b/w printers. All of them were less than 2 years old. None of them were consumer-grade home USB printers.
    Mac Clients:
    My test clients were Intel MacBook Pros and Intel iMacs running 10.5.0 Leopard. All of them had user AD accounts and all Macs were bound to AD using Directory Utility (or dsconfigad)
    The AD clients have a unique naming convention at my company. In my environment we use the initials of the person for their login name (SAM). Example:
    Real “human” Name: “Stephen Paul Jobs”
    Long Active Directory Name: “Steve Jobs”
    Short Active Directory Name: “spj”
    “Legacy” NT Names: “domain\spj”
    Full domain name (used for email etc): “[email protected]
    (you get the idea...)
    Note: My Mac clients are not in an Open Directory domain. No “Magic Triangle” in this environment. Pure AD for the sake of this example. I am not managing the Mac clients via MCX in this scenario.
    Print Protocols:
    All the print queues hosted on the print servers were standard SMB/CIFS print queues. The syntax (UNC) looks like this:
    smb://print_server.domain/queue
    (This syntax is invisible to most users printing to AD-published printers (or any network based printer really) . Most users will have no idea what protocols are being used.)
    Procedures:
    Part 1: Set up a new printer from an existing AD-published print queue:
    From the Apple menu select “System Preferences...” (or launch it from /Applications). The Printer Setup Utility app no longer exists. Apple has discontinued it fro various reasons.
    Click on the Printer & Fax pane.
    Click the “+” button on the left. This will launch the Apple Printer Browser (called “AddPrinter”, and lives in /System/Library/CoreServices), which looks similar to the previous browser in Tiger. The Printer Browser by default will usually show network printers vai Directory Services (AD/OD etc) as well as Bonjour printers and Mac OS X based shared printers – if they are shared via IPP and LPR under certain circumstances).
    Select the desired AD-published print queue you want to print to by highlighting it in the browser list and clicking the “Add” button. (Note: Print queues published via Active Directory will show up as “Open Directory” printers, even though this is not 100% technically correct.)
    Before the queue will be added, you will be prompted to authenticate as a local administrator. If you are not an admin you are screwed. Enter your name and password.
    Once the print queue is added, it will show up on your Mac in several ways (barring any bugs – see below). Here are the ways to tell if you have added the print queue successfully:
    A The new print queue will now be displayed in the Print & Fax system pref pane (but not always – see below).
    B You will see a printer proxy application in ~/Library/Printers/ which corresponds to your new print queue. This is the print monitor app that will show up in your Dock when you print to the queue.
    C You can see the new print queue via the CUPS admin page at http://localhost:631/printers.
    D You can see your new print queue from the Terminal by typing this command: “lpstat –v” (type “man lpstat” for more info on the lpstat and related commands)
    E You can also see your printers by launching an print-enabled application such as TextEdit or Safari and printing a page. You will be presented with Leopard’s new print dialog box (which now includes a print preview pane). From the “Printer” drop-down menu you can see all of your printers. You can add a printer from here too (which takes you to the steps listed above)
    (of course, most end users will only use option A listed above. The other options are more abstract and complicated)
    Now that the AD print queue has been setup on your Mac, you can print to it (maybe).
    Part 2: Printing to an AD-published print queue:
    Open a document you want to print.
    Choose “Page Setup...” from the File menu if you need to configure the job. (Optional)
    Choose “Print” from the File menu.
    From the Print dialog box, choose the desired print queue from the Printer menu
    Click the Print button.
    You will need to authenticate with a valid Active Directory username and password. You don’t have to have administrator credentials, but you have to verify that you are a domain member. In my environment, my Windows print server doesn't require authentication, but for some reason Leopard or CUPS makes you authenticate. (See below). Not only is this a major PIA, but the authentication dialog box itself is formatted to include the wrong credentials format for authentication in the first place.
    Volia! Done. Easy huh? Not really. Read on for the ugly stuff.
    My Complaints and Caveats:
    OK, so here’s where I vent, complain and scratch my head. Join in on the fun.
    Sometimes shared print queues don’t show up in the Print & Fax system preference pane after they have been added. I have no idea why. The local CUPS admin page (http://localhost:631) on my Mac test clients can see the connected queues, and the queues show up in ~/Library/Printers. The “lpstat –v” command shows the connect queues too. But for some reason, sometimes network print queues that I have previously setup (and use regularly) don’t show up in the Leopard Print & Fax preference pane. Local USB printers always show up fine for me.
    2. When challenged to authenticate a print job to a Windows print server (AD), the Mac’s authentication dialog box pre-populates the AD user’s name in the “Name” field incorrectly. Example:
    A user named “Joe Is Cool” (short name “JIC”) prints a job to the print server. The print auth dialog box challenges him for a name and password. It is pre-populated already with the name of “Cool, Joe”. When a valid AD password is entered, the job is rejected (it fails authentication and gets put on hold – which is hard to see this unless you explicitly look at the Printer.app proxy tool in the Dock). However, if the user replaces “Cool, Joe” with his official AD short name of “JIC” and then enters his AD password, the print job is accepted and printed. I wish Apple didn’t try and pre-populate the dialog box! Can this be avoided or prevented?
    In my environment, my Windows print server doesn't even require authentication, but for some reason Leopard or CUPS makes you authenticate. I’m working with my Windows administrators to figure this out. It will only accept user names with the short name format. It will not accept long (full) names or NT legacy names.
    3) The Printer Setup Utility app, which used to live in /Applications/Utilities, no longer exists. Apple has discontinued it for various reasons. Mainly security and simplicity. I wish it was still available, but the system pref pane works fine (well, usually)
    4) Active Directory-based print queues will show up in the OS X Printer Browser as “Open Directory” printers, even though this is not 100% technically correct. Why can’t OS X tell the difference between OD queues and AD queues and label them as such?
    5) Leopard has locked down the ability to add network printers. You now must be a local administrator in 10.5 or later. I understand the importance of this security measure in certain environments, but why can’t there be an option in the Security preference pane to “Allow non-admins to add printers”? This would make me very happy.
    6) Setting the default printer and resetting the CUPS system now require you to right-click in the left side of the Print & Fax pane. There no longer is a button or menu option to do this.
    7) Sometimes after a job has printed the printer proxy app (from ~/Library/Printers) stays in the Dock and won’t go away.
    Conclusion
    Please chime in on your experiences, bugs, opinions and comments.
    Message was edited by: Daniel Stranathan

    I have noticed several of the changes in our system when printing to an AD printer from a Leopard client. I have one issue that is pretty odd and I'm not sure what is going on. When printing an Excel worksheet, I get prompted for AD credentials. After submitting the job, the print queue says "Waiting for Authentication", I have to press the Resume button and then the authentication dialog pops up. I successfully authenticate (My auth dialog is populated correctly and the remember to keychain option is selected) and the job prints fine. If I print the same document again (without closing the worksheet or Excel), or any other worksheet, I still have to reauth. I can print just fine to the same printer from Textwriter and I do not need to authenticate. Weird...

  • LPR Printer via printer policy

    Hi,
    we should install two LPR printers (standard TCP/IP ports) pointing to the same server with different queue names.
    The two printer policies create on the target system only one port named ZENworks_IP.AD.DR.ESS. The last active policy gives the queue name!
    (Support | Cannot configure multiple LPR printers on the same IP address)
    But there is another bug on creating LPR port via ZCM: The port number will be 9100 instead of 515! So I cannot use the printer policy functionality to create LPR printers!
    If I change the Registrykey 'PortNumber' in the hive HKLM\CurrentControlSet\Control\Print\Monitors\Stan dard TCP/IP Port\Ports\ZENworks_IP.AD.DR.ESS from the value hex:238c (9100) to the value hex:203 (515) and restart the service spooler I can print to the queue!
    It would be nice, if in the printer policy would be an option to import printer properties. Actually, I have to import the properties with a bundle and the following command: rundll32 printui.dll,PrintUIEntry /Sr /n "PRINTERNAME" /a CONFIG.dat d
    Regards from Switzerland
    Beat

    bschilliger,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://forums.novell.com/

  • Lpr printing fails

    Configured iPrint with a printer. According to iManager 2.7LPR/LPD Client
    Support is enabled for this printer object. Printer Control shows that the
    printer is ready.
    novell-idsd and novell-ipsmd services are running
    Nonetheless, I can't seem to get it to accept any print jobs. Changed a
    windows client to print to the server ip address with the printer object
    name. It errors while queuing the job. This is the same test that I've
    used in the past for lpr printing through NDPS printers.
    I'd love to debug it further. Unfortunately, I can't enable CUPS printing
    on the OES2 server that I'm using for iPrint since CUPS and iPrint can't run
    simultaneously.
    Where do I start looking for the printing problem?

    I was testing with OES2. If I remember correctly, I responded to my own
    question when I found my stupid mistake. I hadn't opened the tcp/ip port
    through the firewall for lpr printing.
    Thanks for trying to help.
    .....Gregg
    "Dan Sadaka" <[email protected]> wrote in message
    news:Fmk6j.6720$[email protected]..
    > Gregg,
    >
    > What version of SLES?
    > What version of OES?
    >
    > Are you tring to print from the Linux command line (using lp) or are you
    > printing from a Windows PC using the printer iPrint created. If so, did
    > you create the printer using iPrint (http://server/ipp)?
    >
    > let us know...
    > -Dan
    >
    > Gregg Nicholas wrote:
    > > Configured iPrint with a printer. According to iManager 2.7LPR/LPD
    Client
    > > Support is enabled for this printer object. Printer Control shows that
    the
    > > printer is ready.
    > >
    > > novell-idsd and novell-ipsmd services are running
    > >
    > > Nonetheless, I can't seem to get it to accept any print jobs. Changed a
    > > windows client to print to the server ip address with the printer object
    > > name. It errors while queuing the job. This is the same test that I've
    > > used in the past for lpr printing through NDPS printers.
    > >
    > > I'd love to debug it further. Unfortunately, I can't enable CUPS
    printing
    > > on the OES2 server that I'm using for iPrint since CUPS and iPrint can't
    run
    > > simultaneously.
    > >
    > > Where do I start looking for the printing problem?
    > >
    > >

  • How to create HP LaserJet 2420 printer queue on Solaris 10

    Hi Solaris Gurus,
    I am having difficulty creating a printer queue for HP LaserJet 2420 on Solaris 10 (11/9) Sparc (Sun Fire T5220) server. A popular method used is with hppi (HP Jet Direct) tool but it does not have the exact printer driver and alternative printer drivers (e.g. HP LaserJet 4 / 4M, HP LaserJet 2000 series) resulted in only part of the text occupying the wrong side of an A5 page.
    An alternative approach that has worked in the past for simple default paper tray 2 (single paper tray), with tray 1 reserved for manual feed. This method involves creating a working printer queue on a Windows workstation (XP) / server (2000) with the correct driver and having configured to support Unix printing to receive LPR request from Unix systems in general. A remote printer queue would then be defined on Solaris 10 system which points to the Windows system. However, the printing jobs kept going to tray 1 (top manual feed) even though the Windows printer queue was configured to go to tray 3 (bottom tray).
    The earlier method would be simplest but needs the right driver (PDD) but I don’t know where to find it. The latter approach is also not working despite having got the right driver on Windows. A test page on the target Windows printer queue would print to tray 3 (bottom tray) of the printer correctly.
    Printmgr does not work well with HP printers from experience. It is good for serial and local printers.
    Your advice would be much appreciated.
    Thanks,
    Crystal

    Hi Giogio, and welcome to the HP Forums.
    I am sorry to be the bearer of this news, but do the age of the printer, it is not supported by Mac OS X 10.9. I am including a list below of the supported printers from Apple:
    OS X: Printer and scanner software available for download.
    For more information, I would recommend contacting the Apple Support Communities.
    Thank you for posting on the HP Forums.
    Please click “Accept as Solution " if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks" for helping!
    Jamieson
    I work on behalf of HP
    "Remember, I'm pulling for you, we're all in this together!" - Red Green.

  • How to use Linux Print queue in client_text_io.fopen to print from Windows

    We have a forms application deploed on LINUX (Oracle application server 10g).
    I have to print a file from local windows PC to a linux Print Queue from forms
    I have the following code
    PROCEDURE file_to_printer (i_filename_output IN VARCHAR2
    ,i_network_printer IN VARCHAR2) IS
    l_line VARCHAR2(2000);
    l_fileid_output client_text_io.file_type;
    l_fileid_print client_text_io.file_type;
    BEGIN
    l_fileid_output := client_text_io.fopen (i_filename_output,'R');
    l_fileid_print := client_text_io.fopen (i_network_printer,'W');
    WHILE 1 = 1 LOOP
    client_text_io.get_line (l_fileid_output, l_line);
    client_text_io.put_line (l_fileid_print, l_line);
    END LOOP;
    EXCEPTION
    WHEN NO_DATA_FOUND THEN
    client_text_io.fclose (l_fileid_output);
    client_text_io.fclose (l_fileid_print);
    END file_to_printer;
    Everything works fine if I use a windows printer like \\machine\printer.
    I want to use a Linux printer and specified the print queue as
    \\machine\print_queue_name. It's not working
    and I get error ORA-302000 on the following line
    l_fileid_print := client_text_io.fopen (i_network_printer,'W');
    and if I give only the queue name no error but it's not printing.
    Could you please tell me how to use a Linux/Unix print queue in this situation

    the simplest way is to edit the interface file (look in /etc/lp/interfaces for existing printers). Each script is
    run per print job where stdin has your print data, and stdout is going to your print device. You can just
    send the output to a file instead (assuming you can create a file in the windows directory from the solaris
    box). If it's a network share, you could use smbclient.
    -r

  • I hope it's Kappy reading this. My HP Laserjet successfully installed but can't create a print queue...

    Hello Kappy - Thank you for persevering with my printer issues. Firstly, I use Firefox, recently updated & as yet have not discovered how to monitor downloads. The software for HP Laserjet 2200 was eventually automaticallly, and therefore correctly, installed.The Add Printer Pane accessed via the + button in the Printer & Scanner window is blank - the Name & Location and Print Using & Add areas are all grayed out, therefore I can't locate the printer driver even though it is in the Printer folder. I messed around with HP Direct Protocol & Line Daemon functions, entering my IP address, just to see if I could locate the printer driver - I could. However, I get a pop-up window which says 'Unable to verify the printer on your network' but it gives me the option of going ahead anyway, which I did. I was able to create a print queue, able to give a print command, the printer window opens, but the printer appears as 'busy', but of course it's not printing. To look at the issue from another perspective: previously I was running 10.5.8 on my old Power Mac G5 and a week before I shifted over the iMac I paused the printer but when tried to resume printing I got a pop-up message saying IPadmin > enter administrator name + password. Which of course I couldn't do - I discovered this was a bug afflicting10.5 & 10.6 operating systems; the only way I could get around it was by re-creating myself as a new administrator, which I did, and got the printer going again. So, if I have a "Network" printer perhaps there's another route to get the driver recognized... What do you think?
    Alex Carr

    Morning Alexander Carr,
    Thanks for using Apple Support Communities.
    Use this article to troubleshoot printer issues in OS X.
    For more information on this, take a look at this article:
    Troubleshooting printer issues in OS X
    http://support.apple.com/kb/ts3147
    Best of luck,
    Mario

  • HP 1160 printer and HP newer printers and print queues

    FYI. The HP 1160 printer does not support queue based printing.
    We use Novell 5, IPX, and print queues. Our company has always been HP
    LaserJet printers based. They have been very reliable and only recently did
    we need to replace one. We have small workgroups so lighter duty printers
    have been fine and the 1160 seemed comparable to others we still use. Until
    we just purchased the 1160 all previous HP printers had supported Novell
    print queues. Hp tech support said it was a Novell issue..(typical cop out).
    Any input on what new HP printers actually support Queue based printing
    would be appreciated. Nothing on their web site actually indicates this
    support (or lack of it).
    Thanks
    Terry B

    You can always use external jet directs if necessary.
    Additionally, if they support LPR, you can use PrintQs via NDPS.
    ( No NDPS support required on the client side.)
    Terry B wrote:
    > FYI. The HP 1160 printer does not support queue based printing.
    >
    > We use Novell 5, IPX, and print queues. Our company has always been HP
    > LaserJet printers based. They have been very reliable and only recently did
    > we need to replace one. We have small workgroups so lighter duty printers
    > have been fine and the 1160 seemed comparable to others we still use. Until
    > we just purchased the 1160 all previous HP printers had supported Novell
    > print queues. Hp tech support said it was a Novell issue..(typical cop out).
    >
    > Any input on what new HP printers actually support Queue based printing
    > would be appreciated. Nothing on their web site actually indicates this
    > support (or lack of it).
    >
    > Thanks
    >
    > Terry B

  • Can't create a print queue on OS 10.7 via HP driver installed by Apple

    I've ust bought a reconditioned iMac and am getting applications up and running, but I'm unable to get my HP Laserjet 2200DN printer working. The Add Printer pane (Print & Scan Preferences) remains blank: Name & Location and Print Using & Add areas are all grayed out, therefore I can't locate the printer driver even though it has been installed in the Printer folder. I've messed around with HP Direct Protocol & Line Daemon functions, entering my IP address, just to see if the printer driver could be located - it could. However, I get a pop-up window which says 'Unable to verify the printer on your network' but it gives me the option of going ahead anyway, which I did. I was able to create a print queue, able to give a print command, the printer window opens, but the printer is  'busy', but of course it hasn't been given the command to print  anything.  Any ideas?
    Alex Car

    Morning Alexander Carr,
    Thanks for using Apple Support Communities.
    Use this article to troubleshoot printer issues in OS X.
    For more information on this, take a look at this article:
    Troubleshooting printer issues in OS X
    http://support.apple.com/kb/ts3147
    Best of luck,
    Mario

  • HP LaserJet 4100N-print queue reverts to pause

    I've been trying relentlessly to get my iMac (early 2008 model) to print on an HP LaserJet 4100N.  I've been able to establish the connection (via ethernet) using the IP address on the printer and configuring as Protocol LPD, HP LaserJet 4100 Series v.3010.107.  All looks good, including valid connection, etc.  However, when I try to print the printer queue goes into action, shows that it's "printing-copying print data-printing", but as soon as it gets to the next step "connected to printer" the job suddenly drops and reverts to pause mode.  According to the information provided under printer "Options and Supplies", I have driver version 19.5.  HP says that OS 10.6 comes with the necessary driver (where I started before upgrading to Mountain Lion), and that an update for Mountain Lion can be found under Apple's Software Update.  But no such update is found.
    My older PowerBook G4 with OS 10.6 works fine, so I'm assume it's an issue with the software/driver that's supporting Mountain Lion.
    Any suggestions?

    Launch the Console application in any of the following ways:
    • Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    • In the Finder, select Go > Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    • Open LaunchPad. Click Utilities, then Console in the icon grid.
    Select "/var/log/cups/error_log" from the file list on the left side of the Console window. If you don't see that list, select
    View > Show Log List
    from the menu bar. Then select the messages from the time of the last failed printing attempt. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
    If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.

Maybe you are looking for