VOGONS


First post, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

My luck with getting sound to work with Windows 98 seems to be nonexistent.

I have two cards: an AWE64 Value and an Audigy 2 ZS. I can (seemingly) install the first with the onboard drivers from the Win98 install disc, but any time I try to play a sound (like from the system sounds menu), it either tries to play the sound indefinitely or throws up a “your sound card may be in use” error, but it never actually plays any sound.

The Audigy 2 ZS straight-up does nothing. I can install the drivers, and Windows seems to believe they work, but the card outputs no sound. Trying to use any of the features to test the card has Windows tell me the card isn’t detected, even though it is detected in the Device Manager.

I initially had IRQs 5 and 7 reserved for Legacy ISA, and I heard that resource conflicts may cause problems like this, so I flipped everything back to PnP/ISA and tried them again, and nothing happened. The AWE64 says it’s on IRQ7 in Windows and in the DOS startup screen and nothing is sharing that IRQ in the resource menu, but it always either acts like it’s busy or doesn’t respond.

I really wish I knew what I was doing wrong here.

Reply 1 of 23, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie

Are there any other sound cards that do work in the system? Seems unlikely both cards would be faulty in the same way. For a mystery like this I would probably be just re-installing win98.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 2 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

No, only the AWE64 and the Audigy 2 ZS. I know the AWE64 works at least because I’ve used it before, though I had trouble getting it to play nice alongside a SoundBlaster Live so there may be a hidden issue with the card that I don’t have the know-how to diagnose.

I do remember that the AWE64 worked exactly one time on this current system, but then I think I tried changing the IRQ in Windows and it stopped working. Changing it back did nothing. I may have also gotten the wrong driver CD for the A2ZS, which is why sound was supposedly working but nothing was happening.

This Windows 98 install was kind of borked from the beginning because I took the install CD out without thinking at one point. I thought just reinstalling it over the existing installation would fix the issues but I guess not. I’m gonna see if BootIt BM can erase everything in the partition so I can start from scratch, and go from there.

Reply 3 of 23, by Shponglefan

User metadata
Rank l33t
Rank
l33t

If you haven't tried it already, I'd recommend following Jester's guide for installing Audigy drivers on Windows 98: [OUTDATED] Installing Windows 9x and DOS drivers on Audigy cards (version 3.1)

Pentium 4 Multi-OS Build
486 DX4-100 with 6 sound cards
486 DX-33 with 5 sound cards

Reply 4 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

Will look into it. The guide says that having a second card in the system when installing could cause problems. Would it be wise to remove one card when installing the other's drivers?

Reply 5 of 23, by onethirdxcubed

User metadata
Rank Member
Rank
Member

What motherboard do you have? If it's a VIA chipset you'll have a lot of problems with the Sound Blaster Live or Audigy and would be better off with a CMI8738 or ESS Solo-1.

If you have onboard sound is it disabled in the BIOS?

Reply 6 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

Did a completely fresh Win98 install. I haven't removed any cards. The AWE64 apparently detects drivers on the Win98 CD and auto-installs them, taking up IRQ 7 and DMAs 3 and 6. IRQs 3, 4 and 5 seem to be taken up by the USB controllers. I try to play the Start Windows sound and I get the error "Windows cannot play the sound C:\\WINDOWS\media\The Microsoft Sound.wav. Your sound card may be in use."

Would disabling USB until after the sound card installs help, or is there something here I'm missing?

Reply 7 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member
onethirdxcubed wrote on 2026-11-15, 17:15:

What motherboard do you have? If it's a VIA chipset you'll have a lot of problems with the Sound Blaster Live or Audigy and would be better off with a CMI8738 or ESS Solo-1.

If you have onboard sound is it disabled in the BIOS?

I have a DFI G4E620-N with an Intel i845 chipset. I already disabled AC97 sound in the BIOS alongside the parallel and serial ports. The only I/O I didn't disable was the USB and USB2.0 controllers because I don't have PS/2 peripherals handy.

Reply 8 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

I swapped the AWE64 to the very bottom ISA slot, and it didn't change anything. I also swapped the CD audio cable just in case, still nothing. I installed the driver set from the AWE64 CD, and instead of throwing up an error, the sound tries to play indefinitely again without actually playing any sound. I also installed the chipset drivers in case they were required for the card to know what the hell it's doing, and those didn't affect anything.

I'm genuinely stumped. Either this card is dead or something's gravely wrong.

Reply 9 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

