I don't have any petter idea why this is than you do, but I created a 32-bit Vista virtual machine and ran the same basic test; install PowerPro, configure an Open commandlist to fire a messagebox when when Notepad is run, run PowerPro as admin and Notepad as both admin and not admin, then re-run PowerPro not as admin and Notepad both as admin and not as admin. In all cases, the PowerPro messagebox only popped up when PowerPro was at the same privilege level as Notepad. I have also re-tested Open list behavior under XP and everything works perfectly there, so it seems to be a problem produced by the changes made in Vista and later opertaing systems, both 32-bit and 64-bit. Under 64-bit Vista+, there is the added problem of PowerPro not capturing 64-bit applications. Unless someone else knows a workaround to fix the privilege level issue, I think I'm going to have to call this a bug.
--- In [email protected], "brucexs" <bruc...@...> wrote: > > 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" <ligoten@> 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. > > > > > >
