>>I want to schedule a program to run every day, but I can't get the AT command to work (using Windows NT 4.0)
>>
>>I tried as a test:
>>
>>AT 9:00 \\ServerName\DriveName\MyProgram
>>
>>At 9:00 I see a quick flash, but the program didn't run properly (it create a new file, which doesn't exist after the test).
>>
>>I tried also:
>>
>>AT 9:00 "\\ServerName\DriveName\MyProgram"
>>AT 9:00 \\ServerName\DriveName\MyProgram.EXE
>>AT 9:00 "\\ServerName\DriveName\MyProgram.EXE"
>>AT 9:00 MyBatch.BAT (batch file that start my application)
>>
>>But everyone of these fails. The only one I got to work is:
>>
>>AT 9:00 WinMine (or other Windows program)
>>
>>The application work fine if I start it from Explorer or by the run command, but fail everytime I use the AT command.
>>
>>TIA
>
>Does it need to run a PIF file instead of the EXE. If a windows program works fine then this could be the case (especially for your BAT file - windows will not run a BAT file - it creates a PIF file to run it with).

I got this from the NT Help File

"The at command requires you be a member of the local Administrator group. Also, the at command does not automatically load cmd, the command interpreter, before running commands. Unless you are running an executable (.EXE) file, you must explicitly load CMD.EXE at the beginning of the command; for example, cmd /c dir > c:\test.out."

HTH