Xref: news2.mv.net comp.os.msdos.djgpp:5841
From: alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Locking RAM for hardware interrupts
Date: Tue, 09 Jul 1996 21:59:29 GMT
Lines: 26
Message-ID: <836949496.23711.0@abwillms.demon.co.uk>
References: <836858848 DOT 164 DOT 0 AT abwillms DOT demon DOT co DOT uk> <31e1d37f DOT sandmann AT clio DOT rice DOT edu>
NNTP-Posting-Host: abwillms.demon.co.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Charles Sandmann <sandmann AT clio DOT rice DOT edu> wrote:

>The flag
>you propose is like 5 lines of code, but by adding it to a crt0 flag every
>image ever linked gets a copy of it, even though most wouldn't use it. 

Ah, I didn't know it'd be that easy :-)

> The
>routine at a time method is better, but here's a simple example...

Why? Which is 'best'? 

Surely locking the image is 'blanket security', without effectively
disabling virtual memory?

Regards,


ABW
--
I have become... Comfortably numb...

Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk
<A HREF="http://www.hardcafe.co.uk/Alaric/">http://www.hardcafe.co.uk/Alaric/</A>