FileBot 4.7.5 (r4619)
JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86/jnidispatch.dll) not found in resource path ([file:/D:/Portable%20Applications/Platform/PortableApps/FileBot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load x86 (32-bit) native library MediaInfo.dll: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: 9.20
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_111
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 2 Core / 247 MB Max Memory / 20 MB Used Memory
OS: Windows Vista (x86)
Package: PORTABLE
Data: D:\Portable Applications\Platform\PortableApps\FileBot
FileBot 4.7.5 (r4619)
JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86/jnidispatch.dll) not found in resource path ([file:/D:/Portable%20Applications/Platform/PortableApps/FileBot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load x86 (32-bit) native library MediaInfo.dll: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: net.sf.sevenzipjbinding.SevenZipNativeInitializationException: Failed to load 7z-JBinding: D:\Portable Applications\Platform\PortableApps\FileBot\Lib\7-Zip-JBinding.dll: Can't load AMD 64-bit .dll on a IA 32-bit platform
Chromaprint: java.io.IOException: Cannot run program "D:\Portable Applications\Platform\PortableApps\FileBot\Lib\fpcalc.exe": CreateProcess failed, error=216
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_111
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 2 Core / 247 MB Max Memory / 9 MB Used Memory
OS: Windows Vista (x86)
Package: PORTABLE
Data: D:\Portable Applications\Platform\PortableApps\FileBot
You're still using 32-bit Java. Use 64-bit Java instead.
FAQ wrote:Q: Why is MediaInfo not working? Why is 7zip not working? Why is JNA not working? If you are using 64-bit Java you must install 64-bit FileBot. If you are using 32-bit Java you must install 32-bit FileBot. If you have installed 64-bit Windows and 64-bit FileBot and 32-bit Java, the java process will be in 32-bit compatibility mode and the native libraries won't work. So uninstall 32-bit Java and then only install the latest 64-bit Java and latest 64-bit FileBot.
My OS (Vista) and Java are 32-bit.
I downloaded the 32-bit lib files and filebot-r4619.jar.xz - 2016-11-26 11:05:12.
Is the jar 64-bit or why do I need 64-bit Java? That was not the case so far.
If you have a 32-bit OS then you can't run any 64-bit native code and you won't be able to install or run 64-bit Java. Hence 32-bit OS + 32-bit Java + 32-bit native libraries is your only option. The jar is pure Java code which is platform-independent (i.e. not native code).
Your next post then indicates that you've downloaded the 64-bit native libraries which naturally won't work on your 32-bit system.
32-bit OS -> OK
32-bit Java -> OK
32-bit native libraries -> You have downloaded the 64-bit native libraries so it doesn't work. Download the 32-bit native libraries instead.
FileBot 4.7.5 (r4619)
JNA Native: java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/win32-x86/jnidispatch.dll) not found in resource path ([file:/D:/Portable%20Applications/Platform/PortableApps/FileBot/FileBot.jar])
MediaInfo: net.filebot.mediainfo.MediaInfoException: Unable to load x86 (32-bit) native library MediaInfo.dll: Could not initialize class com.sun.jna.Native
7-Zip-JBinding: 9.20
Chromaprint: 1.1.0
Extended Attributes: OK
Script Bundle: 2016-11-26 (r465)
Groovy: 2.4.7
JRE: Java(TM) SE Runtime Environment 1.8.0_111
JVM: 32-bit Java HotSpot(TM) Client VM
CPU/MEM: 2 Core / 247 MB Max Memory / 20 MB Used Memory
OS: Windows Vista (x86)
Package: PORTABLE
Data: D:\Portable Applications\Platform\PortableApps\FileBot
Please confirm that you actually have the right files in the right place. Screenshots and MD5 checksums the files in questions would help confirm if this is a FileBot issue or a user issue.
Sorry, but the problem remains!
It mast be related to the r4619 jar because that is all that was changed.
By the way! The versions r4612 and r4613 work fine. Maybe this helps.