Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Mon, 24 Feb 2003 10:16:07 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin crashes on .Net Server 2003 with Terminal Services enabled Message-ID: <20030224151607.GA10358@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <29759.1046086761@www58.gmx.net> <831-Mon24Feb2003121556+0000-starksb@ebi.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <831-Mon24Feb2003121556+0000-starksb@ebi.ac.uk> User-Agent: Mutt/1.5.1i On Mon, Feb 24, 2003 at 12:15:56PM +0000, David Starks-Browning wrote: >On Monday 24 Feb 03, Christoph Hense writes: >> I try to use cygwin on a .Net Server 2003 RC2 with Terminal Services >> enabled. >> >> However none of the cygwin tools work. > >That's too bad... > >> ... >> >> Does anyone have any idea? > >Please don't ask anyone to look at this until after .Net Server is >formally released. Cygwin makes no attempt to work on un-released >versions of Windows. > >Should the FAQ explicitly mention .Net release candidates? Do we *really* need to add stuff to the FAQ which is already mentioned on the web page? If anything needs to be added or refined, I think it should just be a pointer to the web page for information on what's supported. There shouldn't be any words in the FAQ which conflict with the cygwin web page. 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/