Unexplained cmd.exe closure

[Walter Briscoe]

I run an XP (no service packs) cmd.exe in a W2K SP 4 environment so my
commands are limited to 8 rather than 2K bytes.

Randomly - with a MTBF of the order of an hour - cmd.exe shuts down. I
have taken to running it via stacked.cmd with the following contents:
cmd
echo unstacked; errorlevel=%errorlevel%

This shows the end of a run.
W:\source\bld\sdk\rc\rcos2\os2386 ) dir /s/b d:\sed.exe

d:\wfb ) echo unstacked; errorlevel=-1
unstacked; errorlevel=-1

d:\wfb )

When I set up the same environment again, dir ran normally and cmd did
not terminate.

Has anybody here a suggestion of possible mechanisms?

 

[Marty List]

Have you tried CMD.EXE from SP1 or SP2?

 

[David Wang [Msft]]

"unexplained closure" usually implies a crash of some sort. I suggest
launching cmd.exe under the debugger (like NTSD.EXE which comes with the
OS), and then go about your business -- and when the cmd.exe "unexplainably
hangs", go see if anything is caught in the debugger.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
I run an XP (no service packs) cmd.exe in a W2K SP 4 environment so my
commands are limited to 8 rather than 2K bytes.

Randomly - with a MTBF of the order of an hour - cmd.exe shuts down. I
have taken to running it via stacked.cmd with the following contents:
cmd
echo unstacked; errorlevel=%errorlevel%

This shows the end of a run.
W:\source\bld\sdk\rc\rcos2\os2386 ) dir /s/b d:\sed.exe

d:\wfb ) echo unstacked; errorlevel=-1
unstacked; errorlevel=-1

d:\wfb )

When I set up the same environment again, dir ran normally and cmd did
not terminate.

Has anybody here a suggestion of possible mechanisms?