Archived from groups: microsoft.public.win2000.setup (More info?)
Running Windows 2K Pro in development environment. We use 2 batch files in
the C:\Documents and Settings\All Users\Start Menu\Programs\Startup folder to
be started every time a user logs in. Usually this works fine but we've
noticed that occasionally a batch file will not start at log in. This
happens on different machines at different times. We've been unable to
consistently reproduce the problem. Need ideas why this happens, how to fix
it or troubleshoot further.
Archived from groups: microsoft.public.win2000.setup (More info?)
"lpmace" <lpmace@discussions.microsoft.com> wrote in message
news:CC45A9A5-60E8-4BDE-AC12-265D622CFF02@microsoft.com...
> Running Windows 2K Pro in development environment. We use 2 batch files
in
> the C:\Documents and Settings\All Users\Start Menu\Programs\Startup folder
to
> be started every time a user logs in. Usually this works fine but we've
> noticed that occasionally a batch file will not start at log in. This
> happens on different machines at different times. We've been unable to
> consistently reproduce the problem. Need ideas why this happens, how to
fix
> it or troubleshoot further.
Before you can fix the problem, you must make sure that
it exists. I recommend that you modify your two batch
files as follows:
Batch file 1:
@echo off
echo %date% %time% Start of %0 > c:\test1.log
echo User=%UserName%, Path=%path% >> c:\test1.log
c:\Tools\YourFirstTask.exe 1>>c:\test1.log 2>c:\test1.err
echo ErrorLevel of c:\Tools\YourFirstTask.exe=%ErrorLevel% >> c:\test1.log
echo %date% %time% End of task >> c:\test1.log
Batch file 2:
@echo off
echo %date% %time% Start of %0 > c:\test2.log
echo User=%UserName%, Path=%path% >> c:\test2.log
c:\Tools\YourSecondTask.exe 1>>c:\test2.log 2>c:\test2.err
echo ErrorLevel of c:\Tools\YourFirstTask.exe=%ErrorLevel% >> c:\test2.log
echo %date% %time% End of task >> c:\test2.log
Now run your system until you think one of the batch files
failed to run, then examine c:\test1.log, test1.err, test2.log, test2.err.
It is likely that they contain the information that lets you resolve
your problem.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.