- Jun 23, 2004
- 990
- 0
- 76
I know the purpose for each is the same, to run scheduled jobs. However, I tried to create very simple batch files and setup scheduled tasks for them under my Windows box at work.
One batch file was to reboot the computer. Simple enough? You'd think. The result is always "Could not start". However, when I right click the task and select "Run" or even run the batch file from within Explorer, it works fine. I have another batch file to backup some files, and the scheduled task for it will not run and it also says "Could not start".
At home, it took me about 5 minutes to learn the syntax of adding a line to the cron file. Also, adding scripts to cron.daily, etc. are very simple. In Linux, this stuff works, as I'd expect the same, basic functionality to 'just work' under Windows.
Linux +1, Windows 0
One batch file was to reboot the computer. Simple enough? You'd think. The result is always "Could not start". However, when I right click the task and select "Run" or even run the batch file from within Explorer, it works fine. I have another batch file to backup some files, and the scheduled task for it will not run and it also says "Could not start".
At home, it took me about 5 minutes to learn the syntax of adding a line to the cron file. Also, adding scripts to cron.daily, etc. are very simple. In Linux, this stuff works, as I'd expect the same, basic functionality to 'just work' under Windows.
Linux +1, Windows 0