Some problems with WindowBlinds

I write because I have two problems with WindowBlinds.When a skin is applied, I can't close an Internet window or a Windows Eplorer window by clicking on the buttons on the top-right corner.I'm obliged to do a right click or to press alt+f4.But I can click on these buttons when it is a window of any software. The second problem is that the skin that I had applied before shuting down windows isn't applied next time I switch on my computer. So I would like to know whether it is normal or not. Thanks T3T$UO
1,942 views 6 replies
Reply #1 Top
I'm assuming you have Windows XP, as the first problem is usually an XP-related one and can be fixed turning off 'common names', which I believe is something to do with Internet Explorer. (I'm a 2K user though, so I'm not sure how you turn it off)
Reply #2 Top
yep, it sounds like common names. it's not part of the os, but rather an ie add on. other third party ie add ons can cause problems like this as well.

it's set by default to run automatically, but it may have been switched off in the preferences accidentally.
Reply #3 Top
You were both right, it was a problem due to Common names. Thanks both of you for responding
Reply #4 Top
So the second problem is still here.In fact, when i start my computer, I go to Properties, Appearance, and the skin which is SELECTED is a windowblinds one.But this skin is NOT APPLIED and instead of it, it's a Windows Classic Style one which is applied.I'm obliged to select the Windowblinds skin a second time, to press "apply", and then the skin i wanted is applied...I don't understand. Besides, when i go to WindowBlinds preferences ( WindowBinds Advanced Configuration ), i don't see an option where i would be able to set to " run automatically "... So I hope you will be able to help me. Thanks
Reply #5 Top
Are you using the shareware evaluation version? If so I think that version will not run at startup. You must manually run WB after booting.

The registered or OD versions of WB run at startup.
Reply #6 Top
Yes I do. I thought it would be possible that the problem was due to the shareware version. Thanks for responding