WB 6.00(b).097 = oh noes!

from Stardock Forums
Well, I had WB working ok(ish) and then I had to go and try the beta.... It broke everything once more (under Vista x64), only worse. No skin on startup, no changing of skins, no nada. Got rid of it, but the start menu icons are still broken (severely pixelated) even without WB installed.

That's it, I'll stick with Aero until this is (hopefully) sorted out completely.
windowblinds
9,574 views 17 replies
Reply #1 from WinCustomize Forums Top

roll back to the previous build. tonight';s build is not for vista64. i made the same mistake

 

Reply #2 from Stardock Forums Top
roll back to the previous build. tonight';s build is not for vista64. i made the same mistake


Classic. SDC cannot differentiate between Vista32 or 64. How lame. Why let it update if it's for the wrong version? Where's the checks for this? Scarry.
WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from WinCustomize Forums Top
Classic. SDC cannot differentiate between Vista32 or 64. How lame. Why let it update if it's for the wrong version? Where's the checks for this? Scarry.

If you don't have anything nice to say  . . don't say it.
Or . . try saying it not so much like an ass.
Reply #4 from WinCustomize Forums Top
As an aside, the history in SDC says
[100407 6.00 refresh]
---------------------------
32-bit XP-only: Optimizations to skin changing speed and toolbar icon changes.
32-bit Vista-only: updates for Messenger Plus and WindowBlinds and tab/titlebar issues with some skins and Office 2007.

There are no updates to this installer for x64 Vista. If you are having trouble upgrading from 5.51 to 6.0, please see https://forums.wincustomize.com/?aid=164201#1321795 to check out if there are old wbload.dll files.

If you've experienced a loss of start menu/taskbar skinning on reboot, when posting on the forums, please include what AV package (if any) you are using.
Reply #5 from WinCustomize Forums Top
zubaz is right. i should've checked the history first before updating. i blame no one but myself for the mistake. jrsccivic, i think you need to calm down a lot. your comments are getting to be out of line.
Reply #6 from Stardock Forums Top
Hey, it's not me missing all this stuff. I just point it out. Think of me like that anoying media person who keeps asking all the questions no one else wants to ask and loudly points out the faults in things. Why hide mistakes. Bring them to light and let the devs learn from them. It makes for a better product in the end run... although I keep waiting for that.
Reply #7 from WinCustomize Forums Top
anoying


  
Reply #8 from Stardock Forums Top
zubaz is right. i should've checked the history first before updating.


The program needs to do an OS version check prior to downloading and updateing. It's not hard to have such a check put in place. You see these kinds of checks all the times in software updates... IT'S NOT THAT HARD. Screw all this 2nd grade readme crud. Build INTELLIGENT software if you want to be associated with Microsoft or it's products.
Reply #9 from WinCustomize Forums Top
Their already associated.
Reply #10 from Stardock Forums Top
Their already associated.


My point exactly....


And it's They're, not Their.
Reply #11 from WinCustomize Forums Top
My limited edition 24 carat gold spiked troll club (with comfy ergo grip) is at the ready just say the word

ps: did i mention it's jewel encrusted
Reply #13 from WinCustomize Forums Top

And it's They're, not Their.

...and it's also 'updating', not 'updateing'....

Think "glass houses"...

To be strictly fair, anyone using or wanting to use 'beta' versions of ANY software really should learn to RTFM, irrelevant of any form of OS-checking...as that alone does not indemnify them from [other potential] cock-ups.

Windowblinds, by its very nature has ALWAYS been about beta development to both unbreak things broken by OS updates/revisions and by feature inclusion/s prompted via feedback.

When in doubt stick within the relative comfort zone of 'full-point' [stable] releases....

Reply #14 from Stardock Forums Top
I'm having similar problems here. I installed the beta update to WB6, then read this forum, so I rolled back to the 6.00.05(??) version. It was working fine yesterday, but after today's update, WB 6 won't skin anymore, even after the rollback. Also, after install, WB6 starts copying the files to c:\Documents and Settings\blah...blah..., but it opens up around (the highest count I got) 59 "Calculating time remainig" windows, which ran for about an hour without end. Here's the system info from WB6: Your computer has a Windows Experience Index base score of 5
Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6.0 (build 49 x86 - Vista Edition) - 64 bit OS

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 215TW/216TW, SyncMaster Magic CX213TW(Digital)) 1 is attached to NVIDIA GeForce 7600 GT
() 2 is attached to NVIDIA GeForce 7600 GT
(Generic PnP Monitor) 3 is attached to NVIDIA GeForce 7600 GT

Wblind.dll 2007/10/01 11:46:20
Wblind64.dll 2007/07/24 10:19:08
Wbsrv.dll 2007/07/24 10:19:05
Wbconfig.exe 2007/10/01 17:35:33
Wbload.exe 2007/09/27 17:47:44
Wbhelp.dll 2007/08/27 11:54:07
Tray.dll 2007/09/12 17:58:21
Wbload.dll 2007/09/26 12:53:28
Screen.exe 2007/10/01 11:23:24 I shutdown all viruscaners and spyware scanners before install, which I think is recommended for WB installation, if I remember correctly. Anyway, I hope this helps because I would really, really love to see that animated dragon on my start menu again.
Reply #15 from WinCustomize Forums Top

It appears that the 64 bit installer for the beta is having problems.

When the release notes say that the 64 bit build is not updated it just means it has not changed so there is no need to install the build as it will not change anything.

See if you have a file called wbload.dll in c:\windows\system32 and c:\windows\syswow64.  The two files will be differently sized.

Reply #16 from WinCustomize Forums Top

I have installed it here and found that the problem is SDC has downloaded some 5.51 files rather than the 6.0 files (wblind64.dll and wbsrv.dll).  The information has been passed to the right people so hopefully this will be resolved later today.

I cannot reproduce any problems with the startmenu icons and I doubt that is WindowBlinds at fault.  Did you also install IconPackager or ThemeManager?

Reply #17 from Stardock Forums Top
Yup, I installed Theme Manager. Should I try removing it?