X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
From: "Gerrit van Niekerk" <gerritvn AT gpvno DOT co DOT za>
Organization: GPvNO
To: RayeR <glaux AT centrum DOT cz>, djgpp AT delorie DOT com
Date: Sun, 04 Nov 2007 12:42:51 +0200
MIME-Version: 1.0
Subject: Re: PM interrupt handling - how to call old old ISR with slower rate than my new ISR
Message-ID: <472DBE4B.29513.65ADC026@gerritvn.gpvno.co.za>
In-reply-to: <1194134888.880555.98470@o3g2000hsb.googlegroups.com>
References: <1193997973 DOT 429569 DOT 16180 AT y42g2000hsy DOT googlegroups DOT com>, <1194008972 DOT 850005 DOT 77660 AT k79g2000hse DOT googlegroups DOT com>, <1194134888 DOT 880555 DOT 98470 AT o3g2000hsb DOT googlegroups DOT com>
X-mailer: Pegasus Mail for Windows (4.41)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 3 Nov 2007 at 17:08, RayeR wrote:

> And BTW what INT is better to hook? In some examples I see INT08 and
> in others INT1C.
> I use INT08 which should be hardware timer interrupt.

INT08 is the hardware timer interrupt. INT1C is a software interrupt issued 
by the real-mode INT08 interrupt handler. 

If the objective is to have a fast protected-mode interrupt handler, it won't do 
to just hook INT1C since a mode switch will be required every time the timer 
interrupts.