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: Mon, 24 Feb 2003 12:15:56 +0000 Message-ID: <831-Mon24Feb2003121556+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: Christoph Hense Cc: cygwin AT cygwin DOT com Subject: Cygwin crashes on .Net Server 2003 with Terminal Services enabled In-Reply-To: <29759.1046086761@www58.gmx.net> References: <29759 DOT 1046086761 AT www58 DOT gmx DOT net> 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? Thanks, 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/