WB 5.01 b 014

The latest build hasn't addressed the titlebar, startmenu or taskbar issue.

My system info:
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 2 monitors.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 6100
() 2 is attached to Maxi_Vista_DriverA

Wblind.dll 2006/08/15 17:50:10
Wbsrv.dll 2006/08/15 17:50:18
Wbconfig.exe 2006/03/19 14:33:44
Wbload.exe 2006/03/13 17:54:12
Wbhelp.dll 2004/09/18 16:37:00
Wbui.dll 2005/12/06 21:29:06
Tray.dll 2006/04/13 17:29:04
13,514 views 19 replies
Reply #1 Top

Find the directory which has the skin you are using and delete all files ending in .WB4 then reapply the skin.

Does that help?

Reply #2 Top
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.

(Plug und Play-Monitor) 1 is attached to NVIDIA GeForce FX 5600

Wblind.dll 2006/08/15 17:50:10
Wbsrv.dll 2006/08/15 17:50:18
Wbconfig.exe 2006/07/13 18:37:40
Wbload.exe 2006/03/13 17:54:12
Wbhelp.dll 2004/09/18 16:37:00
Wbui.dll 2005/12/06 21:29:06
Tray.dll 2006/04/13 17:29:04

Hi Neal, I have serious problems with aura since this build, other skins (tested Ecliz2 and 5imple)are okay :









I followed Your tip deleting the .wb4 files, but that didn't do it.


Drivers : ForceWare 91.31
Reply #3 Top
If you switch to 16 bit colour and apply the skin, does it all apply correctly?
Reply #4 Top
Yes, no problems there.
Reply #5 Top
I have gone back to "i", no problems at all.
Reply #6 Top
Kinda same troubles since 5.01i [ b ].013 with lots of "black places" (no troubles with 5.01h.012)
It seems to me trouble it may comes on places where skins are using bitmaps with magic pink instead of .tga and translucy, but i may be wrong ...

Can't leave a system report because i already came back to 5.01h.012   
Reply #7 Top
Changing to 16 bit didn't help, I also rolled back to a previous version.
Reply #8 Top
Odd, this build fixed my issues like this, but now they have issues like I had in the i build.
Will one size fit all?
Reply #9 Top
Maybe it's a WB5-NVIDIA GeForce issue. My ATI seems fine
Reply #10 Top
Aimzzz might be on to something, my laptop has no issues with the latest builds. It has an ATI Mobility Radeon Xpress 200 card.
Reply #11 Top
I also get a NVIDIA card Drivers : ForceWare 91.31 ...
Reply #12 Top
Same problem as Carl

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 2 monitors.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce 6600 GT
(Plug and Play Monitor) 2 is attached to NVIDIA GeForce 6600 GT

Wblind.dll 2006/08/09 18:09:02
Wbsrv.dll 2006/08/09 18:14:26
Wbconfig.exe 2006/07/13 18:37:40
Wbload.exe 2006/03/13 18:54:12
Wbhelp.dll 2004/09/18 16:37:00
Wbui.dll 2005/12/06 22:29:06
Tray.dll 2006/04/13 17:29:04
Reply #13 Top
I was having issues with Aura, as shown in Carl's pics. ( ATI card )
Deleting the WB4 files in folder as Neil suggested seems to have fixed it.
Have changed back to it 5 times since deleting files and it has applied fine every time.
Reply #14 Top
Oops, may have spoke too soon. First few times applying after delete WB4 files only used for a few min. This time have been using aura for a couple hours, corruption just came back. After reapply skin seems ok again but who knows for how long.
Reply #15 Top
Same problem here, with Khado theme; worked fine until last two builds. My video card is a Geforce 6800, 91.28 forceware, running at 1600 x 1200.

Reply #16 Top
Any progress ?
Reply #17 Top
same troubles since 5.01i [ b ].013 with lots of "black places" and 5.01j [b ](no troubles with 5.01h.012)


I've update with 5.01k [ b ].014
After a couple oh hours, the problem does not appear (it appeared after just a few mn with both previous versions)
Maybe i'll find troubles elsewhere but at least this major one seems to have been solved   

Reply #18 Top
Time to give the new build a try!
Reply #19 Top
Looks like we got a winner!