On Wed, Dec 10, 2008 at 12:54 PM, Alex <[email protected]> wrote: > > Hello all, > > I was looking to try to develop a screen saver type application that > would allow users to click on items which would then start a new > process to handle the clicked on items (links, files, etc.). > > My problem is, my computer "locks" itself when the screen saver comes > on (Windows login screen), so it doesn't seem like I can start any > process until a user logs in (which makes sense). Is there a way to > queue the process.start up to execute only after the user has logged > in? > > So generally I would like the process flow to be: > > Computer Locks > Application runs and user clicks on something to start a new process > User is prompted to login > Process runs > > Is this possible? Thanks for any insight!
I remember in older days, Novell did hook into the login process. I have not seen an API from MS to handle something like this. Maybe if you are an MS partner you could get this info? Anyway, why would you want a user to click on something after the computer locks, but before MS Windows can authenticate? Wouldn't you want to authenticate BEFORE you start your process? Or are you trying to do some type of keylogger? Why would you start a new process when a user "clicks" on something before they authenticate? Your steps where: > Computer Locks OK. No biggie. > Application runs and user clicks on something to start a new process Why would an app run before a user authenticates? > User is prompted to login Again, why would/should a user login if you started a process without their knowledge/consent? > Process runs What process?
