delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/03/21/17:42:22

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Stephano Mariani" <sk DOT mail AT btinternet DOT com>
To: "'Alex K. Angelopoulos'" <alexangelopoulos AT hotmail DOT com>,
<cygwin AT cygwin DOT com>
Subject: RE: Cygwin on Win 2000
Date: Thu, 21 Mar 2002 22:41:52 -0000
Message-ID: <00c201c1d129$9866e8f0$0200a8c0@sknet01>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <a7dk4f$2f9$1@main.gmane.org>

I have since resolved the issue... apparently, there are hidden settings
in the windows 2000 installer that can be used to prevent command.com
from being installed (which my company has done). I am thus unable to
run 16-bit code (which I have thankfully never needed to do), but this
is no problem.

I have cmd.exe but no command.{com,exe}. I suspect that this is just a
peculiarity if my system.

Thanks,
Stephano Mariani


> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com] On
Behalf
> Of Alex K. Angelopoulos
> Sent: Thursday, 21 March 2002 9:43 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: Cygwin on Win 2000
> 
> FYI everyone...
> 
> Command.com really *should* be there.  You really *shouldn't* ever use
it
> directly, though.
> 
> If you launch a console app which turns out to be 16-bit, NT/2000/XP
> automatically instantiates command.com (and then passes all of its
> operations  back to CMD.EXE).
> 
> 
> I suspect the OPs problem is that since he tried to launch under
> command.com, it choked since cygwin is 32-bit.  This can just be
resolved
> by calling CMD instead of COMMAND  in the "run" box.
> 
> "Lapo Luchini" <lapo AT lapo DOT it> wrote in message
> news:3C98D3D8 DOT 5B8C115A AT lapo DOT it...
> : > Mine was a clean install in each case with only the service packs
and
> : > some patches being added.
> :
> : I installed it from scratch every time but the first (of course...)
but
> : \winnt\system32\command.com is definitely there, in Win98 is
> : widows\command\command.com.. be it an upgrade of a from scratch.
> : But wait.. when you open command prompt... (well I guess you can
open
> : command prompt, yes?) which executable appears in the task manager?
> :
> : --
> : Lapo 'Raist' Luchini
> : lapo AT lapo DOT it (PGP & X.509 keys available)
> : http://www.lapo.it (ICQ UIN: 529796)
> :
> :
> :
> : --
> : Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> : Bug reporting:         http://cygwin.com/bugs.html
> : Documentation:         http://cygwin.com/docs.html
> : FAQ:                   http://cygwin.com/faq/
> :
> :
> 
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019