Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!adm!Leisner.Henr@Xerox.COM
From: Leisner.Henr@Xerox.COM (marty)
Newsgroups: comp.lang.c
Subject: Re: Looking for C functions to access PC memory
Message-ID: <10346@brl-adm.ARPA>
Date: Sat, 14-Nov-87 15:50:49 EST
Article-I.D.: brl-adm.10346
Posted: Sat Nov 14 15:50:49 1987
Date-Received: Sun, 15-Nov-87 18:41:59 EST
Sender: news@brl-adm.ARPA
Lines: 22

I'm kinda getting tired of the peek and poke discussion on pee-cee.

I think one of the problems with finding clean C semantics to implement
peek and poke is:  

	we're peeking and poking outside of our processes address space.


Peek and poke are not thinks which should be done unless the program has
a very good reason to do it.  If possible, find a more standard
mechanism (like a Bios interrupt which returns the requested
information).

If you run on a machine with memory protection, this discussion becomes
moot.  If you try to access memory you don't have, you get kicked out of
the system.

marty
ARPA:	leisner.henr@xerox.com
GV:  leisner.henr
NS:  martin leisner:henr801c:xerox
UUCP: martyl@rocksvax.uucp