Scripting

I would suggest from the main CMD call the second cmd as cmd /c <path of the second cmd>. & Add try to use Exit command in both the CMD.
For more help you can check cmd.exe /? in the Command prompt.
I hope it will help to solve your problem. cmd

I'd abandon the Stone Age mentatility of batch-building and build a script in a more capable and robust language. That script would test for the existence of a process or processes within a timed loop and take appropriate action when time 'x' has elpased.

Believe me, I am trying to. However, I am a staff of 1 managing over 750+ computers and my free time to learn scripting is scarce.

It was a bonehead mistake in that I was using start /wait with a .cmd instead of calling it which kept it in the same windows alleviating the problem.

Hey Scab, if you'd be interested in helping me abandon the Stone Age please take a look at the question I am about to post on printer installation/vbscript in general.

Thanks,

-DHF

ORIGINAL: VBScab

I'd abandon the Stone Age mentatility of batch-building and build a script in a more capable and robust language. That script would test for the existence of a process or processes within a timed loop and take appropriate action when time 'x' has elpased.