Date: Mon, 29 Sep 1997 11:13:54 +0200 (METDST)
From: Robert Hoehne <robert DOT hoehne AT Mathematik DOT TU-Chemnitz DOT DE>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT edu DOT ar>, djgpp AT delorie DOT com
Subject: Re: Clipboard timing, strange results, Rhide (Was: DJGPP,
In-Reply-To: <Pine.SUN.3.91.970928183439.423F-100000@is>
Message-Id: <Pine.HPP.3.95q.970929110433.12324B-100000@newton.mathematik.tu-chemnitz.de>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Sun, 28 Sep 1997, Eli Zaretskii wrote:

> I have asked this before on this thread, but didn't see any answers,

Sorry, I overlooked this question. RHIDE doesn't hook any
interrupt in any case (this is my strictly rule because there
are too many problems with doing so).

And (as I posted it already) it has really (at least for me)
nothing to do with RHIDE. The user got to the result by
starting RHIDE, then creating a DOS-SHELL and then running the
benchmark (which I could reproduce) but then I tried it also
by spawning the benchmark (clip.exe) from other DJGPP
programs with the same result. That means the reason for
the speedup must be located somewhere in the DJGPP libc code.

To test it, open a DOS-window and run there (I assume that you
have the source from the news compiled):

clip.exe
redir clip.exe

And now look at the results.

Robert
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************