This is normal
Neil Banfield
If the drivers stop reporting it at higher resolutions then the drivers must have decided the card is either too slow to support it at those resolutions, or it has too little video ram, or its a bug. It might be worth your while trying newer & older drivers and possibly contacting Gigabyte for assistance.
This is a bug in the Sun Java Virtual Machine. It is not fully compatible with Windows XP or 2000. If there is a newer JVM download from Sun then try installing it. If not then if the Java app you use can run using the Microsoft JVM then that JVM is XP & 2000 compatible.
Did you set a PNG as your wallpaper? Those enable active desktop and the original wallpaper will still be 'under' it. The preview in wbconfig is not aware of active desktop wallpapers and neither is the taskbar transparency. I would strongly advise against using active desktop anyway due to its incompatibility with the icon shadows feature in XP. The window frame transparency is fully aware of everything thats under it and it even works over videos (when not i
Your Radeon 7200 series will not do the per pixel alpha that WB needs. ATI cards from the 9500 up will support it ok and should work with vista too. So any card from ATI which says it supports Pixel Shaders 2.0, 2.0b or 3.0.
The black boxes appears to be limited to nvidia cards. If you unload WindowBlinds and then open wbconfig, do you still get the black boxes?
Do you mean WindowBlinds 4 or WindowBlinds 5? I am unsure what you mean by lose DLL connections with programs. What sort of error messages are you getting?
Please contact [email protected] with your OD information.
Which skin are you using? Does this happen with non per pixel skins?
Please contact [email protected] who should be able to assist you with your activation issue.
Jonathan: The z order issues are a bug in the OS itself. We have a reproducable test case for this now and will be passing the information over to Microsoft in the hopes that they will fix it. We are currently looking into if the later versions of Windows (2003 server & XP 64 bit) suffer from this problem or not.
What app are you using to remote connect? WB should automatically disable per pixel support when over remote desktop.
Given that even wbconfig is corrupted, it points to a video driver / video hardware problem. The icons in wbconfig for example seem to be shifted out of place. Its certainly not WB at fault. Drop hardware acceleration on the display properties->Advanced->troubleshooting tab and reboot and I suspect all will be fine. What graphics card do you have?
Does this happen with all skins?
Are you sure you are using the latest build on OD? There was a bug in menubar painting which caused it to paint odd things in the menubar with some skins, but this should be fully resolved with the latest build on OD. On the card, the good news is the ATI card should handle WB better in terms of speed & I believe it should also be compatible with Windows Vista when it is released.
I should point out that the software is BETA. This means it might not work, it might crash, hang, it could even cause you to have to reinstall. Now its unlikely the reinstall issue would happen, but crashes etc are normal for Beta releases. I doubt your problem is anything to do with your VGA card or motherboard. Most likely explorer hung on skin apply and you just need to kill it using taskmanager & restart it. If it still happens then we would want to kno
The icon is coming back, not wbload.
Thats a bug in XP I am afraid. Its painting things out of order but you will notice the mouse clicks go to the menu correctly. If you reboot it will all be fine again. Logging in & out might fix it too.
Only skin titlebar means disable WBs non themeaware skinning code. As the macromedia apps are theme aware, their controls continue to skin in skin only titlebar mode.
We are looking into this
The problem is WB only knows what skin the current account is using, not what other accounts are using. Windows security prevents WB from finding out.
BoddhiC: The current version of the beta will not run on Windows Vista.
Just with 64 bit Windows. We will be adding support for 64 bit Windows later in the beta. A 64 bit processor running 32 bit Windows is compatible with the beta.
The 9600 is a much faster card than the GeForce 2, so yes it should run much better than on the Geforce 2.
Andy02369: A lot of the more advanced FPS games released in the past year would take advantage of pixel shaders which your card does not support. They may run in a less graphically advanced mode though depending on the game. I have a feeling DOOM3 for example would just not run at all as its OpenGL and the early ATI OpenGL drivers were not good. If you are interested in running WB5 per pixel frames, I would be on the lookout for a dirt cheap 9500 or higher card. They