KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q49423: WINDOWCOMPAT Directs CodeView to Create a Window

Article: Q49423
Product(s): See article
Version(s): 2.20 2.30
Operating System(s): OS/2
Keyword(s): ENDUSER | S_C | mspl13_basic
Last Modified: 10-NOV-1989

The WINDOWCOMPAT directive in a linker definition file can cause
strange behavior in non-Presentation Manager (PM) programs being
debugged under CodeView. WINDOWCOMPAT is one of three application
types that can be specified after the NAME directive. WINDOWCOMPAT is
used for OS/2 programs that use VIO, MOU, and KBD calls and can be
used inside a PM window or as a separate screen group.

Debugging a non-PM application that was linked with the WINDOWCOMPAT
option instructs CodeView to create a PM window to run the program. In
some cases this feature could be desirable, but for most debugging, a
PM window is only cumbersome. The way to work around this feature is
to relink without the WINDOWCOMPAT directive.

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.