Date: Sun, 2 May 1999 11:19:28 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Endlisnis <s257m AT unb DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: kbhit() and SIGALRM
In-Reply-To: <3728D0E0.B564294@unb.ca>
Message-ID: <Pine.SUN.3.91.990502111850.563O-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 29 Apr 1999, Endlisnis wrote:

> I used uclock() to check.  This worked fine on my machine (Win95,
> 333MHz), but when i ran it on a machine at School (Win3.1 ~40MHz) about half
> the time it would give irratic answers and half the time the correct answer.

Windows 3.X is much worse with `uclock' than Windows 9X.  In fact,
`uclock' is completely useless on Windows 3.X.

It should be possible to rewrite `uclock' so it doesn't reprogram the
timer, but instead uses the timer status byte to decide whether you
are in the first or the second part of the count-down.  I didn't try
to do that, and I don't know if it would solve the problems with
Windows 3.X.  Volunters are welcome, as always.