Scheduled tasks in the Win32 environment (where Win32 > Win98 et al.) are dealt with via the Scheduler service, which must be running.
You enter commands to be run via a console program named at -- no relation to the Unix command of the same name. You could bundle up calls to it via the system call I guess. Come to think of it, that would probably be a good way to have to avoid learning at's syntax. I have to consult the documentation each time I use it. Otherwise I assume one could play around with registry keys, but you would have to be brave to insist on that approach.
On the other hand, Unix systems use a different facility, named cron. There are many ports of cron to Win32. belg4mit has even written a version in Perl. Play with super search for nodes on the subject.
--g r i n d e r
just another bofh
print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';
| [reply] |
The Win32 Scheduler service has two major failings. First, a single instance of a scheduled task can run no more than 1 time per day. To run a task hourly requires 24 entries.
The second major failing is of the Gotcha! variety. If a scheduled task fails, it is quietly descheduled. You have to remove and reschedule the task to get it to run again.
Go with one of the Perl replacements.
| [reply] |
| [reply] |