[Pkg-exppsy-pynifti] Unable to run nifti on Windows XP (missing msvcr80.dll)

Vadim Axel axel.vadim at gmail.com
Wed Apr 8 21:12:24 UTC 2009


Hi Michael,

I solved the problem, which is indeed MS DLL hell. By exploring the stuff
with Process Explorer (of former Sysinternals), I found out that zlib1.dll
is loaded not from the location, where I just installed it, but from
Matlab2008A location. And this matlab's zlib1.dll was built with MSVC 2005
(which loads msvcr80.dll runtime). Nifti module, from its side, expects MSVC
2003 runtime. This is all the story. What I did I just copied zlib1.dll
directly in nifti directory in order that it will be always loaded first.
Another solution is to make the PATH of nifti zlib library before the matlab
path, but I would prefer not to do this since who knows what will happen to
matlab....

With regard to running simultaneously different runtimes this indeed may
happen. Before I reached the solution, I first built the whole python with
MSVC 2005 and there I observed that both MSVC71.dll and MSVC80.dll are
loaded simultaneously. I think that this is something pretty unhealthy,
though  occasionally it may work.

Thanks for help,
Vadim

On Wed, Apr 8, 2009 at 7:44 AM, Michael Hanke <michael.hanke at gmail.com>wrote:

> Hi,
>
> On Wed, Apr 08, 2009 at 12:23:57AM +0200, Vadim Axel wrote:
> > Hi,
> > I installed pynifti (pynifti-0.20090303.1.win32-py2.5.exe) for the first
> > time (Windows XP OS, python 2.5.4).
> > After calling import nifty I got the message about missing missing
> > msvcr80.dll (which is C++ runtime library for MSVC 2005).
> > I have MSVC 2005 installed on this computer, so I just copied the DLLs
> from
> > C:\Program Files\Microsoft Visual Studio
> 8\VC\redist\x86\Microsoft.VC80.CRT
> > to python root folder . However now  I am getting another annoying
> message
> > about an error while loading C runtime library. An interesting thing that
> I
>
> What error is that?
>
> > discovered that msvcr71.dll already loaded in my python process. Can two
> > runtimes coexist? Shouldn't it be compiled with the same C++ runtime
> version
> > as the python?
>
> Well, there are so many Python distributions compiled with whatever.
> Typically, they are built with MS VC.... and I neither have a license
> for it nor would I personally make use of it. I am building the windows
> binaries with the same compiler that is used for all other operating
> systems -- GCC.
>
>
> > I tried different installations of pynifti, but the error
> > persisted. I had no problem at with installing pyMVPA and all its
> > prerequisites.
> > Any ideas?
>
> Not really. I know that DLL handling on Windows is quite a pain, but I
> have no experience with conflicting libs. I know that some people even
> have VC6 around and I cannot possibly support all combinations of
> Python+Compiler.
>
> I think the best way would be to tune up Makefile.win to provide you
> with an easy possibility to build the installer yourself. Currently I do
> this with mingw, but VC2005 should be capable of it as well -- did you
> try?
>
>
> http://niftilib.sourceforge.net/pynifti/installation.html#compile-from-source
>
> and especially
>
>
> http://niftilib.sourceforge.net/pynifti/installation.html#building-on-windows-systems
>
> I'd be happy to update the documentation with a dedicated section on MS
> VC in case you report problems.
>
> Michael
>
> --
> GPG key:  1024D/3144BE0F Michael Hanke
> http://apsy.gse.uni-magdeburg.de/hanke
> ICQ: 48230050
>
> _______________________________________________
> Pkg-exppsy-pynifti mailing list
> Pkg-exppsy-pynifti at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-pynifti
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-exppsy-pynifti/attachments/20090408/b90180b5/attachment.htm>


More information about the Pkg-exppsy-pynifti mailing list