using non-HP network printers

[Marc Ahrendt]

printer: Konica Minolta bizhub di5510
server: HP-UX 11.11 using hppi (E.10.34)
problem: not working as a network printer ...able to configure it, but all print jobs stay queued up

detail: below are the steps i took

hppi -> 1 -> 1 -> 157.165.183.172 -> y (continue ...problem) -> 2 (ignore it and continue the process) -> 58 (HP LaserJet Printer not given in this list) -> 4 (printer connected to other) -> 1 -> orminp01 -> 0 -> y -> q -> q
cat /etc/group | lp -dorminp01 -olandscape
lpstat orminp01
orminp01-1554 root priority 0 Jan 9 09:11 on orminp01
(standard input) 274 bytes
cancel orminp01-1554

note: keep in mind that I generally use HP printers and for years "hppi" just works ...so never really have had to dig deep into printer configuration files on HP-UX. also I want to avoid using this as a remote printer if possible ...so just wondering if there was a procedure to follow to make this printer a network printer.

[Marc Ahrendt]

forgot to mention that I reviewed the forums and found the following posts ...they were close to what I have asked, but just no details on a solution

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=972538
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=971229

[Steven E. Protter]

Shalom,

You might want to try CIFS/9000 which is Samba and includes printer sharing that may work with this printer. Otherwise you'll need an HP-UX driver to make the printer work and there aren't many drivers like that.

There may be a separate cups implementation on http://software.hp.com

Go for either CIFS/9000 or Internex express or cups.

Each have their advantages and pitfalls.

SEP

[Emil Velez]

Does it have a postscript personality that you can set it to or a PCL personality.

Somewhere in the documentation you need to find a way to make it support postscript and/or PCL.

I have made older Postscript (laserwriters) work with HPUX systems using postscript.


good luck

[Bill Hassell · Accepted solution]

A remote printer (in HP-UX SAM terminology) uses RFC 1179 lpr/lpd protocol. However, HP-UX does no preprocessing (read: no lp -o options) so remote printing is undesirable.

SAM's network printer simply calls hppi, a special program to setup HP JetDirect LAN cards. The code is designed to work only with the HP proprietary JetDirect protocol on port 9100 (not port 515). With JetDirect LAN connections, all the printer script options are available (man net_ljx000).

But the Konica probably has it's own internal card and does not support JetDirect (based on the hppi responses) so hppi apparently resorts to remote printer protocol. hppi was never designed to work on non-HP printers so your only choice is to get an HP JetDirect external adapter such as the 170x. Connect the 170x to the parallel port of the Konica and then use hppi to configure the Konica as a network printer.

The SysV spooler does not provide any method to enable -o options as it would require local processing of the options in the spooler. I don't of any plans for HP to redesign the spooler for that end.

[Marc Ahrendt]

thx for the tip steven ...if i had the time i would play around with samba since its on the server

thx bill ...i most likely will be buying that device (looks like convenience will cost me some cash though ...the 170X is ~$100)

[V. Nyga]

Hi,

you also can try to use model type 54, 55 or 56. 55 works for kyocera for ex.

HTH
Volkmar

[Bill Hassell]

You can find these 170X boxes on eBay for less than $30. One nice feature: all your PCs, other HP-UX boxes and even Sun boxes can talk to the Jetdirect box. And since the 170X has lpd/lpr protocol, Linux and most every other OS can also talk to the printer.

[Marc Ahrendt]

i didn't try using other options for the printer like "54, 55 or 56" in hppi since that is not the issue

by chance we have a 170X and i was able to try it out. now at this point hppi behaves better in that it was able to communicate to the printer (yet still had to select a printer type ..choose 58 again). however nothing prints to the printer. the 1st print job went through (not seen in "lpstat") but the second got queued up ...again, neither printed. tomorrow will look at the printer to see if it is even configured to use its parallel port now that we switched the connection from its Fiery NIC to the parallel port (170X connected to this port). i tried simply power-cycling the printer but that did not help...