PRB: Fatal Exit 0x00FF or 0xD000: MakeProcInstance Fails

 Last reviewed: July 22, 1997
Article ID: Q74363
3.00 3.10 WINDOWS kbprg kbprb

The information in this article applies to:

  • Microsoft Windows Software Development Kit (SDK) for Windows versions 3.0 and 3.1

SYMPTOMS

An application running under the Microsoft Windows graphical environment receives FatalExit error 0x00FF or 0xD000, "MakeProcInstance only for Current Instance."

CAUSE

A function in a dynamic-link library (DLL) calls the MakeProcInstance() function using an application's instance handle. The FatalExit() occurs because the current value of the DS register does not match the instance handle passed to MakeProcInstance().

RESOLUTION

A DLL should not call MakeProcInstance() on behalf of the calling application. The MakeProcInstance() function is not designed to be used this way.

MORE INFORMATION

When an application is executing, the value of the DS register is equal to the application's data segment, which is identified by the application's instance handle.

Additional reference words: 3.00 3.10
KBCategory: kbprg kbprb
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 22, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.