GPF When PowerBuilder Watcom Engine Is Run in Separate VDM

 Last reviewed: February 7, 1995
Article ID: Q120426
The information in this article applies to:
  • Microsoft Windows NT workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

If you run the PowerSoft PowerBuilder Watcom database engine DB32W.EXE in a separate VDM, a General Protection Fault (GPF) occurs when another application tries to access the database through DB32W.EXE. In tests with Microsoft Query, the GPF occurred in <unknown> at 00C7:B40A.

CAUSE

When another application sets up ODBC, PowerBuilder's DB32W.EXE passes it a 16:16 pointer what is valid only in the VDM where DB32W.EXE is running.

RESOLUTION

DB32W.EXE will run in a separate VDM if you check the Run In Separate Memory Space box in the Program Item Properties dialog box in Program Manager. It will also run in a separate VDM if you launch it with the START command. Run the querying application and DB32W.EXE in the same VDM.

STATUS

This behavior is by design.

Additional reference words: prodnt 3.50 memory violation
KBCategory: kb3rdparty kbbug3.50
KBSubCategory: nt16ap

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