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 Date: Thu, 5 Aug 2004 11:15:23 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: question about shared memory in the cygwin daemon Message-ID: <20040805091523.GF24647@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Aug 4 14:53, Clarke, Trevor wrote: > > We currently run on 32bit windows and 32/64but solaris with near future > plans to run on 64bit windows. The product is for a specific client so > we can assume 4gb or more of physical ram. You can't access more than 2GB (or 3GB with the appropriate kernel flag) from any 32 bit Windows process. Since Cygwin's shared memory capabilities are restricted to what the operating system allows, Cygwin won't change that for you. When running Cygwin on Windows 64, it's still a 32 bit DLL, only linkable with 32 bit applications so the usual 32 bit restrictions still apply. Just as a friendly reminder, since you're talking about using Cygwin in an apparently proprietary project, I'd like to point you to the Cygwin licensing terms: http://cygwin.com/licensing.html Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/