Published on October 29, 2010 By Nimbin In ObjectDock

ok i have objectdock 2 and when ever i reboot i notice in task manager that objectdock now has 2 processes loaded instead of 1. 1 process being objectdock.exe and the other being objectdock tray.exe. The 1st one is cool because it's needed but objectdock tray.exe didn't ask for permission to run on startup. it can be killed with no effect on OD 2 and there is no where in the settings that enables me to stop this from loading. Whats it for? why do i need it to run? why can i turn it off with no effect on OD 2. and the big question, why is it loading without my permission?


Comments
on Oct 29, 2010

You did give it permission..... it's Aero Peek.

on Oct 30, 2010

You did give it permission..... it's Aero Peek.

 

On Windows XP?

on Oct 30, 2010

On Windows XP?

 

No, it's the Aero Peek option in OD settings.....

on Oct 30, 2010

No, it's the Aero Peek option in OD settings.....

 

enable aero peek on running tasks was not checked. i made doubly sure of it. even checking it then unchecking it. rebooting and still objectdocktray.exe

on Oct 30, 2010

it's Aero Peek.

On Windows XP?

Yes and yes, I have aero peek enabled, killed objectdocktray.exe in task manager, moused over an icon of app that was running, objectdocktray.exe started again to allow aero peek.

on Oct 30, 2010

I suspect it may be loading for the same reason WFX has wfx32.exe and wfx64.exe running, even when WFX is disabled. See reply 30 here.

 It could be a permissions thing. I can live with it but I still blame MS. 

on Oct 30, 2010

I don"t know what any of you people are doing.....

In OD, if the option is un-checked, it doesn't run. Period.

In FX, if the app is disabled, it doesn't run. Period.

If you have any "things" running and they shouldn't be, you have bigger issues then a few permissions and legit services.

 

on Oct 30, 2010

In FX, if the app is disabled, it doesn't run. Period.
I quess you didn't read reply #29 and #30 by Neil Banfield. 

Those processes are left running in WFX even when the app is disabled. If you kill them in TM then they have to be manually restarted to use WFX.


 

 

"Unfortunately that would require the process to elevate itself in order to disable the processes and likewise elevate to turn itself on.  Generally speaking this isn't exactly user friendly and the processes have been designed to use as little memory as possible.  Throw in the possibility of multiple users who may or may not want the app and you end up needing at least one process at all times - the service.

Thats not to say we will not look into the possibility of it shutting down one of the additional processes if it proves viable without producing a poor user experience."

I don't make this $h1+ up.

on Oct 30, 2010

Wiz-

I read it. I understand what you're saying, but what I said was that the FX app was not running. Wfx 32/64 process is a like a zillion other 'service/app processes' on your machine running background waiting for the pleasure of a startup command from you. The only difference being you can see wfx in TM. So what? It doesn't help nor hinder anything.

We OK now Honey?

on Oct 30, 2010

I don't make this $h1+ up.

Oh yeah....

There is something really wrong with your machine...

 

 

....it can't spell shit.

on Oct 30, 2010

I'm just fine now.