The timeout setting on a Novell network is set from under the Novell Client properties under the printer capture defaults. This is the amount of time that Novell waits from the time it last received any data on the lpt port until it decides you are done sending data. It then will stop receiving data on that print job and submit it to the printer.
If you send a streem of data to lpt1, wait 16 seconds and then send more data to lpt1, it will come out on 2 print jobs. If you send a streem of data to lpt1 and only wait 14 seconds, to start senging more data, everything will be on one print job. This is makes up for the lack of a mechanism to be able to tell Novell you are done with a print job. If you increase the setting, users will complain because Novell will sit idle longer before submitting the print job to the printer. Troy ===== Original Message from [EMAIL PROTECTED] at 1/11/02 7:58 am >Thanks, all for your suggestions. Printing from a file seems to be a good >solution. Just curious though, Troy, what timeout setting are you >referring to? In the dark recesses of my memory I seem to recall something >in Novell that holds the printer so that other jobs cannot slip pages into >a multi-page report.....but that was from pure dos capture days, I >think.... > >Bob C. > > > > > >This is caused from the timeout setting beeing too short. >The best solution is what Bernie suggested below. Print it to a file >first. > >out tempfile.$$$ >print rep1 >print rep2 >out screen > >set width 240 >out printer >type tempfile.$$$ >out screen > > >===== Original Message from [EMAIL PROTECTED] at 1/09/02 2:09 pm >>Bob - >> >> Print the two reports to a file and then print the file. >> >>Bernie >>====================================== >>At 03:54 PM 1/9/2002 -0500, you wrote: >>>I have an unusual occurrence and wondered if anyone has had a similar >>>problem. I have a dual DOS report that prints the first report then the >>>second report and it all links up on the same page. >>>OUT PRINTER >>>PRINT REPORT1 >>>PRINT REPORT2 >>>OUT SCREEN >>>There is no report footer in the first repot nor a form feed. Lines are >>>set to 0 on first report. This has worked fine for 4 years and now there >>>is a form feed after the first report prints. This ONLY happens when it >is >>>printing to a network queue, works OK when directly to LPT1. Tried this >on >>>several printers.... Looked at network settings and printer settings, >>>nothing new. Network adminisrator (Novell) made no changes that he will >>>attest to...... >>>Any ideas? >>> >>>Thanks, >>>Bob Castanaro >>> >>> >>>================================================ > > > > > > >================================================ >TO SEE MESSAGE POSTING GUIDELINES: >Send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: INTRO rbase-l >================================================ >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] >In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l
