Ok, I really screwed something up here.  I downloaded a small tool that's used for hiding and showing hidden windows (window handles).  I was trying to find one that was hidden.. and I chose the wrong one from the list (called Player Window) and "un-hid" it.  

As soon as I did that, my winamp went nuts and pretty much made itself full screen, so I went BACK in that program and re-hid the window.  Now my winamp is completely messed up.

When I try to view it in normal mode, it looks fine, like this:


But when I change it to Windowshade mode (the thin display), this happens:



I have rebooted, uninstalled winamp, REINSTALLED winamp (new version even), and it's still doing this.  

I don't know why that "hidden window" would stay modified even after reboots and reinstalls.  There's got to be something in windows that's remembering that window's state.. be it a registry key or something else.. but I haven't the slightest clue where to look.  Also, it only happens with the "modern skin" support enabled.  If I change it back to the ugly old classic winamp style, it functions just fine.


Does anyone have any idea how I can fix this?  Any help is appreciated.. this is a weird problem.

ThanksWas it "Window handles" or was it "WindowBlinds" from Stardock Software?

Handles.  I'm guessing you got windowblinds from when I said windowshade mode.  That's winamp's term for the thin, button-only version.

I used this program:
http://khsw.blogspot.com/2004/08/application-lost-after-crash-of.htmlThat is absolutely the kind of thing I would NEVER install on my computer. You're lucky that that is all that (apparently) happened.

How about a system restore to a point before you installed this?There's nothing wrong with a program like that... I've had to use this type of software before when troubleshooting peoples' computer problems, I just happened to mess with a grumpy window this time.

I'd rather not use system restore as this is not that big of a deal.. it's just annoying.  I'm fine with using winamp's old mode if I have to, but obviously I'd prefer to fix the problem if possible.

If you're curious WHY I used this in the first place.. it's because I was playing a flash game, and I wanted to use a memory editor to give myself extra lives so I could just mess around and practice.. and I couldn't find which process I needed to search in.  So I thought maybe a program that enumerated window handles like this would ALLOW me to see a special window that was used by the flash player and trace back to the parent application.  That's why when I saw "Player Window", I thought it may have been for the flash player.

Anyway, I'd much rather fix the problem than run from it.. so I guess I'll wait and see if anyone else might have a hunch as to how to fix this.  I know it's a pretty off-the-wall problem, so I'm not expecting anyone to know the answer.. but it's worth a shot.

Thanks Quote

There's nothing wrong with a program like that