Created attachment 538 [details] Dubug log Trying to run a simple test case and get: Exception in thread "main" java.lang.UnsatisfiedLinkError: jogamp.newt.driver.windows.ScreenDriver.getAdapterName0(I)Ljava/lang/String; at jogamp.newt.driver.windows.ScreenDriver.getAdapterName0(Native Method) I'm on: Macbook Pro Retina 15-inch Early 2013 Windows 7 x64 jvm 64-bit on Parallels or Bootcamp
Created attachment 539 [details] Test case
Cannot reproduce here on native Window7 (no virtualization) and Java7 and latest JOGL.
(In reply to comment #2) > Cannot reproduce here on native Window7 (no virtualization) > and Java7 and latest JOGL. Yes, all 64bit.
Please test w/ vanilla 2.1.2 or git tip of master .. and ensure you are only using these jar files and native libraries! (Ensure that your lib-path (PATH, property, ext folder) does not contain the newt dll ..) Looks like somewhat you are mixing native libraries, i.e. using an old version or something - weird. Your issue should be also visible w/ a plain unit test of ours, i.e. NEWT GearsES2. The exception is caused due to not finding the desired native method within the native library newt.dll - OR - the newt.dll is linked against something non existing, i.e. unresolved symbol / missing library. Hence, do our NEWT Applets work ? (Website, 2.1.2)
http://forum.jogamp.org/Can-t-use-NEWT-on-Vista-tp4030559.html +++ since jogl 2.1.1-rc-20131018 newt.dll imports functions from user32.dll, which are not implemented in vista's user32.dll. CloseTouchInputHandle GetTouchInputInfo RegisterTouchWindow any solutions/workarounds for this problem? +++ Could be related ..
(In reply to comment #5) > http://forum.jogamp.org/Can-t-use-NEWT-on-Vista-tp4030559.html > > +++ > > since jogl 2.1.1-rc-20131018 newt.dll imports functions from user32.dll, > which are not implemented in vista's user32.dll. > > CloseTouchInputHandle > GetTouchInputInfo > RegisterTouchWindow > > any solutions/workarounds for this problem? > > +++ > > Could be related .. See Bug 901 .. but since you use Windows 7 .. I doubt that.
Was a matter of loading the proper native libraries