delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1999/07/19/13:25:26

From: wanis AT my-deja DOT com
Newsgroups: comp.os.msdos.djgpp
Subject: Re: GPF due to _farpokel
Date: Mon, 19 Jul 1999 16:53:10 GMT
Organization: Deja.com - Share what you know. Learn what you don't.
Lines: 21
Message-ID: <7mvl5g$17l$1@nnrp1.deja.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990718112856 DOT 19517T-100000 AT is>
NNTP-Posting-Host: 128.170.76.61
X-Article-Creation-Date: Mon Jul 19 16:53:10 1999 GMT
X-Http-User-Agent: Mozilla/4.5 [en] (Win95; I)
X-Http-Proxy: 1.0 x31.deja.com:80 (Squid/1.1.22) for client 128.170.76.61
X-MyDeja-Info: XMYDJUIDwanis
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Whoops.  I found the problem, and it was a pretty simple goof.  In my
code, I was creating a descriptor for memory which began at
'cardbasemem', and then I was ALSO adding 'cardbasemem' into the address
of my _farpokel.  All I needed in the _farpokel was the OFFSET from
'cardbasemem'...  I changed the _farpokel statement and now the code
works just fine.

I still have a few questions (mostly questions of curiosity) about
memory allocation, descriptors, and whatnot in protected mode.  Are
there any books/FAQs/web sites that provide a nice thorough introduction
to the subject?  (One thing I'm curious to know:  how did my application
gain the right to POKE the memory locations -- is it just because no
other application created a descriptor to that memory block?)

Thanks again for the help.

-- Paul


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019