|
Replies:
5
-
Last Post:
May 10, 2008 3:01 PM
by: trembovetski
|
Threads:
[
Previous
|
Next
]
|
|
|
|
|
|
Update 10 on Vista - text in Control Panel unreadable
Posted:
Apr 17, 2008 4:42 AM
|
|
|
On Vista, with Update 10 beta, and later builds, I'm finding that the text in the Java Control Panel is unreadble on (the text is white and rendered incorrectly so that it can't be read at all). When Netbeans is installed on top of this version of Java, the text in the Netbeans installer/uninstaller has exactly the same issue.
|
|
|
|
|
|
|
Re: Update 10 on Vista - text in Control Panel unreadable
Posted:
Apr 18, 2008 2:15 AM
in response to: psynixis
|
|
|
I also came across the same problem.:(
|
|
|
|
|
|
|
|
Re: Update 10 on Vista - text in Control Panel unreadable
Posted:
Apr 18, 2008 10:56 AM
in response to: psynixis
|
|
|
DId you file a bug? http://bugs.sun.com
6595317 D3D: some character combinations show color fringing (LCD AA)
talks about text rendering in red.
6687166 D3D: text is missing when the pipeline is enabled [ATI Mobility X1400, Vista] 6613066 D3D: text is missing when the pipeline is enabled [ATI X1600]
talks about missing text but doesn't explicate on why it's missing. it talks about getting a newer driver
|
|
|
|
|
|
|
|
Re: Update 10 on Vista - text in Control Panel unreadable
Posted:
Apr 21, 2008 7:46 AM
in response to: psynixis
|
|
|
Seems fine here (Vista SP1, Update 10 build 22).
The Java entry on Control Panel | Programs ought to have some description of what it does instead of just the icon and the word "Java". E.g. Windows SideShow has "Set up a secondary display to use with Windows SideShow".
|
|
|
|
|
|
|
|
Re: Update 10 on Vista - text in Control Panel unreadable
Posted:
May 10, 2008 6:31 AM
in response to: psynixis
|
|
|
Just tried installing build 23. Everything is working for me now, so the problem appears to have been resolved.
|
|
|
|
|
|
|
|
Re: Update 10 on Vista - text in Control Panel unreadable
Posted:
May 10, 2008 3:01 PM
in response to: psynixis
|
|
|
What is your video board? Could you set this env. variable: J2D_TRACE_LEVEL=4 and run any java application from a command line prompt and post the output?
Even if the problem is resolved with the latest build, it would be useful to know the configuration in which it didn't work.
Thanks, Dmitri
|
|
|
|
|