"Ported" theme not applying at startup

from Stardock Forums
Ok, I am not too keen on exacty how to port an msstyle to wba format, so basically stumbling around in SkinStudio, all I did was import the msstyle theme, then 'zip for distribution' which created the wba file.

However, WB5 applies the file just fine....but, from a cold boot, WB5 won't apply the theme properly. It starts it as a Windows Classic style theme, color intact until I start WB and reapply the theme. (same colors the theme uses, just in Classic style)

Did I do something wrong, skip a step? Help a newb!!!
10,522 views 11 replies
Reply #1 from Stardock Forums Top
Let me know if 'bumps' are inappropriate. Just curious to see if anyone can help.

Thanks.
WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from Stardock Forums Top
Ok people, there's got to be over a 100 years of theming experience out there to pull from...and from those who have used WB since the beginning!! And no one has any idea as to why WB would start a ported theme as a Windows Classic from system startup?

Reply #5 from Stardock Forums Top
Thanks for responding Neil, appreciated.

No they don't. And, until I get some kind of feel as to why this occurs, I haven't tried porting any other msstyle themes just yet.
Reply #6 from WinCustomize Forums Top
i have the same issue but it isn't with ported skins as i have none of those on my system. the skin i use 99.9% of the time is stealthos by mike and i have to reload the skin via wbconfig after every cold boot. as with morpheous416, i see the windows classic gui after every cold boot but that's probably due to the themes service being turned off.
Reply #7 from WinCustomize Forums Top
Snidely, I have the themes services turned off on my laptop, but never have trouble with any blinds not loading at startup.

Morpheous, I have numerous ported blinds on my computers, and have never had a problem with them loading at start up.

I know I am not any help here, just commenting.
Reply #8 from Stardock Forums Top
@jazzy....

Comments are welcome. However, when you let me know that ported themes aren't giving you any probs, please give up some info on what you're system is using...then at least if it's comparable to mine, a simple setting adjustment just might fix the issue!

Reply #9 from WinCustomize Forums Top
please give up some info on what you're system is using...then at least if it's comparable to mine, a simple setting adjustment just might fix the issue!


Sorry about that, Morpheous. Ok, here is what I do when I port msstyles:

I import the msstyle theme. I tinker with it, making any changes I want, if needed. Then I do a "save". If you want to change the name of the skin, you need to do a "save as" (At this point, I still keep skin studio open.) I then close the Windowblinds configuration window. Then I re-open it. Then scroll to the skin. Then I apply the skin.

If everything is the way I want it, then I go back into skin studio, and do a "zip for distribution." At this point, you can go back into the windowblinds config and change your theme to something else, then delete the theme you just made. Then you can re-install it by clicking on the wba file you just made. Or, you can just leave that theme on. If you delete the theme, and re-install it, your file will be smaller, because skin studio will only zip files that are actually being used in the theme.

I hope this helps...if it is clear as mud, let me know....I will try to explain it better.
Reply #11 from WinCustomize Forums Top
You're welcome....hope it works for you.