| delorie.com/archives/browse.cgi | search |
| Message-ID: | <37F59194.8E0E36A6@virtualis.com> |
| Date: | Sat, 02 Oct 1999 15:01:08 +1000 |
| From: | Alex Mendes da Costa <alexmdc AT virtualis DOT com> |
| X-Mailer: | Mozilla 4.51 [en] (Win98; I) |
| X-Accept-Language: | en |
| MIME-Version: | 1.0 |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Locking Memory |
| NNTP-Posting-Host: | a3-p05.syd.fl.net.au |
| X-Trace: | 2 Oct 1999 15:04:42 +1000, a3-p05.syd.fl.net.au |
| Organization: | Customer of First Link Internet Services, Sydney, Australia |
| Lines: | 14 |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
| Reply-To: | djgpp AT delorie DOT com |
Hi all. I've an assembly written keyboard handler which I want to install to interrupt 9. I understand pretty much what to do after reading through the FAQ but the only bit I don't understand is the section which reads: "Lock all the memory your handler touches and the code of the handler itself and any function it calls with a series of calls to __dpmi_lock_linear_region". How do I know which regions to lock and how much of these to lock? I have never worked in protected mode before so I don't understand that much about it. Thanks, Alex
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |