Only the first line of the batch files executes, then ALL pcs cras

[Guest]

Hello,

I got permission to run my code on all 60 machines in a lab over the
weekend.

I log into all 60 machines. I run a .bat file with several lines in it [i.e.
run.exe -p par1.txt
run.exe -p part2.txt
etc]

I run it on only one machine. When it stops executing the first line of the
bat file, the pc crashes, and ALL machines crash, and restart in "maintenance
mode" with the keyboard and mouse disabled.

Would you have any ideas about how I can ensure that only one pc crashes
[and doesn't drag all others with it]?

Would you have any ideas about the reason I can't execute a bat file with
more than one line in it? [If not - what would be a good group to ask about
this issue?]
I used to run this code [using bat files with multiple lines in it] on
Windows 2000, and everything worked...

Thank you for your help!!

 

[GTS]

Running a batch file with more than 1 line isn't a problem. What is the
program you're running doing that it causes these crashes? Have you run
your commands manually on an XP machine? Do they work correctly? Is the
second line dependent on completion of the first? If so your command should
be >start /w run.exe -p par1.txt so the second launches after the first
completes.

 

[Guest]

Running a batch file with more than 1 line isn't a problem. What is the

program you're running doing that it causes these crashes?

It is my personal program [which took years to debug, and that workes well
in Windows 2000 environment.

Is the
second line dependent on completion of the first?

Not really, but the second line should execute when the first line finishes
executing.
Otherwise, if both are run at the same time, it will overwhelm the CPU and
take up all available RAM.

If so your command should

be >start /w run.exe -p par1.txt so the second launches after the first
completes.

Thank you!! I will try it later tonight. It seems that this might resolve
my problem!
Is it the case that Windows 2000 doesn't require the addition of ">start /w"
in front of line 1 to make line 2 run after line 1 completes execution?

Would ommitting ">start /w" in Windows XP result in the machine crashing?

Once again - thank you!

 

[GTS]

You're welcome. The execution of batch commands and the start /w use is
basically the same in XP and Windows 2000, so I don't know if this will
solve the problem. Good luck.
--

Running a batch file with more than 1 line isn't a problem. What is the
program you're running doing that it causes these crashes?

It is my personal program [which took years to debug, and that workes well
in Windows 2000 environment.

Is the
second line dependent on completion of the first?

Not really, but the second line should execute when the first line
finishes
executing.
Otherwise, if both are run at the same time, it will overwhelm the CPU and
take up all available RAM.

If so your command should

be >start /w run.exe -p par1.txt so the second launches after the first
completes.

Thank you!! I will try it later tonight. It seems that this might
resolve
my problem!
Is it the case that Windows 2000 doesn't require the addition of ">start
/w"
in front of line 1 to make line 2 run after line 1 completes execution?

Would ommitting ">start /w" in Windows XP result in the machine crashing?

Once again - thank you!