Page 1 of 1

Spontaneous change to XP theme taskbar?

Posted: Fri Oct 20, 2006 8:21 pm
by hodad
I have my Thinkpad configured to Windows Classic theme desktop but occassionally it will spontaneously boot up to the Windows XP theme taskbar and start menu. I have to manually change it back. Any ideas on why this happening and how I can fix it?
Thank you.

Posted: Sat Oct 21, 2006 2:44 pm
by dsigma6
Just so you know you're not alone, this has happened to me once. I'm going to do some pondering and try to remember what I had concluded regarding the unwanted change.

Posted: Sat Oct 21, 2006 7:07 pm
by hodad
Thanks!
I'd appreciate any help I can get with this annoying problem. I know there is a registry hack which forces the Windows Classic taskbar and Start Menu but I'd really like to know what's causing this. I'm one of those people who likes to have my machine configured "just so" and really resent any intrusions.

Posted: Sat Oct 21, 2006 7:17 pm
by jdhurst
It has never happened to me in several years across two machines. One thing I do and to consider is to go into Performance and set for best performance. That turns all the eye candy off. Turn on Smooth edges of Screen Fonts so as to be able to use Clear type. See if that helps. I not only like my computer "just so", I get frustrated and go on the warpath with my box if it isn't "just so".
Good luck, ... JD Hurst

Posted: Mon Nov 13, 2006 12:00 am
by hodad
I was able to fix the problem with a program called "Tweak Manager"

Posted: Mon Nov 13, 2006 10:44 am
by Purcy
JD, do you mean to go into Performance under Administrator Tools? I did that but cannot find any setting to choose "Best Performance" I'd like to turn off all the excess XP stuff too. thanks for your help.

Posted: Thu Nov 16, 2006 2:34 am
by Musti
Purcy wrote:JD, do you mean to go into Performance under Administrator Tools? I did that but cannot find any setting to choose "Best Performance" I'd like to turn off all the excess XP stuff too. thanks for your help.
If you're sure you will not use the Tonka interface--sorry the Windows default theme and eye candy, disable the Themes service. You'll gain some additional memory as well.

1. Start --> Run --> type services.msc
2. Find Themes, doubleclick.
3. Click Stop and change Startup Type to Disabled.

Enjoy Windows 2000. Don't get me wrong, this is the first thing I do after a clean installation.

rgds.

Posted: Thu Nov 16, 2006 10:54 am
by Purcy
Greetings, thank you for your reply. I will try this, but first want to ask if this change is something I can reverse, say if I want to someday go back to the XP theme. Many thanks

Posted: Thu Nov 16, 2006 11:04 am
by dsigma6
You can start a service just as easily as you stop it.

Posted: Thu Nov 16, 2006 11:40 am
by Purcy
Thank you for your reply. Newbie here, and I just want to be sure; I just made the change and that was easy. I appreciate everyone's help.

Posted: Thu Nov 16, 2006 1:00 pm
by smugiri
I noticed this problem every time I installed IBM's Bluetooth stack.

If you have Bluetooth hardware but do not have the software fully installed, could you check if it happens when you turn on Bluetooth with Fn+F6?

Posted: Fri Nov 17, 2006 1:29 pm
by Musti
Purcy wrote:Greetings, thank you for your reply. I will try this, but first want to ask if this change is something I can reverse, say if I want to someday go back to the XP theme. Many thanks
Just follow the steps and put the Startup Type to Automatic, and click Start. After subsequent reboots, it will automatically start (default XP behaviour) so you won't have to go there and click Start.

Posted: Wed Dec 06, 2006 12:49 pm
by CharleyCross
I have sort of the flip of the question that began this thread. I have a computer set to use the XP theme, but sometimes it spontaneously switches to the Classic theme (often with the task bar a bit messed up). Investigation shows that the Windows Themes service has stopped when this occurs, so it makes sense that the XP theme has died. But the part I can't figure out is why the Themes service is stopping or crashing. The event log doesn't appear to have anything relevant around the time of the problem.

Any wisdom?