16-Bit Windows Environment Stops Responding (Hangs)

 Last reviewed: May 5, 1997
Article ID: Q101266
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1

SYMPTOMS

After a 16-bit Windows-based application generates an exception error and hangs, the rest of the Windows NT operating system also appears to hang. The mouse and keyboard both seem to be disabled.

CAUSE

Normally, the 16-bit Windows environment is protected, running in its own virtual MS-DOS machine (VDM). However, in some cases a 16-bit Windows-based application can appear to hang Windows NT. This can be caused by an application that has enabled journal hooks (a method of recording or monitoring keystrokes and mouse movements). If the application is monitoring journal hooks and then hangs, since the mouse and keyboard are being actively polled by a hung process, they appear to be disabled.

RESOLUTION

Pressing CTRL+ESC to bring up Task Manager disables journal hooks, frees the mouse and keyboard, and enables you to close the application that caused the problem.

Additional query words: prodnt
Keywords : kbother nt16ap ntui
Version : 3.1
Platform : WINDOWS

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.

Last reviewed: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.