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: Verify that PCIIRQ value in "CTSYN …

cyclone3d wrote on 2020-08-05, 17:15: Have you tried cleaning the edge connector on the awe32 yet? Yes of course.

The AWE32 should indeed work with all of your combinations, although I never tested 2x16 because I don't have this kind of modules. As I'm currently on vacation, I can't check what connections to check, but it is very likely that all address and data pins, as well as /WE, /RAS and /CAS are directly …

What are the specs of your system? If I remember correctly, Diagnose.exe has issues with faster computers. K6-III+/450 + ASUS TX97-LE + 384 Mb RAM Yesterday I have temporarily moved the card into 486 (DX4-120), and tested it with both Turbo On / Off = DRAM had been also not detected in both cases. …

This sounds very much like RAM not working properly, but good enough for the windows driver to recognize the size. You are most likely aware that you need to insert two identical modules into the two slots. The AWE32 does not work with a single memory module. In that case, the issue sounds like …

auron wrote on 2020-08-02, 16:27: is the card jumpered to enable memory upgade, MFBEN jumper closed and MPU-401 emulation checked in windows control panel? Three times "yes"

I recently acquired AWE32 CT3980 good in all aspects besides working with ext RAM modules "DIAGNOSE.EXE" in pure DOS is not detecting installed DRAM at all "AWE Control Panel" in Win98 is reporting installed memory size corectly Sound bank loading also works, properly changing "Available" kbytes …

Therefore the later revisions are likely more reliable than the rev. 1.03 - not less. Another aspect is that ASUS also catered for an overclocking audience and some of the later improvements may well have focused on those users. Think for example running a 1Ghz/133 cpu with 4x256Mb of PC133 SDRAM. …

gerwin wrote on 2020-06-20, 21:36: Thanks for the effort, and for sharing. Can you also provide the source code please? Sure! Sorry for delay, didn't have time to clean-up the project. Meanwhile, added support of GCC 10.10 -> more warnings resolved + new executables are somewhat smaller. + Attached …

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. Using the original drivers, right click on My Computer > Properties > Device Manager > Sound, Video and Game Controllers > Creative …

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 …

This is my new build of MBF / HDPMI32 It's still fairly experimental but already tested in more configs and should be good for most cases I do not recommend using version from my previous post any more List of changes vs. the baseline in start topic: Generic improvements CWSDPMI (DMPI host) replaced …

I had a similar card, latest stable driver for Win98SE appeared to be nvidia forceware 77.72 Newer 9x drivers also could be installed but didn't work well, causing ACPI issues and random freezes.

I had issues with Vortex2 installed parallelly with Yamaha YMF719E-S (in pure DOS) - couldn't route Adlib sound to OPL3 w/o fully unloading Vortex driver. In this post there is a patched version of the original Vortex TSR with disabled adlib emulation. I have patched 'modified pure DOS' version from …

I managed to link MBF and SETUP with HDPMI32 (replacing CWSDPMI). This build is working in pure DOS with Vortex 2 soundcard. EDIT: It was a quick fix and it has issues, better use next build from this post