The systray should work if you are logging in as an Administrator. If you are logging in as a limited user, it should work if you start up Object Dock using the "Run As" command using an administrator login (and their might be a better way to accomplish that under XP Pro, I don't know). Generally speaking, if you log in as a limited user and just load up Object Dock, the systray won't work.

One note on the "running as" administrator - the dock settings and any themes you save will be saved under the administrator's documents - the limited user won't be able to access them without running as adminstrator (or the administrator moving them over to the ltd user's docs). I warn you about that before you create a bunch of docks thinking the limited user will be able to just use them.

Also, if you just installed the paid version on top of the free version, try ininstalling Object Dock and then just installing the paid version.

Does that help? Could be other things, which other people here would likely be better at helping with, but this seems like a good place to start.

Having said all that, there are other benefits to the paid version such as tabbed docks, multi-monitor support, multiple docks, and probably other things. I just mention that so that if the systray does turn out to be an issue for you, you at least know what else you're giving up.

I know this is a bit wordy up front, but I'm not a big fan of the drawn out 1 question at a time approach.

actually I did some testing and it appears that there was a change from 1.5-> 1.9 that somehow "broke" it. In version 1.5 the docks move across my multiple virtual desks AND the systray functions with the help of SDMCP.exe, however in 1.9 it doesnt move across the v-desktops (staying only on the main one) and the systray is non existent(both with and without sdmcp). What I would love is if someone can provide me with a 1.6 OD+ at I can try(as my reg key worked fine for 1.5+ ) so i can test is THAT's the release hat broke it or if it was 1.9.

So is the problem the limited user / admin user issue or is it something else?

Well darn. Probably best at this point to start up a ticket with Stardock Support using the form located WWW Link
(it has pull down menues to help get it routed) and reference this thread. They're good about getting back to you, you'll get an auto-response confirmation and then most likely a real response within a day or two (they are primarily Mon-Fri).

While I waa trudging back through posts I did see at least one reference to it working for someone with XP Pro 32 under Admin, but like you I didn't see anything that looks like a good solid fix for a problem otherwise.