public inbox for linux-msdos@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Willem Stumpel <jstumpel@planet.nl>
To: linux-msdos@vger.kernel.org
Subject: Re: dosemu 1.1.3.9 user report
Date: Mon, 16 Dec 2002 22:41:20 +0100	[thread overview]
Message-ID: <3DFE4880.3020604@my.home> (raw)
In-Reply-To: 3DFE2840.3040103@yahoo.com

Stas Sergeev wrote:
> Hello.

And hello to you too!

> Jan Willem Stumpel wrote:
>> According to "top", 1.1.3.9 takes up 99 % CPU even when just
>> displaying the C:> prompt.

> Sure with such a hogthreshold value. Since 1.1.3.8 you don't
> need to set most of the options manually, so just delete the
> $_hogthreshold from your dosemu.conf and you're fine.

OK.. used the new dosemu.conf (everything commented out), set
hdimage to "dos" to make it boot on my system, then only changed
hogthreshold. Tried it (1.1.3.9) with

hogthreshold = 0                      --- 99 % CPU
hogthreshold = 1                      --- quiet behaviour
hogthreshold = 800  		      --- 99 % CPU
hogthreshold commented out altogether --- quiet behaviour

Mmm.. not very intuitive, this. Somewhere in the DOC's it
says that hogthreshold should be related to the clock speed, and
the higher hogthreshold, the quieter dosemu gets. Anyway, you know
what I think about the dosemu doc's.

With all these values of hogthreshold Wolfenstein 3D hangs (it
keeps saying "one moment" forever). This is with everything
commented out apart from hdimage and hogthreshold.

Now I uncomment sound, and set it to 0. Now it works with
hogthreshold values 0, 1, 800, and commented out altogether.

This suggests that sound (on) is the default (as you surely
intended). OK, now trying Nukem 3D (*everything* commented out now
apart from hdimage). Use Duke3d "setup" program (in dosemu) to
select the Sound Blaster card for sound, nothing for music. Run
duke3d. Result: sound, demo visible and audible, when I want to
play it hangs when I choose the difficulty level.

> So you have applied some patches, havent you?

Well of course I did. The patch set posted yesterday by Bart
Oldeman. Or isn't that what you mean? Anyway I get a boot-up
message which begins

Linux DOS emulator 1.1.3.9 $Date: 2002/12/15 $

Extra info: I use ms-dos 6.00. Maybe that's relevant.

Regards, Jan


  reply	other threads:[~2002-12-16 21:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-16 19:23 dosemu 1.1.3.9 user report Stas Sergeev
2002-12-16 21:41 ` Jan Willem Stumpel [this message]
2002-12-16 22:15   ` Bart Oldeman
  -- strict thread matches above, loose matches on Subject: below --
2002-12-17 17:58 Jan Willem Stumpel
2002-12-16 22:09 Stas Sergeev
2002-12-16 19:58 Stas Sergeev
2002-12-15 19:45 dosemu 1.1.3.9 for testing Bart Oldeman
2002-12-16 18:49 ` dosemu 1.1.3.9 user report Jan Willem Stumpel
2002-12-16 19:17   ` Peter Jay Salzman
2002-12-16 19:49     ` Bart Oldeman

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=3DFE4880.3020604@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