United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4452207 : DisplayModeTest broken on WindowsNT running Full Screen Exclusive mode

Details
Type:
Bug
Submit Date:
2001-04-30
Status:
Closed
Updated Date:
2001-08-29
Project Name:
JDK
Resolved Date:
2001-08-27
Component:
client-libs
OS:
windows_nt
Sub-Component:
java.awt
CPU:
x86
Priority:
P2
Resolution:
Won't Fix
Affected Versions:
1.4.0
Fixed Versions:

Related Reports

Sub Tasks

Description
DisplayModeTest as in Full Screen Tutorial gives " Sync out of range " on the monitor on Windows NT build 1381 Service Pack 5 on trying to set certain display modes (usualy ones which are a combination of high resolution and high refresh rates .) To reproduce the bug :

1. You need a Dell Optiplex GX110 (Or maybe a system of the similar configuration ) The cofiguration of the system I tested is Attached . It should be running Windows NT 4.00 build 1381 With Service Pack 5 .

2. Run DisplayModeTest on JdK Merlin Beta Build 61.

3. Select the displaymodes that are errant (They can be found on the error.txt file as attached . )

Comments
WORK AROUND

No Workarounds
2004-06-11 
EVALUATION

I'll commit this to beta2 right now.  Mike can decide how serious an issue 
it is when he gets back.  
eric.hawkes@eng 2001-05-01

We've tried to reproduce this problem on another machine with a similar low-end Intel graphics card / motherboard, but without any luck.  The bug seems to be very specific to Dell's Optiplex.  Even worse, Manish has confirmed that this problem only happens with DisplayMode test and not MultiBufferDuke.  I've sent him a variant MultiBufferDuke which I'm hoping will reproduce the problem.  If not, we might have to simply document this and decommit from merlin until we can get a Dell Optiplex to debug.
michael.martak@Eng 2001-07-30

The variant MultiBufferDuke did indeed cause the problem, which mostly narrows it down to any application that changes the display mode using DirectX more than once on this hardware.  I would like to test this with a native application, but there are not enough resources at the moment.
Since this is obviously a problem with the driver on this particular harware, I am going to have the release notes amended with the information, and close this out as "will not fix".
###@###.### 2001-08-27
2001-08-27


Hardware and Software, Engineered to Work Together