Once I connected (and disconnected) a digital-camera
(USB) LWJGL finds a lot new displaymodes, that my
physical display can never support. (finds 2048x1536)
Is this detectable by LWJGL or should I blame WinXP?
(the cam didn’t require any new drivers)
err - wow ;D
Think we need to filter out more devices than just DISPLAY_DEVICE_MIRRORING_DRIVER
286 modes before and after connecting my digital camera.
Think I need to create some debug builds and send to you. Please send an email to: info@lwjgl.org to get in touch.
After a reboot, the displaymodes were STILL there…
And guess what… they work :o :o :-/
dead slow - fillrate issue, dangerously high refreshrate
(85Hz) for that reso, my monitor should NOT be able to
handle that!
I tried the extreme resolutions, and my monitor
managed to show them without any corrupt colors…
I feel like I they can damage my monitor, but as my
hardware can manage it, from the POV of LWJGL the
display-modes are valid. (?)
Something got seriously screwed on my machine, I
don’t think this problem should be debugged by LWJGL.
Any semi-recent monitor should* be able to protect itself against wrong/harmfull display modes.
*Emphasis on ‘should’. I am not responsible for any damage to your monitor, your self esteem or your cat. 
[quote]I feel like I they can damage my monitor, but as my
hardware can manage it, from the POV of LWJGL the
display-modes are valid. (?)
[/quote]
In the past we used to use invalid display modes, but now we test them (at least in windows) using a windows api call before adding them to the list of valid modes.
I think the issue is that the camera has somehow installed a display and lwjgl is picking it up. The problem is, how do we filter it out - how can we detect it ?
Can you confirm that there is another display in Display Preferences -> Settings: display dropdown ?
No additional Display, but I can ‘set’ the insane
resolutions from the “Display Properties” -> “Settings”
so WinXP thinks they are valid too. LWJGL can’t do
anything about that I think.
For now i just remove all diplaymodes over 1600x1200
from the list. That’d be enough not to blow my monitor
into pieces 
Seeing as the drivers are determined to blow up your machine, I propose we add a system property, org.lwjgl.opengl.Display.safetyCatchOff, which will automatically remove any hi-spec modes like anything over 85Hz or 1600x1200. As time goes by and we solve the problem or it goes away we can remove the safety catch. Even then it can always be set to true to allow all modes through.
Cas
Physical displays are increasing in capabilities
by the day. My new Acer laptop with a ATI X700
mobile chip drives a 1680x1050 LCD. There
should be a more future-proof solution…
and my dual-screen configuration is far above that … :-/