Posted by
Sven Gothel on
Jan 20, 2012; 1:20am
URL: https://forum.jogamp.org/Cross-platform-DLL-selection-tp3667506p3674272.html
On Friday, January 20, 2012 01:57:39 AM Gene [via jogamp] wrote:
>
> Thanks Sven. Extremely helpful as usual. Great to know about the ability to
> turn off this feature.
>
> I was really worried this would turn into a big problem because we needed to
> release and there was no way to delay.
>
> But we've released and had about 1,000 downloads now and only 2 complaints.
> The other looks like a broken Java installation. This is without disabling
> the DLL caching behavior, so you're right it's defaulting correctly.
>
Sounds awesome and we appreciate your direct and 1st hand experience very much,
since we only see the complaints about something not working :)
> However this one installation affects about 32,000 kids, so I'd really like
> to figure it out. It's a big school complex.
Of course.
>
> My reasoning was it's looking for a 586 gluegen native and not finding it,
> so must have already looked for the DLL and couldn't see it.
Oh .. it's the other way around, ie. it tires to use the native JAR file.
This wasn't found on that machine (the stack traces and exception messages
- note: _Catched_). Then it will try to load the plain DLL files from the
usual location (java library path, or PATH, ..).
>
> So I verified by asking the user to check exact file size that the correct
> 32-bit glugen-rt.dll is installed with the main() jar just where it should
> be. I also took Launch4j out of the picture by having them run java -jar
> directly.
>
> I have asked them to install the jogl and gluegen native jars to see what
> happens.
very good. Again: testing the Applet or Webstart may also give some hints.
>
> My bet is that this is some very aggressive non-default DLL search policy or
> else an aggressive virus checker. Schools put these things in place so
> student's can't mess up their laboratory machines.
>
> Perhaps there's something about the DLL manifests or it could be that my
> installer doesn't have a code certificate so the virus checker thinks the
> DLLs are tainted. (I'm in process of getting a code certificate.) Since
> you guys deal with lots of installation issues, I thought maybe someone has
> heard of this kind of thing before.
I remember one post here (but not exactly ..) saying that some virus scanner
had a false positive w/ one of our files .. never experienced this personally though.
Of course, you can try to use on of our _signed_ JAR files (native + pure-java)
of our official RC5 release:
http://jogamp.org/deployment/v2.0-rc5/jar/ (all properly signed)
If they could run the Applet/WebStart (which uses these signed JARs) ..
that may also strengthen this direction / suspicion.
>
> I'll post more if I learn something that may be of use to others.
Yes, please do so! These experiences are very valuable.
> Again
> thanks for your help.
Thank you!
Cheers, Sven
>