From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: dosemu 1.1.3.9 user report
Date: Mon, 16 Dec 2002 19:49:57 +0100 [thread overview]
Message-ID: <3DFE2055.5000802@my.home> (raw)
In-Reply-To: Pine.LNX.4.33.0212151434190.9776-100000@enm-bo-lt.localdomain
According to "top", 1.1.3.9 takes up 99 % CPU even when just
displaying the C:> prompt.
1.1.3.7 does this also; but 1.1.3.0 and 1.0.2.1 do not. They
hardly use any CPU when just displaying the prompt (or waiting for
a keystroke in a text-mode program).
Wolfenstein 3D:
1.0.2.1, 1.1.3.7, 1.1.3.9 play with $_sound = (off) .
1.1.3.0 hangs (with or without sound) after displaying the
start-up (setup) screen. Control-Alt-PgDn is the only way out.
1.1.3.7, 1.1.3.9 hang with $_sound = (on) .
Duke Nukem3D:
1.0.2.1 plays fine without sound.
1.1.3.0 plays without sound, but after a short while suddenly
disappears (no more dosemu window).
1.1.3.7, 1.1.3.9 play, with $_sound = (on) and soundblaster
selected in Duke Nukem Setup. I can see *and hear* the demo
(sounds, no music). When I want to start a game, I can select the
game type ("L.A. Meltdown" or whatever); however, when I try to
select the difficulty level the program hangs.
All this with kernel 2.2.18pre21, $_dpmi = (8192) , $_hogthreshold
= (800).
Regards, Jan
next prev parent reply other threads:[~2002-12-16 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-15 19:45 dosemu 1.1.3.9 for testing Bart Oldeman
2002-12-16 18:49 ` Jan Willem Stumpel [this message]
2002-12-16 19:17 ` dosemu 1.1.3.9 user report Peter Jay Salzman
2002-12-16 19:49 ` Bart Oldeman
2002-12-16 23:57 ` mouse grabbing gotcha (was: dosemu 1.1.3.9 user report) Peter Jay Salzman
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 19:23 dosemu 1.1.3.9 user report Stas Sergeev
2002-12-16 21:41 ` Jan Willem Stumpel
2002-12-16 22:15 ` Bart Oldeman
2002-12-16 19:58 Stas Sergeev
2002-12-16 22:09 Stas Sergeev
2002-12-17 17:58 Jan Willem Stumpel
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=3DFE2055.5000802@my.home \
--to=jstumpel@planet.nl \
--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