Link to home
Start Free TrialLog in
Avatar of acmartin
acmartin

asked on

OS/2 Warp 4 and win-os2 sound

I have a soundblaster 16 sound card which I installed in DOS and win-os2 using the drivers which came with the card.
      After a fresh bootup and while starting my first win-os2 session I would get an error message that my soundblaster configuration is at fault and that my soundblaster wave and midi driver was not working.Advice is then given to reconfigure in control panel.However, on shutting down and restarting the session I get no error messages and my win-os2 sound works okay.
      What could be the problem?
NB.I have checked my os/2 config.sys and hardware manager and compared the IRQ and DMA settings with that of the win-os2 sytem.ini file and also autoexec.bat but there are no conflicts.DOS sound is fine.
Avatar of acmartin
acmartin

ASKER

Edited text of question
ASKER CERTIFIED SOLUTION
Avatar of avk
avk

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I tried this and no go.
Everything seems okay.
try to add this line in your autoexec.bat
[path to sbfiles\]sndinit /b

and check that this line is in your os/2 config.sys

DEVICE=D:\MMOS2\SB16D2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /M:330 /N:SBAUD1$ /Q /P
DEVICE=D:\MMOS2\AUDIOVDD.SYS SBAUD1$

/c = cardnumber
/d = lowdma
/h = highdma
/i = IRQ
/a = base address
/m = midiport
/d = drivername
/q = quiet mode,
     for checking change this to /v
/p = Initialize PNP mode !!

check that those settings are identical to your "set blaster=..." (autoexec.bat) and the winos2 "system.ini" settings

arjan
avk@xs4all.nl
They are identical.The only thing left to do was to add your statement '[path to sbfiles\]sndinit /b' to my autoexec.bat file which was not accepted on opening a session.
      Anymore ideas? You have reached now where I am stuck and cannot think of what else to do.
      In order to install the sound card in DOS, I had to install the ISA plug and play configuration manager in a DOS session. Could this be the source of the problem?