Re: dosemu 1.1.3.9 user report

[Stas Sergeev <stssppnn@yahoo.com>]

Hello.

Jan Willem Stumpel wrote:
> According to "top", 1.1.3.9 takes up 99 % CPU even when just
> displaying the C:> prompt.
[]
> $_hogthreshold = (800).
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.

> 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) .
Very strange... Wolf is the one of
those few progs that used to work with
sound even on early dosemus (like
1.0.2.1) and that was my main testcase
for the new sound engine and I think
I made wolf to sound flawlessly.
So I would suspect there are some
problems in your dosemu.conf again.
Probably XMS/EMS are too low.
Try to throw away all the options from
your dosemu.conf (except for the most
important ones like $_hdimage if you
use some non-standard booting methods)
because the default options are just fine.

> 1.1.3.7, 1.1.3.9 play, with $_sound = (on) and soundblaster
> selected in Duke Nukem Setup.
So you have applied some patches, havent you?

> (sounds, no music).
Well, getting sound and music together is
currently not always possible. But if
you have an SB Live card or some other
card with a hardware mixing abilities
(and the driver supports this), you can
get music working together with sound.
sound-usage.txt of 1.1.3.9 describes the
ways of doing that (thanks to Rob Komar
for the detailed instructions about getting
the music to work on ALSA).

> however, when I try to
> select the difficulty level the program hangs.
[]
> $_dpmi = (8192)
Too low. Remove that option from dosemu.conf
and see if it helps (Duke works perfectly
here most of the time) and if not - try this:
http://dosemu.sourceforge.net/stas/pic_prot.diff
However yes, 100% reliability of DPMI progs
is not yet.