Date: Tue, 28 Apr 1998 13:34:21 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Javier Calleja <dismuntel AT apdo DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: Put an interrupr function in DOS mermory with 'dosputmem'.
In-Reply-To: <01bd71e5$98f53c60$0100a8c0@dismuntel.ctv.es>
Message-ID: <Pine.SUN.3.91.980428133358.27094C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Mon, 27 Apr 1998, Javier Calleja wrote:

>   I could do it with the _go32_dpimi_allocate_real_mode_callback_ret =
> function or similar, but I have read that it's so slow because this =
> function calls to the interrupt function handler which is allocated in =
> the dpmi memory.

I would suggest to begin with the real-mode callback approach and go
to faster but more complex methods only if you aren't satisfied with
performance.  Catching real-mode interrupts is tricky as it is, and if
you plunge directly to the messy waters, you might drown.

With real-mode callbacks, at least you can reasonably expect them to
work.  They were written by somebody who knows the DJGPP/DPMI stuff
inside out, and they were tested in numerous applications.  They do
have drawbacks, but you shouldn't (IMHO) be worried about them unless
and until you actually hit one of them.