• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Do your X-Fi Drivers work?

Status
Not open for further replies.
Then you're just being a blind and just slept through the C2D launch too LOL! Even your buddy ROBSCIX got more sense than that. Or are you some kind a noob!?

I'm not Creative Labs and I'm NOT denying anything except that these are bad drivers as you say. At first, I just thought maybe you're mistaken, now I think you're just clueless:D Please go back through this thread and count the users who say they're NOT having any problems besides switching on Digital? Let's see, your drivers work but you say they're bad? But you're OK with Drivers that don't work, how Lame is that?

I'm not blind and I helped my friend to build a C2D rig, I recommend C2D to him because he wants a new rig but I'm not a noob just because I don't upgrade to C2D, I don't want to upgrade because I know that my rig is good enough to beat your C2D rig at my screen res. This digital switching problem is an old problem, not a new one, people have been mentioning this problem long time ago but did Creative acknowledge this and fix it? That's why I said their driver is bad, because they don't want to fix them and they said the problem is not their problem instead. You are funny, just because you have a C2D rig, you think that your rig is the best and anyone who still use AMD is a noob and a f@nb0y, I think that you are a noob, you don't know much about computer but you buy anything that is better because you have the money but you don't know why it is better.
 
I'm not blind and I helped my friend to build a C2D rig, I recommend C2D to him because he wants a new rig but I'm not a noob just because I don't upgrade to C2D, I don't want to upgrade because I know that my rig is good enough to beat your C2D rig at my screen res. This digital switching problem is an old problem, not a new one, people have been mentioning this problem long time ago but did Creative acknowledge this and fix it? That's why I said their driver is bad, because they don't want to fix them and they said the problem is not their problem instead. You are funny, just because you have a C2D rig, you think that your rig is the best and anyone who still use AMD is a noob and a f@nb0y, I think that you are a noob, you don't know much about computer but you buy anything that is better because you have the money but you don't know why it is better.

I had a Commie 64 in 1983 LOL! Your comments show you for what you are, NOT what I say you are. You can dip and dodge much as you like. X-Fi doesn't have bad drivers and trying align problems with very small numbers of users is a JOKE, a bad one on your part.
I have an AMD rig as well or is that another of the posts you skipped? In fact I have two:)
 
Mine work, but I've had numerous problems with EAX over the years with various Creative Labs sound cards. Many games I've played (BF seris in particular) crash or don't produce sounds correctly when EAX support is enabled.
 
I had a Commie 64 in 1983 LOL! Your comments show you for what you are, NOT what I say you are. You can dip and dodge much as you like. X-Fi doesn't have bad drivers and trying align problems with very small numbers of users is a JOKE, a bad one on your part.
I have an AMD rig as well or is that another of the posts you skipped? In fact I have two:)

That shows you are a noob. You buy everything that is just a little better and you think that you have the best. I don't buy every single new hardware because I know when to upgrade and I know whether my computer is already obselete or not. My own first computer is a Pentium 2, I don't upgrade to Pentium 3 when it came out because I know I don't need it, then when Pentium 4 came out, I need a new computer at that time but I bought an Athlon XP 1800 because it is better than Pentium 4, then I bought another Athlon XP 2500 because my brother needed another computer, Intel still hasn't improved yet. I didn't buy Athlon 64 but jumped directly to Athlon X2 because again Intel hasn't improved. I didn't buy many computers but I did help many friends to choose and build their computers.
 
I had a Commie 64 in 1983 LOL! Your comments show you for what you are, NOT what I say you are. You can dip and dodge much as you like. X-Fi doesn't have bad drivers and trying align problems with very small numbers of users is a JOKE, a bad one on your part.
I have an AMD rig as well or is that another of the posts you skipped? In fact I have two:)

Just because you don't have problems with your X-Fi doesn't make the issues that many others have invalid. It doesn't mean that they are noobs or that they don't know what they are doing. The drivers are certainly in need of improvement. The video card manufacturers release drivers all the time as new games are released to fix issues with them. Creative on the other hand is very unresponsive to problems faced by their customers. Their driver updates are rarer then they need to be and Creative Labs seems very quick to blame someone else for their driver issues.
 
Just because you don't have problems with your X-Fi doesn't make the issues that many others have invalid. It doesn't mean that they are noobs or that they don't know what they are doing. The drivers are certainly in need of improvement. The video card manufacturers release drivers all the time as new games are released to fix issues with them. Creative on the other hand is very unresponsive to problems faced by their customers. Their driver updates are rarer then they need to be and Creative Labs seems very quick to blame someone else for their driver issues.

