Re: [Py2exe-users] Link checksum inconsistency

[Mark H. <ski...@gm...>]

On 26/02/2010 8:03 AM, Gib Bogle wrote:

> She compiled the program with py2exe on her Vista laptop, and the resulting
> executable (+ DLLs) runs on my Windows XP (SP2) machine, and on another XP
> machine, and on a Windows 7 machine.  It fails on two other XP (SP3) boxes.  On
> box 1 it simply fails to start, with a message about faulty configuration info.
>    On the other it starts, and all the Qt stuff works, but fails when the DLL is
> invoked, with a Windows write error message.

You need to tell us exactly what the message said.  I suspect the first 
error is simply that the side-by-side configuration isn't complete - ie, 
the MSVC assemblies (or other assemblies referenced by other modules) 
aren't installed.  I suspect the second error might relate to an 
incorrect DLL being shipped with py2exe.

> Following a suggestion from comp.lang.python, I have been looking at the program
> with Dependency Walker, with intriguing but confusing results.  Putting aside
> for the moment the Windows version issues, I want to understand why it is that
> DW determines that the Link Checksum and the Real Checksum are different for the
> executable.  As far as I've been able to discover, this means the executable has
> been changed since it was created.  Is there another explanation?

py2exe takes a "stub" executable and modifies it - it does not re-link 
anything.  IOW, it is normal that the checksum will be different and 
almost certainly is not related to your problem.

Cheers,

Mark