This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Cygwin on Win 2000
- From: "Alex K. Angelopoulos" <alexangelopoulos at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 21 Mar 2002 16:42:38 -0500
- Subject: Re: Cygwin on Win 2000
- Newsgroups: gmane.os.cygwin
- References: <001701c1d026$8d5531f0$0200a8c0@sknet01> <3C98D3D8.5B8C115A@lapo.it>
- Reply-to: "Alex K. Angelopoulos" <alexangelopoulos at hotmail dot com>
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@lapo.it> wrote in message 3C98D3D8.5B8C115A@lapo.it">news:3C98D3D8.5B8C115A@lapo.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@lapo.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/