Minimwatch unexpected exception

[Jota]

Hi,

I've noticed this the past couple of days. Minimwatch icon is greyed out and when I hover the mouse it says Minimwatch unexpected exception java.lang UnsatisfiedInkError.

I tried to add an attached log but it didn't work so I'll paste it here.

Quote:MinimWatch 0.8.3 update 40, Copyright © 2012-2016 Simon Nash. All rights reserved.
Java™ SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot™ 64-Bit Server VM (build 25.101-b13, mixed mode)
Platform default charset is windows-1252
System look and feel is com.sun.java.swing.plaf.windows.WindowsLookAndFeel
java.lang.UnsatisfiedLinkError: C:\Users\Jota\AppData\Roaming\MinimWatch\tmp\native\ohNet.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
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.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.jminim.lib.OhNetService.createLibrary(OhNetService.java:573)
at org.jminim.lib.OhNetService.createControlPointStack(OhNetService.java:517)
at org.jminim.lib.OhNetService.createDeviceListFactory(OhNetService.java:409)
at org.jminim.lib.OhNetService.access$2100(OhNetService.java:47)
at org.jminim.lib.OhNetService$Proxy.createDeviceListFactory(OhNetService.java:961)​
at org.jminim.lib.ObserverService.startOhNet(ObserverService.java:97)
at org.jminim.lib.ObserverService.access$300(ObserverService.java:42)
at org.jminim.lib.ObserverService$ObserverImpl.start(ObserverService.java:355)
at com.minimserver.watch.MinimWatch.doStart(MinimWatch.java:194)
at com.minimserver.watch.MinimWatch.start(MinimWatch.java:47)
at org.jminim.core.ContextImpl.startComponent(ContextImpl.java:167)
at org.jminim.core.ContextImpl.start(ContextImpl.java:92)
at org.jminim.core.RootContextImpl.startComponent(RootContextImpl.java:47)
at org.jminim.core.ContextImpl.start(ContextImpl.java:92)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:1417)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1100)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:118)
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 org.jminim.launch.Launcher.doLaunch(Launcher.java:621)
at org.jminim.launch.Launcher.launch(Launcher.java:204)
at com.minimserver.watch.launch.LaunchWatch.main(LaunchWatch.java:30)
Startup complete

Edit -
I had clicked the update option in Minimwatch and it never reported a new update but I checked on the forum and found a 0.8.4 and installed that and it seems to be working now.

[simoncn]

(21-09-2016 11:25)Jota Wrote:  Hi,

I've noticed this the past couple of days. Minimwatch icon is greyed out and when I hover the mouse it says Minimwatch unexpected exception java.lang UnsatisfiedInkError.

I tried to add an attached log but it didn't work so I'll paste it here.

Edit -
I had clicked the update option in Minimwatch and it never reported a new update but I checked on the forum and found a 0.8.4 and installed that and it seems to be working now.

In 0.8.4, there is a single Windows download that supports both 32-bit and 64-bit Windows. This change was made to solve this UnsatisfiedLinkError problem, which can occur after Java has updated itself.

MinimWatch 0.8.4 is a new version, not an update. New versions are only advertised by the 'Show updates' button when the installed version is no longer supported. I think the time has now come to drop support for 0.8.3 so that other users don't get confused by this.

[Tell]

Well... dropping the support has given me a nag page and I can't install 0.8.4 Miniwatch it keeps crashing out on jminim-0.6.217.jar, the source file is corrupted. Ideas ?.

OK I put myself of self care. I re-installed 0.8.3, that was OK. I redownloaded 0.8.4 which gives me a second generation of the file, installed it and all was fine. It's Windows 10 Anniversary. I don't know what was going on there.