Are you using nView? If so you may have to disable it as it messes with window coordinates and can cause things to appear in the wrong place. Also are you in proper multiple monitor mode? I.e. do you get two monitors in the display properties settings tab and your taskbar should only be on one screen, not both. Stardock use multiple monitor systems with WindowBlinds without problems. Right now I am using a 6600GT with 2 screens using WB5 and there are no pr
Neil Banfield
This should be fixed in the release version of WB5.
I would guess that in your case the cpu is better at doing per pixel than your graphics card is.
This should be fixed in the next update to KeepSafe
jaidaksqhost: has it ever worked for you?
kmkkid: If you spoke to Nakor online then he will have told you that the problem with dragging windows is indeed with your card. The intel 845G chipset is over 3 years old now and chipsets are usually slower than the current generation low end graphics card when they come out. I also believe the 64MB you mention is taken from the system memory & therefore is not dedicated to the graphics. This means the graphics has rather limited memory bandwidth. I am fa
That troubleshooting text comes from an old WB build. Can you install the latest build & try again.
And this happened with the current build of WB on OD? Please send any info you have on the bug to [email protected]
If WB5 beta 2 says your drivers do not support per pixel borders then this is not going to be supported in the release version of WindowBlinds 5 either.
We have reproduced this and resolved it. WB was not using the masks for most images by mistake.
That appears to be a problem with the MSN skin you are using, not WindowBlinds. The systemwide background colour has changed for the WB skin and the MSN skin is using that rather than a hardcoded white.
This is normal. Apps like that will not work correctly with per pixel skins. As it happens, they are also unlikely to work on vista. You may find that if you click where the buttons would be, they may work though.
The ATI control centre should work with WB. It uses Stardock DirectSkin for the skin!
It is an ATI problem, not a Stardock problem. The drivers report the cards capabilities to apps and in this case the ATI drivers are saying the card cannot do hardware acceleration for that feature.
I think I might know why that is happening now. It might happen if you had already deleted the skin directory from the HD and so WBConfig is unable to switch into the directory when it deletes files.
It should be pointed out that StealthOS is a considerably more complex skin that luna is.
WindowBlinds 5 does not support Windows 2000.
Are you trying to install the app? Installation must be done under an admin account, but WB itself should not have any problems once installed.
godskin: What error do you get?
You should find this is resolved in WB 4.6 and later anyway.
Older versions of ThemeManager are not compatible with WindowBlinds 5.
Did you try rebooting when you had the error? WindowBlinds should have no impact on your banking website and if you have unloaded WB then its not doing anything to interfere with it. Uninstalling WB would have taken a reboot, so I wonder if thats all it wanted. I have also tried excluding internet explorer here with WB5 and it excludes it correctly.
This sounds like a driver problem. I would reboot & see if it continues. If it does then reinstall the drivers and see if that helps as sometimes the ATI drivers do not install correctly the first time.
Please install the latest WB build and see if that helps.
What does the troubleshooting page say?