Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
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: Tue, 25 Feb 2003 19:59:44 +0000
Message-ID: <5792-Tue25Feb2003195944+0000-starksb@ebi.ac.uk>
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Cc: cygwin AT cygwin DOT com
Subject: Re: Cygwin crashes on .Net Server 2003 with Terminal Services enabled
In-Reply-To: <r0i4eu1db4eb$.dlg@thorstenkampe.de>
References: <29759 DOT 1046086761 AT www58 DOT gmx DOT net>
	<3E5A901A DOT 5070304 AT t-online DOT de>
	<r0i4eu1db4eb$.dlg AT thorstenkampe DOT 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/