Virtual Device Drivers (VXDs) Do Not Work in Windows NT

Last reviewed: May 8, 1997
Article ID: Q103012

The information in this article applies to:

Microsoft Windows NT operating system, version 3.1
Microsoft Windows NT Advanced Server, version 3.1

In Windows NT, Windows 3.x virtual device drivers (VXDs) written for 16-bit applications do not work.

Virtual device drivers were originally written to take advantage of 386 enhanced mode functionality in previous versions of Windows (3.x). The VXDs registered themselves in the SYSTEM.INI file upon installation of the application that required their presence.

In Windows NT, these VXDs do not function properly. In most cases, these drivers talk directly to hardware by virtualizing the device to be used. By design, Windows NT does not allow applications to communicate with the hardware directly. Applications that require the use of VXDs must be rewritten to function properly with Windows NT.

Additional query words: prodnt
Keywords : kbother nt16ap ntinterop
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 8, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.