Please post all feedback about the WindowBlinds 6 beta on this thread.

Note that the beta is for 32 bit XP and Vista systems only.  Please do not post about it not working on 64 bit XP/Vista.  Please continue to use WB 5.51 on those platforms.

This beta is for Object Desktop customers ONLY.  Standalone WindowBlinds 5 owners will not be able to activate this build.

Please note that you must have Stardock Central 2.46 Build 154 or later to install the WindowBlinds 6 betas. If you try and use older versions, it'll eventually timeout and give you an error about an invalid URL.

If you have problems with it running at all, please uninstall WB6, reboot and then try reinstalling WB6 again.


Comments (Page 17)
36 PagesFirst 15 16 17 18 19  Last
on Aug 06, 2007

It looks like your diamond skin has been corrupted.  It is a UIS2 skin, not a UIS1 skin.

on Aug 06, 2007
Thanks Neil! That did the trick!


Hey WG, are you running the latest version, deleting the wb4 files did not work for me, even after a reboot. Had to edit skin, see above reply.
on Aug 06, 2007
It looks like your diamond skin has been corrupted. It is a UIS2 skin, not a UIS1 skin.


Thanks Neil, I will delete it for now then and see if it is correct after next version release.
on Aug 06, 2007
Has anyone from Stardock taken a look at my post? Reply #222
on Aug 06, 2007
hmm.. skinstudio say, diamond: uis1+ skin..
on Aug 06, 2007
hmm.. skinstudio say, diamond: uis1+ skin


Yep: decided I will do a uninstall/reinstall, will see what I get when done.
on Aug 06, 2007
Skinstudio 5 may be confused.
on Aug 06, 2007
So...was this skin started with WB4 and the files were left in?


No, this has nothing to do with WB version 4 - the .wb4 files are cache files that WB creates on the fly for certain graphical elements. For reasons too technical for me to understand, they sometimes don't get refreshed properly and can cause some issues with window painting, particularly certain areas using magic pink trans. Deleting the .wb4(cache) files & reloading the skin (forcing WB to recreate them) usually fixes these cache-related display anomalies.
on Aug 06, 2007
I've got a very minor annoyance under XP and limited per pixel mode, no matter which WB I apply they all have the Acrylic winflag.
on Aug 06, 2007
No, this has nothing to do with WB version 4 - the .wb4 files are cache files that WB creates on the fly for certain graphical elements. For reasons too technical for me to understand, they sometimes don't get refreshed properly and can cause some issues with window painting, particularly certain areas using magic pink trans. Deleting the .wb4(cache) files & reloading the skin (forcing WB to recreate them) usually fixes these cache-related display anomalies.


Note that under Windows XP, this delete and refresh took care of the titlebar alignment issues, but now the right mouse button menu (anywhere, like the desktop, for example) is black text on black now. The commands light up if you scroll over them, but...

Submenus appear to be painting correctly as do the start menus, if that helps anyone track this down.

on Aug 06, 2007
My install of WB6 went fine - I am loving the blur effect. I have only noticed two small issues at this point.

1) the per-application feature disabling has been disabled again. My applications that can't handle scroll-bar skinning are noticeably affected.

2) This might have something to do with the Virtual Desktop application - the transparent task-bar shows the background wallpaper from my main window even though I have set the VD to use it's own background as the window's background. Did that make sense? Here's a screen grab to give you an idea:

The left-most image is where you can see the wallpaper (the grassy image) stops just above the task-bar. Then my real background shows through the task-bar.
The right-most image shows what happens when I click to a different Virtual Desktop and then click back. the background of the Quick Launch area goes black. It happened in WB5.5 too, so I'm thinking it is related to VD not WB.
on Aug 06, 2007
It is a UIS2 skin, not a UIS1 skin.


Neil....While looking through the folder for the skin I noticed both of those listed in the skin if thats any help.
on Aug 06, 2007

Ran across a new problem with .026 - active window frame right is painting lighter than the source image, by about 20 RGB points.



The image on the left is how WB6Config previews the close button & top portion of the window frame right (correctly). The image in the middle is the source image. The image on the right is the close button & top portion of the window frame right as WB6 applies it to the active window - you can easily see the lighter hue of the two right-most pixel columns (the top portion of window frame right). Using magic pink trans.

Did not notice this until the .026 update, but could have been there before since it is subtle.

I believe all your painting issues are caused by a bug in the transparentblt support in your graphics card drivers.  The drivers for early ATI boards have buggy alphablend support as well.

This would explain why it works perfectly on all our test boxes.

If you alter the hardware acceleration slider in windows (display properties->settings->advanced->troubleshoot) does the problem go away?

on Aug 06, 2007
Bichur, looks like it's a bad skin cash problem, try open the skin folder and delete all files with the extension ".WB4" and reapply the skin.


okay, I'll give it go after I get home.. thanks
on Aug 06, 2007
Nope, didn't work.

Switched to VistaPlus and Vista32 and on both had the top part of the start orb still there on top. Switched to Twisted and it went away.

I'm seeing glow after effects on all the skin I've tried that had it, but the others seems to be more of a quick residual, then disappear on their own.



WindowBlinds version : WindowBlinds 6 (6.0 (beta build 19 x86))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

(hp pavilion f50) 1 is attached to NVIDIA GeForce4 MX 440 with AGP8X

Wblind.dll 2007/08/03 11:51:20
Wbsrv.dll 2007/08/02 11:25:18
Wbconfig.exe 2007/08/02 11:25:47
Wbload.exe 2007/07/30 13:14:11
Wbhelp.dll 2007/07/24 10:21:07
Wbui.dll 2007/07/24 10:21:06
Tray.dll 2007/07/24 10:21:49
36 PagesFirst 15 16 17 18 19  Last