Thank you all for your input. I've been doing some more research on this to see what I can do.
Sharp, the reason we can't use your solution, because it then keeps a user's computer unlocked for anyone to access. I don't want that :) I am trying to figure out how to programatically handle the locking (the user32.dll has a lockWorkstation() method in it), which it still may be an option. The idea I am trying to work with is a screen saver with an RSS feed. The user can then select an RSS feed which then opens up the article in a web browser. The problem I am running into is since the user session locks (as stated by the setting that Sharp mentioned), how to first allow authentication then run the Process.Start(). I'm trying to see if I can use a hook or some sort of callback mechanism, but I'm not quite sure how to get this to work (or if it can be done). My idea is to somehow "queue" up the Process.Start(..) into the windows messaging queue, or somehow provide a way to tell it to execute after the Session has unlocked. I've found ways to tell when a session is locked/unlocked, but I can't seem to figure out a way to open up my article after the session is unlocked. Now, I did toy with the idea of writing the selected article to a file, then having a windows service poll this file on a session unlock event, however I was hoping there was a way to do this without the use of a file. I think the problem is the windows login/unlock prompt doesn't come up until after the screen saver has closed. Therefore, I am unable to "queue" up any action to run after the unlock occurs. Does this help clarify my situation? Again, any input is welcome. Thanks! Alex
