Julius Schwartzenberg schreef:
Stas Sergeev schreef:

Hello.

Julius Schwartzenberg wrote:

I already tried this, but it
doesn't seem to make any difference.


But dosemu stops complaining about the
port conflicts, right?

Yes, that complaint is gone then.

I just tried it. Wolfenstein 3-D now is able to detect the OPL3 chip, but I can't hear anything (probably because the mixer isn't set).
In Wacky Wheels, I also can't hear anything.


Hmm, would it be possible then to boot
into DOS, set the mixer volumes, then
reboot back to linux (but with the "hot"
reboot, not with the reset button), and
then, if you don't load any ALSA module,
I think the volume will stick.

I do not have a DOS installation on the laptop at the moment (and my floppy drive doesn't seem to work very well), so I can't try that at the moment.


Another thing to try is to open also all
the SB ports to the DOS prog. Then you'll
probably be able to use mixer, and it
is also possible to use the SB ports
for the OPL access.

I'm wondering if opening all SB ports will work, since the chip probably needs a DOS program before it's Sound Blaster compatible mode can be used. Also /proc/ioports doesn't list anything at those other ports.
I tried running the DOS programs from Yamaha in Dosemu. One of the programs quits with an error it can't run in a MS Windows Dosbox, another complains about the lack of EMM386 and VCPI support. I tried loading EMM386, but it says there are already protected mode applications running.

I just found out some more. When I run pmidi with a midi file while Wacky Wheels is running, I can hear both the midi file I am playing and Wacky Wheels, but now I can also hear more of the music from Wacky Wheels than I can hear when I do not play the midi file at the same time. It doesn't matter whether I start pmidi first or Wacky Wheels first.
It seems they are indeed messing with each other.


Thanks,
Julius

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to