Apr 12, '04 09:33:00AM • Contributed by: fghorow
Unfortunately, for Hewlet Packard's psc1210 (1200 series) all-in-one gizmos, when using the proprietary drivers (as opposed to the IJS drivers), the standard hints don't work: After setting up the raw queue, and going through Windows' "Add Printer" rigamarole, one is presented with a dialog box asking you to select a printer driver to talk to the remote IPP/HTTP print queue, and the psc1210 driver is not listed! This is true even after having installed the driver on Windows natively while having the psc1210 attached via direct USB to the Windows box. Basically, I suspect that the multifunction units have too many driver components to call any single one piece the driver, and good-old Windows doesn't seem to know it has a driver already installed in that selection list. Double plus ungood. I really wanted to keep the "proprietary" driver on the Mac, because of the support for scanning, OCR, fine-tuning the copying, etc. etc. etc.
After a number of false starts (including trying to install the DeskJet 3320 driver on the Windows box, which according to the hp inkjet sourceforge site's list of printers is the actual driver for the printer component of the psc1210) I eventually found the following solution:
In addition to the proprietary driver on the Mac, I also installed the hp-ijs driver, and built an additional CUPS queue for the printer using that driver. Once that is done, I grabbed the ppd file for the printer, stashed in into /usr/share/cups/model on the Mac (dunno if this was neccesary, but I did that first), and restarted the CUPS daemon on the Mac.
Once that was accomplished, it was on to dealing with the Windows side. After a bit more surfing, I found the recommendation to use the Adobe postscript driver near the bottom of this page. Installing that on the Windows box, pointing it at a network printer URL (of the usual form:
http://macs-name-or-IP-number:631/printers/foo_printer... and finally pointing it towards a local copy of the appropriate ppd file made the whole system work. Yee-haw!
In theory, not just the psc1210, but any of the HP all-in-one gizmos that work with the hp-ijs driver but are balky with the native Windows drivers might benefit from this same approach. For that matter, it seems to me that this dual driver approach is a general alternative to remotely driving printers, while keeping any benefits "proprietary" Mac drivers might offer.
I hope this helps someone else avoid the hours of tedious experimentation I went through to find this solution.