Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Thu, 1 Jul 2004 16:12:57 +0100 From: Dan Hatton X-X-Sender: ucfbdch@ws3-mirp.geol.ucl.ac.uk To: cygwin@cygwin.com cc: Tim Prince Subject: Re: Cygwin Memory Allocation and heap_chunk_in_mb In-Reply-To: Message-ID: References: <6.0.1.1.0.20040630070530.01f29c70@imap.myrealbox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-UCL-MailScanner-Information: Please contact the UCL Helpdesk, helpdesk@ucl.ac.uk for more information X-UCL-MailScanner: Found to be clean On Wed, 30 Jun 2004, Brian Ford wrote: > That's only half of it. You need to set the > IMAGE_FILE_LARGE_ADDRESS_AWARE flag in the executable's COFF header. Let me check I've got clear what to do: I need to download the source code for the cygwin ld package apply the patch of 6th May, 2004, which will change the coffcode.h header ./configure, make, make install to get my extra gigabyte. If I make my program a bit more efficeint, it _might_ fit in 2.5GB, so this is worth a try. Failing that (and going off-topic,) would I get any more by installing some distro (probably Debian) with a Linux kernel (probably 2.4.18?) BTW, anyone got any idea why I'm getting only 1.5GB, rather than the 2GB XP is supposed to make available, now? -- Thanks Dan -- 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/