Pulled the AWE64 card out and plugged it into an older Windows 98 machine I built last year, and it was detected and configured. I could pass sound thru it from the SoundBlaster Live that's also in here, but if I attempted to use the AWE64 as the primary Wave Out, I hear nothing. I don't get any errors, the system doesn't hang, the card just outputs no sound at all.

I don't want to immediately say the card is dead, because this was tested in a fully configured Win98 environment where I'd already installed/uninstalled the sound drivers multiple times, whereas the DFI board is running a nearly fresh-from-CD Win98 with only the sound and chipset drivers. Still, I suspect there's something wrong with this individual card that's causing a problem, because if the ISA DMA was busted on the DFI board, I feel like the card wouldn't detect at all, right?

Reply 10 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member
Shponglefan wrote on 2026-11-15, 13:36:

If you haven't tried it already, I'd recommend following Jester's guide for installing Audigy drivers on Windows 98: [OUTDATED] Installing Windows 9x and DOS drivers on Audigy cards (version 3.1)

Thank you for this suggestion, it worked perfectly! I got a little worried when the card auto-reserved IRQ 5 because I'll need that when my replacement AWE64 comes in, but then I remembered I could just reserve IRQ 5 as a Legacy ISA interrupt in the BIOS.

It does make me a little worried that when the AWE64 comes in, it won't auto assign to IRQ 5 since it's a PnP card, but if I flip it back to PnP/ISA, the Audigy 2 ZS will just hog it again. Am I just being paranoid?

Reply 11 of 23, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
TheMysteriousGray wrote on 2026-11-19, 00:52:
Shponglefan wrote on 2026-11-15, 13:36:

If you haven't tried it already, I'd recommend following Jester's guide for installing Audigy drivers on Windows 98: [OUTDATED] Installing Windows 9x and DOS drivers on Audigy cards (version 3.1)

Thank you for this suggestion, it worked perfectly! I got a little worried when the card auto-reserved IRQ 5 because I'll need that when my replacement AWE64 comes in, but then I remembered I could just reserve IRQ 5 as a Legacy ISA interrupt in the BIOS.

It does make me a little worried that when the AWE64 comes in, it won't auto assign to IRQ 5 since it's a PnP card, but if I flip it back to PnP/ISA, the Audigy 2 ZS will just hog it again. Am I just being paranoid?

You can override the IRQ assignments in windows resource manager. If the audigy wants to hog IRQ5, disable it, go into the resource manager for the AWE64, set IRQ to 5, then re-enable the Audigy it will be on a different IRQ. Cards with manually assigned resources will stick and other cards set to automatic will shuffle around them.

For DOS, reserve IRQ5 for legacy and set BIOS setting "PnP OS Installed" to Yes, then init the card to the IRQ you want. Setting IRQ5 to legacy won't prevent you from manually assigning it in windows.

I'd also do the same for the low and high DMA you want on the AWE64.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 12 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member
NeoG_ wrote on 2026-11-19, 02:06:

You can override the IRQ assignments in windows resource manager. If the audigy wants to hog IRQ5, disable it, go into the resource manager for the AWE64, set IRQ to 5, then re-enable the Audigy it will be on a different IRQ. Cards with manually assigned resources will stick and other cards set to automatic will shuffle around them.

For DOS, reserve IRQ5 for legacy and set BIOS setting "PnP OS Installed" to Yes, then init the card to the IRQ you want. Setting IRQ5 to legacy won't prevent you from manually assigning it in windows.

I'd also do the same for the low and high DMA you want on the AWE64.

Well that seems simple enough, I’ll give it a shot when my replacement card comes in.

I should mention that I’ll be multi-booting OSes with DOS 6.22 as a separate partition. Would it not be safer to leave PnP OS off so that DOS doesn’t get confused? It doesn’t seem to affect anything in Win98 so far.

Reply 13 of 23, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
TheMysteriousGray wrote on 2026-11-19, 13:23:

Well that seems simple enough, I’ll give it a shot when my replacement card comes in.

I should mention that I’ll be multi-booting OSes with DOS 6.22 as a separate partition. Would it not be safer to leave PnP OS off so that DOS doesn’t get confused? It doesn’t seem to affect anything in Win98 so far.

The setting determines whether the bios itself runs ISA PnP initialisation, DOS is perfectly happy to run without it (when PnP OS is set to Yes). I usually run with it disabled so I can initialise the cards to whatever resources I want manually using their respective drivers.

