From: Alain <alainm@pobox.com>
To: Dosemu <linux-msdos@vger.kernel.org>
Subject: Re: [announce] dosemu-1.3.3
Date: Fri, 30 Dec 2005 22:17:31 -0200 [thread overview]
Message-ID: <43B5CE1B.4000808@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0512311157490.16042@enm-bo-lt.localnet>
Hi Bart,
>> I have made some real improuvements changing the check_key_available()
>> function in int16.c and the delay calls.
>
> The delay calls have also changed in CVS after 1.3.3 so you might want
> to update that again (src/emu-i386/cputime.c).
I will check, is it suposed to change again?
> But if you still have problems even with "speed 0" that won't help.
speed 0 is ok, even something like speed form 2 to sometimes 4. BUT, in
both cases I get 98% cpu usage.
> "grep" is your friend.
Only if you are lost in the forrest XOR you have a lamp, but not both ;-)
Thaks and Happy new year,
Alain
next prev parent reply other threads:[~2005-12-31 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-30 16:15 [announce] dosemu-1.3.3 Alain
2005-12-30 23:04 ` Bart Oldeman
2005-12-31 0:17 ` Alain [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 8:07 Bart Oldeman
2005-12-24 0:07 ` Ralph Alvy
2005-12-24 0:18 ` Bart Oldeman
2005-12-24 1:33 ` Ralph Alvy
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=43B5CE1B.4000808@pobox.com \
--to=alainm@pobox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox