X-Spam-Check-By: sourceware.org Date: Fri, 5 Jan 2007 08:20:19 -0800 From: Christopher Layne To: cygwin@cygwin.com Subject: Re: 1.7.0 CVS mmap failure Message-ID: <20070105162019.GC5674@ns1.anodized.com> References: <20070105095752.GB28768@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 X-Assp-Spam-Prob: 0.00000 X-Assp-Whitelisted: Yes X-Assp-Envelope-From: clayne@ns1.anodized.com X-Assp-Intended-For: cygwin@cygwin.com X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Fri, Jan 05, 2007 at 10:17:19AM -0600, Brian Ford wrote: > > Ok, after further investigation, this is a /3GB boot.ini flag interaction. > Unfortunately, this is a critical flag for our application, so all our > machines are configured this way. That is why I failed to realize its > significance before. I should also note that my system is a 4GB W2003 box w/ PAE enabled (no /3GB switch though). 4GB is available to the OS as well (give or take a small bit). > I understand if this is now too much of an obscure case for you to be > interested in. If so, I'll try to look into it soon on my own. I suspect > it must have been related to your MEM_TOP_DOWN change. Yep. Never had a problem before it. -cl -- 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/