I have never seen that before.
Neil Banfield
Well this is not a fix, this is a query for information so we can work out what the problem is.
If your LCD turns off then the problem is somewhere in the drivers. Does every app freeze at once or ?
Please let us know if it happens again for you.
ExodusCrow: Thats a bug in explorer. Anything using per pixel transparency will vanish when the MS shutdown screen is open. This includes winamp, your taskbar if you have made it transparent, titlebar borders etc etc. Explorer grabs the contents of the screen, but it does not pass in the flag for include per pixel information.
It sounds like ALT is pressed down.
This is a side effect of how the CursorXP cursors work. You don't need to do the first step on your PC, it will happen regardless of that I believe. If you use the inbuilt cursor system in XP then this does not happen. We will see if we can work around this problem with WB.
If you have problems with wbconfig only showing Windows Classic & Windows XP Style & get an ODBC dialog when you open WBConfig, could you try the following please : When you get the message about a DSN, pick the 2nd tab (Machine Data Source). From this please pick MS Access Database & press the New... button. You want a User Data Source, press next, scroll down to find Microsoft Access Driver(*.mdb), press next, press finish. On the new dialog, enter a DSN name (
What does it say on the System Information page in Wbconfig? And what happens when you click apply?
_chris_: so you left the DisableStage1 = 1 line in wb.ini and notepad still used lots of cpu? Do you have a per app setting for notepad set? If you set it to excluded, does it then open with low cpu? I assume you had taskmanager up to see cpu usage, was that skinned ok?
Thats a debug value that you should not leave on as you will find it disables large parts of WB! But it allows us to narrow down the problem. IF you set it back to 0, save it and then open a new app, does that app run slowly? If yes, then set it back to 1 for now, if not then try a reboot & see if its slow again.
We believe this is a database issue and are currently still looking into resolving it.
Open regedit. Go to HKEY_CURRENT_USER\Software\Stardock\WindowBlinds\WB5.ini\FilterCat Delete the values in this key.
William Green: Because the shadows are actually part of the skin. They are not being added later by WindowBlinds.
Does it happen with a particular game?
Could you try the following download & see if it helps. http://support.microsoft.com/?kbid=829558#XSLTH3120121122120121120120 If that does not help, try this : http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037
1) Is the new pc set as the pc to switch to seamlessly? 2) Does MP have the right IP address? 3) Does the new PC have a firewall blocking connections?
gtc954: If WBconfig says you need to reboot, it means that part of WindowBlinds is not installed correctly. Did you get any error messages during install? If you open regedit and look at these keys, do they exist? HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WBSrv In most cases we believe this is caused by an application that is 'protecting' certain registry entries to stop apps from autostarting. While this can be a go
Could you find a file called WB.ini (in the Windows directory) and add the following to it [Global] DisableStage1=1 Now does WB cause high cpu usage?
See if there is an option to disable overlay useage in PowerDVD. It seems some video drivers are unable to display overlays correctly when anything per pixel is on screen.
What is the date of wbload.exe in your WindowBlinds directory? Also what version of Theme Manager do you have installed?
With the other parts WB can fall back to software without any noticable impact (as afterall they don't move, size, repaint often). We are looking into if we should allow you to override the check and live with the higher cpu usage & much worse window dragging, sizing speeds etc.
Based on our testing, the issue almost always occurs after a resolution change. We have even done tests where the resolution change is done before WB is running & the same issue still occurs once WB is loaded up. On some machines it will simply never happen, on others it happens quickly. It seems to be some form of corruption internally in the OS. Basically the OS is painting non always on top per pixel window data on top of always on top per pixel data. Th
Jon Loveless: If you installed WB via SDC then the uninstall is done via SDC. If you installed the shareware version then it can be uninstalled via add/remove programs. We are still investigating this issue. Did you try the steps I posted above to see if they help? Also what applications do you have which load on startup?
WindowBlinds does support multiple accounts. It sounds like her account does not have read/write access to the WindowBlinds directory. You need to give her account this access or WindowBlinds will not work correctly.