This post is reserved for listing the Audigy models that were confirmed to work with this guide:

• SB0090 (retail Audigy 1) - confirmed working by me
• SB0160 (Audigy ES) - confirmed working by user geg81 link
• SB0240 (retail Audigy 2) - confirmed working by me
• SB0350 (retail Audigy 2 ZS) - confirmed working by me
• SB0360 (retail Audigy 2 ZS Platinum Pro) - confirmed working by user Studiostriver link

For those who have several sound cards installed, it's also possible to setup SB16 emulation with non-default settings
I have patched VxD from Audigy2 ZS driver CD ISO in order to modify MPU-401 and Adlib ports

• Input/Output Range: 0330-0331 => 0320-0321
• Input/Output Range: 0388-038B => 0288-028B

Other parameters of the driver can be changed in Windows Device Manager; this should resolve all conflicts

crvs wrote on 2020-06-14, 09:15:

I have patched VxD from Audigy2 ZS driver CD ISO in order to modify MPU-401 and Adlib ports

I don't think this is necessary.

Using the original drivers, right click on My Computer > Properties > Device Manager > Sound, Video and Game Controllers > Creative SB16 Emulation > Properties > Resources and uncheck "Use automatic settings". Then, choose "Basic Configuration 0002" > Change Setting.

This will allow you to manually change any settings except for the Adlib port (0388-038B). If you already have a different Adlib device installed (from a second sound card) it will show a conflict, but that won't affect the playback of the secondary sound card in any way.

You can also choose "Basic Configuration 0004" which will completely disable the Adlib port on the Creative SB16 Emulation device while leaving the MPU-401 available for General MIDI via soundfonts.

Joseph_Joestar wrote on 2020-06-14, 09:53:

I don't think this is necessary.

Depends on what you wished to achieve. I wanted both cards fully functional, including possibility to use MPU / Adlib of Audigy 2.

Joseph_Joestar wrote on 2020-06-14, 09:53:

Using the original drivers, right click on My Computer > Properties > Device Manager > Sound, Video and Game Controllers > Creative SB16 Emulation > Properties > Resources and uncheck "Use automatic settings". Then, choose "Basic Configuration 0002" > Change Setting.

This will allow you to manually change any settings except for the Adlib port (0388-038B).

Any settings besides Adlib (0388-038B) and MPU-401 (0330-0331).

crvs wrote on 2020-06-14, 15:14:

Any settings besides Adlib (0388-038B) and MPU-401 (0330-0331).

I can change the MPU-401 settings without any issues.

Did you follow the steps I posted above? Like I said, you need to use "Basic Configuration 0002" for this to work.

Excellent write up, thank you for this.

SilverHawk wrote on 2020-08-07, 12:40:

Excellent write up, thank you for this.

You're welcome!

Thanks Joseph, your guide worked, somehow, to install my Audigy 2ZS on my Windows Millenium PC. The only however was the DOS Driver Installation. The step 4.3 wont worked, because the setup refused to go saying that I'm not using an Win9x OS.... But it didn't matter because after that, even with an error, the Creative SB16 Emulation showed on my Device List as expected...

undeon wrote on 2020-08-26, 12:21:

Thanks Joseph, your guide worked, somehow, to install my Audigy 2ZS on my Windows Millenium PC.

Unexpected, but nice to hear that this works on WinME as well!

The only however was the DOS Driver Installation. The step 4.3 wont worked, because the setup refused to go saying that I'm not using an Win9x OS.... But it didn't matter because after that, even with an error, the Creative SB16 Emulation showed on my Device List as expected...

Interesting. I think the error occurred because WinME does not process AUTOEXEC.BAT and the SB16 emulation needs to add the DOS portion of the driver (SBEINIT.COM) to it.

DOS games might still work under the Windows prompt, even without SBEINIT.COM, but some issues may arise especially in older titles. Let us know how it turns out.

Thanks for posting such a detailed guide. I'm trying to see if it's feasible to use the Audigy 2 in Pure DOS using AUDIGY12.EXE, and I've been splicing tips and hints from different posts, but it's really helpful to have all the info in one place.

Currently, AUDIGY12.EXE hangs after telling me that it found the device. Cursor continues to blink, but it doesn't respond to any keyboard inputs, and I can't do anything other than restart. Going to try again tomorrow with OP's guide and see if I have better luck.

Renaissance 2K wrote on 2020-09-06, 05:48:

Currently, AUDIGY12.EXE hangs after telling me that it found the device. Cursor continues to blink, but it doesn't respond to any keyboard inputs, and I can't do anything other than restart.

