delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/06/19/10:21:01

Date: Mon, 19 Jun 2000 17:20:16 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Robinson <timothy DOT robinson AT ic DOT ac DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: CWSDPMI r5
In-Reply-To: <394E02BF3AA.7F03TIMOTHY.ROBINSON@hide>
Message-ID: <Pine.SUN.3.91.1000619171347.27216J@is>
MIME-Version: 1.0
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

On Mon, 19 Jun 2000, Tim Robinson wrote:

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

Sorry, this sounds like a contradiction; in fact, two of them.  First, 
"Safe Mode" and "DOS" are two different things AFAIK.  So please clarify: 
do you run DJGPP from a so-called "DOS Mode" or from plain DOS.  The 
latter is when you don't boot into the GUI environment, but instead 
choose "Command prompt only" from the boot menu.  The former is when you 
boot into the GUI environment, then switch to "DOS Mode" from there.  If 
you type "exit" from the DOS Mode, you get back to Windows, while in 
plain DOS, typing "exit" has no effect.

The other contradiction I see in the above sentence is that if you indeed 
boot into Windows, HIMEM.SYS is *always* loaded.

In any case, if HIME is *not* loaded, according to what Charles said, the 
only problem you should see is that you have 64MB instead of 96.  No 
crashes should happen.

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

That's why I think it is something specific to your hardware or 
software.  Please provide the details I asked for in another message.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019