> Thread-Topic: VB upgrade crashes with Data Execution Prevention
> thread-index: AcWC0vV0cSgNG/FYSkudPqn1/yTk1g==
> X-WBNR-Posting-Host: 193.129.24.5
> From: =?Utf-8?B?UGhpbCBSb2RnZXJz?= <PhilR@ku.oc.2i.reverseme>
> Subject: VB upgrade crashes with Data Execution Prevention
> Date: Thu, 7 Jul 2005 02:05:02 -0700
> Lines: 12
> Message-ID: <ABF76282-2E48-45C2-A598-C0ADDD0D1F56@microsoft.com>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="Utf-8"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> Content-Class: urn:content-classes:message
> Importance: normal
> Priority: normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> Newsgroups: microsoft.public.dotnet.languages.vb.upgrade
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.languages.vb.upgrade:1124
> X-Tomcat-NG: microsoft.public.dotnet.languages.vb.upgrade
>
> I had a peculiar problem yesterday which I thought I'd post here in case
> anyone else runs into it. I'd successfully run the VB upgrade wizard a
while
> ago on quite a complex VB6 project, and I was trying to run it on another
> one. But whatever I ran it on, it reported a crash in vbu.exe, "The
exception
> unknown software exception (0xc00000fd) occurred in the application at
> location 0x7c9379cd". In fact 0xc00000fd is stack overflow. It turned out
> that this problem was caused by having Data Execution Prevention switched
on
> - my machine has hardware DEP support - and if I turned it off the
upgrade
> wizard ran OK. So it looks like there are some DEP issues in the upgrade
> wizard.
>
> Phil Rodgers
>