Message-ID: <3692B1AB.BD2391B7@montana.com>
Date: Tue, 05 Jan 1999 17:43:23 -0700
From: bowman <bowman AT montana DOT com>
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp AT delorie DOT com
Subject: Re: timing in u sec range
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990103103639 DOT 12860B-100000 AT is> <36928BD8 DOT 8FED643D AT cyberoptics DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com



Eric Rudd wrote:
> 
> timer routine failed similarly, I have concluded that Win95 (in its infinite
> wisdom) is periodically tampering with the 8254, so I gave up on uclock(), and

How were you attempting to read the 8254? It has been a while since I've
played with it, but my impression was if you use inport*(), Windows32 is
only allowing you access to a virtual 8254, with very little effort
given to maintain in in sync. I moved a Windows16 app that was
manipulating the speaker, and using the 8254 for timing, and it fell
apart completely on Windows32, to the point where I had to generate a
pcm buffer and use the mmio extensions to get any control over pitch and
timing.

There is a decent timer in the mmsystem package, but this is assuming
you are building a windows app.