INFO: WIN31COMPAT Flag Allows Compatible Win3.1, Win95 VxDs

Last reviewed: June 4, 1997
Article ID: Q169582

The information in this article applies to:

Windows 95 Device Driver Kit (DDK), version 4.0

SUMMARY

By using the WIN31COMPAT flag, you can build a VxD that is binary compatible between Windows 3.1 and Windows 95. A number of DDK header files check for this flag because certain functionality is new for Windows 95 and would not work under Windows 3.1.

MORE INFORMATION

You can define this flag in your header file:

   #define WIN31COMPAT

Alternately, you can pass the flag to the assembler in the makefile, using -DWIN31COMPAT. For example, in the Windows 95 DDK under \ddk\base\samples\generic, the makefile contains the line:

   AFLAGS = -coff -DBLD_COFF -DIS_32 -W2 -c -Cx -Zm -DMASM6 $(DDEBUG)

You can simply insert -DWIN31COMPAT on this line.

To ensure binary compatibility in your VxD between Windows 3.1 and Windows 95, you must not call services that are new for Windows 95.

Keywords : NTDDKVDD kbinfo
Version : 4.0
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: June 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.