---------- Forwarded message ----------
From: Neal Gompa <[EMAIL PROTECTED]>
Date: Jul 10, 2006 5:59 PM
Subject: Re: Link or rename wcmd.exe to cmd.exe?
To: Thomas Kho <[EMAIL PROTECTED] >
Most applications I know of will check not for cmd.exe, but for command.com. I believe Windows uses a stub
command.com to open up cmd.com with more limited capabilities. I believe we need both cmd.exe and
command.com on ReactOS, in order to ensure compatibility. However, the state of wcmd.exe makes me think that it is not quite ready for regular usage. As such, I think you should just add a stub
command.com that forwards everything to wcmd.exe, and nearly all Windows apps that have commandline dependencies (MikTeX comes in mind) use
command.com, not cmd.exe. Just my 2ยข.
On 7/6/06, Thomas Kho <[EMAIL PROTECTED]> wrote:
On 7/1/06, Alexandre Julliard < [EMAIL PROTECTED]> wrote:
> "Thomas Kho" <[EMAIL PROTECTED]> writes:
>
> > I'm currently looking into what would be required for something like a
> > symlink to wcmd.exe, but at the same time I'm wondering the historical
> > reasons for choosing 'wcmd' and if it should be changed to just 'cmd'.
>
> Yes, I think it should be renamed to cmd.exe, at this point it's
> supposed to be a complete replacement.
It's a ~500k patch to rename programs/wcmd to programs/cmd so I want
to get this as right as possible prior to submitting a patch. How much
of wcmd's identity should remain? That is--should it be a wholesale
s/wcmd/cmd or should wcmd keep the name wcmd with just the executable
name changed?
Thomas Kho
