BUG: App Error While Changing Install Dir for Visual C++

Last reviewed: July 24, 1997
Article ID: Q141866
The information in this article applies to:
  • Microsoft Visual C++, 32-bit Edition, versions 4.0, 4.1, 4.2, 5.0

SYMPTOMS

After you change the Install Directory during the setup process, an error similar to the following occurs.

On Windows NT:

   The instruction at "0x00415900" referenced memory at "0xa6375ebf".
   The memory could not be read.
   Click on OK to terminate the application
   Click on CANCEL to debug the application

On Windows 95:

   The program has performed an illegal operation and will be shut down.
   If the problem persists, contact the program vendor.

   Pressing the details button reports:
   ~VCxxxx caused an invalid page fault in module ~VCxxxx.TMP at 0137:
   00415900.

   Note that in the above description xxxx represents a random number.

CAUSE

The total length of the installation directory exceeded 248 characters.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The error occurs in a temporary file. Setup.exe copies the [CDROM Drive]\Msdev\Setup.bin file onto your destination drive as a temporary file after which it is erased.


Additional query words: crash
Keywords : kbsetup vc40setup vcbuglist400 vcbuglist500
Version : 4.0 4.1 4.2 5.0
Platform : NT WINDOWS
Issue type : kbbug


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