delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:731 |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Mouse code - How do I lock memory? |
Date: | Sun, 28 Jan 1996 17:05:09 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 11 |
Message-ID: | <310c0125.sandmann@clio.rice.edu> |
References: | <4eg5ci$8h4 AT brickbat DOT mindspring DOT com> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | clio.rice.edu |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> Does the function click_handler() get locked into memory by the call > to _go32_dpmi_allocate_real_mode_callback_retf? No, it doesn't (how would go32_dpmi_... know how long it was?) This would probably work until this routine was run in a very tight memory situation, in which case it might be swapped out. Look at the helper routine _go32???lock_code in dpmi.h, and provide the length as init_mouse - click_handler (with the appropriate casts, of course). If it's a relatively small piece of code, you can include crt0.h and set
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |