How do I set a skin as default?

[Ulaa]

How do I set a skin as default so it will STAY as the default.?
I have read the FAQ, looked at the documentation and searched the forums and cant find the answer.

In Winamp2.x when you selected a new skin, WinAmp would default to that skin when ever it opened. With WinAmp3 I have to reselect the skin and color scheme each time I reopen it (IE if I boot or close it for some reason I end up with the "Classic Default" skin and have to go thru the process of loading the skin again.)

I am using the latest version of the MMD3 skin and it works beautifully in all other ways, I have no other problems with WinAmp3 at all, it works beautifully right outta the box. Fantastic job guys keep it up .

[Nunzio390]

In Winamp2.x when you selected a new skin, WinAmp would default to that skin when ever it opened.

This is no problem for me. It always remembers and saves whatever skin I had opened last when I close, and then reopen Winamp3.

I am using the latest version of the MMD3 skin and it works beautifully in all other ways

I am also using the latest version of the MMD3 skin and it works beautifully in EVERY way. It is my default right now. The only problem with it is that it causes Winamp3 to take longer to open, as opposed to using the designated default or classic skins supplied with the program.

My system (although it shouldn't really matter)...
WinXP Pro build 2600

[Ulaa]

When you shut down Winamp3 and reopen it it keeps the skin at whatever you had it set at?.

mmm, I spent quite a while the other day trying to figure out how to do this. I right click or open the skins chooser, choose the MMD3 skin, then choose blue and it reloads and all is good.

If I then shut down Winamp and come back to it, it always reloads as the default skin. I went through preferneces and options through this board and couldnt find an option for it. I assume the chosen skin is supposed to stay as default but for some reason it doesnt.

Im running a Dell GX150 with 512MB Ram and win2k in a large commercial environment. Im the guy in charge of the MP3 server hehehehe

[Ulaa]

Thanks for your reply Nunzio

[Ulaa]

Only just noticed this. After I shut down Winamp in a skin I get an application error (Im usually switching windows so fast I didnt notice.)

Application exception occurred:
App: Studio.exe (pid=1228)
When: 11/15/2002 @ 09:24:40.814
Exception number: c0000005 (access violation)

*----> System Information <----*
Computer Name: DELETED
User Name: DELETED
Number of Processors: 1
Processor Type: x86 Family 6 Model 8 Stepping 10
Windows 2000 Version: 5.0
Current Build: 2195
Service Pack: 2
Current Type: Uniprocessor Free
Registered Organization: DELETED
Registered Owner: DELETED

Ive checked and I can see several errors logged in drWatson for winamp. Would it be worth posting this to the bug board do you think?

[Flotser]

This problem happens to me with most of the skins, the skins work great but wehn i close winamp3 i get an error (WIN XP) , and the next time i open winamp, it wont remeber prefernces also the skin...

[Ulaa]

Thats exactly the same with me. I thought at firast it was the skin itself, but it happens with any skin I download.

[Nunzio390]

When you shut down Winamp3 and reopen it it keeps the skin at whatever you had it set at?

Yes. Never had any problem that way at all. Occasionally though, on switching skins, I have received application errors. But this I concluded was due to a problem inherent to the skin of the 3rd party developer, and not the program. In those cases, if the error occurred with too much frequency on any particular skin, I simply deleted that/those skins.

Right now I only have 3 skins to choose from, and I'm happy with them. The first 2 come bundled with the software, default and classic. The other (and the one I use most often), is the MMD3 skin. It gives me no problems at all and is really the only one (in my opinion) with enough class and functionality to set it above all others I've tried. Kudos go to the author/developer on that one.

Now... since at least one (possibly more) of you guys are running WinXP like me, and you are having problems where I'm not, I feel it cannot be an operating system problem/conflict with Winamp3. If that were the case, I'd have the problem too. I can however take an educated guess at what the problem "might" be...

Perhaps you all have downloaded/installed one SPECIFIC component/mod that you all HAVE but are unaware of, that is contributing to this problem. It's the only thing that makes sense to me. Ya know... another 3rd party component that you all share. And perhaps this one SHARED component contains bad coding that is causing ALL your skin problems. I'm not necessarily referring to a SKIN... this may be the case, but I feel it's more likely to be another component that you all may have/share.

So... troubleshoot. Just like in anything else, through elimination and then discovery. This has to be approached in 2 ways...

1. non-skin mods/components
2. individual skins

Go with number 1 first, since I feel it is more likely that it's not a skin causing this. If troubleshooting that fails, then start eliminating individual skins. It could be one individual skin too.

OK... Begin removing components you may have added that did not initially come bundled with the software. After each individual removal, fully TEST your skins AGAIN and AGAIN, to see if the problem disappears. If it DOES disappear, then you have isolated the component that is messing with all your skins, can REPORT that it is in fact that one component, and then push to get the 3rd party developer to FIX the problem.

This is the only thing that makes sense to me and the only thing I can suggest.

GOOD LUCK!!!

[Ulaa]

Nunzio,
Sorry I havent been back in a while. Good ideas, basic troubleshooting. Unfortunately Im not running any plugins for winamp3. Just the basic winamp 3 build and MMD3 skin, thats it. Problem is so annoying im going back to 2.8 till I see the next build is out.