From: XXguille AT XXiies DOT XXes (Guillermo Rodriguez Garcia)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: kbhit() and SIGALRM
Date: Thu, 29 Apr 1999 01:18:25 GMT
Organization: Telefonica Transmision de Datos
Lines: 24
Message-ID: <3728b2a4.1601280@noticias.iies.es>
References: <372048CA DOT 39306E43 AT fiar DOT finmeccanica DOT it> <37284866 DOT 2405010 AT noticias DOT iies DOT es> <199904262035 DOT QAA24388 AT envy DOT delorie DOT com>
NNTP-Posting-Host: iies254.iies.es
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: Forte Agent 1.5/32.451
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

El día Mon, 26 Apr 1999 16:35:03 -0400, DJ Delorie <dj AT delorie DOT com>
escribió:

>
>> >(I know, uclock() could fail under Win95).
>> 
>> More info on this, please? Under which conditions will uclock() fail?
>
>When you're running under Win95.  Win95 reprograms the timer to a mode
>that makes uclock() fail.

I am running under Win95 and Win98 in different machines and uclock()
works perfectly for me. I am measuring time ellapsed between changes
in an external signal which is attached to a bit in the serial port,
and the times I get are accurate (I am checking them with a digital
oscilloscope). So uclock() doesn't always fail under W95. Could anyone
please tell me when and where uclock() fails ?

Regards,
GUILLE

----
Guillermo Rodriguez Garcia
XXguille AT XXiies DOT XXes (ya sabes :-)