godskin: Are you using beta2 by any chance?
Neil Banfield
If WB is removed and your PC still hangs then WB isn't the problem. See if you have a file called SDMCP on your HD and rename it, any better? geekboy2000: the mentions of hanging apps & ghost windows is nothing to do with WB making apps hang. Its how WB handles windows which have hung.
What do you see in WB & WBSrv keys?
Open RegEdit. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify Right click on Notify and select permissions. What does it show? Also what sub keys do you have under Notify? I.e. wlballon etc.
Even with the very latest RC on SDC?
When they get corrupted, does the corruption apply to all those parts at once? And on all apps at once?
This sounds like the overlay colour is not being set correctly by the app.
The answer is in your troubleshooting information. The current WindowFX build is not compatible with WindowBlinds 5. In this case its the window open animations that are the problem.
Please post the dates, times & sizes of wblind.dll, wbconfig.exe and wbsrv.dll
You may have to reinstall WB after removing panda.
I just tried this out with the latest WB and I do not see the problem. I used ALT-F7 to search and then dismissed it with escape and if I use the arrow keys you can see the focus moving up & down the directory listing. Is there something else I should be trying?
If WB says it is not supported then thats what the drivers are reporting to WB.
Did this happen with the earlier WB5 betas?
Hatu: If you have a current OD subscription when WB is released then WindowBlinds 5 will be free for you.
We made some changes to how oversized startbuttons work which mean the shadow from the startmenu overlaps the start button slightly. This can be avoided by disabling the shadow on the startmenu in the skin & adding one via WBs per pixel support. The startmenu should never overlap the startbutton though.
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
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.