Date:	Mon, 26 Apr 1999 11:26:17 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	cssl AT geocities DOT com
cc:	djgpp AT delorie DOT com
Subject:	Re: Hooking interrupts: VERY strange behaviour !
In-Reply-To:	<199904260148.SAA28421@geocities.com>
Message-ID:	<Pine.SUN.3.91.990426112556.15084Q-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 26 Apr 1999 cssl AT geocities DOT com wrote:

> The following program (partially copied from PDMLWP sources) on my 
> machine, the FIRST time it's run it prints "cnt=1", all the following 
> times it prints "cnt=7" or "cnt=8", that's the result I'm expecting...

What's strange about this?  Simply, as soon as you enable the periodic
interrupt, you get the first interrupt, and the counter gets bumped to
1.  The rest are coming in at 250-ms intervals, since you never
reprogram the clock back to its original interrupt rate before the
program exits.

- Raw text -