Mail Archives: djgpp/1996/11/14/16:56:02
From: | gminer AT Newbridge DOT COM (Glen Miner)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Memory Protection
|
Date: | 14 Nov 1996 17:44:21 GMT
|
Organization: | Newbridge Networks Corporation
|
Lines: | 20
|
Message-ID: | <56flpl$q6v@kannews.ca.newbridge.com>
|
NNTP-Posting-Host: | 138.120.136.238
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
I am currently porting a 16 bit program to djgpp, and I am being
introduced to the wonderfull world or memory protection. It seems that
video memory is protected, and I'm not allowed to freely read/write in it.
I have discovered that I can use some macro to disable the memory
protection in my program, but I am wondering if this is wise.
If I disable memory protection, will my program run faster?
Is it less safe? (Ie: if I lead a pointer astray, will it crash harder?
ie: reboot not just segmentation fault).
Would it be wiser to somehow take ownership of the video memory buffer so
that it doesn't have to be protected from me?
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
- Raw text -