Start Menu Button

from Stardock Forums

I am using ObjectDock 1.90 Plus / Build 535U on WIndows XP Pro SP3. When I login as a Power User, I get the following message when clicking for the second and each subsequent time on my OD created Start Button;

"StartMenu helper file was injected but failed to take effect. Can not show start menu at this time, please try again."

When I click on it the first time, the start menu shows, but any expanded menu choices show up behind the start menu graphic.

This is only happening when I am logged on as a "Power User" under Windows. It does not happen when I grant myself Administrator privileges under this same account.

I have seen a few posts relating this same error, I have tried the suggestions and none have worked. Is there another suggestion anyone may have?

David

 

I just noticed the systray is not showing under this power user as well.

objectdock
15,298 views 5 replies
Reply #1 from WinCustomize Forums Top

Start menu - Best solution I know of is the vbs approach:

Create a new text file using notepad in the directory you want to save the vbs file to.  Copy/paste the following text into it:

set wShell=wscript.createobject("wscript.shell")
wShell.sendkeys "^{ESC}"

Save the file as or rename it to something e.g. StartMenuOD.vbs  Create a shortcut to that file in object dock.

Systray - Best solution I know of is to start up Object Dock by right-clicking on the OD icon instead of left-clicking on it, then selecting "Run As" and running it as a user with adminstrator rights.  You will be saving themes, opening themes, modifying themes of the administrative user though, not as the logged in Power User.  i.e., if you modify a theme while doing this, the next time you log in as the admin user the theme will reflect the changes.  You likely would want to save the Admin's themes and the Power User's themes with different names so you can load each up when you want.

+2 Loading…
Reply #2 from Stardock Forums Top

Thanks for the script. It appears to perform the same function as the Windows key.  ("^{ESC}") I ASSUME the ^ is for the control key.

As for the systray, I guess I will just have to TEMPORARILY re-enable the Windows taskbar and hide it off-screen. I access quite a few items from there. I appreciate the suggestion, but I really do not wish to have to remember to sync different profiles for OD. My administrator account does not have OD enabled or any other eye candy for that matter. It is just a basic reminder to turn off my WiFi when I log on to this account.

I am now trying to think outside of the box and figure another way to access these systray items through ObjectDock. The only way to access my firewall is through systray. I am using Kerio 4 and I get a login (name/password)box when I try to access it any other way (and it won't let me connect to it) and I haven't delved into that issue yet. But, this may be my opportunity to finally get that resolved. But, I digress.

Thanks for the help and suggestions. This program has increased my ability to work quicker in Windows. So, it is a pleasant break from the usual PC's I am asked to troubleshoot and a definite difference from my ho-hum machine at work.

I am still open and willing to try any other suggestions.

David

Ashes of the Singularity II
Reply #3 from WinCustomize Forums Top

My administrator account does not have OD enabled or any other eye candy for that matter

If there's only one user actually using Object Dock then there's really no problem, the config files will just be sitting under the admin's docs.  It only becomes an issue if more than one logon is using Object Dock with the Admin logon or "Run As" and therefore sharing the config files.  That's when it becomes tedious.  Executing the "Run as" is a bit annoying to me in itself, but like I said, best way I know of to deal with it.

In case it interests you, the "Run As" only needs to be executed once per logon session to kick-start the systray service as long as a theme is loaded that includes the systray dock (e.g., the Admin theme even if Admin never actually uses it).  Once a systray dock has been loaded during the current user session you can unload Object Dock, then restart it again with the usual left-click and the systray will work and you'll be back to using the logged in user's settings.

Reply #4 from Stardock Forums Top

"I SEE!!!!" says the optically challenged person.

I will use that piece of information in my new configuration.

I am getting an error on several OD shortcuts even when using the aforementioned "Run as...." command. They are all system programs and/or programs that make use of system programs. I will continue to work on those as well.

Reply #5 from WinCustomize Forums Top

Just playing with Computer Management which requires permissions here's what I see while under a Limited Logon:

If I leave OD loaded with the Admin run as, a Computer Mgmt shortcut on the dock will execute with the Admin rights with a usual leftclick - the Admin rights carry through.

If I then unload the Admin OD startup and reload OD normally, a leftclick on Computer Mgmt will behave as it usually does when launching under a limited user - crippled.  You can right click on the OD icon and use the "Run As" for the individual shortcut from there, entering the Admin info at that point to have the app run with rights.

Might very well depend on exactly what you're trying to launch.  The 1-time Admin "Run As" / Unload-OD / Restart-OD-normally just gets the systray service started though, it doesn't retain rights for all the shortcuts (and that makes sense to me).