X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Fri, 14 Mar 2008 13:41:28 -0400 From: "Jason Alonso" Reply-To: jalonso@media.mit.edu To: cygwin@cygwin.com Subject: Re: Cygwin doesn't install on Windows Server 2008 (x64). In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hello, On Fri, Mar 14, 2008 at 1:26 PM, Popper, Samuel (US SSA) wrote: > Your PATH does not yet have any part of cygwin in it, so I just added > it: > export PATH=$PATH:/bin:/usr/bin > > Try adding it to your path and see if you get better results. > > But the behavior I saw was different- when the shell couldn't find a > command, it gave an error message but did not spawn a new process. I was about to comment similarly, but I was observing that it sounds like non-Cygwin processes were being spawned (or doing the spawning). So, a couple of things: 1) Try sending the output of cygcheck -s. It sounds like this is going to be a problem, so at least report the output of echo $PATH. 2) If the wrong executables are being launched, putting /bin and /usr/bin at the end of PATH isn't going to help, but putting them at the front will (export PATH=/bin:/usr/bin:$PATH). Cheers, Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/