Problems When Exiting Windows or WFWG After Running 386 Enh (86705)
The information in this article applies to:
• Microsoft MS-DOS operating system 5.0
• Microsoft MS-DOS operating system 5.0a
• Microsoft MS-DOS operating system 6.0
• Microsoft MS-DOS operating system 6.2
• Microsoft MS-DOS operating system 6.21
• Microsoft MS-DOS operating system 6.22
• Microsoft Windows 3.1
• Microsoft Windows 3.11
• Microsoft Windows for Workgroups 3.1
• Microsoft Windows for Workgroups 3.11
This article was previously published under Q86705
3.10 3.11 | 5.x 6.x
WINDOWS | MS-DOS
kbnetwork kbbuglist kbtshoot kb3rdparty kbenv
When you quit Windows or Windows for Workgroups after running in 386
enhanced mode, the system stops responding (hangs).
This problem can occur when one or more of the following conditions exist:
• Your system does not properly support loading MS-DOS high (DOS=HIGH) in
the CONFIG.SYS file.
• Your system is using an incorrect A20 handler for HIMEM.SYS.
• You are using a WINSTART.BAT file.
• Your system has a upper memory block (UMB) conflict.
• Your network interface card (NIC) is not correctly terminated.
• You are loading a network card driver (such as 3C509.COM) after running
NET START (typically in your AUTOEXEC.BAT file).
• You have a corrupted .WAV file playing as the Windows exit sound.
Microsoft has confirmed this to be a problem in Windows versions 3.1 and
3.11 and Windows for Workgroups versions 3.1 and 3.11. We are researching
this problem and will post new information here in the Microsoft Knowledge
Base as it becomes available.
To work around this problem:
For more information about WINSTART.BAT, refer to your Microsoft Windows or
Windows for Workgroups "User's Guide."
| Modification Type:
|| Last Reviewed: