Yet another Vista problem... ERR!!!!

Proxy

Pumpkin Ghost
Joined
Apr 24, 2005
Messages
4,308
Ok, I have just installed the patch for Vista that is "suppose" to fix problems for those of us with more than 3gigs of RAM. Well, I also installed the latest drivers for my X-Fi, and the newest BIOS for my motherboard. When Vista starts up I get horrific, loud, static noise. Does Vista just not play nice with XFi's?
 
Ok, I have just installed the patch for Vista that is "suppose" to fix problems for those of us with more than 3gigs of RAM. Well, I also installed the latest drivers for my X-Fi, and the newest BIOS for my motherboard. When Vista starts up I get horrific, loud, static noise. Does Vista just not play nice with XFi's?

What version of X-Fi? I just installed Vista 32bit and the sound is much better under vista for me. (Under XP, the volume controls would only affect the front speakers and I could not adjust the volume of the rear speakers -- what the fuck?) I have the Xtreme Gamer version of X-Fi.
 
I have the same as you. Due to me having 4gigs of RAM, I have x64 Ultimate.
 
I had the same issue... a reinstall of the drivers fixed that, but there's still stutter/popping/noise when browsing and listening to music... damn drivers...
 
Beta drivers or MS signed release?

From Creative, there are only one set of drivers out for Vista. They are beta right now I think. I have been searching their website but, I think I'm just gonna call the tech support there and see if they have an suggestions.
 
Why is it that one of the largest pc sound hardware vendors in the world hasn't been able to write a working set of drivers to Vista?

Why is it that similar problems have been occurring with every other hardware vendor whose hardware is related to AV reproduction?

Inquiring minds want to know..
 
because they have your money are are swimming in it like Scrooge McDuck in their money bin...
 
^^ hehe, Creative??
mcduck.jpg



Anyway, I am upgrading to Vista 64 and wanted to go to the XFi Gamer edition. This really sucks that I keep hearing about driver issues, especially for an OS that has been out for months. :confused:
 
Why is it that one of the largest pc sound hardware vendors in the world hasn't been able to write a working set of drivers to Vista?

Why is it that similar problems have been occurring with every other hardware vendor whose hardware is related to AV reproduction?

Inquiring minds want to know..

Microsoft pulled DirectSound from DirectX 10.0 at the last minute. Creative had no time to rewrite their drivers and software before release. As far as I know, alot of Creative's technology depended on DirectSound. Microsoft pretty much wiped them all out in one fell swoop. Not really Creative's fault, but then it's not really Microsoft's fault either. I'm sure they had their reasons.
 
More like these companies need to make proper drivers for their hardware that's in our Vista machines.

Or more like MS needs to stop taking out perfectly good hardware APi's for no published reason in the last month before launch....
 
Your blaming MS for Creative's driver writing :rolleyes:

Does no one here realize the X-FI has horrible driver problems with every OS. Creative has yet to fix the static, popping, and crackling noises on any OS including Vista.

Or more like MS needs to stop taking out perfectly good hardware APi's for no published reason in the last month before launch....

They also have had plenty of time to rewrite the driver....there are plenty of companies with Audio and Video drivers that work perfectly with Vista. Also it has been almost a year (if not longer) that Creative should have had a copy to work their drivers for with the DirectSound components removed....that was not a very last minute change before release, it came changed in quite a few betas before the final version.

People have to stop blaming MS for lazy developers that dont get their act together...
 
Your blaming MS for Creative's driver writing :rolleyes:

Does no one here realize the X-FI has horrible driver problems with every OS. Creative has yet to fix the static, popping, and crackling noises on any OS including Vista.



They also have had plenty of time to rewrite the driver....there are plenty of companies with Audio and Video drivers that work perfectly with Vista. Also it has been almost a year (if not longer) that Creative should have had a copy to work their drivers for with the DirectSound components removed....that was not a very last minute change before release, it came changed in quite a few betas before the final version.

People have to stop blaming MS for lazy developers that dont get their act together...

I certainly dont diminish the need for proper drivers. I agree with you 100%. Creative still doesnt have Xfi drivers for ALSA either. And alsa is a far better sound architecture, with far better documentation, and support. It's a fully functional stable API that has been in use for quite a few years now, and they still dont have proper drivers for it.

I can fully appreciate your anguish as I'm in exactly the same boat.
 
I just wish they would fix the stupid thing cause its a great card, but the crackling in BF2142 during big explosions makes me wanna scream! :p
 
i have the sound blaster 2 nx usb card. Its EOL so i'm lucky they even put out a driver. The drivers for vista won't auto sense headphones being plugged in. Its kind of irritating.
 
They also have had plenty of time to rewrite the driver....there are plenty of companies with Audio and Video drivers that work perfectly with Vista. Also it has been almost a year (if not longer) that Creative should have had a copy to work their drivers for with the DirectSound components removed....that was not a very last minute change before release, it came changed in quite a few betas before the final version.

People have to stop blaming MS for lazy developers that dont get their act together...

Thoroughly agree. It is rubbish to suggest that Microsoft pulled some sneaky, last minute stunt! Creative dropped the ball with respect of the needs of Windows users, and they did so a long time before Vista arrived. They're perhaps the biggest contributor to the problem which led to (and necessitated) the removal of DirectSound from the DX API, and they were exceptionally tardy in addressing the situation once it did arise!
 
Also it has been almost a year (if not longer) that Creative should have had a copy to work their drivers for with the DirectSound components removed....that was not a very last minute change before release, it came changed in quite a few betas before the final version.

where are you getting your info from? the DirectX10 API (with DirectSound3D removed) wasn't fully baked until just shy of three weeks before RTM. How is that "quite a few betas before the final version?" I was following the run-up to RTM quite closely because we did a lot of DirectX video processing (for the casino industry) at my last job and things inside the API were quite "fluid" all the way up till the very end.
 
Thoroughly agree. It is rubbish to suggest that Microsoft pulled some sneaky, last minute stunt! Creative dropped the ball with respect of the needs of Windows users, and they did so a long time before Vista arrived. They're perhaps the biggest contributor to the problem which led to (and necessitated) the removal of DirectSound from the DX API, and they were exceptionally tardy in addressing the situation once it did arise!

DirectSound was NOT removed. It's still there. DirectSound3D was removed.
 
Thanks for that clarification of a point of detail. And to clarify your own point of detail, the absolute, final word on the DX10 API might have been released a few weeks before RTM but that's only to be expected. The pre-release testing period is for determining whether or not the proposed changes are to be implemented in their originally proposed form or whether decisions already made need to be changed.

The likelihood of it being removed was known LONG before that final, definitive statement was made, though ;)
 
Back
Top