abraka1
28th January 2003, 18:02
When using a script to print to multiple printers from HPUX.
It prints OK on the line printer but other printer which is a LaserJet,
Printout is too big to fit in one page and it prints remaining bit on other page. Below is the script. Printer is defined as direct in BaaN device.
cp $1 ~$USER/ftp.data
lp -dUK_DAVQA -p7 -onb ftp.data
lp -dRXC_printer -p7 -onb ftp.data
How to make it print OK on both the printers?
OmeLuuk
29th January 2003, 13:14
Does these printers use the same printerdriver?
I guess what you are doing is copying the printfile which is printerspecific (after being processed by filter6.1, which replaces "universal" Baan code in the tmpfile with printerspecfic code in the tmp file which is the output of filter6.1) and send it to another printer...
abraka1
29th January 2003, 15:20
Thanks, both the printers use same driver (etext_fx-->one used in line printer) in ttadv3100m000, in UNIX $BSE/lib/printinf/ has different drivers for both the printers when used alone.
. Is there any work around?
ssbaan
29th January 2003, 17:03
a liitle confused?
How can you use the same BaaN printer driver for a line printer and a laser jet printer and have normal printed reports be Ok.
I though there were different drivers for each?
Second thought... was the last report printed on the laser jet in
large print and the printer was never reset to the defaut font size? or is the default font size large?
abraka1
29th January 2003, 17:59
There is a printer defined in baan ttaad3100 with following data
device type: Direct
Driver : etext_fx
device Queue : /var/adm/test/multi_print %s
in the multi_print script baan temp file is copied to
and directed to two different printers-->
cp $1 ~$USER/ftp.data
lp -dUK_DAVQA -p7 -onb ftp.data
lp -dRXC_printer -p7 -onb ftp.data
Windows printing is ok and uses jet direct for UNIX printing.
please let me know if you need further info.
OmeLuuk
29th January 2003, 18:28
... so you are sending lineprinter code to the laserjet.
This must be one of the laserjet's features, epson compatibility... so some extent.
You are asking for a work around.
Create an filter6.1 script that calls the original filter6.1 (renamed) binary.
Analyse the incoming string (which has some 20 arguments, among which the driver for the line printer) and call the same original filter with a modified argumentline to be sure to use the laserjet driver and another 12th argument for the printer dependent output file.
Leave the original printerfile as is, and send the 12th argument (modified) to the laserjet.
an argumentline then could be:filter6.1 -p etext_fx -c 1 -f 1 -t 999999 -i /usr4/b40_c4/bse/tmp/tmp023467856 -o /usr4/b40_c4/bse/tmp/tmp023468032 -l 66 -m 1 -n 0 -L ISO-8859-1so call one time with this line and a second time withfilter6.1 -p hp_lj4 -c 1 -f 1 -t 999999 -i /usr4/b40_c4/bse/tmp/tmp023467856 -o /usr4/b40_c4/bse/tmp/tmp023468032.hp_lj4 -l 66 -m 1 -n 0 -L ISO-8859-1and afterwards send the /usr4/b40_c4/bse/tmp/tmp023468032.hp_lj4 to the laserjet printer.
abraka1
30th January 2003, 15:24
Thanks OmeLuuk.It is OK now.
OmeLuuk
30th January 2003, 15:49
Can you post your solution for future reference?