From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,89d65c5ea403ba58 X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: System Clock update rate of 0.055 milliseconds in DOS/Win95 and Ada.Calendar Date: 1999/01/10 Message-ID: <36984ebc.31381254@news.pacbell.net>#1/1 X-Deja-AN: 430797553 References: <01be3c40$f93dc120$3804fbd1@longslide> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.pbi.net 915951673 206.170.24.14 (Sat, 09 Jan 1999 23:01:13 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Sat, 09 Jan 1999 23:01:13 PDT Newsgroups: comp.lang.ada Date: 1999-01-10T00:00:00+00:00 List-Id: There are different ways for different OSes. If you have access to the hardware (DOS) you can reprogram the clock to interrupt more often, or you can modify ada.calendar.clock to read it more accurately. (See the replacement Calendar body I uploaded years ago to the old Janus BBS that does the latter.) If you're unfortunate enough to be running on such a "modern" OS as Windows, there's a system call to get the time down to the submillisecond (see, eg, the Ada.Calendar in RRsoftware's latest version of their Ada 95). Getting faster interrupts is somewhat more difficult, since you need get the OS's permission.