Date:	Mon, 19 Jun 2000 20:13:19 +0530
Message-Id:	<200006191443.UAA00968@midpec.com>
From:	Prashant TR <tr AT midpec DOT com>
To:	timothy DOT robinson AT ic DOT ac DOT uk
CC:	djgpp AT delorie DOT com
In-reply-to:	<394E02BF3AA.7F03TIMOTHY.ROBINSON@hide> (message from Tim
	Robinson on Mon, 19 Jun 2000 12:23:43 +0100)
Subject:	Re: CWSDPMI r5
References:	<394A554E1A2 DOT A7A4TIMOTHY DOT ROBINSON AT hide> <394d59f5 DOT sandmann AT clio DOT rice DOT edu> <394E02BF3AA DOT 7F03TIMOTHY DOT ROBINSON AT hide>
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

> > 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.

Are you talking of "Safe Mode Command Prompt"? And more importantly,
what is your system config (especially what BIOS your system has)? I
can actually send you a small test program which could tell us whether
it's due to the "large memory" support added or something else.

> > 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.

And also how often does it reboot? Everytime, sometimes, rarely?

Prashant

- Raw text -