py2exe

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 <cool-rr@...> 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.
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Py2exe-users mailing list
> Py2exe-users@...
> https://lists.sourceforge.net/lists/listinfo/py2exe-users
>
>

On Wed, May 12, 2010 at 3:31 AM, David Escobar
<davidescobar1976@...:

> 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 <cool-rr@...> 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.

On 12/05/2010 12:51 PM, cool-RR wrote:
> On Wed, May 12, 2010 at 3:31 AM, David Escobar
> <davidescobar1976@... <mailto:davidescobar1976@...>> 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", ... ]

...

> Thanks for the advice David. I tried it now but it didn't help.

Check powrprof.dll isn't already in the py2exe dist directory - adding 
that setup option will stop it being copied in future runs, but will not 
delete existing ones.

If that doesn't work, then carefully check the dist directory for any 
other DLLs you don't recognize and aren't part of your app - eg, if 
somehow you ended up with comctl32.dll in that dir you would wind up 
with a similar crash.

Mark

On Wed, May 12, 2010 at 5:01 AM, Mark Hammond <skippy.hammond@...:

> On 12/05/2010 12:51 PM, cool-RR wrote:
>
>> On Wed, May 12, 2010 at 3:31 AM, David Escobar
>> <davidescobar1976@... <mailto:davidescobar1976@...>> 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", ... ]
>>
>
> ...
>
>
>  Thanks for the advice David. I tried it now but it didn't help.
>>
>
> Check powrprof.dll isn't already in the py2exe dist directory - adding that
> setup option will stop it being copied in future runs, but will not delete
> existing ones.
>
> If that doesn't work, then carefully check the dist directory for any other
> DLLs you don't recognize and aren't part of your app - eg, if somehow you
> ended up with comctl32.dll in that dir you would wind up with a similar
> crash.
>
> Mark
>

I already confirmed powrprof isn't there.

To your second suggestion: I am not intimately familiar with which DLLs are
normal to be included and which not. How could I tell between them?

Ram.

Ram,

On 12/05/2010 14:06, cool-RR wrote:
> On Wed, May 12, 2010 at 5:01 AM, Mark Hammond <skippy.hammond@...
> <mailto:skippy.hammond@...>> wrote:

...
>
> To your second suggestion: I am not intimately familiar with which DLLs
> are normal to be included and which not. How could I tell between them?
A basic wxPython based script will need:

- all wx*.dll's
- pythonxx.dll
- the msvcXnn.dll's with Py 2.5 this is msvcX71.dll's, with Py 2.6 it is 
msvcX90.dll's.
- you might also need gdiplus.dll, I just include it as it sometimes 
gives errors which don't easily lead you to know that this is missing.

See here http://wiki.wxpython.org/py2exe for additional info regarding 
wxPython and py2exe.

Werner

Werner F. Bruhin <werner.bruhin <at> free.fr> writes:

> A basic wxPython based script will need:
> 
> - all wx*.dll's
> - pythonxx.dll
> - the msvcXnn.dll's with Py 2.5 this is msvcX71.dll's, with Py 2.6 it is 
> msvcX90.dll's.
> - you might also need gdiplus.dll, I just include it as it sometimes 
> gives errors which don't easily lead you to know that this is missing.
> 
> See here http://wiki.wxpython.org/py2exe for additional info regarding 
> wxPython and py2exe.
> 
> Werner

Success!

The offending dll was UxTheme.dll. I put it in `dll_excludes` and now my app 
works on Win 7 when packaged from XP.

Thanks everyone!