Creative Audigy Fx

[Rosamunda Froats]

Actuallynot 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.

I recently got a new computer (Dell Dimension 8400) with a Creative Labs SoundBlaster Audigy LS sound card. Having had Arch Linux on my other machine, naturally I wanted to install it on this computer as well (Arch is just that good). Unfortunately, I have had nothing but trouble getting this particular machine to cooperate. Thus far, I have overcome many difficulties with the help of the Wiki and this forum. However, this one has me stopped cold:

Each of which gave me an error. For whatever reason, I decided to reboot and try again. This time I was able to modprobe all of them just fine. I then continued with the instructions and tried to run alsamixer (as root), which gave me the following error:

The harddrive is SATA, RAID level 0, but I had to disable RAID in the BIOS in order to install Arch. I have to enable/disable it each time I want to switch booting between Windows XP and Arch, which is annoying--but that's a different question altogether.

Having seen somewhere that the audigyls driver is to be replaced by the ca0106 driver, I tried to get that driver working, but couldn't get alsa-driver 1.0.7 to configure --with-cards=ca0106. I tried the cvs version of alsa-driver and got it to configure and install, but I was unable to modprobe snd-ca0106 (modprobe ca0106 didn't work either).

jesus man, you are using hotplug i assume!

try to disable hotplug in the daemons array, and reboot, this means that you also must put your usb modules in the modules array,

uhci-hcd and ehci-hcd ,

Prediction...This year will be a very odd year!

Hard work does not kill people but why risk it: Charlie Mccarthy

A man is not complete until he is married..then..he is finished.

When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!

3a8082e126