The reason maya turns white is because their app fails to process messages for more than a set amount of time. XP decides the app is hung and so turns it into a ghost window so users can move, size & kill it easily. As it happens it can be turned off per process (by the app itself) if it causes a real problem, but in general if you have to turn it off then your app needs fixing.
This is not true. WindowBlinds 5 supports limited user accounts. It seems your problem is your limited user does not have access rights to the WB directory. You need to (from your admin account) set the access rights on the WindowBlinds to allow every user read & write access.
WinCustomize Forums
The application on the pc you are using to connect? If so that sounds like a bug in the MS remote desktop app. What version of that do you have installed as Stardock use Remote Desktop without problems.
Ahh yes, thats perfectly normal. The classic menu style is supposed to look like windows classic. Only the new XP style menu gets skinned as WB skins only have parts for the XP style menu.
WindowsBlinds 5 supports 64 bit XP. We have users running it without any problems! Even the shareware build supports it. There was a problem in some of the betas, but this was fixed up for the final RC before release. What problems are you having?
Find a file called WBsys.dll in the system32 directory. If you rename this file (deleting will fail), and then try your app with WB still running, does it now work?
If you click on the frame first and then try opening a menu, does the same thing happen? If so, its the OS z-order bug which requires a fix from Microsoft. Later versions of Windows (2003 & 64 bit) do not have this bug as they fixed it, but XP has not yet been fixed.
Could you e-mail [email protected] directly with a saved copy of your HKCU\SOFTWARE\STARDOCK\WindowBlinds registry keys (save from regedit)
What skin are you using, and what graphics card do you have (system information in wbconfig will tell you this)
Do you have panda internet security/AV installed?
Ahh, well we have a fix for that in WB. Open the file wb.ini in the Windows (NOT WB) directory. If it does not exist then you will need to create it. Add the following : [Global] NoGhostSupport = 1 This will prevent any app from 'ghosting' when it stops responding, so you will be able to run Maya in XP mode. I should point out that their app should not stop responding for such long periods of time. Suggesting people use 2000 mode is no
We have had a couple of reports of this. What other apps do you have installed?
Windows explorer. Some people rename it and that can confuse WB.
I believe they should support start menu skinning. I assume your explorer is called explorer.exe?
Now can you use regedit and show us the contents of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify\WBSrv key please.
The start menu should skin assuming the skin you are using supports it. Could you let us know what skin you have selected please.
If you do not exclude the app, does WB skin anything? Also when not in compatibility mode, does the app skin & work at normal speed?
Firefox isn't listed in the stardock installs...
Firefox isn't listed in the stardock installs...
Smart Exception should have written a log though.
It sounds like WindowBlinds is not correctly installed on your PC. Can you please post a directory listing of your WB directory including filesizes.
You think all the per pixel transparency is done using cpu only?
Open WBConfig & press rebuild the skin list button.
In what way are they not readable? Could you post a screenshot?
WinCustomize Forums
I was able to reproduce this once and then it stopped which made tracking it down difficult. I plan to revisit it next week.