Discussion Locked

Win '98 - DOS program print problem

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Win '98 client on a NetWare network that is not directly connected to a printer. I have captured the printer port for the network printer using the LPT1 and the path for the Network printer. When I print from MS-DOS while editing a file (such as config.sys and choosing file, print) or by using the "type [filename]>lpt1" command the print jobs come out immediately. However, when I print from the actual DOS program the job just sits in the queue (shown as being spooled) until I print directly from DOS to "force" the print job. I have the spool settings set to "spool print jobs so program finishes printing faster - Start Printing after first page is spooled" and the spool data format is RAW. What can I do to get the job to printand not remain in the queue?

7 replies

by jimbb

You're mixing two things here. "Spool print jobs..." or "RAW" are Windows' spool settings, while it seems that your program is using the Novell queue a bit strange.
Long time ago dBase did the same, only the network version printed properly.

What you can try is to play a little with the capture parameters. Possibly the timeout ("/ti=xx") may help. The timout is meant for DOS programs that print in bits and pieces: if nothing more comes within the specified amount of seconds, Novell considers the printjob finished and sends it to the printer.

This timeout parameter can be set in the login script, as in "#capture l=1 Q=MyQueue ti=10", or it can be done in the Settings of the capturings you make on the workstation itself.

Jim

by raymond wong

Hi,
The problem exist when the application sending the print job is not network capable.
I would agree that you need to use the ti option to have a cut off time. The value for ti is in seconds.
The other option is to close the application which would then close the print job for printing.

by lelton

Don't forget the timeout attribute in the capture command. I would suggesting putting the capture command into the login scripts. I found when using the GUI interface the users were give the opertunity to disable those captures upon bootup. The dos captures in the login scripts fixed this problem.

Les

This discussion is closed to new replies.