Bug 604

Summary:	Archive style applet embedding triggers "pixel format 17" error
Product:	[JogAmp] Jogl	Reporter:	Karel Knoest <karelknoest>
Component:	applet	Assignee:	Sven Gothel <sgothel>
Status:	RESOLVED WORKSFORME
Severity:	critical
Priority:	---
Version:	2
Hardware:	pc_x86_32
OS:	windows
Type:	---	SCM Refs:
Workaround:	---
Attachments:	Jogl debug log

Description Karel Knoest 2012-07-06 09:14:46 CEST

Created attachment 361 [details]
Jogl debug log

To embed the applet, we tested the "archive" tag and jnlp method as suggested in the section "Normal-Applet using native-JAR lib loading" and further, http://jogamp.org/wiki/index.php/Using_JOGL_in_a_Java_applet.

Tese methods are simple and elegant and works on almost all machines. Unfortunately, two windows xp machines (ATI Xpress 200 and 600 video cards) don't play along (neither with java 6 nor 7, IE8, Chrome 20, FF 13) and give the below exception. Both xp machines do work when the JNLP launcher is addded to the mix, but then only with Java 7 (Java 6 still gives the pixel exception). I've attached the entire jogl debug log as well.


------------------------------

Exception in thread "AWT-EventQueue-2" javax.media.opengl.GLException: Unable to set pixel format 17 for device context 0xa5010ad3: error code 0
        at jogamp.opengl.windows.wgl.WindowsWGLGraphicsConfigurationFactory.updateGraphicsConfiguration(WindowsWGLGraphicsConfigurationFactory.java:205)
        at jogamp.opengl.windows.wgl.WindowsWGLGraphicsConfiguration.updateGraphicsConfiguration(WindowsWGLGraphicsConfiguration.java:136)
        at jogamp.opengl.windows.wgl.WindowsWGLDrawable.setRealizedImpl(WindowsWGLDrawable.java:70)
        at jogamp.opengl.GLDrawableImpl.setRealized(GLDrawableImpl.java:163)
        at javax.media.opengl.awt.GLCanvas$2.run(GLCanvas.java:571)
        at jogamp.common.awt.AWTEDTExecutor.invoke(AWTEDTExecutor.java:49)
        at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:557)
        at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:399)
        at javax.media.opengl.awt.GLCanvas.paint(GLCanvas.java:482)
        at sun.awt.RepaintArea.paintComponent(Unknown Source)
        at sun.awt.RepaintArea.paint(Unknown Source)
        at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source)
        at java.awt.Component.dispatchEventImpl(Unknown Source)
        at java.awt.Component.dispatchEvent(Unknown Source)
        at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
        at java.awt.EventQueue.access$000(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.awt.EventQueue$3.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
        at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.awt.EventQueue$4.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
        at java.awt.EventQueue.dispatchEvent(Unknown Source)
        at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
        at java.awt.EventDispatchThread.run(Unknown Source)

Comment 1 Karel Knoest 2012-07-06 09:46:44 CEST

Updating the drivers of both video cards (ATI Xpress 200 and Xpress 600 Mobile)to the latest versions (10.2) solved the problem. 

The "problem" with this fix is that Windows XP doesn't recognize these drivers as valid versions. They need to be manually selected and installed while ignoring warnings by Windows.

Comment 2 Sven Gothel 2012-07-06 20:27:22 CEST

1st of all thank you for the report.

So it looks like the driver bug (as it seems) is solved, great.

Due to the bug ownership and the fact that WinXP is EOL
allow me to close this issue.

Honestly we have a few unresolved WinXP 'issues',
however we are not able to reproduce them here w/ our machines available
and the reporting person was not able to allow us access to the machines
so we can create a fix.

Only if you are able to give us access to the machine 
and think it's worth the effort (hours of debugging for this EOL product)
we may consider going deep into this .. then pls reopen this bug.

Thank you.