sound support (Re: XMS problem with Aladdin demo)
Hello.
Quoted 1 line · Julius Schwartzenberg
Any idea why it is only 'half' working?
I can think of 2 things: either it is a conflict with the linux driver, or with dosemu. You can isolate the both possibilities.
1. Disable sound in dosemu config. Then dosemu will not even try to grab an OPL ports. Yes, SB won't work, but Wolf might still be able to see Adlib, and you'll be able to tell if it works any better.
2. Disable all the sound drivers in linux and reboot the machine just in case. Make sure they are still not loaded after reboot. Maybe they configure your card somehow that the DOS prog starts having problems.
Stas Sergeev schreef:
Quoted 6 lines
Hello.
Quoted 1 line · Julius Schwartzenberg
Any idea why it is only 'half' working?
Quoted 10 lines
I can think of 2 things: either it is a conflict with the linux driver, or with dosemu. You can isolate the both possibilities.
1. Disable sound in dosemu config. Then dosemu will not even try to grab an OPL ports. Yes, SB won't work, but Wolf might still be able to see Adlib, and you'll be able to tell if it works any better.
I already tried this, but it doesn't seem to make any difference. Everything works exactly as when it is enabled, just without digital sound.
Quoted 6 lines
2. Disable all the sound drivers in linux and reboot the machine just in case. Make sure they are still not loaded after reboot. Maybe they configure your card somehow that the DOS prog starts having problems.
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.
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?
Thanks,
Julius
Quoted 5 lines · Julius Schwartzenberg
When I set up the OPL3 chip in Linux, I specified it should use port
0x388and 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.
Signature · 1 line
Ryan Underwood, <[email protected]>
Quoted 7 lines · Ryan Underwood
Quoted 5 lines · Julius Schwartzenberg
When I set up the OPL3 chip in Linux, I specified it should use port
0x388and 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?
Quoted 5 lines
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 use0x220, and these are very rare. Only program I know of that uses0x228is sb-sound.com. So0x388is 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...
Signature · 1 line
Ryan Underwood, <[email protected]>
Ryan Underwood schreef:
Quoted 9 lines
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...
It also didn't work for me with the CVS version from 26-12-2004. (Same results as with the current version.) I think I'll install version 1.2 and see what that one does.
Thanks,
Julius