Is there a reason why it only happens when I relaunch the msi after a
force reboot?
________________________________
From: James Finnigan [mailto:[EMAIL PROTECTED]
Sent: September 10, 2007 3:53 PM
To: Man, Shirley; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] What makes a custom action incompatible with
DataExecution Prevention on Vista?
Certain versions of ATL can do this.
http://www.google.com/search?q=ATL+NX+DEP&rls=com.microsoft:en-US&ie=UTF
-8&oe=UTF-8&startIndex=&startPage=1
http://en.wikipedia.org/wiki/Data_Execution_Prevention It's a general
issue though. Executing code on the stack, self-modifying code, etc.
can cause this.
But I think ATL that shipped with vc6 is the most common cause.
HTH,
James
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Man,
Shirley
Sent: Monday, September 10, 2007 3:39 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] What makes a custom action incompatible with Data
Execution Prevention on Vista?
Hi all,
When I restart an installation after a force reboot, in the "Validating
Install" phase, I get the error "Windows Installer has stopped working"
and a systray bubble saying the installer was closed due to Data
Execution Prevention.
I only get the error when I relaunch the msi after a failed installation
on Vista
What makes a custom action DEP incompatible?
Thanks,
Shirley
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
