From: "Ben Peddell" Newsgroups: comp.os.msdos.djgpp References: <3e489301 DOT sandmann AT clio DOT rice DOT edu> Subject: Re: how to make a Timer Lines: 21 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Message-ID: <%v22a.45175$jM5.113869@newsfeeds.bigpond.com> Date: Tue, 11 Feb 2003 18:34:49 +1000 NNTP-Posting-Host: 144.139.175.101 X-Trace: newsfeeds.bigpond.com 1044952187 144.139.175.101 (Tue, 11 Feb 2003 19:29:47 EST) NNTP-Posting-Date: Tue, 11 Feb 2003 19:29:47 EST Organization: Telstra BigPond Internet Services (http://www.bigpond.com) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Why not make use of RDTSC? Just divide it by 84 for every 100MHz of CPU speed. (i.e. for a 1GHz [100MHz x 10] processor, divide by 840; for a processor with a 13.5x multiplier on a 143MHz FSB [1933MHz], divide by 1620.) Charles Sandmann wrote in message news:3e489301 DOT sandmann AT clio DOT rice DOT edu... > > However problem with uclock resolution not solved. > > Ah, yes, I believe it's delay() that was fixed, not uclock. > > The problem with uclock is the bios tic rollover isn't aligned with the > PIT counter under Win2K. It happens at roughly the same point in the > cycle - but not exactly - each time. > > Someplace I have code that works "better" - but still not perfect. > I haven't decided if "better" is worth putting in since it's still > broken - just less noticable (which might be worse...) >