delorie.com/archives/browse.cgi | search |
Date: | Thu, 11 May 2000 09:30:00 -0400 (EDT) |
Message-Id: | <200005111330.JAA13176@indy.delorie.com> |
From: | Eli Zaretskii <eliz AT delorie DOT com> |
To: | joe tujillo <wakko_fr AT yahoo DOT com> |
CC: | djgpp AT delorie DOT com |
In-reply-to: | <20000511054522.20185.qmail@web1101.mail.yahoo.com> (message from |
joe tujillo on Wed, 10 May 2000 22:45:22 -0700 (PDT)) | |
Subject: | Re: crazy question! |
References: | <20000511054522 DOT 20185 DOT qmail AT web1101 DOT mail DOT yahoo DOT com> |
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 |
> 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) Not easily. Some portions of memory are not mapped into your address space; accesing them will generally trigger either a Page Fault or a GPF exception, and abort your program. 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.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |