New PC - WB Won't Fully Load Skins

from WinCustomize Forums
New PC, custom built by Falcon-Northwest. Just got around to installing WB5, latest beta on it.Installed it, along with my other OD apps, via SDC, as always. Rebooted PC after WB installation. Then after the restart, I tried to load Cyclops. No skinning on the title bars, taskbar, and most dialogs. Very few items were skinned - the Wait dialog looked perfect. But nothing else does. I finally had to unload it and restore previous settings.

Thanks for any input.

Here's the Sys Info from WB:

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.

(ViewSonic VA1912w SERIES) 1 is attached to NVIDIA GeForce 7900 GTX
(ViewSonic VA1912w SERIES) 2 is attached to NVIDIA GeForce 7900 GTX

Wblind.dll 2006/08/23 17:13:20
Wbsrv.dll 2006/08/23 17:18:30
Wbconfig.exe 2006/08/19 14:24:16
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
windowblinds
15,508 views 7 replies
Reply #1 from WinCustomize Forums Top
What driver versions?
All skins or just cyclops?
Reply #2 from WinCustomize Forums Top
Drivers for what?

And I didn't try all skins, but I tried five of the ones already listed in the WB interface and none of those worked.

Thanks.
Sins of a Solar Empire II
Reply #3 from WinCustomize Forums Top
Drivers for what?


NVIDIA GeForce 7900 GTX


Reply #4 from WinCustomize Forums Top
Oh, gotcha. I'm on my notebook now. I'll post the driver when I get back to the desktop PC, though I updated to the latest from NVIDIA about three or four weeks ago and I don't see anything newer on their site.

I'll post the details when I get back to the other machine. Though in all honesty, if the solution involves dropping back to a previous driver or firmware, I won't be doing that just to get WB working. The present driver has been tested and is working extremely well with my digital video editing/authoring package. (The previous one did not)

I can't risk that to get WB to work; One helps feed me, while the other is pretty but does nothing else!

Thanks, Sir Zubaz.
Reply #5 from WinCustomize Forums Top
I can't risk that to get WB to work; One helps feed me, while the other is pretty but does nothing else!


Reply #6 from WinCustomize Forums Top
I can't risk that to get WB to work; One helps feed me, while the other is pretty but does nothing else!





Zubaz,

Sorry - didn't mean that in a bad way. Just that I can't afford to change my system setup in a way that will foul up my main productivity applications, only to get WB rendering as it should. While WB does look good, I can't have it up at the expense of anything else!

BTW, I do have the latest driver package from Nvidia: 91.31. 91.28 is the one that was troublesome for my system.

Also, I notice that the WB system info screen shows that I have two of the same monitor, which is not correct. Actually I have one ViewSonic VP2130 as my primary monitor, and one ViewSonic VA1930W monitor as the secondary; one for the application(s) I'm working with, and the other for viewing my edited video files as I work on them.

Where does WB pull that info from? The Nvidia Control Panel shows the display config correctly.

Thanks again, Zubaz.
Reply #7 from WinCustomize Forums Top
Sorry - didn't mean that in a bad way.


I didn't take it in a bad way. I totally understand the difference between need an want.
Also, I notice that the WB system info screen shows that I have two of the same monitor, which is not correct. Actually I have one ViewSonic VP2130 as my primary monitor, and one ViewSonic VA1930W monitor as the secondary; one for the application(s) I'm working with, and the other for viewing my edited video files as I work on them.

Where does WB pull that info from?


Dunno . . question for Neil I guess.

Wish I could help more but it looks like it's beyond "community" help and might be Stardock support time.

Can you post a screenshot? That helps sometimes.