From: Paul Shirley <Paul AT no DOT spam DOT please>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE: CPU working at full capacity
Date: Sat, 17 Jan 1998 14:44:38 +0000
Organization: wot? me?
Distribution: world
Message-ID: <BquK7EAWPMw0EwL$@foobar.co.uk>
References: <RClOBSAGakv0EwTE AT foobar DOT co DOT uk> <m0xtCoB-000S23C AT inti DOT gov DOT ar>
Reply-To: Paul Shirley <Paul AT chocolat DOT obvious DOT fake DOT foobar DOT co DOT uk>
NNTP-Posting-Host: chocolat.foobar.co.uk
Mime-Version: 1.0
Lines: 27
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <m0xtCoB-000S23C AT inti DOT gov DOT ar>, "Salvador Eduardo Tropea
(SET)" <salvador AT inti DOT gov DOT ar> writes
>RHIDE never eats the CPU I think W95 GIVES the CPU to RHIDE if there is no 
>other task to run and hence RHIDE "usage" is 100%.

The problem is in the way Win95 handles DOS apps, its not smart enough
to notice polling loops and taskswitch away from them, and DOS boxes get
a BIG slice of the timeslice cake in the first place. _dpmi_yield
explicitly yields control so things improve, the alternative is to let
DOS call the idle time int (usually by letting BIOS calls wait for the
keyboard) and you get *all* the dead time handed back to windoze.

RHide does not need to do anything to get near 100% cpu usage, actively
doing nothing suffices ;) Its not that Rhide (or apps like JED) are
wrong, they just don't give win95 enough help in detecting idle time.

>> Paul Shirley: my email address is 'obvious'ly anti-spammed
>Yes and anti reply too. 

2 reasons: I don't want mailbots seeing my address anywhere, I really
hate cc'ed replies (particularly if I've not asked for help)

...and most people who've tried to mailbomb me were'nt smart enough to
alter the address ;)

---
Paul Shirley: my email address is 'obvious'ly anti-spammed