> Problems like this can be solved with dependencywalker
> (google for it). The walker displays binary dependencies for images.
Thankfully dependency issues like this seem to be rare....
> Using it I found this: win32net.pyd from build 204 does *not*
> use the LsaLookupNames2 function in advapi32.dll. However,
> win32net.pyd links to netapi32.dll (among others), and
> netapi32.dll links to advapi32.dll, using the name
> LsaLookupNames2. This was on WinXP.
>
> On win2k, netapi32.dll will not link to advapi32's
> LsaLookupNames2 - otherwise it would not work.
>
> So, your exe *should* be able to run on win2k - except if you
> distribute XP's netapi32.dll with your exe (I've checked this
> with a trivial py2exe'd script).
I just checked... And guess what... Py2exe is bundling netapi32.dll...
I am working on a new beta, so I'll test to see if it will work
on XP without netapi32.dll being bundled... If so, then we should be
kosher...
Good catch... I'll have to grab dependencywalker
to get some practice...
> py2exe isn't very good at determining which dlls belong to
> the operating system, and so must not be distributed -
> netapi32.dll is such a beast. You should remove netapi32.dll
> from the dist directory, and it should work on win2k.
That's what I suspect....
> And sorry for the false alarm on the threads you mention above ;-)
It's okay.... I just miss McMillian's installer...
It's unsupported, so I've moved to py2exe... But
McMillian's package seemed to be better with
the dependency issues.... And offered a few
features that don't exist in py2exe... (Or at least
are not easily handled in py2exe...)
On the plus side, py2exe has handled packages lately
that I just could not get McMillian's installer
to work reliably with... Which is why I switched...
Oh well... Progress...
- Benjamin
_______________________________________________
Python-win32 mailing list
Python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
