www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/10/15/01:28:49

Date: Sun, 15 Oct 2000 07:27:13 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp AT delorie DOT com
Message-Id: <3405-Sun15Oct2000072712+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.5h
In-reply-to: <I%3G5.110185$47.1397536@news.bc.tac.net>
Subject: Re: Locking memory
References: <I%3G5.110185$47 DOT 1397536 AT news DOT bc DOT tac DOT net>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> From: "J" <a AT a DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sat, 14 Oct 2000 14:14:17 +0100
>
> Is there any other situation that's non-interrupt releated in which
> you would want to lock memory also?

You need to lock memory touched by any code that is executed in an
interrupt context.  Besides your own interrupt handlers, one other
situation is a real-mode callback for functions like the mouse handler
(registered with function 0Ch of Int 33h), because the mouse driver
calls that callback from within a n interrupt handler.

- Raw text -


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