>
> Hi Sean,
>
> I'm back on the topic of messages that one can send to other users
via the Task Manager/Users tab. I
> experimented with it as you suggested, and noticed that powerpro
can't detect the actual message
> window popping up on a user's desktop. I tried to trap it with the
New Windows special list, and with
> HookWindowsEvents, but they don't show it at all. How can this be,
do you have any idea? And how
> could I detect when this window is created?
OK, here is what I'm understanding now, however, I can't guarantee
it's absolutely correct as I never gave a detailed investigation on it
as this feature is not needed for me: Terminal Service. And I'll use a
bit more strict terms than before.
The current user here is the interactive user in Session 0 whereas the
target user here is the interactive user in Session 1. To exaggerate
it a little, session0 and session1 are separate computers, but not
totally disconnected, they connect to/share the same server/resource
(:kernel). So, each can know about other's kernel data (server-side),
but cannot know bout other's user data (client-side) unless a special
communication routine is set up.
So, the current user can find out what processes (i.e., pids) are
running in the target user's session, but cannot find out what windows
are currently created there (I think pids are kernel data and windows
are user data).
To conclude, I don't think PP as it is now is able to know about the
running windows in other sessions. I'm not sure if even Process
Explorer can do that. However, there could be a way that I'm
absolutely unaware of.
Sean
Attention: PowerPro's Web site has moved: http://www.ppro.org
SPONSORED LINKS
| Computer monitoring software | Power pro | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "power-pro" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
