Quote: I tried it on both my system (Windows XP) and the test one and it ran fine on mine: "C:\WINDOWS\system32\cmd.exe" is a valid path!
I just got an @ERROR of 255 and no output when trying the same code on the test system.
I guess that's why I'm asking about the internals of the shell command, but maybe this is related to CMD.EXE? I looked through autoexec.nt and config.nt on both my system and the test one and found no differences. These two files may only affect things executing under COMMAND.COM, though.
Urk! That's truly bizarre
Sorry for asking again, but are you sure that "%COMSPEC%" on the failing system points to a valid exe?
I have seen instances where %COMSPEC% is set to an expected (and apparently valid) value, but the actual EXE is not at the location.
Try typing at the command prompt: Code:
%COMSPEC% /C echo OK
on the failing machine.
Welcome to my world
I just ran what you asked me to and got...
Code:
Microsoft(R) Windows NT(TM) (C) Copyright 1985-1996 Microsoft Corp.
