What's with the enable MCP 0/1 in the common Win reg folder for SD?

from Stardock Forums
This is getting really annoying. WB creates a regedit entry under HKEY_CURRENT_USER Software/StarDock/Common labeled MCP enable / disable and defaults MCP enable to disable which causes the systray in OB to disappear. You have to use regedit to re-enable with a "1" and reboot. OB systray comes back, but your installed skin may not and WB shows the last installed skin as untitled until you perform a refresh. I am also not a believer in the SD support answer to install the latest MCP, that is not the problem. If you install it, systray comes back "until" you re-install or upgrade WB.

So far SD Desktop Suite (MSRP $50) has proven to me that this product has not been through QA as each program seems to step on the other. I am playing with two WB skins, Kol's Tiger 2 (which is excellent) when WB actually works and Steve's Tiger which is more Panther like with barber shop scroll bars. SD also needs to seriously look into hardware registration to remove the WB activation limit.

Yes I would like cheese with my whine. This is nuts!
objectbar
742 views 8 replies
Reply #1 from WinCustomize Forums Top
edit - nm
Reply #2 from Stardock Forums Top
More friendly for yah now?

I think this thread may be dead now, we beat it to death in another.
SoundPackager - Customize the Windows sound scheme
Reply #3 from WinCustomize Forums Top
I've never had WB do that on a reinstall or upgrade - I have the full Object Desktop (3yrs now)

The only one I had step on another was IconX and DesktopX = run at startup - they used to be tied together than became separate programs - dtx run at start used blank out iconx run at start
Reply #4 from Stardock Forums Top
WB creates a regedit entry under HKEY_CURRENT_USER Software/StarDock/Common labeled MCP enable / disable and defaults MCP enable to disable which causes the systray in OB to disappear. You have to use regedit to re-enable with a "1" and reboot.


Hmm, Although I don't have WB or OBar installed I *do* use OD+ that uses the system tray feature. I enabled it through SDC and it runs from the registry location:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Notify (it's called MCPClient).

I also have the registry entry you mention above, and it is set to 0 yet the OD+ system tray comes up fine every time.

I'm not sure if your config is meant to be an alternative activation method when you install the Stardock apps from outside of SDC (just guessing this last part since you don't mention whether your apps came via SDC or individual purchases).

Reply #5 from Stardock Forums Top
WB seems to be the one that throws the wrench into the works. It's like this; OB overrides OD's auto hide the task bar, and it appears that WB overrides OB's MCP setting.
Reply #6 from WinCustomize Forums Top
WB does not use the MCP and never has done.  It should not be touching that registry key.
Reply #7 from Stardock Forums Top
So far I have installed most everything in ObjDesktop and then removed them all except WB, OD, & OB. So what beauty left this gift behind in the registy? It does seem to effect OB's behavior when displaying the systray.
Reply #8 from Stardock Forums Top
So far I have installed most everything in ObjDesktop and then removed them all except WB, OD, & OB. So which beauty in the ObjDesktop suite left this gift behind in the registy? It does seem to effect OB's behavior when displaying the systray and leaving behind a default of 0 seems to be a bad thing.