But Dan, just because some are having problems doesn't mean those who aren't are lucky because they have BAD drivers as he's trying to say. Sure the drivers could be improved, I've never said or implied that they are great. I said they work, work = Good. I'm NOT talking about the drivers just working for me. I'm talking about out of every 20 folks I ask, 1 reports problems. Now please compare that to how many folks have working nVidia motherboard software, not Graphic cards as he tried to change the subject to?

I'd planned to upgrade my A8N to the 32X Deluxe version but it caused me more problems, not less. Remove that platform from this and we're talking about FAR fewer complaints=P He's not saying the Drivers could stand to be improved or that tweaking them would help, not many would argue with him, including me. He's saying the Drivers are BAD:)

Example--->
That shows you are a noob. You buy everything that is just a little better and you think that you have the best. I don't buy every single new hardware because I know when to upgrade and I know whether my computer is already obselete or not. My own first computer is a Pentium 2, I don't upgrade to Pentium 3 when it came out because I know I don't need it, then when Pentium 4 came out, I need a new computer at that time but I bought an Athlon XP 1800 because it is better than Pentium 4, then I bought another Athlon XP 2500 because my brother needed another computer, Intel still hasn't improved yet. I didn't buy Athlon 64 but jumped directly to Athlon X2 because again Intel hasn't improved. I didn't buy many computers but I did help many friends to choose and build their computers.

He'd posted all that and NOTHING about the nVidia Mobo software as I asked about only got more dodging LOL! I'm not going to point out that P4C kicked the crap out of AthlonXP 2500 of those days, I had both. [H]'s reveiw pointed out the same. Being Loyal is silly (except loyal to my wallet) and Geeks buy what's best, not Intel or AMD, or wrongly bashing Creative Labs to act as a sales rep for XMeridian.

We Buy whatever works or is faster for the best price at that, be it X2/Opteron or C2D/Xeon. Since I only had the 2500+ for 4 days, I don't even count it as something owned. WHY, even as the much waited for 2500+ Mobile was more overclockable, my 2.6C at 3.42GHz still kicked the crap out of it. Yes it was more stable as well, HTT worked and etc.....sheesh!
 
That shows you are a noob. You buy everything that is just a little better and you think that you have the best. I don't buy every single new hardware because I know when to upgrade and I know whether my computer is already obselete or not. My own first computer is a Pentium 2, I don't upgrade to Pentium 3 when it came out because I know I don't need it, then when Pentium 4 came out, I need a new computer at that time but I bought an Athlon XP 1800 because it is better than Pentium 4, then I bought another Athlon XP 2500 because my brother needed another computer, Intel still hasn't improved yet. I didn't buy Athlon 64 but jumped directly to Athlon X2 because again Intel hasn't improved. I didn't buy many computers but I did help many friends to choose and build their computers.

I'll be whatever you think, just answer the question about nVidia?
 
Not a single problem with nVidia's software for me so I don't think that I need to post that before because I know there are people who have problems with the driver but nVidia never blamed other companies. So for me nVidia is better than Creative.
 
Not a single problem with nVidia's software for me so I don't think that I need to post that before because I know there are people who have problems with the driver but nVidia never blamed other companies. So for me nVidia is better than Creative.

Hehehe, why would nVidia blame someone else when their OWN software doesn't work on their own boards? Oh wait, they'd have to blame themselves, right, you're making a lot of sense here.
 
Not a single problem with nVidia's software for me so I don't think that I need to post that before because I know there are people who have problems with the driver but nVidia never blamed other companies. So for me nVidia is better than Creative.

ever try nvidia firewall :p
 
let's keep this on topic guys and let's not turn this into a flamewar.
 
Remove that platform from this and we're talking about FAR fewer complaints=P He's not saying the Drivers could stand to be improved or that tweaking them would help, not many would argue with him, including me. He's saying the Drivers are BAD:)

How have you confirmed that the CL issues with the X-Fi does or does not involve the drivers and that they are not "Bad"? The drivers might be "Good" but maybe the board is just horribly designed and CL's QC department just took a crap for their QC check on the board. How can anyone really test this when CL just tells everyone to use lower powered video cards and fix our latency timings!?! I suppose just putting the X-Fi in as many different boards as possible and building up a database of compatibility might help.

