Xref: utzoo comp.sys.att:9734 comp.sys.ibm.pc.programmer:1821
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!accuvax.nwu.edu!delta.eecs.nwu.edu!kaufman
From: kaufman@delta.eecs.nwu.edu (Michael L. Kaufman)
Newsgroups: comp.sys.att,comp.sys.ibm.pc.programmer
Subject: Re: How does DOS time work?
Message-ID: <8669@accuvax.nwu.edu>
Date: 6 Jun 90 03:55:05 GMT
References: <1094.266605B1@onebdos.UUCP> <980@soleil.UUCP> <3163@bnr-rsc.UUCP>
Sender: news@accuvax.nwu.edu
Reply-To: kaufman@delta.eecs.nwu.edu (Michael L. Kaufman)
Organization: Northwestern U, Evanston IL, USA
Lines: 12

In article <3163@bnr-rsc.UUCP> mlord@bnr-rsc.UUCP (Mark Lord) writes:
>...
>You need some code to intercept the timer interrupts and cause every 34th
>one to be skipped.  

This could be quite dangerous.  You don't know what the timer tick is doing
besides updating the clock.  The system might (as one example) be using the
tick to control the drives.  Much safer is to update the clock, but don't do
it every 34 ticks.

Michael Kaufman