It doesn't affect windows since windows can operate ISA PnP cards by itself.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 14 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

I got a replacement AWE64, it's detected and the drivers are installed from the Win98 install CD, and... the same thing happens. The card is detected, no conflicts are detected, drivers installed, but the Wave Out still does nothing. I don't get a "Your sound card may be in use" error, but I get the same problem as with the other Win98 rig where sounds try to play and the file seems to freeze, not playing any sound or doing anything. MIDI data is being sent to the SC-55, tho I can't hear any MIDI music (likely because the Line In port is muted, but I don't have the AWE64-specific utilities installed yet). SoundBlaster audio in a Windows DOS prompt also doesn't work.

I really just do not get it. There must be a driver or file that I'm missing that's preventing the card from working.

Reply 15 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

I tried getting Duke Nukem 3D to detect the card. It detects MIDI but it plays what I'm pretty sure is the Audigy's MIDI synth and not the SC-55, which shows no activity. It fails to detect the AWE64 as a SB car at all, even though the card can be successfully configured in Setup playback will always fail.

Again, there has to be some kind of non-communication between the card and the system going on. the AWE64 utilities setup told me to add some lines to config.sys pointing to certain files, but when I went to the directory that those files were supposedly installed on, I can't find them anywhere.

Has anyone ever had a similar issue to this when trying to get an AWE64 to work in Win98?

Reply 16 of 23, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie

DOS games inside windows 98 still use the direct hardware access method and windows passes it through, so for example if the Audigy drivers have Sb16 smulation enabled and is taking port 330, using GM port 330 in duke nukem 3d will output sound using the Audigy synthesizer.

My recommendation would be to force the AWE64 to use 330 for MPU401 duties in device manager and disable audigy SB16 emulation since you already have a proper SB16 equivalent. Whether the MIDI data goes to the EMU8000 chip or the joystick port depends if "Allow MPU401 emulation on this device" is enabled or not in AWE control panel.

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 17 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

Turning that setting off for the AWE MIDI synth means I get DOS MIDI data running, but that's the only thing that's changed. I deliberately didn't install the Audigy 2's SB16 emulation drivers in anticipation of getting a new AWE64, so the AWE64 is the only SB-compatible card in the system. It's at port 220, IRQ 5, DMAs 1 and 5 by default and absolutely nothing else is sharing those values. The card simply refuses to actually play any sound, like a grumpy toddler.

Reply 18 of 23, by NeoG_

User metadata
Rank Oldbie
Rank
Oldbie
TheMysteriousGray wrote on Today, 03:14:

Turning that setting off for the AWE MIDI synth means I get DOS MIDI data running, but that's the only thing that's changed. I deliberately didn't install the Audigy 2's SB16 emulation drivers in anticipation of getting a new AWE64, so the AWE64 is the only SB-compatible card in the system.

In that case what you did hear must have been the EMU8000 MIDI on the AWE64, not the Audigy

98/DOS Rig: BabyAT AladdinV, K6-2+/550, V3 2000, 128MB PC100, 20GB HDD, 128GB SD2IDE, SB Live!, SB16-SCSI, PicoGUS, WP32 McCake, iNFRA CD, ZIP100
XP Rig: Lian Li PC-10 ATX, Gigabyte X38-DQ6, Core2Duo E6850, ATi HD5870, 2GB DDR2, 2TB HDD, X-Fi XtremeGamer

Reply 19 of 23, by TheMysteriousGray

User metadata
Rank Member
Rank
Member

Makes sense. At least I know the card works(?). But it never initializes sound. Playback fails in Duke3D setup, MIDI data is sent but no audio is heard even though the Line In port is definitely unmuted now, any .wav sounds I try to play freeze indefinitely when AWE64 Wave Out is the primary playback device, etc. Two AWE64s and they both have an identical problem on two separate motherboards.

I could try installing the card in DOS 6.22 to see if it would work there, since that's where I'll be getting the most use out of it. I could also try testing the PicoGUS I have under Win98 to rule out any issues with the ISA slots themselves. I could even try yanking out the Audigy 2 and completely reinstalling Win98 just to see what happens.

If it came down to it and the PicoGUS is all I can use, would it be possible to use the Audigy 2 ZS solely for CD audio and CDROMs under DOS? I'm pretty sure there are drivers for initializing the A2ZS in pure DOS (though I dunno anything about their specifics), and I have an external mixer so mixing the two together is no issue.