Linux MS DOS discussions
 help / color / mirror / Atom feed
From: Julius Schwartzenberg <julius@zgod.cjb.net>
To: linux-msdos@vger.kernel.org
Subject: Re: sound support (Re: XMS problem with Aladdin demo)
Date: Wed, 09 Mar 2005 10:27:16 +0100	[thread overview]
Message-ID: <422EC174.2040400@zgod.cjb.net> (raw)
In-Reply-To: <20050308230541.GE28434@dbz.icequake.net>

Ryan Underwood schreef:
> More reply:
> 
> On Tue, Mar 08, 2005 at 11:03:23PM +0100, Julius Schwartzenberg wrote:
> 
>>>If you have the hardware, this works fine.  However, dosemu must be
>>>started as root.
> 
> 
> PS. Or sudo.
My Dosemu owned by root already has u+s. I thought that was about the 
same as running as root, but that indeed doesn't do.

>>Cool, I've just got this to work!
>>It doesn't seem to work fully though.
>>I've added this to my dosemu.conf:
>>$_ports=" device /dev/snd/seq range 0x388 0x38b"
>>I'm using a YMFPCI chip which seems to contains an OPL3.
> 
> 
> Yes, these chips do have a real OPL3, but must be enabled by the PCI
> configuration.  Since you are using this for MIDI seq, it is likely the
> case.  But the ALSA OPL3 driver may be using MMIO access and not PIO.
> Check your /proc/ioports to see where ALSA claims the OPL3 ports
> actually exists.
> 
> You can also enable IO-tracing for all of the mentioned ranges
> (0x220-0x223, 0x228-0x229, 0x388-0x38b) to see where the app tries to
> write OPL commands to.  If it is writing to the wrong range relative to
> the real hardware, it's possible to redirect that access.  Redirected
> access would be slower but with OPL this doesn't make much difference
> since there is so little I/O traffic.
In /proc/ioports the OPL3 is only listed at 0388-038b, which is why I 
set up that port range in Dosemu. The other ranges you mention to seem 
not to be used. Here is the full output of catting /proc/ioports:
http://haar.student.utwente.nl/~julius/ioports-laptop
I believe Wacky Wheels and Wolfenstein 3-D worked without problems when 
I ran them without Linux/Dosemu in DOS, so the hardware seems to be capable.

Thanks,
Julius

  reply	other threads:[~2005-03-09  9:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 19:24 sound support (Re: XMS problem with Aladdin demo) 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 [this message]
2005-03-09 15:21         ` Ryan Underwood
2005-03-09 17:39           ` Ryan Underwood
  -- 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-09 17:25 Stas Sergeev
2005-03-09 19:02 ` Julius Schwartzenberg
2005-03-09 19:48   ` Ryan Underwood
2005-03-11  5:17     ` Ryan Underwood
2005-03-11  9:25       ` Julius Schwartzenberg
2005-03-08 19:45 Stas Sergeev
2005-03-08 21:25 ` 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=422EC174.2040400@zgod.cjb.net \
    --to=julius@zgod.cjb.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