Oma, Sounds like a memory problem starting the batch file. What if you make a shortcut to your batch file and make the appropriate memory settings on the shortcut. Then run the shortcut instead of the batch file in your AT service. Troy ===== Original Message from [EMAIL PROTECTED] at 6/18/01 11:52 am >I'm using AT service in NT 4.0 Server(SP5) to run Rbase 6.5 Windows to >perform a automatic backup and verification routine. > >I'm setting the AT this way: >Option 1 >at 21:00 /every:M,T,W,Th,F,S "d:\bat\autoback.bat" >Option 2 >at 21:00 /every:M,T,W,Th,F,S cmd /c "d:\bat\autoback.bat" > >but not both at the same time! > >Autoback.bat is like this: > >rem rename current rbase.dat to rbase.cur to hold normal login settings >rename d:\newdixie\rbase.dat rbase.cur > >rem rename rbase.bak to rbase.dat for automatic backup settings >rename d:\newdixie\rbase.bak rbase.dat > >rem start rbase >start "Rbase Backup" /dd:\newdixie /high /wait rbg65.exe > >rem rename rbase.dat to rbase.bak to hold automatic backup settings >rename d:\newdixie\rbase.dat rbase.bak > >rem rename rbase.cur to normal login settings >rename d:\newdixie\rbase.cur rbase.dat > >exit > > >The rbase.dat is the normal login startup and the rbase.bak is the >autobackup routines. > >I can run the autoback.bat at the command prompt(window) and it runs fine. >But if it is run from the AT command(using either options above) it hangs >and does not complete the batch file! Rbase remains as a process but not as >an application in task manager. > >Does anyone have any suggestions or alternatives??? The client wants to >eliminate the human element for running this routine.(their people can never >remember to run this each afternoon before they go home) > >Thank you, >Best regards, > >Oma Cox