I remember trying to get the Audigy2 ZS to work in DOS 6.22 one time and failing with similar issues. Not sure why this happens, as the card works perfectly fine in pure DOS 7.1 using the "Restart in MS-DOS mode" shutdown option from Win98. I didn't experiment with DOS 6.22 any further though.

That said, the main goal of this guide was to get that awesome soundfont-based General MIDI music in DOS games, which is only possible when you run them under the Win98 DOS prompt. In pure DOS, you cannot load soundfonts on this card, so you're stuck with ECW sets for General MIDI music or Creative's FM emulation for FM synth music. Neither of those two sound particularly good.

Renaissance 2K wrote on 2020-09-06, 05:48:

Thanks for posting such a detailed guide. I'm trying to see if it's feasible to use the Audigy 2 in Pure DOS using AUDIGY12.EXE

YES. Audigy 2 ZS works in DOS 6.22 like a charm. I fixed similar issues pretty quickly so don't remember exact steps, try the following:

1. Verify that PCIIRQ value in "CTSYN.INI" (basing on screenshot, in your case it's 10) equals to IRQ assigned to the card by BIOS
2. Check same IRQ isn't shared with other devices - in particular mass storage or LAN - in true DOS it may cause instant freeze
3. Like other SB PCI cards, Audigy needs EMM386 or alternative (I also succeeded with JEMM386) - make sure it's properly configured, parameters like for SB Live! will fit

+ If you have more than one sound card in your system, there could be also other conflicts.

Thank to both of you for your replies. I wiped my Windows 98 partition and reinstalled everything from scratch, following Joseph's instructions in the OP to the letter. At least in Device Manager, I got the end result I wanted - including the dual SB16 emulation devices, one of which has a conflict - but I'm starting to wonder if there's something more fundamental wrong with my hardware or its configuration.

AUDIGY12.EXE runs in Windows 98 MS-DOS mode without hanging, which is great. Unfortunately, the system hangs instead - blank empty screen, except for a blinking cursor - when I try to start a game. Someone in a Retro PC Discord said this means that I misconfigured the sound hardware during the game's setup, but one of the games I tested - One Must Fall 2097 - doesn't offer any configuration other than the hardware type (I chose "Sound Blaster 16") and audio quality; no need to specify IRQ, DMA, etc. To make matters worse, as the afternoon wore on, Windows 98 suddenly stopped booting into MS-DOS mode, getting stuck on the same empty screen with a blinking cursor after the Windows desktop disappears.

Gonna table that for a moment, since @crvs inspired me to try MS-DOS 6.22 again.

After disabling all vestigial devices in my BIOS, the Audigy was auto-assigned IRQ 11. The only device that it shares the IRQ with is one of the Serial Bus Controller devices. I've disabled all the serial ports, and if I force an IRQ for a PCI slot in my BIOS, the same SBC device adopts the new IRQ as well. I don't know if this is just an alias for one of the I/O devices on the Audigy itself, or if there's some other IRQ black magic going on, and this is actually why I'm getting the insta-freeze behavior.

I ran MSD, and it confirmed that IRQ 11 belongs to the Audigy. Or, at least, that's how it looks.

I edited the two PCIIRQ lines in CTSYN.INI, ran SBECFG, and double-checked AUTOEXEC.BAT and CONFIG.SYS. Unfortunately, I got the same result when I ran AUDIGY12 again. Hmm.

If I can't figure out why Windows 98 MS-DOS mode isn't booting, I might try to wipe and reinstall again and see if I can triple check that the audio config for some of these DOS games is indeed correct. Otherwise, it might be less trouble (though more money) to get an AWE64 for these DOS titles. My motherboard does have an ISA slot, and juggling multiple sound cards doesn't sound like much trouble if I just disable the AWE in Windows and use it only in Pure DOS.

Again, many thanks for the detailed posts.

Renaissance 2K wrote on 2020-09-07, 05:12:

Someone in a Retro PC Discord said this means that I misconfigured the sound hardware during the game's setup, but one of the games I tested - One Must Fall 2097 - doesn't offer any configuration other than the hardware type (I chose "Sound Blaster 16") and audio quality; no need to specify IRQ, DMA, etc.

I would try with a simpler game, like Doom or Descent for example. Both of them allow you to select address, IRQ and DMA in setup.

Before that, right click on My Computer > Properties > Device Manager > Sound, Video and Game Controllers > Creative SB16 Emulation > Properties > Resources and check which values are assigned. By default, it should be Address = 220, IRQ = 5, low DMA = 1, high DMA = 5, FM synth = 388 and MPU-401 = 330. If those values are different, then the card has a resource conflict with something else on your system.

After disabling all vestigial devices in my BIOS, the Audigy was auto-assigned IRQ 11. The only device that it shares the IRQ with is one of the Serial Bus Controller devices. I've disabled all the serial ports, and if I force an IRQ for a PCI slot in my BIOS, the same SBC device adopts the new IRQ as well. I don't know if this is just an alias for one of the I/O devices on the Audigy itself, or if there's some other IRQ black magic going on, and this is actually why I'm getting the insta-freeze behavior.

It could be the Audigy's own FireWire port, but you seem to have a lot of devices on that system so it's hard to say. To ensure that you have no IRQ or DMA conflicts, under Win98 go to Start > Programs > Accessories > System Tools > System Information. Once there, click on Hardware Resources and then check the IRQ and DMA sections.

This should show you if any of the IRQ or DMA values used by your sound card are shared with other devices. If they are, try turning off those devices and see if it helps. Specifically, turning off the serial and parallel ports in BIOS is helpful, unless you use them. Same for the integrated USB controller.

Since installing the Audigy drivers is difficult enough even without any hardware conflicts, I would also suggest physically pulling out any cards from your motherboard other than the Audigy and your GPU. You can add them back later, one by one, after successfully configuring the Audigy and see which one causes the conflict.

Renaissance 2K wrote on 2020-09-07, 05:12:

I edited the two PCIIRQ lines in CTSYN.INI, ran SBECFG, and double-checked AUTOEXEC.BAT and CONFIG.SYS. Unfortunately, I got the same result when I ran AUDIGY12 again. Hmm.

Here is my minimal config that 100% works in MS-DOS 6.22, at least in my machine, maybe it will give you a clue. Just note that "SET BLASTER" values (and respective parameters in "CTSYN.INI") are non-standard, as I have 2 soundcards in this setup.

PS: An idea to disconnect all other extension boards while testing is really good. You can also try to put Audigy into a different PCI slot, sometimes it helps. By the way, which motherboard/chipset are you using?

Motherboard is an Asus P3B-F, which is the 440BX chipset. I had the sound card in a different slot originally, but my BIOS seems to give PCI 1 and 2 a dedicated IRQ, while 3/6 and 4/5 share IRQs, so I moved the sound card to PCI 2. I also disabled the serial and parallel ports, but had to leave USB intact since none of my USB-to-PS/2 adapters seem to work, and my dedicated PS/2 peripherals are en route.

The device sharing an IRQ with the Audigy was an USB 2.0 expansion card, which I removed. Still, even with a clean install and a near-empty motherboard, I still ran into the same issues. In Windows, the Audigy was showing non-standard IRQ and DMA assignments, DOS 6.22 would freeze upon running AUDIGY12.EXE, and DOS 7.1 would freeze upon starting a game (if it made it to DOS Mode at all).

And then something crazy happened...

After installing a new game, I ended up on the Windows 98 boot menu, which defaulted to Command Prompt mode. I was about to reboot into Windows, but then I saw the SB-related AUTOEXEC commands in the console, so I figured... why not try to boot up a game. I ran AUDIGY12.EXE successfully, booted OMF, and - BOOM - heard that game-starting thunder crack in all its 16-bit glory. Needless to say, I'm thrilled.

Not quite the route I expected to take, but it works. I have SB16 emulation in Pure DOS if I launch it from the Windows 98 Boot Menu. Still not sure why I suddenly can't use "Restart into MS-DOS Mode" but that's a question for another day, I guess.

Thanks again, everyone.

Renaissance 2K wrote on 2020-09-07, 22:28:

Motherboard is an Asus P3B-F, which is the 440BX chipset

I have the same MB, rev 1.03 🤣 You should definitely try my package for DOS "as is".
Install Audigy2 into the 5th PCI slot (counting from processor) and assign to it IRQ 10 in BIOS, I believe all should just work.

crvs wrote on 2020-09-08, 19:26:

Renaissance 2K wrote on 2020-09-07, 22:28:

Motherboard is an Asus P3B-F, which is the 440BX chipset

I have the same MB, rev 1.03 🤣 You should definitely try my package for DOS "as is".
Install Audigy2 into the 5th PCI slot (counting from processor) and assign to it IRQ 10 in BIOS, I believe all should just work.

Well, hot damn!!

I think I'm in pretty good shape now. I adopted @crvs' interior decorating skills and moved my sound card to PCI 5, forced IRQ 10 for it in the BIOS, and DOS 6.22 booted up without a hitch. I heard glorious, glorious sound in Doom and OMF without issue. After adding back my Voodoo 2s and my PCI expansion card, everything was still working perfectly. I'm ecstatic. Thank you so much.

I did try to get sound working in Windows 3.11 as well, but that might be a bridge too far. We'll see.

Looking forward to finally screwing the cover back on my case and enjoying the new machine.