Here are some things that I did to get sound running satisfactorily in Warp with my Soundblaster 16.
Bear the follwing in mind:
OS/2 and Windows sessions still cannot share the card. But, it is a simple matter of taking the Windows sessions down and enabling OS/2 sounds when you need to. Be sure and turn off OS/2 sound before bringing up fastload session again. I put a shadow of the sound folder on my desktop to make it easier to switch OS/2 sound on and off.
Windows applications running within a fastload session can share the card since they are essentially running under the Windows session created by fastload. Separate sessons and full screen sessions can't share because you then have several copies of Windows trying to run.
By the way, it may be confusing at first that, even though applications running within the fastload session generate sounds, the only opening and closing sounds you get is at start and close of the fastload session. When you realize that the fastload session IS the Windows session, then it s easy to understand: the other sessions within fastload session are not starting Windows. It s already running.
I have found a few of my sound applications still can t get to the ound card even with these workarounds and even though they bear the Creative Labs name. But, I think these applications (like a talking schedular) came with a Microsoft package and may have been written this way on purpose. The schedular and other apps that came with the sound card work fine.
For multimedia, there are some things you can do with the CDFS file system to improve audio playback. Increase the buffers and such by changing the line in onfig.sys:
IFS=E:\OS2\BOOT\CDFS.IFS /C:8 /m:20 /q