Sounds like a PEBCAK issue.
How about you present us with an example of your scheduled job (and
the script contents) before leaping to weird, unfounded conclusions?
I have lots of batch jobs running in NT/2000/XP via AT
>at
Status ID Day Time Command Line
----------------------------------------------------------------------
---------
1 Each M T W Th F S Su 5:00 AM
C:\Scripts\Bat\UpdateReports.BAT
2 Each M T W Th F S Su 5:00 AM
C:\Scripts\Bat\MoveMail.BAT
==============================================================
ASB - http://www.ultratech-llc.com/KB/?File=~MoreInfo.TXT
==============================================================
"Do witches run spell checkers?"
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Adam Smith
>Sent: Monday, October 08, 2001 7:06 PM
>To: NT 2000 Discussions
>Subject: AT Service
>
>
>
>Hiyaz,
>
>The Windows NT 4.0 "AT" service does not launch any Non
>32-bit programs
>(ie batch files) when they are scheduled to be run.
>
>It's totally idiotic and rediculous that such an operating
>system should
>be designed with such flaws, but hey, do I look like *I'm*
>complaining?
>
>--anyway--...
>
>I did some experimenting and the AT service runs any 32-bit program
>correctly, such as Explorer.exe or any other process I tell it to,
>however when scheduling a .CMD file to run just completely
>shits itself
>and the CMD never runs.
>
>
>Any ideas (besides 'move to unix')
>
>
>
>Adam Smith
>IT Officer
>SAGE Automation Ltd
>
>[EMAIL PROTECTED]
>http://www.sageautomation.com
>
>Phone: (08) 8276 0703
>Fax: (08) 8276 0799
>Mobile: 0414 895 273
>
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
