From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: Sound in Doom
Date: Thu, 27 Jun 2002 02:24:41 +0400 [thread overview]
Message-ID: <3D1A3F29.10600@yahoo.com> (raw)
Hello.
Stian Sletner wrote:
> | You have to pay attention also to other patches since they can also
> be quite usefull.
> It was not apparent that they were needed. But it works now.
I kind of asumed that people
looking to get sound working,
will first of all apply the SB
patch and only if this doesn't
help, they'll start looking at
an extensions such as the hack
to make doom working.
The fact that dosemu claims to
already have an SB support, must
no longer confuse people: not
that it is completely non-functional,
but the progs that can work with
it, can be counted by fingers.
Anyway I have added a note on the page.
> It is quite choppy, though (the sound that is, not the game),
> is that to be expected?
Yes, unfortunately this is all my
patch can do for it. Most progs
must work well but not the ones
that uses DMA regs for synchronisation
instead of SB interrupts. The problem
is that for speed-up purposes dosemu
does DMA transferrs by a large blocks
rather than by single bytes, as a
real DMAC does. This confuses such
progs.
Make DMAC to be a separate thread
will solve the problem only partially:
OSS sound drivers doesn't like a
small transferrs.
So solution for that is not planned.
Use Linux ports of Doom instead.
One of such ports called "prboom"
have much better graphics than an
original one, so there is really
no reason to use dosemu for running
doom anymore.
next reply other threads:[~2002-06-26 22:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 22:24 Stas Sergeev [this message]
2002-06-26 23:17 ` Sound in Doom Stian Sletner
2002-06-26 23:21 ` Bart Oldeman
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 23:31 Stas Sergeev
2002-06-26 16:59 ` Stian Sletner
2002-05-27 15:57 Stas Sergeev
2002-06-19 21:08 ` Stian Sletner
2002-05-26 22:44 Stian Sletner
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=3D1A3F29.10600@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@vger.kernel.org \
--cc=stas.orel@mailcity.com \
/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