X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 12 Nov 2009 15:14:52 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygwin-64bit Message-ID: <20091112141452.GA19308@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4AFBF760 DOT 6090903 AT tlinx DOT org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AFBF760.6090903@tlinx.org> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Nov 12 03:54, Linda Walsh wrote: > I am having my first experiences on 64-bit windows and noticed that 32-bit > processes, more so than 64-bit user processes are virtualized are not able > to access or see parts of the machine. This is especially noticeable in the > registry. Did you notice the /proc/registry32 and /proc/registry64 keys in Cygwin 1.7? Also, did you notice the new regtool options --wow32 and --wow64? And, did you notice the virtual $SYSTEMROOT\Sysnative folder which allows to access the 64 bit system32 folder since Windows Vista? A 64 bit Cygwin would be cool, but we lack time and especially active community support to get this done. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple