| delorie.com/archives/browse.cgi | search |
| Date: | Wed, 18 Aug 1999 16:53:06 +0300 (IDT) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Ben Parnell <zaik AT kc DOT net> |
| cc: | djgpp AT delorie DOT com |
| Subject: | Re: Timer interrupt |
| In-Reply-To: | <Pine.GSO.3.96.990817215814.5987A-100000@tortugas.idir.net> |
| Message-ID: | <Pine.SUN.3.91.990818165152.10490d-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 Tue, 17 Aug 1999, Ben Parnell wrote: > 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. I'm not sure incrementing the timer counter is all there is to it. I think chaining to the previous handler is a prudent thing to do, and it also shouldn't do any trouble.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |