SkinStudio Problem! Is this happening to you?

from WinCustomize Forums
This morning I downloaded and installed (on ODNT) the latest SkinStudio (2.10)
Since then I've had nothing but problems.

1. The "XP Tutorial" skin does not skin the taskbar.
2. Any new skin I create also does not skin the taskbar.
(It isn't WB because my skins that are already created work just fine as do all other skins by other authors that I've downloaded from WinCustomize.)

3. Constant crashing of explorer when SkinStudio is running.


I've uninstalled and reinstalled many times.
I've tried XP's "System Restore" to the day before all of this started, to no avail.
I've completely erased all traces of anything to do with Stardock software and then redownloaded and reinstalled everything.

Nothing is working.

I wish I could return to the previous version of SkinStudio. It worked just great. Unfortunately it is now not available on ODNT.

Anyone else experience one or all of these problems with SkinStudio 2.10??

Any help greatly appreciated.

P.S.

I have left a description of the problem at Stardock's SkinStudio newsgroup. No answers there.
2,837 views 7 replies
Reply #1 from WinCustomize Forums Top
sorry i can´t help. but SkinStudio was crappiest program that ever was on my computer. (not including B**ya) crashed every 2 minutes and did not save the changes to the UIS file. pretty bad, because i like WindowBlinds since vertsion 3.3.
Reply #2 from WinCustomize Forums Top
OK, this is really messing up my taskbar. This new version of SkinStudio is not working right. My taskbar is flat and grey. (although my tray is skinned and the quicklaunch bar is skinned....also, if a taskbar button is present then the area behind the button is skinned, just not the rest of the taskbar.)

Also, the tray arrow is flat and grey. (it doesn't even contain an arrow, it's just a flat grey box.)

Also, the clock which I know is set to a size of 18 actually displays at some ridiculous size. (somewhere around 100 or so)

This is nuts.

It looks like my "career" as a skinner is short-lived. As well, my subscription to ODNT and WinCustomize will definately not be renewed. What would be the point if the software that is needed to create the skin doesn't even work.
Ashes of the Singularity II
Reply #3 from WinCustomize Forums Top
motion, you're not the only one......I'm getting slightly annoyed at my problems.
Here's the list!!
I'm making a wb skin and I've got numerous strange things happening.

1. When I try to add the section for horzizontal taskbar arrow (systray) it won't let me add any attributes, so now I get a little grey box. *note I can add the vertical arrow - sounds like what motion said above

2. All my bmps seem to have been bleached slightly. eg the blue is not the same shade of blue as in the .bmp file

3. Every time I apply the skin, although my taskbar is set to locked the horizontal 'sizer' appears on top of the taskbar. If I unloack then relock it, it disappears.

4. When i log in to my computer, the task is supposed to be blue, but where the tasks go is white until I open an app? - another one which sounds similar to what motion said

Please don't make me learn how to skin msstyles.....I like windowblinds
Reply #4 from WinCustomize Forums Top
Go see stardock.skinstudio.binaries. There is a file in the last thread from Adam which fixes some of the problems listed here. He apparently mis-named a key file. Just dl the file into to correct folder.

Powered by SkinBrowser!
Reply #5 from WinCustomize Forums Top
werewolf: thanks that's sorted the systray arrow, but I still have all the other problems.....is it just me or is it happening to others as well?
Reply #6 from WinCustomize Forums Top
Thanks werewolf. I knew about the fix. I'm the one who reported the problem to Stardock. (I'm also know as Tim C. )

Yes, the fix works great.

honz12: It should fix problems 1 and 4 in your list. The other problems are new to me. I would go to the stardock newsgroup and post the other problems there to see if there might be a fix.
Reply #7 from WinCustomize Forums Top
I had similar problems. I copied and pasted all the content from the xpstuff.xp to the WBA file and that fixed it for me.