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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Tue, 25 Feb 2003 15:30:36 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: David Starks-Browning cc: cygwin@cygwin.com Subject: Re: Cygwin crashes on .Net Server 2003 with Terminal Services enabled In-Reply-To: <5792-Tue25Feb2003195944+0000-starksb@ebi.ac.uk> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 25 Feb 2003, David Starks-Browning wrote: > 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 How about making a statement to the effect that "Cygwin may not work with release-candidate systems, such as a .NET server. Among the known problems is a conflict with Terminal Services, which will likely not be addressed until this OS version is actually released". Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- 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/