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.
MacTheTiger
I have tried installing the trialware via download and via SD download. I have more stability when I install the trialware then activate it through SD. All default paths.
It came in OEM stock but I removed all the freeware and it is running XP Pro SVC Pak 2 not Home. No games or cutese shareware installed either and the system has never had a virus nor has it ever become unstable. Wierd yes with SD installed.
More friendly for yah now? I think this thread may be dead now, we beat it to death in another.
Hand raised! Oooh Oooh Mr. Carter. I seem to be finding all the bugs, but then I actually "attempt" to use this product. It shouldn't be this hard guys!
Installation of WB5 likes to reset OB MCP Notfication to disable which disables the systray in OB upon reboot.
2.38.436
It makes it difficult for the average newbe to understand this behavior. Obviously upon installing OB, your Win Taskbar disappears and cannot be restored through OD, you can't get the Win Taskbar back to click on anything, it's hidden and Win Taskbar properties unavailable. While in OD, you are re-directed to OB to un-hide Win Taskbar how? Yet another undocumented SD "feature".
Thanks, but not the issue. Basically when OB is installed, the OD "hide win task bar" becomes non-functional and doesn't tell you that since OB is installed you must use OB to enable or disable "hide win task bar". Poor implementation between the two apps and not documented. At least gray out this option in OD so you have to ask why and find the answer in FAQ.
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 Y
When un-installing any one program in SD and checking delete associated skins, etc, launching SD results in loader.exe not found. So if I uninstall OB and check un-install skins, etc for this program, the shortcut for SD in Start, Programs, Stardock, SD Central is changed to loader.exe and cause XP to go searching for it. I have to change properties and get SD to point to sdcentral.exe. What's up with that?
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 Y
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 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 s
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
So you provided a more friendly means to turn MCP back on which gets turned off again by a WB upgrade or re-install?
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?
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.
So are you saying that the only two options are to clear the sub menu and close the torn off menu? In many Win apps you can re-launch the sub menu and drag the torn off menu close to where it was originally and it will snap back to it's original location off the sub menu. Once snapped back (re-attaches to the sub-menu), closing the sub menu closes the child sub menu as well. "Snap to" is also used in the context of mouse behavior where you are near a clickable item but don't have to be
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
I am a bit confused when under OB General Options, Startup Options, Run OB at startup is checked it places a shortcut in the Startup folder with the param "-startup". This causes OB to launch as well as the Theme Editor on each boot. Why? I have to remove the "-startup" param each time I change the Run OB at startup option so that only OB launches.
I have un-installed OD & WB and un-installed and re-installed only OB 2.0 with the same result. Help!
WB says I have run out of activations? Heck yes, because I have to keep re-installing it. Because every time I install another Stardock product systray disappears from Object Bar, Object Bar fails to remember I selected show the Windows task bar, and WB keeps loosing the skin I select and defaults back to Windows Classic.
Zubaz, I need for info on the re-attach ophan windows. I clicked on Programs (Stardock icon) which brought the app list up and then dragged the orphan over to where it was originally launched. It just ghosted an overlay and did not snap back to the primary app list.