[Insight-users] Linking SimpleITK.dll on 64-bit Windows XP

[Ben Horstman]

Hello all,

I have been using the SimpleITK Java bindings to do ansiotropic diffusion.  I have gotten things to work on Windows 7 64-bit and Mac OS 10.8 64-bit by using the binaries from the sourceforge page.  I was also able to compile the linux binaries and run things under Ubuntu 64-bit.

Here is the page I used for the binaries and java files:
http://sourceforge.net/projects/simpleitk/files/SimpleITK/0.5.1/Java/

However, I cannot get the 64-bit Windows binaries to work under Windows XP 64-bit.  Is there anything I can do to work around it?  Is 64-bit XP even supported?

Here is the exception I get:

CB16-01 Nov-16-2012 10:50:41.843 ERROR Denoise__Ansiotropic_Diffusion_ failed to link simpleITK manually...
  -- Exception : java.lang.UnsatisfiedLinkError
C:\Documents and Settings\MIM\Local Settings\Temp\mim3368\extTemp1353081039750\lib\SimpleITKJava.dll: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem
  at java.lang.ClassLoader$NativeLibrary.load(Native Method)
  at java.lang.ClassLoader.loadLibrary0(Unknown Source)
  at java.lang.ClassLoader.loadLibrary(Unknown Source)
  at java.lang.Runtime.load0(Unknown Source)
  at java.lang.System.load(Unknown Source)
  at sample.control.Launcher.runOnSession(Launcher.java:51)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at com.mimvista.extensions.d.run(d.java:7)
  at java.lang.Thread.run(Unknown Source)
  at com.mimvista.extensions.j.run(j.java:2) 

The call I am trying to do is basically "System.load(path)", where path is the absolute path to the SimpleITKJava dll.  Loading it explicitly like this doesn't change anything; the error I get from the Java JNI wrapper trying to link the library is the same.  I'm reasonably certain it is finding the file, since the error changes if I make the path wrong.  So my guess is that the .dll is incompatible somehow...

Thanks for reading,
~benjamin

************************
Benjamin Philip Horstman
Software Lead - Rho Team
MIM Software Inc.