Keyboard Interface Not Available for MS-DOS Based Applications

 Last reviewed: August 6, 1996
Article ID: Q123216
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

After you create a Program Information File (PIF) for COMMAND.COM or CMD.EXE, an MS-DOS based application, such as EDIT.COM, that is run from AUTOEXEC.NT does not have access to the keyboard interface. Keyboard strokes made during the execution of the MS-DOS based application are displayed after you exit the application. The mouse interface still works correctly.

If you run the same PIF without the MS-DOS based application in AUTOEXEC.NT and load the application from the command prompt (either COMMAND.COM or CMD.EXE), this problem does not occur.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5. This problem was corrected in Windows NT version 3.51.

KBCategory: kbtool kbbug3.10 kbbug3.50 kbfix3.51
KBSubcategory: ntutil
Additional reference words: prodnt 3.10 3.50

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: August 6, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.