UMS Won't Start; incompatible JNA native library
Forum rules
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Please make sure you follow the Problem Reporting Guidelines before posting if you want a reply
Re: UMS Won't Start; incompatible JNA native library
As far as I am aware UMS works on windows Vista onwards, there was a recent bugfix to get to work with Vista.
Java stopped supporting winXP in 2014 so that is why you can't install anything later than that version, which would be too old for UMS to use.
I don't know if there are any work arounds besides upgrading your windows, but that might not be the best option given the age of your system.
Maybe an older version of UMS might work that isn't dependent on a newer version of Java?
Java stopped supporting winXP in 2014 so that is why you can't install anything later than that version, which would be too old for UMS to use.
I don't know if there are any work arounds besides upgrading your windows, but that might not be the best option given the age of your system.
Maybe an older version of UMS might work that isn't dependent on a newer version of Java?
Logs are important for us to help, Please follow This Link before asking for support. Just a forum cleaner, Will help if I can but no expert.
Re: UMS Won't Start; incompatible JNA native library
DMS still works on XP, so that isn't entirely true. Although you are shown a "warning" when installing Java that things "might not work", they actually do. I've found nothing that actually doesn't work with Java 8 on Windows XP.
So, the things that break it do so because of decisions made in UMS. First of all, all native executables must support it (FFmpeg etc, they are often compiled with more a more recent compiler, which doesn't see to that the output file will run on XP). In addition, JNA is an issue. JNA stopped caring about XP support quite some time ago, so unless you stay with an older JNA version, loading of for example MediaInfo will fail.
So, the things that break it do so because of decisions made in UMS. First of all, all native executables must support it (FFmpeg etc, they are often compiled with more a more recent compiler, which doesn't see to that the output file will run on XP). In addition, JNA is an issue. JNA stopped caring about XP support quite some time ago, so unless you stay with an older JNA version, loading of for example MediaInfo will fail.
Re: UMS Won't Start; incompatible JNA native library
From version 9 onward I think all versions are "standalone" - that is, with embedded Java. That won't help you a bit though, because all that means is that Java 8 is bundled with the package. There's no guarantee that this version will work on XP, so a "non-standalone" version would be desirable for a XP system - where you find a Java version that actually works and installs that locally.
I don't know if this goes for all the latest Java 8 versions, but I know that if you download a somewhat older version of Java 8 at least, it will work just fine on XP if you just ignore the warning during installation.
But, the JNA problem is independent from the Java issue. The JNA issue is absolute, the problem is that the DLL that goes with JNA isn't compiled with support for Windows XP. This goes for all versions of JNA compiled on Visual Studio 2015 or later if my memory serves me correctly. At some version JNA upped their "platform" to VS2015, and at this point the DLL is no longer working on XP because it uses API calls that doesn't exist on XP.
I find it quite ridiculous that they did this, because there are no new functions in JNA (at least it weren't at the time) that required this. I had quite lengthy discussions with the JNA team about this at the time, but I came nowhere. My conclusion is that they simply didn't care if they broke XP support, their convenience of using VS2015 (which I assume was the version they had installed for other uses as well) was what was important. Microsoft is ultimately to blame, because they were the ones that (silently) made sure that everything compiled with VS2015 didn't work on XP, while compiling the same program on VS2012 would. Microsoft's motivation for doing this isn't very hard to see through, as they had huge problems with a significant part of their users continuing to use XP. After a "sabotage" campaign where they made sure that pretty much everything stopped working on XP, including making deals with other companies issuing "warnings" like the one you see when you try to install Java, the marked share for XP has dropped significantly.
This is how they treat their paying customers, despite that some may be using hardware that is only supported on XP. It's good to keep in mind if one considers to buy something else from Microsoft in the future..
I don't know if this goes for all the latest Java 8 versions, but I know that if you download a somewhat older version of Java 8 at least, it will work just fine on XP if you just ignore the warning during installation.
But, the JNA problem is independent from the Java issue. The JNA issue is absolute, the problem is that the DLL that goes with JNA isn't compiled with support for Windows XP. This goes for all versions of JNA compiled on Visual Studio 2015 or later if my memory serves me correctly. At some version JNA upped their "platform" to VS2015, and at this point the DLL is no longer working on XP because it uses API calls that doesn't exist on XP.
I find it quite ridiculous that they did this, because there are no new functions in JNA (at least it weren't at the time) that required this. I had quite lengthy discussions with the JNA team about this at the time, but I came nowhere. My conclusion is that they simply didn't care if they broke XP support, their convenience of using VS2015 (which I assume was the version they had installed for other uses as well) was what was important. Microsoft is ultimately to blame, because they were the ones that (silently) made sure that everything compiled with VS2015 didn't work on XP, while compiling the same program on VS2012 would. Microsoft's motivation for doing this isn't very hard to see through, as they had huge problems with a significant part of their users continuing to use XP. After a "sabotage" campaign where they made sure that pretty much everything stopped working on XP, including making deals with other companies issuing "warnings" like the one you see when you try to install Java, the marked share for XP has dropped significantly.
This is how they treat their paying customers, despite that some may be using hardware that is only supported on XP. It's good to keep in mind if one considers to buy something else from Microsoft in the future..
Re: UMS Won't Start; incompatible JNA native library
Win10 is the stuff of the devil IMO, I'm still using Win7 on most of my computers. That said, if you don't care about all the surveillance, the push to use Microsoft's "store", the nagging about using an "online"/Microsoft account giving them access to everything you do or the terrible UI - I guess Win10 is just fine. Except for the things I mentioned, it's essentially identical to Win7.
My point here is that there's no real reason why UMS shouldn't work on XP, it's basically due to laziness of the JNA devs (and to some extent UMS devs, because I think the version of FFmpeg that is bundled doesn't work on XP either). There is nothing that is "better" by using a newer OS, you get nothing "new" or "more". If you want to upgrade for other reasons, that's obviously a way to make many such potential problems go away, since Microsoft's change to Visual Studio has penetrated most software these days so that almost nothing work on XP in newer versions.
I don't remember the exact version of JNA that was the last to support XP, but it was earlier than 5.1.0. I think the last version that worked was 4.2.2. For DMS I have compiled the JNA binary myself, without using Visual Studio, so that a newer version actually works on XP.
My point here is that there's no real reason why UMS shouldn't work on XP, it's basically due to laziness of the JNA devs (and to some extent UMS devs, because I think the version of FFmpeg that is bundled doesn't work on XP either). There is nothing that is "better" by using a newer OS, you get nothing "new" or "more". If you want to upgrade for other reasons, that's obviously a way to make many such potential problems go away, since Microsoft's change to Visual Studio has penetrated most software these days so that almost nothing work on XP in newer versions.
I don't remember the exact version of JNA that was the last to support XP, but it was earlier than 5.1.0. I think the last version that worked was 4.2.2. For DMS I have compiled the JNA binary myself, without using Visual Studio, so that a newer version actually works on XP.
Re: UMS Won't Start; incompatible JNA native library
You will have almost as many problems using 32-bit Windows 7 as using Windows XP in the time to come. 32-bit support is disappearing rapidly, so you should absolutely go for 64-bit if you consider upgrading for better general compatibility.