WindowBlinds 5 Startup Problems
Wednesday, November 30, 2005 by Andrew Robinson | Discussion: WindowBlinds
My system is:
AMD Athlon XP 3200+
1.5 GIG DDR400
Geforce 6800 Ultra 256MB
Windows XP SP2 (Fully Updated)
Any help is appreciated.
[ Update ]
I have read a few of similar problems here, looked for .CMD in MSCONFIG, yet thats not listed.
Reply #142 Saturday, January 7, 2006 11:10 PM
| What are the main features that WB 5 supports that WB4.51 does not? |
The main difference is the support for "alpha-blending" or "per-pixel blending" which allows the use of transparency in the Taskbar, Titlebars, and menu backgrounds (except the Favorites menu).
WB 4.6 supports Start Menu transparency due to the lack of need to resize dynamically.
If you have Stardock Central, you should be able to update to WB 4.6, which is a nice step up from 4.51 due to support for many of the skins designed for that version.
Reply #143 Sunday, January 8, 2006 12:47 AM
It's a bit of a productivity killer!Reply #144 Sunday, January 8, 2006 2:10 AM
RonW: You're this close! If you are still using Spybot S&D, run the resident (Tea Timer) and try "allowing" WindowBlinds. Also, if you do get WB5 running without this, you will want to add Spybot to the "Exclusion List" in WBConfig. I say this because WB doesn't paint it correctly as Spybot has it's own "skins". You may find that you cannot see the Block and Allow buttons when and if you run the Tea Timer. Hang in there, RonW. With a little patience, you will get this running on your machine, and I am almost certain you will enjoy the heck out of the skins. I think that if you use the 77.77 drivers for your nVidia, and after they do their thing with your activation, you should be good to go. It really is worth the $20.
Reply #145 Sunday, January 8, 2006 3:12 AM
| cnlevo: Sorry about my garbled message earlier... I had meant to write that if you have teatimer enabled, first try disabling that, rebooting and then re-installing WB5. If that didn't work, uninstall both apps, reboot and try reinstalling WB5 and see if it's still there on subsequent reboot. You get the picture. As it stands, and as Corky notes, if you don't really care that much about the per-pixel blending you can happily stay with 4.6 until a later build of WB 5 is released (and works on your system). For me, I can't STAND having these kinds of conflicts and keep at it until I have figured out/arrived at a workaround It's a bit of a productivity killer! |
I hear you, I hate when stuff doesn't work. However WB is not a needed app for me, especially since 4.51 works for me. I've never been big into WB because you have to customize with a standard...as in, there will always be a task bar and a start menu, etc...hopefully litestep will have x64 support soon. I just needed something to get rid of the boring old windows so I figured WB would be my best bet....so far, other then the WB 5 problems, i'm happy with it

Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #141 Saturday, January 7, 2006 11:03 PM
We need to wait for someone at Stardock to reset it.
This is unfortunate, because I was hoping the "Enable if you have corrupted titlebar buttons & menu backgrounds" option in the System Information panel of WB5 would set things straight. I should have remembered this one earlier.
Hopefully Neil or someone else with access, and have been cruising the boards will see this one tonight or tomorrow and reset your activation account for you. Note - I have just left a thread titled "Maximum activations reached" and requested a reset, as well as sending an E-mail as backup. I have had to do this twice now, due to the old "install WB / test / uninstall WB / reinstall OS / install WB...." for beta testing purposes.
Note - they are happy to reset for us, so no worries there.
I apologize for not being better help here. If it does not get fixed by the option I mentioned above, then I would tend to agree that a refund is the next viable option - as you have obviously tried just about everything to fix it.