WinXP cmd.exe renamed to command.com

[Peffse]

Hey, I'm curious... does KernelEX have any effect on those dependencies awergh mentioned?

[PROBLEMCHYLD]

I'm not sure which version to install

http://cygutils.fruitbat.org/consize/index.html

[PROBLEMCHYLD]

if i renamed the file to Cmd.exe and run this batch file here

http://www.infionline.net/~wtnewton/batch/fixcmd.htm

can i use this as default?

[os2fan2]

Win95cmd comes in two versions: NT4 = 233k and NT5 = 307k. These were released as part of the SDK, but have become loose-distributed.

If you want functionality to match the 2K/XP cmd.exe, ye need to download the larger one (NT5). The smaller one emulates NT4's cmd.exe. In any case, putting it into \windows\command is a useful thing, because ye might want start | run | cmd.

I don't think it's a good thing to set COMSPEC globally to it, but you do need to set comspec in its session for things to work properly, ye use this reg file.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]
"AutoRun"="set comspec=c:\\windows\\command\\cmd.exe"
"PathCompletionChar"=0x00000009
"CompletionChar" = 0x00000009

The first sets the comspec (ye need to change the path and exefile name, if Windows is not in c:\windows.) Pathcompletion sets tab to scroll through partly completed paths.

[PROBLEMCHYLD]

What about this reg file

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]

"AutoRun"="SET COMSPEC=C:\\WINDOWS\\Cmd.exe"

[HKEY_LOCAL_MACHINE\Software\CLASSES\.cmd]

@="cmdfile"

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile]

@="Windows NT Command Script"

"EditFlags"=hex:d0,04,00,00

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell]

@=""

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\open]

@=""

"EditFlags"=hex:00,00,00,00

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\open\command]

@="C:\\WINDOWS\\Cmd.exe /C \"%1\" %*"

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\print]

@=""

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\print\command]

@="C:\\WINDOWS\\NOTEPAD.EXE /p %1"

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\edit]

@="&Edit"

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shell\edit\command]

@="C:\\WINDOWS\\NOTEPAD.EXE %1"

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shellex]

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shellex\PropertySheetHandlers]

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\shellex\PropertySheetHandlers\{86F19A00-42A0-1069-A2E9-08002B30309D}]

@=""

[HKEY_LOCAL_MACHINE\Software\CLASSES\cmdfile\DefaultIcon]

@="C:\\WINDOWS\\SYSTEM\\shell32.dll,-153"

Edited July 29, 2008 by PROBLEMCHYLD

[os2fan2]

That works too. It just does not handle pipes though.

Solution: Use both.

[3dnowex]

the version of win95cmd.exe is 5.00.2144.1,seems from Windows 2000,

Can any body find one in Windows XP sp2(5.10.2600,or hihger)?

3Q!

[os2fan2]

cmd.exe in Windows 2k is the same as the one in xp. So the 5.00. version will handle all of xp stuff.

I suspect also that there is no version to match xp, since by this time, development on the win9x line had largely stopped.

[PROBLEMCHYLD]

How do I change this to inf format?

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]
"AutoRun"="set comspec=c:\\windows\\command\\cmd.exe"
"PathCompletionChar"=0x00000009
"CompletionChar"=0x00000009
;

[jds]

Another alternative CMD.EXE can be found in ReactOS, version 0.3.1 (or earlier, for W9X compatibility).

Neither version supports the "for /f" option. Otherwise, quite handy.

BTW, for the MS (WIN95CMD.EXE) version :

1) Caps Lock is treated as a Shift Lock (bug).

2) This is what I use for the Pipe Work-around (based on Charles Dye) :

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]
"AutoRun"="set comspec=e:\\windows\\cmd.exe"
"CompletionChar"=dword:00000009

Joe.

Edited October 26, 2011 by jds

[PROBLEMCHYLD]

Another alternative CMD.EXE can be found in ReactOS, version 0.3.1 (or earlier, for W9X compatibility).

Neither version supports the "for /f" option. Otherwise, quite handy.

BTW, for the MS (WIN95CMD.EXE) version :

1) Caps Lock is treated as a Shift Lock (bug).

2) This is what I use for the Pipe Work-around (based on Charles Dye) :

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor]
"AutoRun"="set comspec=e:\\windows\\cmd.exe"
"CompletionChar"=dword:00000009

Joe.

I'm curious as to why you don't use "PathCompletionChar".

Also this method here does nothing

REGEDIT4 

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor] 
"AutoRun"="set comspec=c:\\windows\\command\\cmd.exe" 
"PathCompletionChar"=0x00000009 
"CompletionChar"=0x00000009 
;

but using the dword values you posted above did work.

Edited October 30, 2011 by PROBLEMCHYLD

[jaclaz]

Just for the record, and in the hope to avoid misunderstandings, here is the post by Charles Dye:

http://www.infionline.net/~wtnewton/batch/w95cpost.txt

And here is Technet:

http://technet.microsoft.com/en-us/library/cc978715.aspx

http://technet.microsoft.com/en-us/library/cc940805.aspx

jaclaz

[PROBLEMCHYLD]

Between the two which one should I use?

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor] 
"AutoRun"="set comspec=C:\\WINDOWS\\COMMAND\\CMD.EXE" 
"CompletionChar"=dword:00000009
;

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor\AutoRun]
"set comspec"="C:\\WINDOWS\\COMMAND\\CMD.EXE"
"CompletionChar"=dword:00000009
;

[Steven W]

Forgive me if this is a stupid question, but I'd like to know if it's possible to set WIN95CMD.EXE as the default command interpreter in Windows 98? Would the Shell command in config.sys allow for that? Would Windows still boot? What would the consequences be?

[jaclaz]

Forgive me if this is a stupid question, but I'd like to know if it's possible to set WIN95CMD.EXE as the default command interpreter in Windows 98? Would the Shell command in config.sys allow for that? Would Windows still boot? What would the consequences be?

It is not a stupid question.

It only shows that you skipped over the previous posts without really reading them.

You CANNOT have Win95cmd.exe as the DOS command processor.

You can have it as the default processor once in GUI mode (or, if you prefer, when you open a command prompt from a booted Windows 98, NOT when you boot to DOS 7.1).

This is the idea behind setting the comspec:

jaclaz