The problem is that your client is trying to use a non-HP printer. While the addqueue command works fine, as you have demonstrated with the use of -i 9998 which uses a generic printer script.
> I'm trying to find a solution that is both simple, and easily repeatable for non HP-UX people. Altering printer model scripts and adding escape characters is more complicated process than I'd like to provide.
As you might expect, HP is not going provide printer scripts for non-HP printers. If the client cannot use a modified printer script, then tell the client to replace all the printers with HP printers.
> There are a few different makes and models of DM printers here, so this would end up being a customized process for each. Also, I do not have any documentation for any of them, so I do not know what the exact codes are.
Therein lies the difficulty in trying to support a lot of different printers. However, most printers can print plain ASCII so a dumb printer script should work.
> What I was hoping for was a way to set up some sort of "dummy" queue. Anything sent to that queue would be put through the ux2dos fileter and then back out to the printer.
The issue is with the -i 9998 choice. This is definitely NOT a generic printer but a rather full-featured HP PCL printer script. Although not intuitive at all, the script called dumbplot_printer_cr (which is -i 9992) will fix the basic problem with line feeds. Just remove the printer and re-add it like this:
removequeue -q Q_NAME
addqueue -b off -h XXX.XXX.XXX.XXX -q Q_NAME -i 9992
You'll see the contents of all the JetDirect scripts in /opt/hpnpl/sh. The dumbplot_printer_cr script is only 32 lines long and should handle any basic printer requirements (even HP printers) although there are no options available with this script.
Bill Hassell, sysadmin
