Slow Printing under Windows



		Technical Support

	Slow Printing under Windows Customer is experiencing slow or delayed output from the printers when operating under Windows 3x or Windows95. The following articles are taken from the Microsoft Knowledge Base - Slow Network Printing from MS-DOS-Based Programs Article ID: Q140036 Creation Date: 21-NOV-1995 Revision Date: 22-NOV-1995 The information in this article applies to: Microsoft Windows 95 SYMPTOMS When you print from an MS-DOS-based program, it may take from 60 to 90 seconds before printing begins, causing the program to pause. Quitting the program causes printing to begin immediately. This behavior may also occur when you use the PRINT SCREEN key in an MS-DOS-based program. CAUSE This problem can occur if the MS-DOS-based program does not close the printer port. By default, Windows 95 waits 45 seconds after the program stops sending information before printing the document. RESOLUTION To resolve this issue, add the following lines to the appropriate sections of the System.ini file, and then restart your computer: [Network] PrintBufTime=10 [IFSMGR] PrintBufTime=10 NOTE: If the [Network] or [IFSMGR] sections do not exist in the System.ini file, add the sections after the [386Enh] section of the file. These settings are in seconds. The lower the value you use, the sooner the document is printed. If you do not receive any printout, or documents are printed over multiple pages, the settings may be too low. Increase the settings until documents are printed correctly. MORE INFORMATION The entry in the [Network] section controls the network printing timeout using the real-mode redirector (outside of Windows 95). The entry in the [IFSMGR] section controls the network printing timeout using the protected- mode redirector (within Windows 95). By default, this value is set to 45 seconds. Note that these settings may affect local as well as network printing. ------------------------------------------------------------------------ KBCategory: kbprint kbnetwork KBSubcategory: win95 Additional reference words: 95 THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. ©1997 Microsoft Corporation. All rights reserved. Legal Notices. Spooling Print Jobs from MS-DOS-Based Applications in Windows Article ID: Q98585 Creation Date: 10-MAY-1993 Revision Date: 02-JUL-1996 The information in this article applies to: Microsoft Windows for Workgroups versions 3.1, 3.11 •Microsoft Windows 95 The following article contains information on the use of Windows for Workgroups and Windows 95 with third-party products or configurations that have not been tested and are not supported by Microsoft. If the steps or procedures described in this article do not function properly, contact the manufacturer of the third-party product for more information or use a supported configuration. NOTE: In this article, the term "Windows" refers to Windows for Workgroups 3.x and Windows 95. SUMMARY Windows does not have the ability to spool local print jobs sent to the printer by MS-DOS-based applications. This article contains a potential workaround for this situation. This workaround may also alleviate device- contention errors. To spool print jobs from MS-DOS-based applications, you must print from one computer to another using a dummy port and then redirect the job back to the first computer. The print job is then put in the print queue. This process may eliminate device conflicts when you try to print to the local printer. NOTE: This workaround works only if the application has the ability to choose the LPT2 port instead of the LPT1 port. MORE INFORMATION The following example shows how the print job is redirected over the network. The diagram illustrates the flow of the data, and the text explains how to configure your system to obtain this functionality. ---------------- -------------- \| Server \|=<<===LPT1=<<====<<====LPT2====<<===\| Client \| ---------------- (shared) (to network) -------------- \| \| \| \| \| \| \| ==>>== LPT2 ====>>====>>==LPT2.DOS===>>==== \| (to network) (shared) \| \| (Local, LPT1) \| Printer: LPT1 \| From the server, share LPT1. 2.From the client, connect to the server using LPT2. 3.From the client, install a printer driver for the port "LPT2.DOS" and share it. 4.From the server, connect to the client's newly created share using LPT2. 5.From the server, print from the MS-DOS-based application to LPT2. Your print job is now effectively spooled to the printer. ------------------------------------------------------------------------ THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. ©1997 Microsoft Corporation. All rights reserved. Legal Notices. KBCategory: kbprint kbnetwork kbpolicy KBSubcategory: wfw wfwg win95 Additional reference words: 3.10 3.11 95 device contention printing dos msdos server client app apps spooler bounce prompt virtual machine vm printers drivers

	Email your support questions to tech@versaform.com

	This information is provided as a courtesy. VersaForm Systems Corporation has provided this information "AS IS" without warranty of any kind – express or implied. In no event shall VersaForm Systems Corporation be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.