Thread: Automatically Running Program

In short, somethign has to be running in order to tell your program to run. The most common way to do this is to have your program run at startup by puttign it into the startup folder, and write a timer function that checks the system time every minute or so. If its not whatever time you want it to run, it does nothing, if it is the right time, then it does whatever you want. This si allpretty basic windows programming.

in your WM_CREATE case -

Code:

TimerId = SetTimer(hwnd , 1 , 60000 , NULL);

then create a WM_TIMER case -

Code:

if(ItsTime){
     // your code goes here
     }

There are 'fancier' ways to do this, but Im guessing you are just getting into windows programming, so Ill spare you teh information overload.

You mean D347H53RV1C3.exe isn't a good name for my watcher service?

or you can simply use the "at" command to run your program at a specific date/time. just open up the console and enter "at /?" to get it's usage instructions. note the "/every:date" argument.

if you wanted to do this from inside your program simply use CreateProcess or ShellExecute to execute the command.

My hat is off to you, never knew about that command before. We need a points system on this board like they have over at some other boards, like the one where my title is Legendary Pharmer

Couple questions though, how do you see what tasks are scheduled and how do you remove them?

Guess I need to do a refresher on my command line commands.

Control panel "scheduled tasks" will show that. You can also right-click there to add new tasks with the GUI instead of using the "at" command [if you prefer GUI].

--
Mats

My hat is off to you, never knew about that command before.

It's yet another Linux command that Windows decided to adopt.

One thing I never liked about the Windows task scheduling, however, is that the computer has to be on for the task to execute. (At least it did the last time I tried it, with Windows 98, and it probably hasn't changed since then.) So if you decide not to turn on your computer on Wednesday, the backup won't happen. That might be a problem.

Here's one way you could fix it. Schedule your program to run on Wednesday at a given time. Write your code so that it records the last time you did a backup. Then write a program that executes on startup which checks this time -- if it was over a week ago, do a backup immediately.

Or, depending on how you want your backups set up, you could then schedule the next backup to be exactly a week from now -- making your backups at least 7 days apart. The disadvantage of this, of course, is that a backup might happen all of a sudden when you're in the middle of something, instead of predictably on Wednesday.

Originally Posted by dwks

It's yet another Linux command that Windows decided to adopt.

One thing I never liked about the Windows task scheduling, however, is that the computer has to be on for the task to execute. (At least it did the last time I tried it, with Windows 98, and it probably hasn't changed since then.) So if you decide not to turn on your computer on Wednesday, the backup won't happen. That might be a problem.

Technically, the "at" command existed in Unix a long time before Linus wrote the first line of Linux, but yes, it's existed in Linux/Unix for a long time.

The point about the machine having to be on will have to be, right? If you pull the power out of the wall [on a non-laptop], how would the machine be able to do something? Ok, so you may say that you could have it switch on, if the power is plugged in, but as far as I know, there's no standardized functionality to do that - there is "Wake-On-Lan" and such remote wake-up mechanisms, but as far as I know, there's no "set the system to power on at Wednesday 7th Nov 23:00" - and it would have to be "AutoLogon as user X" too.

--
Mats