BUG: Invalid Page Fault or GPF Results When Making an EXE File

Last reviewed: October 16, 1996
Article ID: Q150220
The information in this article applies to:
  • Enterprise Edition of Microsoft Visual Basic, 32-bit only, for Windows, version 4.0

SYMPTOMS

If the Application Description field (on the Tools menu, select Options dialog, and select Project tab) contains more than 101 characters, then making an EXE file for the project causes a General Protection Fault or Invalid Page Fault.

STATUS

Microsoft has confirmed this to be an issue in the Microsoft products listed at the beginning of this article. Microsoft is researching this issue and will post new information here in the Microsoft Knowledge Base as it becomes available.

WORKAROUND

Avoid the problem by ensuring that the Application Description is less than 101 characters in length. Descriptions of this length are not recommended in any case, because some Object Browsers can truncate the string due to its size.

MORE INFORMATION

This problem only occurs if the Remote Server Support files are generated for the project. This is controlled in the Options for the EXE file which can be obtained by pressing the Options button in the Make EXE dialog box.

Steps to Reproduce Problem

  1. Start a new project in Visual Basic. Form1 is created by default.

  2. From the Insert menu, select Class Module to create the module.

  3. Press F4 to invoke the Properties for the Class module, change the Instancing property to 2-Createable MultiUse, and change the Public property to True.

  4. From the Tools menu, select Options. Then select the Project tab, and type in an Application Description that is greater than 101 bytes long. For example:

    0123456789012345678901234567890123456789012345678901234567890123456789 01234567890123456789012345678901

  5. From the File menu, select Make EXE, and in the dialog box, select the Options button. Select the Remote Server Support Files check box. Click OK, and then attempt to make the EXE file. An Invalid Page Fault or a General protection Fault occurs.


Additional reference words: 4.00 vb4win vb432 buglist4.00 GPF
KBCategory: kbprg kbbuglist
KBSubcategory: PrgOther


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