From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10206100508.AA11823@clio.rice.edu>
Subject: delay() on Win2K
To: djgpp-workers AT delorie DOT com (DJGPP developers)
Date: Mon, 10 Jun 2002 00:08:45 -0500 (CDT)
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

delay() calls int 0x15, ah=0x86 - on Win2K this fails (carry set).
My bios reference says this means some other timer is active.
It seems we should handle this case somehow.  For example, we can get
55 ms accuracy (roughly) using the bios area tics; we can get greater
than 1ms accuracy watching the msb from the timer register.

In any case, some delay (even if slightly inaccurate) should be better
than no delay at all.  If uclock() worked we could use it in a busy 
loop; even if it's buggy it's accuracy might be good enough for delay
when the carry set happens.  thoughts?