How do I select an ibmpro driver in JetDirect v10.34, UXv.11.11

[MArtin at unixera dot d]

Hello all ..
We are migrating to new server 5430 UX v11.11. Since JetAdmin no longer is supported, I have installed JetDirect v10.34 for 11.x, from the HP web site.

All Hp printer work now fine, but for 3 matrix printers on a 3 port JetDirect box, I cannot select an apropriate driver, ibmpro, oki or similar. (They work ok on the 11.0,JetAdmin machine).

I have tried the choice 55 (Plotter, printer no CR, with no luck )

It is crucial for the migration that all printers work.
I have had an output through server hpj2593a4 port1, as normal remote print, but not on port2 and port3.

A pointer to an apropriate driver or any other advice would be greatly appriciated.

Regards MArtin andersen mra@unixera.dk

[Thierry Poels_1 · Accepted solution]

Hi,

the Centronix or dumbplot drivers generally do the trick for matrix printers.

regards,
Thierry.

[MArtin at unixera dot d]

thanks ..
Yes , in the meantime I have found this paper in technical knowledge base

HP Jetdirect Print Servers - Choosing a Model Script for a Non-HP Printer

Date: 10/14/03
Document description: HP Jetdirect Print Servers - Choosing a Model Script for a Non-HP Printer
Document id: bpj02668


I have followed the instructions here, and finally get something out, to let the application format on hte printers.

I use hppi and add a dumbplot printer and correct it in Advanced to net_genericprinter. 0 to save .

We test the application this afternoon.

I'll post results ..
MArtin

[Bill Hassell]

There are no real drivers for printers, just printer scripts. Since there are thousands of printer models, it is impossible to provide something for every printer. So for non-HP printers, use the 'dumb' printer model script and then modify the script if you need special featurs such as found in the man page for HP printers (ie, man net_ljx000, You can read the net_ljx000 script for ideas at: /opt/hpnpl/sh/net_ljx000

[MArtin at unixera dot d]

Thanks to you both ..

The end of the story is, that the dumb on did the trick , since "dumb" is what the application expect.

My lesson learned, is to search wider than the forum, hence the article I found in the Technical Knowledge Base
See above.

Se you around..
Regards MArtin