on HP and using a remote printer on a NT print server

[Marc Ahrendt]

i am trying to print from my K380 "hulk" running 10.20 to a remotely configured printer "hilcopy1" on a NT print server.

GOOD: i can print to hilcopy1 from hulk
BAD: none of the lp options like "-olandscape" work

any idea why? thx

1) hilcopy1 was setup in sam as a remote printer ...i've checked/unchecked the BSD option, no help
2) i disabled hilcopy to check the control file being sent ...looks OK

Hhulk
Proot
Jhilcopy1-2
C
Lroot
B
K1
Olandscape
T/etc/publickey
FdfA002hulk
fdfA002hulk
UdfA002hulk
N/etc/publickey
A0

3) the printer is a Minolta Dialta Di520 ...which is actually copier that also allows for network printing to it

[Bill Hassell]

Absolutely normal. HP-UX uses a SysV print spooler, similar to Solaris and since SysV did not define remote printing early in the design, all the -o options are completely ignored when you send the job to a BSD-based spooling system. There is no fix, that's just the way it works. In a BSD spooler, the job is run through tools to perform special formatting according to the printcap config file, then the result is sent to the printer or remote system (ie, preformatted). In SysV, printer scripts are used to create the special features but these only work with local printers (including JetDirect connections).

The only choice you have is to change the LAN interface to an HP external JetDirect box, or take a model script and turn it into a filter so the appropriate options will take effect locally and the final print job will contain the required codes.

Note that HP model scripts only work for HP's PCL language, so unless the Minolta understands PCL codes (emulates an HP printer), then -olandscape wouldn't work anyway. If you have written a custom Minolta model script, just strip off the options and option processing portion and turn it into a filter.

[Steven E. Protter]

You can print to this printer, if you add a print spool to your system.

I doubt its worth it in this case, and you'll have to customize the PCL codes and it still might not work.

But here is a relatively inexpensive, full featured print spooler for HP-UX

http://www.easyspooler.com

SEP

[Jose Antonio Orozco]

We have implemented a trick to put PCL prints with nt tcp/ip printing

After you setup TCP/IP printing, change to 1 the following REGEDIT entry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\LPR Port\Ports\{printerport}
HpUxCompatibility

hope this works.

[Jose Antonio Orozco]

sorry, but the last comment was for PCL Unix prints to NT box used as LPD gateway to several laser printers attached to windows clients desktops using (also in Win9x) LPD software.

[Marc Ahrendt]

twang: i have done all that you have stated ...NT system sends information unaltered to the printer

bill: thx for the information ...just wish i knew how to make a model script to act as you say

i would really like to figure this out because there a several non-HP printers i cannot currently use (not jetdirect cards) from my HP 10.20/11.00 servers yet are being used by our NT servers. i have opened a call with HP support to try to get some guidance on the model script creation.