Article ID: 103361
Article Last Modified on 10/31/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
This article was previously published under Q103361
In Windows NT, if you lose your connection to a network printer and it is set as the default printer, 16-bit Windows-based applications may load significantly slower than usual or appear to hang completely.
When 16-bit Windows-based applications, such as Write, attempt to load, they may search for a printer. If the printer is a network printer and the connection has been broken, the application may load very slowly or appear to hang.
WORKAROUND
To work around this problem, install a local printer and set it as the default, reestablish the network connection, or remove the network connection entirely.
MORE INFORMATION
Steps to Reproduce Problem
- In Print Manager, connect to a network printer and set it as your default printer.
- Close Print Manager and return to Program Manager.
- Open Write from the Accessories group twice.
NOTE: The reason for doing this twice is that if no other 16-bit Windows-based applications have been loaded, the first launch of Write will take longer because it has to load the 16-bit Windows Subsystem.
- Notice the time Write takes to load.
- Close all instances of Write.
- Unplug the network cable from the network card.
NOTE: Consult with your Network Administrator before removing any network hardware.
- Restart Write and notice the extra time it takes to load.
Additional query words: prodnt wow
Keywords: kbprint kbnetwork KB103361
