Date:	Sun, 16 May 1999 13:55:03 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Sean <sproctor AT enter DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: uclock trouble
In-Reply-To:	<373DCBAB.DB9BC535@enter.net>
Message-ID:	<Pine.SUN.3.91.990516135445.26252Y-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 15 May 1999, Sean wrote:

> But uclock() is very inaccurate.  Maybe it's just my
> computer, but when I run it it seems like it counts up to like 0x1200 or
> so, then goes down to -0xFFFF or so.  I'm just guessing because I can't
> really tell when, I'm just printing stuff to the screen.

First, please post a short test program that exhibits this behavior.

And second, describe the operating system you are running (DOS?
Windows? which version?).  `uclock' is known to have problems on some
versions of Windows, but you don't tell enough to decide whether this
is your problem.

- Raw text -