delorie.com/archives/browse.cgi | search |
From: | "A. Sinan Unur" <asu1 AT cornell DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | locking memory for real mode callbacks |
Date: | Mon, 21 Apr 1997 19:05:54 -0400 |
Organization: | Cornell University http://www.cornell.edu |
Lines: | 19 |
Sender: | asu1 AT cornell DOT edu (Verified) |
Message-ID: | <335BF2D2.7286@cornell.edu> |
Reply-To: | asu1 AT cornell DOT edu |
NNTP-Posting-Host: | cu-dialup-0007.cit.cornell.edu |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
if i allocate a real mode callback using _go32_dpmi_allocate_real_mode_callback_iret, do i need to lock conventional memory at the segment:offset returned by this function? if so, what size should i assume? (this could probably be answered by checking the sources but i do not have them locally, and they take a while to download on a 14.4 connection.) or is just locking my callback function (and any related data) enough? -- Sinan ******************************************************************* A. Sinan Unur WWWWWW |--O+O mailto:sinan DOT unur AT cornell DOT edu C ^ http://www.people.cornell.edu/pages/asu1/ \ ~/ *******************************************************************
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |