scaudill

Join Date 08/2006

Systray Revisited

Works on one machine... not on another.

Hey,
My first post here! I've got ObjectDock on my main computer and everything is working fine with the systray. All the usual suspects are there. On my travel laptop, though, I've got the same set up, and I can't for the life of me get the tray icons to show up.

I've made sure that SDMCP.exe is up and running. I just downloaded Stardock Central and set the options to 'enable MCP notification area support' and 'Smart Startup' as per other posts I've read. I've reinstalled the whole package a couple of times and tried loading OD at startup and starting once the system is up and running. No luck.

I looked at the pref file in my user profile and the tray function is set to work. Are there any known conflicts that I'm not aware of. Come to think of it, this happened after I upgraded to version 1.3 - and the laptop is running an ATI card. I read about ATI conflicts but that seemed to be with performance.

Is there a way to get the prior version to see if that clears it up? Thanks for any suggestion or thoughts!
-scaudill

objectdock

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

ZubaZ

Join Date 11/2001

+917

Try the stand alone MCP: Stand-alone MCP

Successfully updated karma reason!

Thanks Zubaz. Tried that file, but still not working. I'm at a total loss here. All that needs to be installed and services that need to be running are. I'll keep an eye on the boards and maybe try a total clean install of the app.
-scaudill

Successfully updated karma reason!

Follow up. I had the prior version still. Wiped the current install - everything, cleaned the registry, and installed the older version and still had no tray.

There must me a windows update, or other conflict at play here. I'm going to futz around and see if I can figure out what it is. Thanks for the help!
-scaudill

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

BigDogBigFeet

Join Date 12/2005

+474

Have you tried reverting to plain XP. That is, don't let WB5 load, if it does select Windows Classic then unload WB5 and reboot. If your systray is restored (this can often work for me) manually restart WB5 at this point. You should then also get a startup manager of some type that will allow you to visually check which programs load at starup and of course a registry cleaner. These will enable you to find the culprit software that is causing the conflict and stop it from loading. I've used these methods and they work to restore order in the systray for me. Just fire up the Windows Task manager and you will see awhole lot of processes that autoload, most of them you seldom even use. When I startedup my machine one day awhile back which has a gig of ram and was left with just 450 MB of ram for programs after startup, I reliazed it was time to start blocking these autostart programs from loading. I now have far fewer software conflicts and WB5 autoloads just fine. It was all those other programs that want to put an autoupdater or 16 pt. icon in my systray so I will notice them that I gave the boot.

Successfully updated karma reason!

Try this one, I have several, this is free..... If you can't get it done with msconfig, try it.
I don't know the policy on submitting download links, so I hope I'm not doing the wrong thing here...
http://www.glarysoft.com/quick-startup/

Successfully updated karma reason!

Koasati

Join Date 07/2001

+21

BigDogFeet.... I don't see the connection between WB5 and the systray in ObjectDockPlus....

Successfully updated karma reason!

FWIW, I'm having the exact same problem. I did a search on the forums about it (still sifting through the results and interestingly, this systray problem (and variations of it) seem to affect many Stardock products. I'm guesssing this means they may share a common .DLL or something but haven't dug that far yet. There are 5+ pages of posts dating back to 2004!

There is clearly an issue here and one that seems to have evaded a fix for a long time. I'll post more if/when I learn more.

Successfully updated karma reason!