public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kenneth Wolcott <kennethwolcott@gmail.com>
To: cygwin@cygwin.com
Subject: mksnt sh is invoked when executing cygwin icon;
Date: Thu, 26 Nov 2015 08:26:00 -0000	[thread overview]
Message-ID: <CADex0xxaqFsuJHmMacc_6dQ+GRjdfKZ2eDgmt_eYa=9BqfbU5g@mail.gmail.com> (raw)

Hi;

  It seems that a 32bit Windows server with a pre-existing MKS Toolkit
installation prevents an interactive Cygwin window (mintty) from
starting properly.

  If the c:\mksnt directory (where MKS Tookkit is installed) is
renamed to c:\NOTmksnt, then double-clicking the Cygwin icon results
in:

"Failed to run C:/mksnt/sh.exe: No such file or directory"

But if the c:\NOTmksnt directory is renamed back to what it was, then
the window opens up with sh.exe from mksnt instead of bash and seems
to hang for a very long time.

   Why is this?  Part of me thinks that Cygwin and MKS Toolkit should
just coexist just fine, each not knowing about the other (c:\cygwin
and c:\mksnt).  Part of me thinks that I'd like to have Cygwin come
first in the path rather than having c:\mksnt first in the path.  Is
there a way to force the Cygwin install process (or fix it afterward)
to put Cygwin first?

  I tried to change /etc/profile so that the PATH variable was set to
exclusively Cygwin stuff, but that had no effect.

  How to fix this outside Cygwin? (The Windows side)

  How to fix this inside Cygwin?

Thanks,
Ken Wolcott

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2015-11-26  1:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  8:26 Kenneth Wolcott [this message]
2015-11-26  9:30 ` David Macek
2015-11-26 13:16   ` Thomas Wolff
2015-12-01  2:14     ` Kenneth Wolcott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADex0xxaqFsuJHmMacc_6dQ+GRjdfKZ2eDgmt_eYa=9BqfbU5g@mail.gmail.com' \
    --to=kennethwolcott@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).