From: Paul Shirley <Paul AT no DOT spam DOT please>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: RHIDE: CPU working at full capacity
Date: Tue, 13 Jan 1998 17:43:58 +0000
Organization: wot? me?
Lines: 30
Distribution: world
Message-ID: <ccyt2zAef6u0Ewb1@foobar.co.uk>
References: <34baa59b DOT 26212656 AT news DOT cs DOT tu-berlin DOT de>
 <69f4po$34p$1 AT titan DOT globalserve DOT net>
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
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

In article <69f4po$34p$1 AT titan DOT globalserve DOT net>, Curtis Wensley
<eto AT globalserve DOT net> writes
>
>>I'm running Rhide under Win95 with 48 MB RAM and a
>>Pentium 133. Everything works fine, but after booting Rhide the CPU is
>>working non-stop at full capacity. I tried to change the way Win95
>>starts MS-DOS programs but it did not help. I also found no hint in
>>the FAQ.
>>
>>This state even keeps on after closing RHIDE when loaded from
>>a MS-DOS window. I have to close the MS-DOS to make the
>>CPU-usage come back to nomal.
>
>
>With win95, this is the same with ANY DOS-based program.. What you can try
>is setting the IDLE SENSITIVITY to HIGH in the MISC tab in the dos box's
>properties.. this may help free up CPU time when rhide is running and is
>idle.

Not strictly true, its usually caused by the way some DOS programs scan
the keyboard. Using software polling loops seems to soak up unlimitted
ammounts of CPU time, letting the BIOS wait for keys allows Windoze to
taskswitch away from the DOSbox.

Try setting the RHIDE dos box settings under Misc/Background to 'Always
suspend'. That should give the CPU back to windoze if you switch away
from RHide which may be enough. Alternatively its time to hack RHIDE.

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