"Backward Compatibility Hack Enabled" Warning

 Last reviewed: July 23, 1997
Article ID: Q107692
3.10 WINDOWS kbprg

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows version 3.1

The debug version of Windows that comes with the Windows SDK version 3.1 produces the following warning message: 

   wn Kernel: Backward compatibility hack enabled: xxxxx
This warning message is related to the information in the [Compatibility] section in the WIN.INI file that the USER and GDI modules use for backward compatibility with Windows 3.0. That is, if your application is compiled for 3.1 only, it will not be affected by the [Compatibility] section, and therefore the above warning message will not be generated.

Suppose that a Windows-based application is compiled to be compatible with both Windows versions 3.0 and 3.1 by using the /30 switch on the Resource Compiler (that is, rc /30). Then, the above warning message will be generated only when the application's module name matches with one of the module names in the [Compatibility] section of the WIN.INI file.

To avoid this warning message, make sure that your application's name is different from the ones in the [Compatibility] section, or do not resource compile with the /30 switch.

Information regarding the purpose of the [Compatibility] section for a listed application in the WIN.INI file and the identity of the application is confidential to Microsoft.

Additional reference words: ini 3.10
KBCategory: kbprg
KBSubcategory: KrDebug
Keywords : kb16bitonly

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: July 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.