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" <cgarrett@siscom.net>
Subject: System Clock update rate of 0.055 milliseconds in DOS/Win95 and
 Ada.Calendar
Date: 1999/01/10
Message-ID: <01be3c40$f93dc120$3804fbd1@longslide>#1/1
X-Deja-AN: 430741128
X-Trace: news.siscom.net 915934804 209.251.4.56 (Sat,
 09 Jan 1999 21:20:04 EDT)
Organization: Newshosting
NNTP-Posting-Date: Sat, 09 Jan 1999 21:20:04 EDT
Newsgroups: comp.lang.ada
X-Complaints-To: support@newshosting.com
Date: 1999-01-10T00:00:00+00:00
List-Id: <comp.lang.ada>

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