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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: Thorsten Kampe Subject: Re: Cygwin crashes on .Net Server 2003 with Terminal Services enabled Date: Tue, 25 Feb 2003 20:53:45 +0100 Lines: 26 Message-ID: References: <29759 DOT 1046086761 AT www58 DOT gmx DOT net> <3E5A901A DOT 5070304 AT t-online DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: 40tude_Dialog/2.0.3.1 * Markus Schönhaber (03-02-24 22:35 +0100) > Christoph Hense wrote: >> I try to use cygwin on a .Net Server 2003 RC2 with Terminal Services >> enabled. >> >> However none of the cygwin tools work. >> >> All of the commands like ls, ps, pwd just return tons of error messages. >> >> If I deinstall the Terminal Services cygwin runs o.k. >> I am also able to run cygwin on a Windows 2000 Server with Terminal Services >> enabled. > > 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. Thorsten -- Content-Type: text/explicit; charset=ISO-8859-666 (Parental Advisory) Content-Transfer-Warning: message contains innuendos not suited for children under the age of 18 -- 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/