niccat cousin maifield
Vita Wanberg
Actually not entirely true. The Rx doesn't use the SoundCore processor like the Recon3D or SBZ - it uses CA10300 which is derived from CA0108 (EMU10k2.5), and has similar capabilities/features/etc to Audigy 4 and Audigy 2 Value. HOWEVER, it also has a PLX bridge chip on there to work on PCIe, and my guess is that will cause problems with DOS (I don't know if the PLX chip will be "transparent" - based on a few bridged graphics cards I've had over the years, it will not be). I would probably try to find a PCI Audigy, unless you already own the Rx (in which case, try it and tell us if it works ?).
Yeah I'm guessing the PLX chip will pretty much assure that, but if the Audigy 2 Value or Audigy 4 work with the Audigy DOS driver, and the PLX chip doesn't cause issues, it may actually work. See this thread about the DOS driver: audigy dos drivers
This card in a weird way, is better than the Recon 3D and Z series cards in that it still has a hardware MIDI synth! Its weird how the EMU 10k refuses to die, yet the poor EMU20k gets killed off. I'm also surprised they are using a PCIe-to-PCI bridge as Creative's cards tended to have trouble with them (and hence the need to develop the PCIe native EMU 20k2 chip).
I'm now interested in this card, not because of MS-DOS, but because it seems to be the latest and greatest Creative card that still supports XP as well as all the new Windows versions. I'm assuming it has full EAX support under XP and through ALchemy under Vista+
I'm surprised it's supported in DOS, though. I can't imagine the soundblaster emulation will be up to much, and by the stage the Audigy was released, DOS games were no longer a thing as far as I'm aware.
I think the same. But do you know wheter the PCI-PCIe bridge has to be supported/initalized by BIOS then ?
I mean, sometimes devices in Win9x didn't work properly, when I had got a yellow mark for an ISA/PCI bridge (missing driver / INF for the bridge).
Just asking, the whole PnP detection/enumeration thing is a bit of a mystery to me (does a PCIe/PCI bridge work in a 486 ?).
You've got it the wrong way round - it's a PCI to PCI-e bridge chip, so the card is effectively PCI internally, but a bridge chip has been added to make it work in PCI-e systems. The physical card is PCI-e. 486s are too old to use PCI-e.
I know, but sometimes there's a PCIe bridge on PCI cards. To "backport" newer devices to older systems.
I think I've seen such a thing on an USB 3.0 card some time ago, but can't find it right now..
I though the same. But I've seen a lot of strange stuff already. For example, USB Legacy Support for keyboards and mice. It works fine in DOS.
And it works fine in Win9x until it loads drivers for the USB Host Controller. After this, legacy support is gone,
but Win9x hasn't installed USB mouse/keyboards drivers yet. At this point you have reached a dead end. Windows shows you
a "click continue to install driver" window and you can't progress. You need a PS/2 or serial mouse to click the button and to
install the mouse driver..
I'm speculating but I imagine that, yes, it would work in a 486. The problem would be driver support, and CPU features, especially if they depend on SSE etc. The easiest way would be either to find a PCIe network card with legacy (Windows 2000) drivers - it'd be horrendously slow, or perhaps better NetBSD with the same, to see if it worked.
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
c01484d022