Date: Thu, 1 Feb 2001 11:09:34 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp AT delorie DOT com
Subject: Re: DJGPP timer slowdown
In-Reply-To: <95a1qh$gkt4b$1@ID-57378.news.dfncis.de>
Message-ID: <Pine.SUN.3.91.1010201110914.13803K-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 31 Jan 2001, Alexei A. Frounze wrote:

> Timer itself generates IRQs at a constant rate, right. But the DOS program
> being run under windows (or with presense of such things as SMARTDRV) can
> not have a perfect time measurement and perfect cycle measurement.

As you can see from the message posted by Damon Casale, I wasn't
talking about the code timing, I was talking about system clock
slow-down apparently caused by a file-compression program.

> Try to reread my post and see why.

I think I understood the first time, that's why I wrote what I wrote.