Date: Sun, 28 Sep 1997 18:34:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>
cc: Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE>, djgpp AT delorie DOT com
Subject: Re: Clipboard timing, strange results, Rhide (Was: DJGPP, 
In-Reply-To: <m0xEEUD-000S1xC@inti.edu.ar>
Message-ID: <Pine.SUN.3.91.970928183439.423F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Thu, 25 Sep 1997, Salvador Eduardo Tropea (SET) wrote:

> In plain DOS the effect is the reverse. RHIDE slows down the programs, or at 
> list the timing routines seems to indicate that. My plasmas run slower from 
> RHIDE and the meassured time is less stable than trying from
> DOS. Why? I don't know.

I have asked this before on this thread, but didn't see any answers,
so I will ask again: doesn't RHIDE hook the timer inetrrupt?  If it
does, and if it doesn't unhook it when running child programs, then
this might explain the behavior on DOS (an extra level of interrupt
handling).  And Windows might change its scheduling of a program that
has hooked the timer.