To note, I have used both an X-Fi Fatality and Extreme Gamer in an nF4 Ultra, SLI, and X16 based boards as well as in the 975X chipset board (my current rig). While the problems of SCP were not prevalent in every game, there were/are several big ones (Battlefield notably) that were marketed as THE game to take advantage of the X-Fi's power, when it was the same game that gives the most problems.
 
My X-Fi drivers are a pain in the ass..and the always have been....
 
let's keep this on topic guys and let's not turn this into a flamewar.

That is also a reason why I don't want to post about nVidia, it is off topic. The topic here is X-Fi's driver, it usually works but the failure rate is high, not to mention the "need to be expected" glitches. The problem is Creative doesn't improve their driver, I don't know whether they don't want to or they are not capable of improving it. For me the driver is bad because of these reasons. A lot of people are expecting a solution for their problems, saying "this is not our problem because our driver works on other computer", "you have this problem because you have a weak platform" wouldn't help at all. The problem is also not only specific to one platform, the problem exist on all platform. Like I said before, if they can't make their "hardware acceleration" to work properly without a high number of failures, they shouldn't use the "hardware acceleration" in the first place. Just because it works on your computer, it doesn't mean that the driver is not bad, some people use a modded driver because for them, it works better than the official Creative's driver.
 
let's keep this on topic guys and let's not turn this into a flamewar.

Most certainly will do. See, you get folks posting that their drivers work, then bang, posts about who knows what, please sign this petition and etc..., etc.... !
 
I used my Audigy 2 ZS on an nForce 4 SLi platform for some quite time. The only issues I experienced were due to a corrupt driver update of some sort (Creative is directly to blame in this instance). The motherboard, chipset and NVIDIA software, such as nTune, have never given me reason to doubt my motherboard purchase, and to this day, I've yet to experience any chipset-related issues with my nForce 4 SLi-based LanParty SLi-DR Expert. I've also used the NVIDIA firewall for some time, and although not nearly as extensible and easy to use as Outpost Pro (a fantastic piece of software), it functioned perfectly fine.

Others may have experienced extensive issues, though I have zero regrets.

The same could never be said about my experience with the Audigy 2 ZS, but that isn't the subject of this topic. For the sake of minor clarity, let's just say that I didn't shatter my Audigy 2 with a sledgehammer because I was disappointed with the hardware itself.

I have an Elite Pro en-route, so once I receive that, I'll let you guys know if I experience any issues with that card on my NF4 system. I severely hope that I do not regret this purchase.

Donnie27 said:
Some boards from the same line but but made by different companies have been fixed with BIOS flashes. What's Creative supposed to do, LIE on themselves?
Consider the possibility, for a moment, that these BIOS revisions were released in an attempt to accommodate for Creative's lack of motivation in fixing a potential Sound Blaster issue. Motherboards and motherboard chipsets are extremely complex systems, and Creative's hardware may or may not agree with the way these systems may work. Let's not automatically assume that Creative's hardware features 100% cross-platform robustness, and let's not even assume that their hardware is in accordance with certain standards or specifications necessary for correct operation on all properly compliant motherboards. Unless we have all the cards on our tables, let's not start trying to build temples with them.

I'm not saying that the NF4/X-Fi issues necessarily stem from problems with Creative hardware, but we need to be aware that it is a possibility that it is a Creative hardware issue.

Consider the 8800/Source engine fog issue, for example. The issue only occurs when using an 8800-series card, but is it a direct 8800-series card issue? No. In this case, it is a Valve/Source issue and something that must necessarily be fixed by Valve. The situation may be very similar to the NF4/X-Fi issue.

Rather than play the "blame game", let's try to determine the commonality of the basis for these issues. Let's see some facts.
 
That is also a reason why I don't want to post about nVidia, it is off topic. The topic here is X-Fi's driver, it usually works but the failure rate is high, not to mention the "need to be expected" glitches. The problem is Creative doesn't improve their driver, I don't know whether they don't want to or they are not capable of improving it. For me the driver is bad because of these reasons. A lot of people are expecting a solution for their problems, saying "this is not our problem because our driver works on other computer", "you have this problem because you have a weak platform" wouldn't help at all. The problem is also not only specific to one platform, the problem exist on all platform. Like I said before, if they can't make their "hardware acceleration" to work properly without a high number of failures, they shouldn't use the "hardware acceleration" in the first place. Just because it works on your computer, it doesn't mean that the driver is not bad, some people use a modded driver because for them, it works better than the official Creative's driver.

But you're still doing it!;) If you don't like what I said about weak platforms take it to the motherboard side of the forum?

The Topic was X-Fi drivers when you brought up a Petition.

