Date: Thu, 14 Nov 1996 19:05:04 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Hee Dong,Lim" <dkh AT chungbuk DOT ac DOT kr>
Cc: djgpp AT delorie DOT com
Subject: Re: Lock Code and Lock Data?
In-Reply-To: <328B37BC.7734@chungbuk.ac.kr>
Message-Id: <Pine.SUN.3.91.961114190218.8809A-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 15 Nov 1996, Hee Dong,Lim wrote:

> _go32_lock_code or _go32_lock_data function is used in soome other
> sources.
> in other dos extender like dos4gw, I never have seen this..

Don't know how dos4gw handles this.  Maybe it always lock the handler and 
never asks, but that's just a guess.

> DPMI uses VMM therefore code and data are possible to swap.
> interrupt handler or callback function is often locked..
> in other dos extender, this is not happened..
> why?

You should always lock the code and data that any hardware interrupt 
touches, precisely so that they won't be swapped out.  DJGPP has special 
functions that allow you to do just that.

> I wanna know..
> I can't UNDERSTAND!

Do you now?