Date: Mon, 19 Apr 1999 17:28:07 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Michal Strelec <strelec AT adam DOT osu DOT cz>
cc: djgpp AT delorie DOT com
Subject: Re: RM or PM interrupts
In-Reply-To: <7ffaoa$l3n$1@ns.felk.cvut.cz>
Message-ID: <Pine.SUN.3.91.990419172524.14514B@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 19 Apr 1999, Michal Strelec wrote:

> In my case it's harware interrupt from communication.

Hardware interrupts are handled in protected mode under DPMI.

> Ya, time interupt always occure, but I wrote my own handler (for some
> reasons), where some actions are taken and then execution is passed to old
> (original) handler. AND THAT'S a problem because it calls BIOS function (I
> suppose and SWITCH to RRRMMM).

Yes, chaining to the BIOS handler involves a mode switch.

> QQQQQQ: Any idea how to solve it?

Why do you need to chain?