Thanks for the reply. Yes, at.exe is very simple but as I said, after the object gets created, it doesn't run.
For example, I issued the CLI command: at "12:30" /interactive "python.exe example.py" where example.py is some sample Python program. Well, 12:30 came and gone and nothing happened. Regards, -- John Konstantin Veretennicov wrote: > On 7/14/05, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > >>Hello list, >> >>I am having trouble working with the Windows XP Task >>Scheduler. > > > ... > > >>There is also a at.exe program which is suppose to >>have been replaced by the schtasks.exe. It's a lot >>simpler then schtasks.exe and doesn't prompt you for >>anything - it simply creates a simplified task object >>in the Scheduler folder for you. However, when the >>time come to execute, nothing happens. > > > At.exe + subprocess module should be fine. Are you able to schedule > tasks with at.exe manually from command line? You may need to > double-check datetime format and "/interactive" switch. > > >>Does anybody know of any other way to interact with >>the Scheduler? Hopefully, this is something that can >>be accessed from Pythonwin32, rather then through the >>CLI programs. > > > I guess you can control it via ITaskScheduler COM interface: > http://msdn.microsoft.com/library/en-us/taskschd/taskschd/task_scheduler_start_page.asp > But calling at.exe is simpler IMO. > > - kv > > _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32