Re: Dosemu and clipper applications eating all CPU

[Maurilio Longo <maurilio.longo@libero.it>]

Stas,

clipper calls time-of-day interrupt when idle, don't have right number 
of interrupt call here at home, but I did write some years ago a little 
TSR to release cpu under OS/2 and I'm using a home-made dosemu 1.0.x at 
work with a changed handling of this interrupt call inside dosemu code, 
tomorrow I'll tell you the right call.

regards.



Stas Sergeev wrote:

>
> Hello.
>
> Maximiliano Curia wrote:
>
>>> Problem of clipper I presume? If it
>>> just runs in a busy loop while idle,
>>> dosemu can't really help.
>>
>>  Yes, that dosemu doesn't detect the clipper idle calls.
>
> But *what kind* of idle calls?
> This is the vital info. If you
> can't find the answer, then the
> problem can't be fixed:)
> int 0x28 is the real idle call,
> but since dosemu catches that,
> I suspect clipper does something
> else.
>
>> It still eats the cpu, with nice -n 19, but now the 60% is marked as
>> nice.
>
> Yes, and the system must not be
> crawled now at least. At least in
> a theory:)
>
>> I'm trying to understand the freedos idle.
>
> That might be not the case either.
> FreeDOS can just call int16 to do
> a blocking wait for a keypress, and
> that will do the trick.
> You have to find out what exactly
> the clipper does however.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

-- 
 __________
|  |  | |__|  Maurilio Longo
|_|_|_|____|