LPR Printing to Windows 2000

[Sean Furman_2]

We are trying to improve the performance of some of our print jobs in HP UX 10.20. We have found that when we spool the jobs to Windows 2000 via an LPR remote printer, the jobs print very fast (no pausing between pages). The pauses occur becuase our ERP system sends each page as a job for some reason.

The problem that we are encountering, is that when we send the job to the 2000 queue, the text on the HP8100 is very small (15 cpi). We need 10cpi for the forms to print correctly. Windows 2000 is obviously overiding the settings in the control panel on the printer. I have also changed the printer driver to a generic text only. This outputs the text in the right size however, it puts some wierd characters on the page and does not allow us to access the other tray in the printer. Maybe there is a different model script for the printer that could improve its printing???We are very interested in getting this working. Any input would be much appreciated.

[Sandro Schaer_1]

Sean

we had similar problems and found a rather simple solution.

All our printfiles are plain text files on the unix machine. before printing on windows via lp command we 'cat' an escape sequence into a work file and append the print file using 'cat >>'. Now we 'lp' this work file. since the escape sequence is at the very beginnig of the file it sets up the printer the way we need prior to printing the rest.


hope this helps

[John Flanagan]

I have done this to a number of different printers. There are 2 things you need to do.

1. You need to add a reg key 'Simulate pass through' = 1 on the win2000 print server

2. Modify your printer script file on the unix box to add the control characters.

This works well enough but the best solution is to use a print server and connect both systems directly to the printer.

In you need more details let me know.

Regards,

John.

[John Flanagan]

That Reg Key is

'SimulatePassThrough'=1 and you should add it at

Hkey_local_machine/system/currentControlSet/Services/lpdsvc/parameters

[Richard Saldivar]

First:
There is a parameter in the Jet Direct card called IDLE TIMEOUT: Default = 90 or 270
This parameter is the time the printer wait between jobs for the job to complete. So when the ERP/UNIX system sends a one page job it then waits 90 seconds to make sure that it has completely finished the getting and printing the job then it releases hold and goes get next job. This is an old hold over when different HOSTs printed and you needed to insure your job came across as one continous print job, but with lasers they suck in the whole job and print as opposed to old line printers which took in one line at a time.

With newer LANs I have set this to 15 seconds to get rid of the pauses between the print jobs. You may have to play with this parameter because if set too low the print server assumes that a disconnect occurs and goes and gets same job over and over again and HPUX will tell you on one page disconnect and reconnect then print out the page that it assumed it dropped. This happens when the Network segment gets really busy with people downloading music/movies etc.

Telnet into jetdirect card
Enter a "/" to see what is set up
Enter a "?" to see how to type parameter

idle-timeout:15 .
type "quit" or exit to save parameters. depending on jetdirect card and firmware.

Update to latest firmware(always) to insure little problems go away.


Second:
We have a similiar system execept that we are going one step further to send jobs through Citrix to remote users.

You may find that if you set up the QUE system in SAP/ERP (If that is what you are using) that set it ot HPLH4: Hp Laserjet4 series PCL5 that this works the most consistant.

I have to disagree with the assessment that either host is controlling the print layout.
The application normally handles the font, layout etc. The Unix system passes thru these parameters and when passing to a Win2K system that system should just pass thru the layout and font.

Once any control characters come across be it application(ERP), UNIX, WIN server it does override the control panel of any of the HP line.

I believe that it is the application doing the format not the UNIX queue or Win2K.

The reason you have to set up UNIX and define type of printer for UNIX and WIN is so that if the OS has to print it has the correct driver.

Sorry if there was too much information, but you have described two problems.

The original problem about the time delay could be handled with the top suggestion of setting IDLE-TIMEOUT: to a lower setting.

And if the ERP system driver may have to be tweaked for a different font.

Good Luck
Richard

[John Flanagan]

What is Your ERP system and does it send pring jobs as a text file or in PCL or PS format?

Regards,

John.