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 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.4000305@zib.de> <6.0.1.1.0.20040120095121.03921320@127.0.0.1> <400D49BE.1090108@zib.de> <400D5539.7010809@zib.de> <400E4029.4070204@zib.de> <400EA309.1050204@zib.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/