Message-ID: <373DCBAB.DB9BC535@enter.net>
Date: Sat, 15 May 1999 15:31:55 -0400
From: Sean <sproctor AT enter DOT net>
X-Mailer: Mozilla 4.51 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: uclock trouble
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 207.16.153.93
X-Original-NNTP-Posting-Host: 207.16.153.93
X-Trace: 15 May 1999 15:31:22 -0400, 207.16.153.93
Organization: Enter.Net
Lines: 10
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I've been using uclock() from libc, since clock() from there is horribly
imprecise.  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.  It counts back
up after it reaches its low point, which has been making all my timing
terribly off.  If anyone knows why, I'd appreciate it.  (preferably mail
me too, just in case I forget to check the response)  Thanks.

Sean