Note that another issue with this board, this time on Windows Vista,
has been reported:
(The fix for this bug doesn't address . I will file a separate bug.)
Unfortunately updating to the lateset available drivers didn't
help. I suspect that the problem is with Present() calls
with regions - I have seen similar issues on other nvidia boards
in full-screen mode: if Present is called with non-NULL rectangles
sometimes the rendering gets screwed (we even have a workaround
for this for the full-screen mode). The submitter reports
that using -Dswing.bufferPerWindow=false helps, and the likely
reason is that in this case there are no partial updates.
The issue went away after the user updated the driver to version 184.108.40.20665.
So we're going to restrict the pipeline to this driver version.
The ouptut with the new version:
[I] Adapter Ordinal : 0
[I] Adapter Handle : 0x10001
[I] Description : NVIDIA Quadro NVS 110M
[I] GDI Name, Driver : \\.\DISPLAY1, nv4_disp.dll
[I] Vendor Id : 0x10de
[I] Device Id : 0x1d7
[I] SubSys Id : 0x1c21028
[I] Driver Version : 220.127.116.1165
[I] GUID : D7B71E3E-4297-11CF-B965C92100C2CB35