Re: Dosemu and clipper applications eating all CPU

[Stas Sergeev <stsp@aknet.ru>]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Hello.

Maximiliano Curia wrote:
> Yes, that dosemu doesn't detect the clipper idle calls.
OK, some nice guy at SF finally
provided a clipper-based program
for testing (that's why I like
the SF tracker) and I was able to
have a look at what it does myself.
Indeed it calls int21h/1Ch, although
so infrequently, that it doesn't
seem to be usefull here.
It calls int16h/11h a bit more
frequently, although also rather
rarely.
The attached patch makes it to
release the CPU a little, although
perhaps still not enough.
Also note that clipper will work
in protected mode only in dosemu
1.3.1. On any other versions it
can work in real mode only, which
may have a different CPU loads.

[-- Attachment #2: delay.diff --]
[-- Type: text/plain, Size: 424 bytes --]

--- src/base/bios/int16.c	Sat Mar 13 00:40:05 2004
+++ src/base/bios/int16.c	Sat Mar 13 01:15:29 2004
@@ -126,7 +126,7 @@
       trigger1=0;
     if(trigger1 >= config.hogthreshold*500) {
       if(oldESP==_ESP) {
-        if (++trigger >= config.hogthreshold*20) {
+        if (trigger++ >= (config.hogthreshold - 1) * 20) {
           usleep(INT2F_IDLE_USECS);
           trigger=0;
           keyptr = get_key(extended);

[-- Attachment #3: Type: text/plain, Size: 81 bytes --]

Scanned by evaluation version of Dr.Web antivirus Daemon 
http://drweb.ru/unix/