delorie.com/archives/browse.cgi | search |
From: | sandmann AT clio DOT rice DOT edu (Charles Sandmann) |
Message-Id: | <10206100445.AA21243@clio.rice.edu> |
Subject: | Re: uclock() on Win2K |
To: | djgpp-workers AT delorie DOT com (DJGPP developers) |
Date: | Sun, 9 Jun 2002 23:45:48 -0500 (CDT) |
In-Reply-To: | <no.id> from "sandmann" at Jun 09, 2002 10:52:29 PM |
X-Mailer: | ELM [version 2.5 PL2] |
Mime-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> On my Win95 box it doesn't work either - the timer seems to stay on > rate generator (so it's not continuous); there are jumps in the time. It now seems to be working on Win95. Miracles never cease. Sometimes the timer reprogram takes, sometimes it doesn't? It seems that the time between tics on Win2K isn't very even; I'm seeing anything from 280 msb per tic and 252 msb per tic. When I let it run for a long time it seems to settle down to an average of around 256 msb per tic. The first calibration tic always has much more than 256. Maybe it reacts to the calibration and tries to bring an emulated timer in line? In any case, it would seem difficult to fix.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |