Powerpro uses global hooks, which cause a powerpro dll to run as part of another program. According, to this microsoft article: http://msdn.microsoft.com/en-us/library/aa905330.aspx under the section User Interface Privilege Isolation, this should work in all cases where powerpro has equal to or greater privileges that the other program. That is why I don't understand the case where powerpro running as admin does not work. Maybe something in the article will help you figure it out.
--- In [email protected], "ligoten" <ligo...@...> wrote: > > You just gave me an idea for a test, and it had interesting results. What if > the hooks don't work if PowerPro is running at a DIFFERENT privilege level > than the launched app, not just if PowerPro is at a particular privilege > (administrator)? I just tried running PowerPro as an admin and then made sure > to start my other 32-bit program (SpaceMonger) as an admin too. If PowerPro > is at admin, SpaceMonger only triggers the test message if it's at admin too. > If PowerPro isn't at admin, then SpaceMonger only triggers the test message > if SpaceMonger is also not at admin. > > --- In [email protected], "brucexs" <brucexs@> wrote: > > > > > > > > --- In [email protected], "ligoten" <ligoten@> wrote: > > > > > > No, but I did try that; once again PowerPro only caught programs launched > > > by PowerPro. > > > > Based on my reading of the MSDN docs, this sounds like the behavior you get > > if Powerpro is running at a lower privilege level than other programs. > > Since it is running as admin, I am afraid I am out of ideas. > > >
