Unable to return to standard Windows XP theme

Desktop locks up and corrupts when Windows XP theme is selected

from Stardock Forums

WindowBlinds 5.0 System Information Report:
STATUS : WB+ SRV+ HLP+ UI+ TRAY+
WindowBlinds is installed correctly on this PC.
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.
You have one monitor in total.
(L768) 1 is attached to RADEON X800 Series
Wblind.dll 2005/11/28 13:57:10
Wbsrv.dll 2005/11/28 15:52:00
Wbconfig.exe 2005/11/28 16:19:00
Wbload.exe 2005/11/25 19:30:58
Wbhelp.dll 2004/09/18 16:37:00
Wbui.dll 2005/11/20 12:23:40
Tray.dll 2005/11/02 13:28:26


XP Pro SP2, ASUS AX800PRO/TVD, 2GB RAM, HyperThreaded P4 3G Intel


Symptoms:



  • Selecting Windows XP theme in Windows Blinds dialog after any other theme is active (WB4 or 5 themes) results in Windows Classic being applied.

  • Selecting Windows XP theme in Display Properties dialog after any other theme is active (WB4 or 5 themes) results in locked 'Please Wait'.  Logging out from task manager results in screen corruption and abnormal termination of dialog process.

  • All themes other than standard Windows XP appear to be working fine.

Workaround:



  • Revert to Windows Classic, reboot.  Windows XP theme can then be applied.

Although some may be wondering "why go back to Windows XP theme?", the answer is "software developers need to test applications and create user documentation using the standard Windows themes".  In this regard, it is a serious problem (rebooting is not a great option when you have long running background processes or server processes being accessed from other machines).


BTW Very disappointed to lose the ability to skin Command Prompt - I use it more than transparency effects, particularly as I have yet to find may WB5 skins that are usable (semi-transparent = unreadable clutter when you have a desktop full of open applications).  They are very pretty (and the result of considerable talent) but not very practical for getting work done.


 


 


 
9,176 views 7 replies
Reply #1 from Stardock Forums Top

Follow Up:


I am using the latest Catalyst drivers from ATI.


I have tested on an earlier system image before the ATI drivers were installed and there is no problem with the bog-standard default VGA driver that comes with XP (though no full featured effects either).


Looks like it doesn't like the latest Catalyst drivers for some reason.  Or perhaps the per pixel skinning engine (which is presumably not available with the standard VGA driver) is trying to load Windows XP as if it is a WB skin?


Also: Fiddling with the check boxes to disable per pixel and fix titlebar corruption does not fix the problem, although the titlebar checkbox seems to make the problem delay one change of skin (2 changes and you're out).  However, switching that on prevents windows being drawn properly for open windows (right hand side of window missing, titlebar over edge by a centimeter or so).


 


 

Reply #2 from Stardock Forums Top

looking at the dates on your system info...is that trial version?


if it's a paid version, try updating WB through SDC.  If you don't have SDC go here: https://www.stardock.com/products/sdcentral/

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top

It's the latest paid version brought down by the latest version of SDC.


Another workaround: Unload WindowBlinds, then select Windows XP Theme.  Perhaps WB is simply not unloading itself when default Windows themes are selected?


 

Reply #4 from Stardock Forums Top

 


Specifically, SDC reports: WB5 5.00.001 5/12/2005.  Downloaded 2 days ago to replace WB4 (which was uninstalled and rebooted as prompted before installing WB5).  First ever download of WB5 on a freshly built machine.


 

Reply #5 from WinCustomize Forums Top

Unload WindowBlinds, then select Windows XP Theme

This is the way I have always done it.

If I am not mistaken, WB 5 uses ".dll" files to apply the skins, versus the older 4.x version using "wbload.exe". This may be creating some sort of issue with the "uxtheme.dll" file reloading on your machine.

I have also found that the Catalyst 5.9 version driver is the most stable "current" version in conjunction with my X700 Pro card.

Just some input.

Reply #6 from Stardock Forums Top
check 'show pre release' in SDC to see if you get an option to update WB
Reply #7 from Stardock Forums Top

Thanks for that tip - I'll try it cautiously and see.  Usually I'm reluctant to use prerelease software, for obvious reasons.


I have another clue which may help the diagnosis:


If I import a Windows XP style and convert it to WB format with Skin Studio (eg: Luna or Royale), then after loading that theme in WB5, I can switch to the built-in Luna without lockup, except that for some reason menu items in applications have white patches around them.


This implies that there is a difference between imported/converted msstyles and the typical WB themes out there that triggers the problem.