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: Tue, 25 Feb 2003 19:59:44 +0000 Message-ID: <5792-Tue25Feb2003195944+0000-starksb@ebi.ac.uk> From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Thorsten Kampe Cc: cygwin@cygwin.com Subject: Re: Cygwin crashes on .Net Server 2003 with Terminal Services enabled In-Reply-To: References: <29759.1046086761@www58.gmx.net> <3E5A901A.5070304@t-online.de> On Tuesday 25 Feb 03, Thorsten Kampe writes: > > cygwin works like a charm on my .NET Standard Server 2003 RC2 with remote > > desktop enabled. > > I tried it myself and it is definitely "Terminal Services" that make > Cygwin fail. In a few months there will be dozen of questions like > "Cygwin doesn't work on Windows Server 2003", because there won't be > lots of changes from the Release Candidate to the actual release. I think it's reasonable to describe what we know about the Terminal Services in the FAQ. David -- 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/