This article was previously published under Q138340
This article has been archived. It is offered "as is" and will no longer be updated.
After you start a non-interactive application with the AT.EXE schedulerprogram, one or more of the following symptoms occur:
The application appears to hang.
The application remains loaded in memory even though it should quit.
You are unable to quit the application.
You can see the process with Process Viewer but Process Viewer is unable to kill it.
If the application is trying to access a device, for example a tape drive, you cannot access the device until the application is cleared from memory.
Memory is not freed if the application fails, and if different applications are hung in memory, system performance degrades.
Some applications allow multiple instances; and if they do not clear from memory, performance degrades.
NOTE: Applications you start with the AT.EXE command, by design, do notappear in Task Manager.
To remove the non-interactive application from memory after it does notquit, do one of the following:
Reboot your computer.
Use the Windows NT Resource Kit utilities TLIST.EXE and KILL.EXE. These utilities allow the administrator to detect and then clear the application from memory based on the application Process ID.
Tlist.exe and Kill.exe utilities are available in the Windows NTResource Kit versions 3.1, 3.5, and 3.51. Help for both utilities isavailable from the command line. (For a hung process use the Kill -fOption.)
NOTE: AT Scheduler has no way to control an application already started.