Unresolved symbols in MSVCRT.DLL when running a py2exe packaged program.

[Parzival Herzog]

Thank you for your kind replies. I have not yet found what the actual problem
is, my app will indeed run quite nicely on several different machines, with
several different MSVCRT.DLL's, and even on this offending machine, provided
that I do not use py2exe. I can't figure out what is different about this machine,
being essentially a brand new machine churned out by a disinterested
corporate IT support group, and foisted on users loaded with antivirus
and corporate policy software, but otherwise untouched, and unconfigured.

Thanks to the responders, I now know that there is
a difference in DLL policy between Win2k and Win NT. Anyways I'm not that
interested in replacing MSVCRT.DLL in the system directory of my client's machines,
that's just what we tried to do in order to find the cause of the problem.
I just want my packaged Python app to work on any machine it is distributed to
without trouble. Has no one experienced this sort of problem for themselves?
Has anyone resolved it? How?

- Parzival


"Tom" <NoSpam at NoSpam.com> wrote in message news:hVBn6.7888$UZ4.3012833 at news4.rdc1.on.home.com...
> One difference (between the Win2K & WinNT machines) is the new system file
> protection 'feature' in Win2K.  It is supposed to disallow inappropriate
> updates to system DLL's (of which MSVCRT.DLL is one).  Another aspect of
> this feature is that apps can load their own versions of system DLL's, so
> multiple different versions MSVCRT.DLL can be memroy resident at the same
> time (but not on NT, just 2K).
>
> Someone suggested deleting the DLL to see if it is in use.  I'm not sure
> about DLL's, but with drivers (.SYS) you can delete it even while it is in
> use (wierd).  There are utilities around that will tell you what DLL's your
> app has loaded.  Maybe even the sysinfo utility, included in Win2K, might
> tell you this?
>