Let others be forewarned:
My customer was complaining that they always got the Microsoft GDI (software-only) OpenGL driver when running my Jogl application.
After much investigation, I've found that in some circumstances, the Java heap conflicts with where the Intel OpenGL Device Driver for the various Intel chipsets (eg 82865G) wants to load (either to put itself, or to store its internal stuff).
By removing the -Xmx argument (or lowering the specified max heap size) they get the Intel driver to load and run.
My application is a stand-alone application (neither an applet nor a WebStart app), using Jogl 1.1.0-rc3, jdk1.4.2 or 1.5.0.
I believe this is related to the issue previously mentioned as only an applet/IE issue:http://www.java-gaming.org/forums/index.php?topic=16324
My theory is that since the Intel chips store all their info in memory, they may have particular address spaces they want to use (or some particular alignment), and just bail out if they cant get it.
Has anyone else run into this issue?
Is this something that Java could avoid some day?
Attached find the trivial Jogl app I used to test this. Note that this app is also a generic "print out basic system info
and Jogl / OpenGL capabilities" application, useful for debugging client installs.