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 From: "Dave Korn" To: Subject: RE: Cygwin Memory Allocation and heap_chunk_in_mb Date: Wed, 30 Jun 2004 18:41:15 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 30 Jun 2004 17:41:15.0515 (UTC) FILETIME=[714744B0:01C45EC9] > -----Original Message----- > From: cygwin-owner On Behalf Of Dan Hatton > Sent: 30 June 2004 16:34 > 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? More or less. It would have been a better idea to just duplicate that line and add the /3gb switch to the duplicate, i.e. [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 multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional with 3GB switch" /fastdetect /3GB just in case it became unbootable owing to a side-effect of the /3gb switch; I don't think that switch would be disabled by booting in safe mode, so if it had caused boot failure, you would have had a hard time getting your system back. As to the general issue about why the extra memory didn't help, Brian has answered that. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/