Forwarded because accidently did not add wine-devel to it. Also, noting that this is about Wine, not ReactOS. But both still apply.<br><br>---------- Forwarded message ----------<br><span class="gmail_quote">From: <b class="gmail_sendername">
Neal Gompa</b> <<a href="mailto:ngompa13@gmail.com">ngompa13@gmail.com</a>><br>Date: Jul 10, 2006 5:59 PM<br>Subject: Re: Link or rename wcmd.exe to cmd.exe?<br>To: Thomas Kho <<a href="mailto:tkho@ucla.edu">tkho@ucla.edu
</a>><br><br></span>
<div>Most applications I know of will check not for cmd.exe, but for <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://command.com/" target="_blank">command.com</a>. I believe Windows uses a stub <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://command.com/" target="_blank">
command.com</a> to open up <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://cmd.com/" target="_blank">cmd.com </a>with more limited capabilities. I believe we need both cmd.exe and <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://command.com/" target="_blank">
command.com</a> 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 <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://command.com/" target="_blank">
command.com</a> that forwards everything to wcmd.exe, and nearly all Windows apps that have commandline dependencies (MikTeX comes in mind) use <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://command.com/" target="_blank">
command.com</a>, not cmd.exe. Just my 2�.</div>
<div><span class="e" id="q_10c5a74007113944_1"><br><br>
<div><span class="gmail_quote">On 7/6/06, <b class="gmail_sendername">Thomas Kho</b> <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:tkho@ucla.edu" target="_blank">tkho@ucla.edu</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 7/1/06, Alexandre Julliard <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:julliard@winehq.org" target="_blank">
julliard@winehq.org</a>> wrote:<br>> "Thomas Kho" <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:tkho@ucla.edu" target="_blank">tkho@ucla.edu</a>> writes:<br>><br>> > I'm currently looking into what would be required for something like a
<br>> > symlink to wcmd.exe, but at the same time I'm wondering the historical <br>> > reasons for choosing 'wcmd' and if it should be changed to just 'cmd'.<br>><br>> Yes, I think it should be renamed to
cmd.exe, at this point it's<br>> supposed to be a complete replacement.<br><br>It's a ~500k patch to rename programs/wcmd to programs/cmd so I want <br>to get this as right as possible prior to submitting a patch. How much
<br>of wcmd's identity should remain? That is--should it be a wholesale<br>s/wcmd/cmd or should wcmd keep the name wcmd with just the executable<br>name changed?<br><br>Thomas Kho<br><br><br></blockquote></div><br></span>
</div>