Systray does not display w/downloaded via SD, does when installed as trialware

Grab the lastes stand-alone MCP from here.  That should fix you up

I have been using ObjectBar 1.99e for a long time now, and just today I have noticed this behavior too. None of my system tray icons will display when OB is running. I have even tried to run "trayserver.exe" and that didn't help.

Can someone see what is up? This is VERY annoying!! I will have to turn off ObjectBar until this can get resolved. Grrrr!!!! OB is my favorite of the Stardock apps. Esp. the virtual desktops. Please hurry!

Einstein47

Ok - call me blind - I just saw the link in the post above mine, and after an install and reboot my systray is back. I should have known that uninstalling the MCP on Win2K was a BAD THING. I was just wanting to see the memory footprint of MCP - thinking I would easily be able to reinstall it from SD Central. Boy was I wrong.

Today's lesson boys and girls - never uninstall anything unless you are 100% sure you can reinstall it later. Because you just never know.

The actual repair for this issue is to go into regedit and find HKEY_CURRENT_USER, software, Stardock, Common. You will find a registry value that sets MCP to enable or disable. "One" of the SD products likes to set this value to disable which causes systray to disappear in OD.

NO this is NOT the actual repair. You need the file SDMCP.exe loaded as a process to "create" Systray equivalents within ObjectBar, ObjectDock, Right-Click and DesktopX.

The way to set it is to open Stardock Central > Tools > Settings > under "General" check "Enable MCP notification area support" > then REBOOT. Now you should have Systray ability in all Stardock programs. What Zubaz gave you is a link to a "Standalone" fix for people not using Stardock Central. If you not installing your Stardock software this way (which ain't too bright) you can get it HERE

Yes, and re-installing WB turns off Enable MCP notfication and the OB systray disappears. So you provided a more friendly means to turn MCP back on which gets turned off again by a WB upgrade or re-install?

I only installed WB once. So if it was turned off then I turned it back on.....once.

I've reinstalled WB a couple of times in 3 yrs and have not yet had to turn back on mcp - and i do have it enabled in SDC

I've been using WB since version 2 and have upgraded at least 30 times and have yet to have it to turn off. I use ObjectBar daily on my home machine with the systray and Object Dock daily on my office machine with the systray so I would've noticed. If this was happening to a large number of people then there would be a large number of threads to that effect. Yours is the only one I've seen so it must be something unique to your setup.

The average person is going to install OB, OD, & WB, so then the OB systray disappears or they select display beta releases and upgrade WB and they know where to find out how to fix the systray issue how? OB & OD don't have beta releases currently. So it's logical the average person is going to install the freeware, decide to purchase, install SD, & upgrade WB to beta and loose the OB systray.

Nothing unique or special about my system. These are inconsistencies in the SD Object Desktop software. Adding Icon Packager, Theme Manager, DesktopX only seem to exacerbate the combination of config issues.

All trail versions require that you uninstall them prior to installing the full version. Based on your timeline above you skipped that part. This may be what has caused your issue.

I'm average
I run OB, DTX, WB
I figured it out

I run betas and don't lose the tray

No Troll......your special.....

I un-installed all the freeware, deleted the Stardock folder in C:\Documents & Settings\user id\local settings\Application Data\Stardock. Deleted the HKEYS_Current_User entries for Stardock out of the registry, deleted the files in C:\Documents and Settings\user id\Local Settings\temp, and deleted C:\Program Files\Stardock. Then I re-booted and re-installed SD and used SD to re-install WB, OB, OD. So here I am today, screwed and out of WB activation attempts.

Did I miss something? And some software companies even make installers that detect the freeware version and remove it before installing the licensed version.

Sounds comprehensive. Try the zapper. Back up your skins first.
ZAPPER

It also would be nice if someone could restore my WB counter. I'll try the zapper, but nothing will come back together until I can get WB back in working order. SD really needs to impliment hardware registration to avoid this kind of crap.

I believe your count has been reset.

If you are constantly reinstalling WB and somehow managed to hit the limits (which is most unusual - even I have never hit the limits), it would be wise to backup sig.bin from the WB dir and put it back after reinstalling and so avoiding the need to reactivate.

If you only knew the number of days and nights I have been trying to get WB, OD, OB to integrate together. Hardware registration would be a plus to implement, then you would realize that I only have the software installed on a desktop & laptop and if SD noticed to many "matched" hardware activation attempts (I suggest allowing 3 max), SD could send an email saying "can we help you?".

I have learned much through this exercise, but I shouldn't have had to.

Most important, Thank You!

I can see OB + OD+ have systray issiues (had issues with IconX and DTX's run at startup) - but I don't see how WB factors in.

Installation of WB5 likes to reset OB MCP Notfication to disable which disables the systray in OB upon reboot.