delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/10/08/10:26:04

Date: Tue, 8 Oct 1996 16:17:20 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
Cc: "John M. Aldrich" <fighteer AT cs DOT com>, djgpp-workers AT delorie DOT com
Subject: Re: Stub error messages (Was: Re: 'Cannot open')
In-Reply-To: <Pine.NEB.3.95.961008153746.21692H-100000@ananke.amu.edu.pl>
Message-Id: <Pine.SUN.3.91.961008161336.6704C-100000@is>
Mime-Version: 1.0

On Tue, 8 Oct 1996, Mark Habersack wrote:

> exact amount of memory stored elsewhere, but where? For now, the only solution
> seems to be a 'brute force' method, namely the one used by BIOS POST code. It
> just writes patterns to memory and reads them back, comparing whether they are
> returned correctly. If it writes to an address which is non-existent on the
> computer - it'll know that's the end of installed memory. BTW. This is exactly

I would suggest something much simpler: if you get 0 from the code I 
posted, just tell them that they have ``at least 128MB of memory''.  
Machines which have that much, really don't have to worry about the
exact number...

A still better solution is to check the physical memory returned by the 
DPMI functions, and if it's more than 128MB, add 128MB to the value 
returned by CMOS.

- Raw text -


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