If anyone believes any of this stuff you posted, just look at your nVidia software comments, now that doesn't make the rest of it real believable. So far you've proven that you'll write anything to try and make a point.

Last but not least, it's not what Donnie27 is saying but what many of the posters here have posted that makes your claims of Bad Drivers Bogus and that's NOT OFF TOPIC. Does their saying "I've had Zero/No Problems" and etc.. mean they don't know what they're talking about? Now you might want to find a forum full of Creative bashers who might go along with you? But people here aren't that confused and know if their drivers work or not.
 
I used my Audigy 2 ZS on an nForce 4 SLi platform for some quite time. The only issues I experienced were due to a corrupt driver update of some sort (Creative is directly to blame in this instance). The motherboard, chipset and NVIDIA software, such as nTune, have never given me reason to doubt my motherboard purchase, and to this day, I've yet to experience any chipset-related issues with my nForce 4 SLi-based LanParty SLi-DR Expert. I've also used the NVIDIA firewall for some time, and although not nearly as extensible and easy to use as Outpost Pro (a fantastic piece of software), it functioned perfectly fine.

Others may have experienced extensive issues, though I have zero regrets.

The same could never be said about my experience with the Audigy 2 ZS, but that isn't the subject of this topic. For the sake of minor clarity, let's just say that I didn't shatter my Audigy 2 with a sledgehammer because I was disappointed with the hardware itself.

I have an Elite Pro en-route, so once I receive that, I'll let you guys know if I experience any issues with that card on my NF4 system. I severely hope that I do not regret this purchase.


Consider the possibility, for a moment, that these BIOS revisions were released in an attempt to accommodate for Creative's lack of motivation in fixing a potential Sound Blaster issue. Motherboards and motherboard chipsets are extremely complex systems, and Creative's hardware may or may not agree with the way these systems may work. Let's not automatically assume that Creative's hardware features 100% cross-platform robustness, and let's not even assume that their hardware is in accordance with certain standards or specifications necessary for correct operation on all properly compliant motherboards. Unless we have all the cards on our tables, let's not start trying to build temples with them.

I'm not saying that the NF4/X-Fi issues necessarily stem from problems with Creative hardware, but we need to be aware that it is a possibility that it is a Creative hardware issue.

Consider the 8800/Source engine fog issue, for example. The issue only occurs when using an 8800-series card, but is it a direct 8800-series card issue? No. In this case, it is a Valve/Source issue and something that must necessarily be fixed by Valve. The situation may be very similar to the NF4/X-Fi issue.

Rather than play the "blame game", let's try to determine the commonality of the basis for these issues. Let's see some facts.

Great post and I respect what you're saying. I taked to folks who are BIOS writers and the stuff they talked about was over my head. Many of them (3) agree it was something in the Chipset but that it wasn't one cause. But again that's for another thread. The question was "Do your X-Fi Drivers work?" and then if no why? I didn't ask if they were Great Driver or perfect? I don't know of any Hardware with Perfect dirvers.

If we're doing this motherboard chipset by chipset, and then different boards within the same line and the results looked like (Example)
Motherboard X-Fi compat problem
XZYxxxx 2%
YZZxxxx 1.5%
ZZYxxxx 65%
Sub Catigories
ZZYx1 1%
ZZYx2 64%

Would you wonder why ZZY X2 was so much higher or would you just blame the card?

Hit the button too soon?
 
I used my Audigy 2 ZS on an nForce 4 SLi platform for some quite time. The only issues I experienced were due to a corrupt driver update of some sort (Creative is directly to blame in this instance). The motherboard, chipset and NVIDIA software, such as nTune, have never given me reason to doubt my motherboard purchase, and to this day, I've yet to experience any chipset-related issues with my nForce 4 SLi-based LanParty SLi-DR Expert. I've also used the NVIDIA firewall for some time, and although not nearly as extensible and easy to use as Outpost Pro (a fantastic piece of software), it functioned perfectly fine.

Others may have experienced extensive issues, though I have zero regrets.

The same could never be said about my experience with the Audigy 2 ZS, but that isn't the subject of this topic. For the sake of minor clarity, let's just say that I didn't shatter my Audigy 2 with a sledgehammer because I was disappointed with the hardware itself.

I have an Elite Pro en-route, so once I receive that, I'll let you guys know if I experience any issues with that card on my NF4 system. I severely hope that I do not regret this purchase.


