Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 24 Oct 2002 10:47:35 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: no dice yet on .net server? Message-ID: <20021024144735.GE5754@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 0 DOT 2 DOT 1 DOT 1 DOT 20021023200722 DOT 01ab1178 AT mail DOT eskimo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.0.2.1.1.20021023200722.01ab1178@mail.eskimo.com> User-Agent: Mutt/1.5.1i On Wed, Oct 23, 2002 at 08:08:07PM -0700, John Franco wrote: > >Hello, > >I've installed cygwin on a Microsoft .Net Server machine (yes, a >"release candidate" build) just so that I can use bash, but it refuses >to run. I've noticed the web page says 'The Cygwin DLL works with >all non-beta, non "release candidate", ix86 versions of Windows >since Windows 95, with the exception of Windows CE.' Does that >mean cygwin deliberately checks the OS version and bails out if >it's not among those expected, or simply that you haven't yet tested >it on this OS and I've hit an incompatibility? It means that we put words like this on the web page specifically to stop people reporting "Hey! It doesn't work on .Net!" Apparently this technique is less than perfect. cgf -- 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/