Date: Tue, 9 Sep 1997 19:34:16 -0700 (PDT)
Message-Id: <199709100234.TAA28535@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: a DOT hofkamp AT wtb DOT tue DOT nl, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Tell me something about `locking' (please).
Precedence: bulk

At 02:41  9/9/1997 GMT, Albert Theo Hofkamp wrote:
>In article <5v3icu$g7s$1 AT sun1000 DOT pwr DOT wroc DOT pl>,
>	_stary_ AT geocities DOT com writes:
>> 	What does `locking' mean? The FAQ mentions two funcitons: one for
>> locking code and one for data, but it doesn't explain what they ACTUALLY
>> do! All I know is that I should `lock' all data and code `seen' by my
>> interrupt handling routine. I feel a bit uneasy about not knowing why
>> I'm doing something.
>
>Basically, you tell the OS not to swap that memory to disk.
>The reason is that in the interrupt vector of the machine you set the
>address of your routine, and the machine expects it to find it there when
>the interrupt occurs, which might not be the case if the OS is allowed to
>swap the memory out.
To be pedantic: It's not the OS you tell, but the DPMI server.

Nate Eldredge
eldredge AT ap DOT net