All of lore.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: Tue, 17 Dec 2002 18:58:44 +0100	[thread overview]
Message-ID: <3DFF65D4.6070002@my.home> (raw)

Stas Sergeev wrote:

> Nope... The fact that you got any sound at all from Duke3D
> without an immediate hang, is something very unusual. To get a
> sound from Duke3D and no hangs, this patch is a mandatory:
> http://dosemu.sourceforge.net/stas/dpmi_sti4a.diff Also read
> the comments about an adjustments you have to make to
> dosemu.conf after applying it.

I did, and now it works! A voice begins to utter threatening
language as soon as I select the difficulty level, and the game
goes on. In the demo there were only shooting sounds, etc. Maybe
voice synthesis is a different kind of task than making just "sounds".

Wolf3D still hangs at the start screen, however. At the bottom
right it says V1.1.

> Also please produce a log of a sound events (-D9+S) and mail it
> to me compressed, and maybe I'll see the problem.

I'll do that (as soon as I've found out how).

Regards, Jan



             reply	other threads:[~2002-12-17 17:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-17 17:58 Jan Willem Stumpel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-16 22:09 dosemu 1.1.3.9 user report Stas Sergeev
2002-12-16 19:58 Stas Sergeev
2002-12-16 19:23 Stas Sergeev
2002-12-16 21:41 ` Jan Willem Stumpel
2002-12-16 22:15   ` Bart Oldeman
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=3DFF65D4.6070002@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 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.