Originally Posted by
James
I'm running into some trouble, and would like to get some input on this.
I wrote a program that injects a dll into an app and does "stuff" everything works fine when I run it under my account.
I setup a Windows task schedule to start the application twice a day. Once in the AM and once in the PM.
The task starts "technically" because I see it running in task manager when I monitor it, but it seems that when a task is started through task scheduler it runs in a "silent" mode of some sort. In other words it suppresses the GUI, even if I run the task under the account name that I am concurrently logged into...
This is an issue for me because my application is automated by using the GUI and interacting with the menus. It auto clicks and selects all the windows and other objects within the process until everything I want to do is finished and then the process exits.
So my question is... Do any of you know any way around this "suppressed" method of scheduling tasks. I want the process to start as though I am logged in and manually clicking on the shortcut to start an app (even though I am not logged in).
Any thoughts?