Windows Forum

Ask something
Discussion Locked

Using the AT command in NT

0 helpful
7 replies

by mwc

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I feel really dumb. Using the AT command (scheduler service is running)in nt to do simple xcopy commands on my network. Works fine when using *.exe but when using *.bat the command window opens and closes without completing a simple xcopy command onmy network. *.bat runs fine from the command prompt but will not run from AT 17:30 driveletter:\*.bat. I am logged in to the Novell network and have proper access rights. Would like to learn more about this and writing scripts in nt do you have anysuggestions or a web site with some good info on using AT commands?

7 replies

by icrovop

I tried finding you a copy of Winat. Microsoft's GUI version of the scheduler, but it seems to dropped of the face of the internet. You can however, download and install IE5 with the offline browsing pack. this will install MSTask. This is a GUIprogram also.

You can also check here for a possible solution to your problem. http://support.microsoft.com/support/kb/articles/Q142/4/32.asp?LN=EN-US&SD=gn&FR=0&qry=at%20scheduler&rnk=11&src=DHCS_MSPSS_gn_SRCH&SPR=NTS40

try these 2 links for more info on scripts and batch files
http://www.robvanderwoude.com/index.html
http://www.cableyorkton.com/users/gbraun/batch/

by lo

Hi - I don't do a lot of AT, but I do a fair amount of .BAT so ... And besides, I will watch the post to see what/how.

AT is relatively simple. If you HELP AT, that is about all it does and has. There are not other commands, just switches that give the AT program parameters, etc.

I am assuming that DRIVELETTER is a .BAT on your system and .\*.bat is an argument to that procedure but, that is just a guess.

If you are copying to the system the AT is executing from, it is possible you are overlaying the file you are executing (DRIVELETTER) and that is causing an abort.

Might post the file (with changes to anything that might be confidental).

Humm, looking it looks like driveletter:\*.bat. Not sure what what would do. The argument to AT is an NT Command, either an executable, .COM, .EXE or a .BAT file. If driveletter:\*.BAT is something like C:\*.BAT, that is a path/file and would be an argument to a .COM, .EXE or .BAT

Might try AT 17:30 XCOPY x:\*.bat y:\*.bat
or put XCOPY x:\*.bat y:\*.bat into a .BAT file and then AT 17:30 . x: and y: would be real devices for your PC and/or network.

by don christner

Your problem usually happens when people first start using AT. If you are not launching an EXE file, you must preface calling the BAT file with CMD /C.

Go to Start|Help and then type at. It will give you three topics to look at. Print out allthree and read them. In the last topic, there is one little mention of using CMD /C.

Don

This discussion is closed to new replies.