The only conflict with this old setup(I'm now using just the 82C929A - I would have used a SoundBlaster Pro 2.0, but I can no longer get it to work with the SoundBlaster sound option in X-Wing no matter what computer I plug it into. What the hell did I do to this thing? Ever since I tried a dual setup with the SoundBlaster Pro 2.0 and the SoundBlaster AWE64, the SoundBlaster Pro 2.0 has stopped working with the SoundBlaster sound option in X-Wing) was address range 388, the AdLib port(don't worry, I know you need different base addresses, IRQs and DMAs for each sound card). With the Windows 95 drivers for the OPTi 82C929A, you MUST cause a conflict at I/O range 388 with another ISA sound card in order to get any sound using the SoundBlaster sound option in X-Wing. Using just the DOS drivers, the 82C929A works perfectly with X-Wing using both the AdLib and SoundBlaster sound options(but I need to use a CPU slowdown tool since the slowest working computer I have runs on a 266MHz Pentium II - the YMF262 does not like CPUs faster than 133MHz and will output garbage when playing the floppy disk edition of X-Wing on a CPU faster than that).
But this bug also happens when the SoundBlaster AWE64 is used by itself. Here it is playing X-Wing using the General MIDI with SoundBlaster sound option(NOTE: turn the volume down, as X-Wing doesn't sound very good with the AWE64's default soundfont - I don't have a RAM module for my AWE64, so I can't load any soundfonts bigger than 512KB since I have an AWE64 Value): http://www.youtube.com/watch?v=BdoB-IKHHc4
The PCM at one point just stops working until I pause and unpause the game, same like when the AWE64 and 82C929A were working together.
Even my SoundBlaster 16 WavEffects model CT4170 suffers from the same bug, and this is using just the SoundBlaster 16 WavEffects.
Creator of The Many Sounds of:, a collection of various DOS games played using different sound cards.