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 Message-ID: <400EAE3B.5090301@etr-usa.com> Date: Wed, 21 Jan 2004 09:52:11 -0700 From: Warren Young User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 MIME-Version: 1.0 To: Cygwin-L Subject: Re: running the latest cygwin on a windows 2003 server References: <400D3B18 DOT 4000305 AT zib DOT de> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040120095121 DOT 03921320 AT 127 DOT 0 DOT 0 DOT 1> <400D49BE DOT 1090108 AT zib DOT de> <400D5539 DOT 7010809 AT zib DOT de> <400E4029 DOT 4070204 AT zib DOT de> <400EA309 DOT 1050204 AT zib DOT de> In-Reply-To: <400EA309.1050204@zib.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Stefan Zachow wrote: > > "why is this all happening only to the Windows Server 2003 machine"? Because Microsoft tightened down a lot of things in Win2K3 that previous Windows OSes allowed. I upgraded a server from Win2K to Win2K3 a few weeks ago, and already we've been bit by two of these paranoia changes. I don't yet have any experience that bears directly on your problem; this is just a general observation. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/