From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-msdos@vger.kernel.org
Subject: Re: sound support (Re: XMS problem with Aladdin demo)
Date: Thu, 10 Mar 2005 23:17:52 -0600 [thread overview]
Message-ID: <20050311051752.GK28434@dbz.icequake.net> (raw)
In-Reply-To: <20050309194808.GR11254@dbz.icequake.net>
On Wed, Mar 09, 2005 at 01:48:08PM -0600, Ryan Underwood wrote:
> On Wed, Mar 09, 2005 at 08:02:37PM +0100, Julius Schwartzenberg wrote:
> >
> > When I set up the OPL3 chip in Linux, I specified it should use port
> > 0x388 and not another port. I'm able to change this port to something
> > else through the module settings. Would it be a good idea to change this
> > value?
>
> Most programs that want an Adlib or OPL3 chip expect the port to be
> 0x388. Only programs which used the dual-OPL2 of SBPro usually use
> 0x220, and these are very rare. Only program I know of that uses 0x228
> is sb-sound.com. So 0x388 is the best setting for now. I can't explain
> your other problems until I test this myself.
I checked this myself. Something strange is definitely happening. If I
enable tracing, I can see the adlib traffic, but no sound is coming out.
I also tried without tracing and with 'fast' and nothing happens there
either. The volume is OK because I've written a program on Linux side
that sets up a random adlib instrument to play, and I can hear the
sound there.
I wonder when this was broken, I know it worked perfectly only a few
months ago...
--
Ryan Underwood, <nemesis@icequake.net>
next prev parent reply other threads:[~2005-03-11 5:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 17:25 sound support (Re: XMS problem with Aladdin demo) Stas Sergeev
2005-03-09 19:02 ` Julius Schwartzenberg
2005-03-09 19:48 ` Ryan Underwood
2005-03-11 5:17 ` Ryan Underwood [this message]
2005-03-11 9:25 ` Julius Schwartzenberg
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 19:42 Stas Sergeev
2005-03-10 18:13 ` Julius Schwartzenberg
2005-03-10 18:45 ` Julius Schwartzenberg
2005-03-08 19:45 Stas Sergeev
2005-03-08 21:25 ` Ryan Underwood
2005-03-08 19:24 Stas Sergeev
2005-03-08 21:23 ` Ryan Underwood
2005-03-08 22:03 ` Julius Schwartzenberg
2005-03-08 22:15 ` Ryan Underwood
2005-03-08 23:05 ` Ryan Underwood
2005-03-09 9:27 ` Julius Schwartzenberg
2005-03-09 15:21 ` Ryan Underwood
2005-03-09 17:39 ` Ryan Underwood
2005-03-08 15:58 Stas Sergeev
2005-03-08 13:01 Stas Sergeev
2005-03-08 18:28 ` Julius Schwartzenberg
2005-03-08 19:31 ` Ryan Underwood
2005-03-08 22:15 ` Ryan Underwood
2005-03-08 20:39 ` Bernhard Bialas
2005-03-08 21:22 ` Ryan Underwood
2005-03-13 5:09 ` 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=20050311051752.GK28434@dbz.icequake.net \
--to=nemesis-lists@icequake.net \
--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