Consider the possibility, for a moment, that these BIOS revisions were released in an attempt to accommodate for Creative's lack of motivation in fixing a potential Sound Blaster issue. Motherboards and motherboard chipsets are extremely complex systems, and Creative's hardware may or may not agree with the way these systems may work. Let's not automatically assume that Creative's hardware features 100% cross-platform robustness, and let's not even assume that their hardware is in accordance with certain standards or specifications necessary for correct operation on all properly compliant motherboards. Unless we have all the cards on our tables, let's not start trying to build temples with them.

I'm not saying that the NF4/X-Fi issues necessarily stem from problems with Creative hardware, but we need to be aware that it is a possibility that it is a Creative hardware issue.

Consider the 8800/Source engine fog issue, for example. The issue only occurs when using an 8800-series card, but is it a direct 8800-series card issue? No. In this case, it is a Valve/Source issue and something that must necessarily be fixed by Valve. The situation may be very similar to the NF4/X-Fi issue.

Rather than play the "blame game", let's try to determine the commonality of the basis for these issues. Let's see some facts.

I hit the button too soon I wasn't finished. I asked if the drivers worked and I've had words put into what I asked and said. I said any driver that works is good. I didn't say they were great, they didn't need improvement and other stuff attributed to me.

Originally Posted by ROBSCIX
No kidding?! Saying Creative has good drivers shows either a lack of research or a lack of involvment with Creative products or just a plain lack of knowledge. or all of the above."

Go to the Guru3D forums where I got that and you'll see alg7 agreeing with him on this and other comments. I had merely pointed out that my drivers work. Now if the drivers work, what's so bad about them? I don't know of anything that's perfect, do you?
 
Would you wonder why ZZY X2 was so much higher or would you just blame the card?
The first inclination I'd have is to definitely see if there's something wrong with ZZY X2. Like you said, if there's a problem on one particular kind of chipset, then the first assumption is that it is very likely an issue with that chipset.

I just don't want to go down this road assuming that it is a chipset issue because it occurs most frequently (VERY much most frequently) with that chipset. Naturally, that's the first thing you want to point the finger at, but pointing fingers has never done anyone any real good. I shattered my Audigy, but I'm not 100% certain the problem was with the Audigy. If I could get in deep at the software level, I could be sure, but not a moment sooner. But then, rage is not such a reasonable thing :)

I don't know to what extent NVIDIA and Creative have addressed this issue, so excuse my ignorance of that. What is NVIDIA's statement, and what is Creative's? Do they blame each other, or are there glimmers of either taking responsibility of some sort?
 
What is NVIDIA's statement, and what is Creative's? Do they blame each other, or are there glimmers of either taking responsibility of some sort?
This is Creative's statement. I don't search for nVidia's statement because I think that they are not blaming Creative because they are trying to fix the problem with their BIOS fixes. I'm disappointed with Creative's statement because other users on other platforms will not have the issue fixed because Creative don't want to fix it.
 
I'm just concerned that Creative hasn't addressed similar problems on non-NF4 motherboards. Obviously, it does happen, so a pure NVIDIA blame-game doesn't seem like the right answer. It also seems like a potential driver issue on Creative's part.

It might be just the right combination of fault between NVIDIA and Creative, but NVIDIA and its AIBs are the only ones delivering some sort of satisfaction. It's obvious, given the fact that only an initial statement was made (with zero follow-ups) that Creative is not at all concerned with users who experience similar issues on both NF4 and non-NF4 platforms.

Also, this post is very interesting.
 
The first inclination I'd have is to definitely see if there's something wrong with ZZY X2. *Like you said, if there's a problem on one particular kind of chipset, then the first assumption is that it is very likely an issue with that chipset.

I just don't want to go down this road assuming that it is a chipset issue because it occurs most frequently (VERY much most frequently) with that chipset. Naturally, that's the first thing you want to point the finger at, but pointing fingers has never done anyone any real good. I shattered my Audigy, but I'm not 100% certain the problem was with the Audigy. If I could get in deep at the software level, I could be sure, but not a moment sooner. But then, rage is not such a reasonable thing :)

I don't know to what extent NVIDIA and Creative have addressed this issue, so excuse my ignorance of that. What is NVIDIA's statement, and what is Creative's? Do they blame each other, or are there glimmers of either taking responsibility of some sort?

*That's it and that's the main point I presented. I had a Second Audigy #1 that has four 7.62mm holes in it LOL! Now that bad boy had bad drivers. I feel your pain. If I picked computer parts on the bases of who's NOT ripped me off, I'd not have a computer. I gotten bogus deals from almost all of the folks in this Market.

