Date: Mon, 19 Jun 2000 12:23:43 +0100
From: Tim Robinson <timothy DOT robinson AT ic DOT ac DOT uk>
To: djgpp AT delorie DOT com
Subject: Re: CWSDPMI r5
In-Reply-To: <394d59f5.sandmann@clio.rice.edu>
References: <394A554E1A2 DOT A7A4TIMOTHY DOT ROBINSON AT hide> <394d59f5 DOT sandmann AT clio DOT rice DOT edu>
Message-Id: <394E02BF3AA.7F03TIMOTHY.ROBINSON@hide>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver 1.25.07
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 18 Jun 2000 23:23:33
"Charles Sandmann" <sandmann AT clio DOT rice DOT edu> wrote:

> Unless you have more than 255Mb of virtual memory defined, or 128Mb or 
> more of physical memory it won't do much of anything for you, unless
> you have need for one of the obscure enhancements.  And as noted elsewhere,
> it misbehaves on some systems and noone knows why.  96Mb shouldn't cause
> any problems at all (other than maybe only using 64Mb of it if himem.sys
> isn't loaded).
Himem.sys isn't loaded; I'm running under Safe Mode Win95 DOS.

> I suspect this is more likely due to the application you are running 
> using uninitialized memory, or some device driver doing bad things it
> shouldn't do.
Well, the application concerned is make.exe, or gcc, or nasm, or ld, or
all four.

------------
Tim Robinson
timothy DOT robinson AT ic DOT ac DOT uk