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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME 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: "Craig Garrett" Subject: Re: System Clock update rate of 0.055 milliseconds in DOS/Win95 and Ada.Calendar Date: 1999/01/10 Message-ID: <01be3cc8$0d0af420$3304fbd1@longslide>#1/1 X-Deja-AN: 430949923 References: <01be3c40$f93dc120$3804fbd1@longslide> <36984ebc.31381254@news.pacbell.net> X-Complaints-To: support@newshosting.com X-Trace: news.siscom.net 915992790 209.251.4.51 (Sun, 10 Jan 1999 13:26:30 EDT) Organization: Newshosting NNTP-Posting-Date: Sun, 10 Jan 1999 13:26:30 EDT Newsgroups: comp.lang.ada Date: 1999-01-10T00:00:00+00:00 List-Id: > If you have access to > the hardware (DOS) you can reprogram the clock to interrupt more > often, That sounds like EXACTLY what I want to do.... ummm.... now how do I do that? In the Bios? In the OS? In Ada? Where and how? (code would be really nice) Now, I am meaning for this to run on Win95, but I thought that Ada.Calendar.Clock is "presice" enough, but the date it reads is the EXACT same value from the system clock for 55 milliseconds at a time, that is the problem. I dont think its Ada.Calendar's fault, because you can subtract time types and get really "precise" floating point numbers, so that is not the issue, I need the faster (umm, more frequent) clock interrupts, how is that done? Craig