Sound Blaster Audigy Ls

[Jacinto Man]

Irecently upgraded from my Sound Blaster Live to the Audigy ZS in my Windows 98 Machine. I am currently having alot of issues getting the card to run, so far i have installed the WDM drivers manually from a Driver CD i found on Vogons, but the sound keeps cutting out.

Historically, was the Audigy 2 and it's variants intended for Windows 98? Some searching around, leads me to think it was marketed for Windows XP. Obviously it can be made to work for 98. Is this a mild hack or work around of some kind? Creative's website also did not list any Windows 98 drivers when I select any of the Audigy 2 models.

I use an Audigy in my Windows 98 build. Far as I know, it covers EAX 1.0, 2.0, and 3.0. Contemplating if I would want to upgrade it to an Audigy 2. However I wasn't able to determine if it was meant for Windows 98. Besides a bare driver, would any applications to configure and play with the card also work?

Yes, the bundled mixer and EAX control apps work on Win98. Games wise I've had Diablo 2 and Tron 2.0 working with EAX enabled. Did get some crashes with Tron with it enabled but that's not necessarily Win98 specific.

I also have this card, and will soon be installing it into my 440BX Win98 machine. Are you saying this card does not work in DOS at all without fiddling around? What if you open your games through a DOS prompt in Windows?

The catch in DOS is that pretty much all games that used sound talked directly to the metal, and the Audigy2 isn't any kind of hardware that they know how to talk to. This is kind of a problem with most PCI (and MCA, for that matter) sound cards and USB sound devices, and the reason why folks recommend ISA cards for DOS. A few PCI cards have DOS drivers that provide SBPro/SB16 emulation - the Ensoniq AudioPCI (SB PCI128) and Aureal Vortex2 both do.

Windows drivers sometimes provide an emulation layer for DOS games (while Windows is running), causing whatever card is installed to act like a Soundblaster 16, SB Pro or some other similar thing. Apparently the Audigy2 drivers don't do that, though I can't confirm - I've used many an Audigy2, but only ever under Windows 2000/XP/7/10 or Linux.

I've tried installing the Audigy 2 ZS on my Asus P2B (440BX), pointing the device manager to the VxD path. End result was it crashed. I didn't bother revisiting the issue, but if other people are getting theirs to work, I'm going to try at it again. Could be because I had a cheap Creative value sound installed previously and didn't scrub the drivers completely.

Hello thanks for taking time out to review my inquiry with regards to my concern with Windows 10 ver 1903 deployment. My sound blaster Audigy FX sound card worked excellent up until your deployment of Windows 10 version 1903. The prior Windows 10 version 1809 my sound card had absolutely no issues what so ever. Now I did my due diligence and began to update my sound cards drivers, uninstall the the sound card, uninstall the drivers, perform a thorough clean sweep of any left over driver files in safe mode, reinstall the sound card, re-install the drivers, update to the latest Creative drivers but to no avail. My sound blaster Audigy FX is not broken because it is showing in my pc's device manager clearly plus it shows the sound control panel my sound card shows as disabled in all the audio connection. Please FIX this issue you break you repair it Thank You

If issue still persists, contact Sound Blaster Audigy FX support for better assistance.

Else, if it is less than 10 days for your upgrade to V1903, you can roll back to V1809. Go to Settings > Update & Security > Recovery > click Go back to previous version.

let troubleshooter do it's thing and hopefully it will end with a suggestion to try installing with "these settings', if it does give it a go. If it doesn't, try creatives website for updated drivers.

MOST of the driver issues are on the hardware manufacture not Microsoft. They way I understand it Microsoft will work with any hardware manufacturer to get their drivers updated to work with new Windows 10 releases. If Creative has chosen to NOT do that it is NOT Microsoft's fault and your only options at that point is to either downgrade to a Windows 10 version which has driver support for your hardware or upgrade your hardware.

I personally ditched Creative back in the late 90's/early 2000's just for their apparent lack of driver support for older hardware models. Superb hardware with lacking driver support does not make a good hardware purchase IMHO. For example a quick search of the Creative website revealed the latest driver release for your sound card was 2015.

