From: Glen Miner Newsgroups: comp.os.msdos.djgpp Subject: Re: Memory Protection Date: Fri, 15 Nov 1996 12:37:02 -0500 (EST) Organization: Newbridge Networks Corporation Lines: 24 Message-ID: NNTP-Posting-Host: 138.120.136.238 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To: DJ Delorie In-Reply-To: <199611151733.MAA21304@delorie.com> To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp > > Ahh, this makes sense now. I suppose my next question is: how does the > > dosmem put/get functions get around this? Do they resize before and > > after? Wouldn't this be painfully inneffeicient? > > They use a different segment, which overlaps the DOS memory instead of > the program's memory. Ahh, I see. I don't know much about pmode programming, but I know real mode inside and out, and this is starting to make more sense. > For further protection, you can create a segment that covers only the > video memory and use that instead. How would this be done? This would be ideal; if you could setup another segment (a 64k window to vidoe memory), and it would be "unprotected", then you could just use the movedata function with that segment's selector, right? Peace ===[ Gabo / [ABC] : gaminer AT undergrad DOT math DOT uwaterloo DOT ca ]=================== Latest ABC Shogi: http://www.undergrad.math.uwaterloo.ca/~gaminer/shogi.html "What Greenpeace spends in a year General Motors spends in four hours" -Moby