All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Dosemu and clipper applications eating all CPU
Date: Wed, 10 Mar 2004 21:36:15 +0300	[thread overview]
Message-ID: <404F601F.9050001@aknet.ru> (raw)


Hello.

Peter B. Steiger wrote:
>> Problem of clipper I presume? If it
>> just runs in a busy loop while idle,
>> dosemu can't really help.
>  That is exactly the problem.  On NT/XP systems, there is a third-party
>  program called TAMEDOS which intercepts the busy loops and does
>  something so that the CPU is free but the application does not slow
>  down.
If some prog can do that, then dosemu
should either. It is just a matter of
knowing what exactly that program
intercepts ("intercepts the busy loops"
is too obscure).
Maybe a test-case of a clipper prog can
be found somewhere to see what it does?

> know at least one of the loops is a constant keyboard poll:
dosemu is catching that. It is also
trying to catch a mouse polling, and
then people complain that programs
slows down when mouse is inactive:)
It also intercepts the timer polling
and some other things. I have no
guesses as to what's missing.

             reply	other threads:[~2004-03-10 18:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-10 18:36 Stas Sergeev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-28 17:32 Dosemu and clipper applications eating all CPU Stas Sergeev
2004-04-28  5:55 Mgr. Peter Tuharsky
2004-04-28 19:52 ` Maximiliano Curia
2004-03-15 19:17 Stas Sergeev
2004-03-15 17:50 Stas Sergeev
2004-03-15 18:07 ` Maurilio Longo
2004-03-12 22:33 Stas Sergeev
2004-03-15 11:53 ` Maurilio Longo
2004-03-11 18:44 Stas Sergeev
2004-03-10 19:36 Stas Sergeev
2004-03-10 22:55 ` Maurilio Longo
2004-03-11  8:29   ` Maurilio Longo
2004-03-09 20:16 Stas Sergeev
2004-03-10 15:29 ` Peter B. Steiger
2004-03-10 19:11 ` Maximiliano Curia
2004-03-08 16:11 Maximiliano Curia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=404F601F.9050001@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.