Posted by
Gene on
Jan 20, 2012; 12:57am
URL: https://forum.jogamp.org/Cross-platform-DLL-selection-tp3667506p3674245.html
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.
However this one installation affects about 32,000 kids, so I'd really like to figure it out. It's a big school complex.
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.
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.
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.
>>> Added after initial post:
As early as Windows XP SP1 there was a policy option to load only signed DLLs, so this is moving up the ladder as a good possiblity for what is wrong. The reference is
http://technet.microsoft.com/en-us/library/bb457006.aspx.
>>> End addition.
I'll post more if I learn something that may be of use to others. Again thanks for your help.