I am also having a similar problem with creative sound blaster audigy fx 5.1 pcie-express sound card. I used to have it in my older pc 32 bit running Windows 10 and it was working fine. But recently I upgraded the pc to Windows 10 64 bits and moved the card over. Installed the driver and the program controller. The program controller did not recognize the sound card. It keeps reporting that "Sound card not found" but Device Manager sees and installs the card.

Hi guys i am a small developer, i really like to use my sound blaster cards on my machines and i love also coding, so when i find the source code for the kx audio driver on git hub and then Eugene, the creator of kx audio driver decided to no longer maintain the project, i decided to start working on a mod of this driver and maintain it.

With my mod, created starting from the sources of the last official version of kx audio driver and all the small commiunity updates, i am working to keep the driver compatible with the latest mac os versions and to improove the driver over time.

- more user-frienly names for the cards in the settings and other system menus (so the name will be, for example, SB live! 5.1 SB0060 instead of kx SB0060 [e880] witch was shown in the original driver)

Just for who wants to see which audio cards will be recognized by the audio driver, i link to you a .cpp code file which is used to recognize the audio cards in the driver, if you have a copy of the latest official sources, you will find the original version into the project folder/driver/frname.cpp, you can not use mine file as replacement for the frname that there is in the official sources because i use some custom properties, methods and variables that needs changes in other parts of the code to work

Finally i am releasing an alpha of the kx driver mod, there are two ways to use it, with the installer pack and the kext only pack, i suggest the first option, says that, install it and test it on your machines and give me feedback

As those cards are almost the only choice for internal cards the development of this driver should get more attention by all the serious Hackintosh users. Unfortunately, just like in the PC world, most people don't care about getting a "real" sound card and stick with the onboard sound.

these are not the only alternative for internal sound cards, but are some of the cheapest internal cards that you can find (including the audigy rx that you can find in shops today) there are other alternatives, but they are some professional stuff or expensive stuff, or there are also some sound blaster x-fi that are quite cheap and works with voodoo hda instead and also some professional grade cards works with my kx driver mod

ok, so, specify which card when switching between posts, first I suggest to you to try mine driver mod and to make sure that the card is properly installed and that you use the kext-dev-mode=1 boot arg that allows the driver to run properly on recent versions of Mac OS

I tried both ways to install the kext. Placing it in EFI/CLOVER/KEXTS/OTHER did not work. Using the installer which places the kext in S/L/E did not work either. I got as far as selecting a sound effect to test for sound, when the system froze. This has been the result ever since El Capitan.

for clover you don't have to place the kext in EFI/CLOVER/KEXTS/OTHER, but in EFI/CLOVER/KEXTS/[the folder named with the version of mac os you are using] so for example for sierra you have to put the kext in EFI/CLOVER/KEXTS/10.12 for yosemite you have to put it in EFI/CLOVER/KEXTS/10.10 instead, if the driver works you will see in system preferences->sound and in the outputs section a new device that will be named sound blaster audigy 2 zs, i suggest also to boot with -v to and send me video of the booth process with the kext installed, so i can tell to you what is happening and if the driver is working or if it is a hardware problem from the card its' self, also i suggest to you tu try mine installer with the installer packet that will clean previous kext installations of kx driver and will install it in s/l/e or try to install only the kext in clover to EFI/CLOVER/KEXTS/[kext named like the version of mac os you are using] if you use EFI/CLOVER/KEXTS/OTHER the kext will not be loaded at all since that folder is used only for versions of mac os that clover doesn't know, so on sierra you have to to use it, just use the latest version of clover and put the kext in EFI/CLOVER/KEXTS/10.12 and check if you are using kext-dev-mode=1 and -v in the boot args. and then check if does not work check if its an hardware problem, for example use programs like DPCI manager that will list all the pci devices, so if the card appears here the driver should see it, we should investigate what's the error

My post states that I did install with your installer to s/l/e. I did see the driver in preferences, sound, output, but when I clicked on sound effects my system froze. This has happened since El Capitan. I wll try to install to kexts/10.12. I am using kext-dev-mode=1

the driver (and the original driver that I used to start my work) is limited to use only the green output, currently I don't know how to get work the inputs (I'd like to get at least the pink input to work) on Mac OS X on that cards, I have a prototype of the driver that has the inputs in preferences, but the inputs doesn't works yet, if some one can help me to get it working it will be very help foul (need guys with some experience in driver developing on Mac)

3a8082e126