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.2 required=5.0 tests=BAYES_00,FROM_NUMERIC_TLD, INVALID_MSGID,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,894846be18e92713 X-Google-Attributes: gid103376,public From: steved@pacifier.com@199.2.117.163 (Steve Doiel) Subject: Re: ADA, Windows NT and Real-Time (was GNAT R/T Annex and Win95) Date: 1996/04/21 Message-ID: <4ldqbf$kmq@news.pacifier.com>#1/1 X-Deja-AN: 150656631 references: <96041916380674@psavax.pwfl.com> <317916B0.A5C@ccmail.orl.mmc.com> organization: Pacifier BBS, Vancouver, Wa. ((360) 693-0325) reply-to: steved@pacifier.com (Steve Doiel) newsgroups: comp.lang.ada Date: 1996-04-21T00:00:00+00:00 List-Id: In <317916B0.A5C@ccmail.orl.mmc.com>, "Brian K. Catlin" writes: >processor clock rate !). NOTE: The granularity of the timer service on PC (Intel) >platforms is 10 milliseconds (ancient PC architecture standard). Details, details but: According to the OS/2 Control Programming Guide (regarding timers on PC hardware) "On most hardware, clock ticks occur approximately 32 times a second, so each tick interval lasts approximately 31.25 milliseconds." The 10 msec number didn't sound right, since most of the real time OS's I've usd have had a 10 msec timer. But then again on the systems I've done they're mostly event driven so the resolution of the system timer isn't that significant. > To build a real-time system with a small latency window (less than 1 millisecond) >would require that you write your system as an NT device driver (you may also want >to get a programmable timer board for fine granularity timers). But if your >latency window is larger, then writing it in user-mode is fine. > > -Brian >-- > >Brian Catlin, Sannas Consulting (310) 798-8930 >Contracting to Lockheed Martin Real-3D (407) 356-0637 >Windows NT Internals and Device Driver Consulting