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: <6.1.2.0.0.20041119101224.020fae48@imap.myrealbox.com> X-Sender: tprince AT imap DOT myrealbox DOT com Date: Fri, 19 Nov 2004 10:21:11 -0800 To: cygwin AT cygwin DOT com From: Tim Prince Subject: Re: Compatibility to Windows2003 (64-bit) In-Reply-To: <20041119153306.GF23956@trixie.casa.cgf.cx> References: <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20041119090055 DOT 041dd3e0 AT pop DOT prospeed DOT net> <20041119153306 DOT GF23956 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-IsSubscribed: yes At 07:33 AM 11/19/2004, Christopher Faylor wrote: >... >so, AFAIK, Cygwin should work on 64 bit windows: > >http://cygwin.com/ml/cygwin-announce/2004-09/msg00002.html > >I'll change the main web page if/when 64 bit windows goes out of beta. >Or is it there already? It looks like the AMD/EM64T Windows has months to go in beta. We've been running 32-bit cygwin on the 64-bit Windows on Intel CPUs (EM64T and IA64). No complaints, except visibility of Windows environment variables to cygwin is intermittent. We don't think that's the fault of cygwin, nor is it unique to the 64-bit OS. Tim Prince -- 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/