CMD.EXE behaves differently if called with full path!
I've just run across a strange problem which I can't track down any
The topic already suggests, that different versions of CMD.EXE are
called, but so far I claim to have excluded this. Here's what happens:
For test-purposes I've been editing the registry with the following
@="C:\\WinNT\\System32\\Cmd.exe /E:ON /k echo %1"
-- or --
@="Cmd.exe /E:ON /k echo %1"
which apparently should be exactly the same as long as there are no two
different cmd.exe in my path. I said I'm almost sure to exclude this.
The difference in behaviour is, that the first version, using the full
path for calling cmd.exe ends up using the long-filename syntax,
whereas the second version ends up using the 8.3 (short) filename
I can't figure out why this is so, but I'd be highly interested in the
reason for this behaviour!
Any help greatly appreciated!
Regards and merry christmas,