Re: [Py2exe-users] Executable produced on XP fails on Win 7

[cool-RR <co...@co...>]

On Wed, May 12, 2010 at 3:31 AM, David Escobar
<dav...@gm...>wrote:

> This may or may not solve this particular problem, but one of the gotchas I
> ran into when making an .exe in Windows 7 was the POWRPROF.dll. I needed to
> add that dll to the "dll_excludes" list:
>
> "dll_excludes": [ ..., "POWRPROF.dll", ... ]
>
> Excluding that .dll has no effect on Windows XP builds, so you can use the
> same setup.py for both operating systems.
>
>
> On Tue, May 11, 2010 at 8:20 AM, cool-RR <co...@co...> wrote:
>
>> Hello,
>>
>> I'm developing a wxPython application. I've produced an executable of it
>> on an XP VM. It works well in there. But when I move it to a Win 7 VM, it
>> fails in a few separate points in the program.
>>
>> In one of these points, (Trying to load a simulation from file,) it just
>> exits the program with no message. In another point, (Creating a new
>> simulation,) it gives a Windows error dialog saying the program must be
>> closed, with these details:
>>
>> """
>> Problem signature:
>>   Problem Event Name: APPCRASH
>>   Application Name: GarlicSim.exe
>>   Application Version: 0.4.0.0
>>   Application Timestamp: 4918019c
>>   Fault Module Name: COMCTL32.dll
>>   Fault Module Version: 6.10.7600.16385
>>   Fault Module Timestamp: 4a5bd976
>>   Exception Code: c0000005
>>   Exception Offset: 00006a71
>>   OS Version: 6.1.7600.2.0.0.256.1
>>   Locale ID: 1033
>>   Additional Information 1: 0a9e
>>   Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
>>   Additional Information 3: 0a9e
>>   Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
>> """
>>
>> If you need any more details, let me know.
>>
>> Does anyone have a clue what to do here?
>>
>> (Please `cc` any replies to me personally.)
>>
>> Thanks,
>> Ram Rachum.
>>
>>
Thanks for the advice David. I tried it now but it didn't help.

Ram.