Customer is running their trading application on the following hardware:
- OS: Microsoft windows 2000, v5.00.2195, Service Pack 4.
- PC: Intel Pentium 4, CPU 3.20GHZ, 1 Giga of Ram.
- Display adapter: Matrox Millennium G450 DualHead DVI PCI.
* CPU type: Matrox G450
* CAN - DAC: Integrated, 360 MHZ
* Memory: 32 MB
* Bios Version: v1.3.005.
* Driver used:
# Name: Matrox G400/G450/G550 DualHead
# Provider: Matrox Graphics Inc.
# Driver Date: 14/09/2004
# Driver version: 5.93.9.0.
# Driver Signature: Microsoft windows hardware compatibility.
When using the above PC configuration, with dual monitor mode activated, any Java application
will experience repaint/screen refresh problems. The most obvious symptoms are mouse pointer
trails being left behind and a failure to paint JTables correctly.
The problem is easier to reproduce if your test application has at least one JTable with 15
columns and 100 lines. The problem is easily reproducible using jEdit as the test application.
The problem has been seen under JDK 1.3.1_02 and 1.3.1_10. It does not appear on the same
hardware configuration using JDK 1.4.2_05.
###@###.### 2005-1-26 17:42:18 GMT
- OS: Microsoft windows 2000, v5.00.2195, Service Pack 4.
- PC: Intel Pentium 4, CPU 3.20GHZ, 1 Giga of Ram.
- Display adapter: Matrox Millennium G450 DualHead DVI PCI.
* CPU type: Matrox G450
* CAN - DAC: Integrated, 360 MHZ
* Memory: 32 MB
* Bios Version: v1.3.005.
* Driver used:
# Name: Matrox G400/G450/G550 DualHead
# Provider: Matrox Graphics Inc.
# Driver Date: 14/09/2004
# Driver version: 5.93.9.0.
# Driver Signature: Microsoft windows hardware compatibility.
When using the above PC configuration, with dual monitor mode activated, any Java application
will experience repaint/screen refresh problems. The most obvious symptoms are mouse pointer
trails being left behind and a failure to paint JTables correctly.
The problem is easier to reproduce if your test application has at least one JTable with 15
columns and 100 lines. The problem is easily reproducible using jEdit as the test application.
The problem has been seen under JDK 1.3.1_02 and 1.3.1_10. It does not appear on the same
hardware configuration using JDK 1.4.2_05.
###@###.### 2005-1-26 17:42:18 GMT