Date: Tue, 17 Aug 1999 22:01:41 -0500 (CDT)
From: Ben Parnell <zaik AT kc DOT net>
X-Sender: zaik AT tortugas DOT idir DOT net
To: djgpp AT delorie DOT com
Subject: Re: Timer interrupt
In-Reply-To: <7pcdkd$eos$1@news04.btx.dtag.de>
Message-ID: <Pine.GSO.3.96.990817215814.5987A-100000@tortugas.idir.net>
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

Actually, I don't think it would cause too much of a problem with DOS,
since I have some code that will increase the tick counter at 
0x46c approximately 18.2 times second, even though the timer is programmed
to generate an interrupt other than 18.2 times a second.

On Tue, 17 Aug 1999, Vinzent Hoefler wrote:

> Ben Parnell <zaik AT kc DOT net> wrote:
> 
> >I'm writing a program that reprograms channel 0 of the programmable timer
> >and hooks the timer interrupt, without passing control to the previous
> >handler.  I was wondering if this would cause any problems with any
> >popular TSRs in use today.
> 
> It wouldn't only cause problems with T&SRs, it would also cause more
> or less big trouble with DOS. The timer interrupt is used for all
> timing purposes, disk cache, floppy motor ... shall I continue
> counting?
> 
> 
> Vinzent.
>