I've had far worse drivers than my Current X-Fi drivers and software.

I'm NOT sure who's fault it is on that one Platform that has way more problems that the others. That one platform does make this worse than it would have been otherwise IMHO.
 
I'm just concerned that Creative hasn't addressed similar problems on non-NF4 motherboards. Obviously, it does happen, so a pure NVIDIA blame-game doesn't seem like the right answer. It also seems like a potential driver issue on Creative's part.

It might be just the right combination of fault between NVIDIA and Creative, but NVIDIA and its AIBs are the only ones delivering some sort of satisfaction. It's obvious, given the fact that only an initial statement was made (with zero follow-ups) that Creative is not at all concerned with users who experience similar issues on both NF4 and non-NF4 platforms.

Also, this post is very interesting.

I agree with you because other sound cards don't have this problem on the same platform. When you use the exact combination, the probability would be higher, so both of them have the problem but only one side is trying to fix it. The other side did nothing so the problem on other platform will still exist.
 
I agree with you because other sound cards don't have this problem on the same platform. When you use the exact combination, the probability would be higher, so both of them have the problem but only one side is trying to fix it. The other side did nothing so the problem on other platform will still exist.

Other sound cards don't feature Hardware acceleration like X-Fi. So you have no MLP, OpenAL or etc... clearly not the same. They require fewer Drivers so less of a chance to cause a problem in the first place.
 
Other sound cards don't feature Hardware acceleration like X-Fi. So you have no MLP, OpenAL or etc... clearly not the same. They require fewer Drivers so less of a chance to cause a problem in the first place.
So they are allowed to screw up and they don't need to fix their problem just because they have the "hardware acceleration"?
 
Crosshairs;1[COLOR="Red" said:
[/COLOR]030515301]what was the point of this thread?
Was it so you could insult people that have trouble with creative?

GG

edited - O/T ---- magnetik

#29 Donnie27
Originally Posted by mr saturn
I bought one, caused blue screens and never installed right (using rig in my sig). Returned it and found out all of them would have the same problem (via creative forums) so I just gave up and went with a modded Live!.

To this day I wish it would have worked, but even if I do get one that installs correctly I hear theres a bad crackling issue when the system is under load.

Donnie27 said:
Yes that is a good reason to NOT mess with it. NO sound card is worth screwing up your whole system over. But what's been going on here, is that folks are saying stuff like, it doesn't work on mine so the Card and the Drivers suck. That's just NOT right, right?

So where did I dis' this guy? I expect stuff like this (to not work on every system) to happen, the sheer sized this market means odds are with something this complex, problems are $#it will happen. The problems pop up when folks introduce excuses for one company while bashing another.
 
I will reopen this thread. if it even comes close to heating up.. I will close it faster than the light that got sucked into a black hole. ;)
 
Well on Vista Creative forgot to add bass redirection. Not too happy about that. :mad: But I heard new (and WHQL'd too) Vista drivers are coming March 8thish, maybe then.
 
I seen a set of X-fi2 drivers and they look alot differnt then the stock X-fi drivers. Maybe they are gonna be similar to these. Creative Labs maybe just put out s imple set to get things running while they were working on the maind driver set for Vista. We shall see.
 
I gave forewarning.

Thank YOU. You did and I take responsibility for my part in screwing it up as well. I'll do my best to not let that happen again.

Anyway, as I said on the other thread, I left the whole crap load of the software installed and my Drivers work. I now have two buds using it with Vista and 32bit seems to have fewer problems that 64bit. Creative has some work to do.
 
Two of my Buds have Vista and both said they seemed to be running XP on their Dual Booted systems more times than not.
 
Repaired a system that was giving a user problems. Creative Labs was the problem the user reported. Error, "No compatible device found". No creative drivers would install.

The card had worked loose from the PCI slot. Shut down the computer, flushed power by hold the power switch and reseated the card. Card works, no re-installs or etc.. I didn't charge the person to repair the computer but won a $50 bet:) The bet was that either the Card had died or was loose vs. bad Drivers and card NOT being loose or bad.

I love the simple looks of my Lian-Li 7B but it sucks when it comes to Rigidness or strength.
 
My drivers work (Windows XP) for my X-Fi XtremeMusic, they've always worked. The only problem I had was crackling noises, but that was due to the PCI nForce networking controller fighting with the soundcard during multiplayer games. So I changed my primary to the PCI-E networking adapter. Problems gone.
 
Status
Not open for further replies.
Back
Top