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,start
X-Google-Attributes: gid103376,public
From: Paul Whittington <paul@grep.net>
Subject: Re: System Clock update rate of 0.055 milliseconds in DOS/Win95 and
  Ada.Calendar
Date: 1999/01/09
Message-ID: <36984F3F.FA6C58C3@grep.net>#1/1
X-Deja-AN: 430797554
Content-Transfer-Encoding: 7bit
References: <01be3c40$f93dc120$3804fbd1@longslide>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: newsabuse@remarQ.com
X-Trace: 915951217 HLLAGTWDSD872C 07C usenet53.supernews.com
Organization: GrepNet, Incorporated
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1999-01-09T00:00:00+00:00
List-Id: <comp.lang.ada>

There are at least two possibilities.  One is Win32 specific and the
other Intel specific.

1) Win32 API call.  The GetTickCount function retrieves the number of 
milliseconds that have elapsed since Windows was started.

2) Use the RDTSC instruction on the Intel Pentium processor to
read the timestamp counter.

Both of these are not platform portable.  The first is accurate to one
millisecond while the second is accurate to one processor cycle.

TTFN Paul

Craig Garrett wrote:
> 
> In Dos/Win95, the system clock is only updated every 0.055 milliseconds,
> which from a real-time simulation perspective is absolutely pitiful.  Is
> there a system call to force the OS to update the system clock more
> frequently or on demand?  I am sick of having such low resolution.  How do
> real-time games such as Quake and flight-sims on PCs running Dos/Win95 get
> around this problem?
>   Craig

-- 
Paul Whittington
GrepNet, Inc.
(208)523-7375
paul@grep.net

"Even if you're on the right track you'll get
 run over if you stand still."

Will Rogers