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: Wed, 30 Jun 2004 12:23:02 -0500 From: Brian Ford Reply-To: cygwin AT cygwin DOT com To: Dan Hatton cc: Tim Prince , cygwin AT cygwin DOT com Subject: Re: Cygwin Memory Allocation and heap_chunk_in_mb In-Reply-To: Message-ID: References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040630070530 DOT 01f29c70 AT imap DOT myrealbox DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes On Wed, 30 Jun 2004, Dan Hatton wrote: > On Wed, 30 Jun 2004, Tim Prince wrote: > > > cygwin doesn't emulate a 64-bit OS. Did you try setting up XP with /3GB to > > see whether that would give another 1 GB, or check the archives for any > > reports on such an attempt? > > I've now added " /3GB" to the end of the last line of my boot.ini, making > the complete file: > > [boot loader] > timeout=30 > default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS > [operating systems] > multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /3GB > > Is that what I was supposed to do? It's made no difference to the > results either of max_memory, or of running my calculation. That's only half of it. You need to set the IMAGE_FILE_LARGE_ADDRESS_AWARE flag in the executable's COFF header. See: http://sources.redhat.com/ml/binutils/2004-05/msg00151.html which is not yet in the Cygwin binutils release. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained pilot... -- 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/