Have you got some version info to look for? I might have two different sets of driver/software floppy disks iirc, but no idea which version it needs to be to support SF2. I also don't know if the driver disks are localized.

Maybe you are looking for Vienna Soundfont Studio that came with the installation bundle?

Vienna 2.0 or 2.1 needed for win3x awe32

Linoleum wrote on 2024-08-30, 14:20:

Maybe you are looking for Vienna Soundfont Studio that came with the installation bundle?

Vienna 2.0 or 2.1 needed for win3x awe32

I've tried this software and nope not that. Also I've loaded Sound Font files and played midi files with the soundfont. I have upgraded memory as well to 28MB.

Linoleum wrote on 2024-08-30, 14:20:

Maybe you are looking for Vienna Soundfont Studio that came with the installation bundle?

Vienna 2.0 or 2.1 needed for win3x awe32

The AWE32 control panel version is 1.10 that I am using. There are two distinct interfaces for Windows 3.1 One has tabbed menus along the top with different options. The other is ther one menu with a few buttons and lack of SF2 support. I have videos of me playing MIDI files with SF2 roms loaded into memory. I think if we clear this issue up it will help others in the future.

You're right! It's not Vienna, but truly integrated into the drivers through AWE Control Panel... Turns out, I have it installed on my Sound Blaster 32 system.

Look for the Sound Blaster 32 PNP CD ISO on Archive.org, that probably the driver set that I installed...

While I can't offer any help regarding the issue, I can at least confirm that the AWE Control panel for Win 3.1 which ships on the AWE64 Value driver CD does support soundfonts in the SF2 format.

Not sure if that can be installed on AWE32 cards though.

Perhaps you can install the drivers from the AWE64 Gold CD.

Linoleum wrote on 2024-08-30, 15:01:

You're right! It's not Vienna, but truly integrated into the drivers through AWE Control Panel... Turns out, I have it installed […]
Show full quote

You're right! It's not Vienna, but truly integrated into the drivers through AWE Control Panel... Turns out, I have it installed on my Sound Blaster 32 system.

The attachment IMG_5394.jpg is no longer available

The attachment IMG_5395.jpg is no longer available

Look for the Sound Blaster 32 PNP CD ISO on Archive.org, that probably the driver set that I installed...

Linoleum you got it! It was that specific ISO image SB32.ISO. While I know there is an SB32 and an SB32AWE. This image works with my awe32 just fine. So ya its all good! Thank you everyone for the QUICK replies. So happy now!

CrazyKickBoxer wrote on 2024-08-30, 15:25:

Linoleum you got it! It was that specific ISO image SB32.ISO. While I know there is an SB32 and an SB32AWE. This image works with my awe32 just fine. So ya its all good! Thank you everyone for the QUICK replies. So happy now!

The only difference between cards labeled "Soundblaster 32" and "Soundblaster AWE 32" is that the former cards do not have 512KB onboard wavetable RAM, while the latter ones do. The "Soundblaster 32" cards always have 30-pin SIMM sockets, and can be upgraded to up to 28MB (using 2*16MB SIMMs). Some "Soundblaster AWE 32" cards, for example (or only?) the "Soundblaster AWE 32 value edition" does not have SIMM sockets, so you are limited to 512KB sample RAM. From a driver perspective, a "Soundblaster 32" with 2*256KB SIMMs installed, and a "Soundblaster AWE32" in default configuration are identical, so software for one card will work with the other card as well.

Software for the AWE64 will also work fine on the AWE32: The wavetable synthesizer part of these cards is identical. The AWE64 drivers include a software MIDI synthesizer ("WaveGuide synthesis") that adds 32 extra voices to the nominal 32 voices of the EMU8000 hardware synthesizer. It is likely that AWE64 software CDs also contain the latest AWE32 control panel.