Date: Thu, 11 May 2000 22:16:56 +0500 (MVT)
From: Prashant TR <prashant_tr AT yahoo DOT com>
X-Sender: tr AT vsnl DOT net DOT in
To: Eli Zaretskii <eliz AT delorie DOT com>
cc: joe tujillo <wakko_fr AT yahoo DOT com>, djgpp AT delorie DOT com
Subject: Re: crazy question!
In-Reply-To: <200005111330.JAA13176@indy.delorie.com>
Message-ID: <Pine.LNX.4.10.10005112206330.1493-100000@vsnl.net.in>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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 Thu, 11 May 2000, Eli Zaretskii wrote:

> > Date: Wed, 10 May 2000 22:45:22 -0700 (PDT)
> > From: joe tujillo <wakko_fr AT yahoo DOT com>
> > 
> >     How could I read each byte of my RAM?
> >     (from 0x00000 to finish)
> 
> What do you need this for?  There might be a way of doing it, but it
> only works in some specially-set environments, so it is not clear
> whether it's good enough for what you have in mind.

I tried something similar for a diagnostic that I was writing. It was
supposed to do the walking 0s and 1s test on the entire physical memory.
But it wasn't worth the all the pain. The DPMI lies about physical memory
size most of the time, so you need to do some extra work to find out the
memory size. Plus problems I mentioned in the other mail.

Otherwise, I don't think anyone could do some useful by just reading
arbitrary portions of the memory.

Prashant