2869 nForce Audio Drivers on WindowsUpdate

Hello.
I didn't see anyone else post this, so I thought I would.
No idea what the changes are...
Good luck!

The reason why i stick the 5.10.2849 audio drivers (inside the MSI 2.29 chipset drivers) and still not yet updated is that i get the strongest rear channels output (even louder than the front). On the other hand all windows update nForce audio drivers as i noticed have a rather low rear channels volume.
I would appreciate if someone who tried out this new driver can give me a feedback about the rear channels volume.
I am using the MSI Audio CNR card and the Logitech Z-540 Analog 4.1 speakers
Thanks
Markoul

Similar Messages

New Nforce audio drivers?

I noticed that nvidia have done a special release of just their audio drivers, has anyone tried these on the neo2, does it solve problems as they say it does?
http://www.nvidia.com/object/nforce_audio_4.57_win2kxp
there are no READMEs or instructions telling you how to install it.
very strange.. probably a reaction to pressure from the half life 2 people..
you can tell it has been done in a hurry because the "installation hints" tell you to uninstall your DISPLAY driver first hehe.
I guess it will give a similar benefits to that Bas described earlier when he did the same thing manually.

Quote
Originally posted by Rafterman
I do not use the onboard sound but AFAIK imapi is a part of the Windows O/S, and has got to do with image mastering that applies to CD recording. If you are using a burner then you probably do need it.
No, this is a new service. The service that you are referring too is called "IMAPI CD-Burning Com Service". That service is required (though it can stay in manual) and is part of XP and came from Microsoft.
However, after installing the new Nvidia audio driver, a new service was added, called "Imapi Helper". This service is not part of XP, and did not exist on my system prior to installing this nvidia audio driver (I keep very close tabs on services and the like that run on my system, and this one was not there yesterday).
Furthermore, if you go into MSconfig Services tab, and choose to hide all microsoft services, this service does not get hidden. It's not a Microsoft service, it was added by the Nvidia driver.

Alc850 & nforce audio drivers/control panel

Hi,
REALTEK ACL850 works fine with nforce ac97 drivers & control panel except one thing: i'm unable to have microphone working ?
An idea ?
thanks,
alex

Hello Mouse:
Ah, OK, now I understand what you mean, thanks for posting that picture.
If I recall correctly my previous ThinkPad (T42p) had something like that - it is sort of like an extra sound control panel that is provided by the hardware vendor that supplies the sound parts inside the laptop.
I am going to hazard a guess here (I emphasize a guess) that perhaps Microsoft has added sufficient control for different sound features into the new W7 OS that the hardware vendors no longer need to provide a third party control panel to let you take advantage of all the things that the sound hardware can do.
FYI, I never saw any kind of hardware-vendor-unique sound control panel on the Vista version of my current computer, even when it first arrived from Lenovo with the factory load on the hard drive.
So - although you don't have it any more, it might turn out that you are actually not missing anything. We may need to wait and see how this plays out.
Michael
W520 (4270 CTO), which replaced a W500 (4062-27U), which replaced a T42P, which replaced an A21P...

Asio & openal support in recent nforce audio drivers

Hi there,
maybe i just didn't recognize someone else writing about it -- anyway here is what i discouvered in the nforce.zip:
[c:\transfer\nforce\audiodrv]ls
Volume in drive C is Enforcer Serial number is 944C:DF88
Directory of C:\Transfer\nforce\audiodrv\*
20.10.2002 20:11 .
20.10.2002 20:11 ..
18.10.2002 13:18 5.120 alut.dll
18.10.2002 13:18 4.096 nvack.dll
18.10.2002 13:18 218.880 nvapu.sys
18.10.2002 13:18 60.288 nvarm.sys
18.10.2002 13:18 19.968 nvasio.dll
18.10.2002 13:18 13.184 nvax.sys
18.10.2002 13:18 13.440 nvax9x.sys
18.10.2002 13:18 15.490 nvmcp.cat
18.10.2002 13:18 25.719 nvmcp.inf
18.10.2002 13:18 780.160 nvmcp.sys
18.10.2002 13:18 10.240 nvmpu401.sys
18.10.2002 13:18 28.160 nvopenal.dll
18.10.2002 13:18 44.032 openal32.dll
1.238.777 bytes in 13 files and 2 dirs 1.261.568 bytes allocated
7.187.054.592 bytes free
[c:\transfer\nforce\audiodrv]
nvasio.dll, nvopenal.dll and openal.dll look pretty interesting. Funny enough those files are NOT being installed with the supplied installer / .inf..
Any1 into this ? Are we getting native ASIO and OpenAL support ? More features, more bugs ?
regards,
Andy XS

I've been asking for working OpenAL drivers ever since the 1.13's came out. The DLL's are included, but as you noticed they aren't installed with the install routine. :O
Manual installation doesn't work either. X(
I would like to get them working since I play UT 2003 and OpenAL is the native audio codec in this game. It might also alleviate the BKSODs in some DX games.
-r

A few simple tips and questions. Neo2 system XP re-install, which audio drivers?

My questions:
I'm re-installing my XP Pro system because I have decided I don't want to go with a 2GB primary partition as my first partition. Here are my questions.
1) Should I update from 1.4 to BIOS 1.5 ?
2) Which audio drivers should I use? nVidia Driver package 4.57? Or the Realtek ALCXXX_73 from nVidia website? Last time I actually accidentally installed the 4.60 audio MCP driver from the nForce 4 standalone package 6.39, but alas the sound was fine. (perhaps a little strange seeing as how my Neo2 is nForce3 and the 4.60 was from the nForce4 package.
Which audio drivers should I install?
3) What is nVidia nTune, what can I do with it and should I bother with it?
4) Which Catalyst driver should I install? The 29.7 MB driver with Catalyst Control Center or the 23.1 MB driver with Control Panel. Whats the difference and should I care?
I'll be using MSI update, keeping the windows IDE drivers, I may use the "speedfan" program but no digicell and no corecenter.
thanx,
My tips, See below:
0) Do your first install with a minimum of hardware installed (add your PCI cards later)
1) Research here for the proper BIOS settings for stable first boot and system install.
-Disable Agressive Timings in BIOS
-Turn Off NV/ATI Speedup in hidden BIOS
2) Install XP and SP2
3) install video drivers
4) Install nVidia UDP 5.10 (preferably without audio) and don't install the nVidia IDE drivers, just keep the XP drivers. (Use the XP windows IDE drivers) I used the nVidia LAN and it worked fine.
5) Install Zone Alarm (or your prefered software firewall) and then hook up LAN, preferably behind a router
6) Windows update once you have internet working
7) Install AMD Athlon 64 processor driverv1.1.0.18
8) Install audio drivers

Thanx 10-4 on that one. I edited my system install to reflect your idea by inserting Zone Alarm install BEFORE connecting to the internet. As an aside, I have a router which our PC's are connected to, so I'm reasonably safe for a few minutes
Also, I won't really be installing the ATI Catalyst drivers now, as I'm just using a Gforce2 GTS 32MB AGP for now and XP Pro installs perfectly adequate drivers. When I get my card back from ATI I'll install the Catalyst drivers then. I'd still like some advice on which driver to install when I do though
Anyone have any other tips in regards to my questions?

K8N Neo Platinum with Nvidia Unified Audio Drivers

Hi, I have two hard drives in my PC. I'm testing out the feasibility of me running X64 at the moment. I have newly installed X64 Windows XP on one new 2nd drive and used 5-5_xp64_dd_cp.exe for my ATI 9800 pro card with no problems. Then I have installed the nForce_6.25_WinXP64_international.exe audio drivers for my on board Realtek AC97 because i have heard they are better than the Realtek drivers themselves and the Nvmixer utility looks good. Ok, no problems.
I was so impressed with the X64 Nvidia drivers that I have decided in the meantime to replace the Realtek drivers with Nvidia ones on my 1st drive that has already got Windows XP Pro installed on it. So I uninstalled the Realtek and replaced them with these nForce_5.10_WinXP2K_WHQL_english.exe unified audio drivers.
But, for some reason, they dont work. As I understand, the Nforce 5.10 are unified drivers and should replace the original Realtek ones i had installed on my 1st drive. I see no speaker icon on my taskbar and when i click to open nvmixer on my programs list, a message appears stating it cannot open as there is no nvidia compatible sound hardware present in my machine. I already know this is not the case as the X64 Nvidia drivers work for my X64 installation on the 2nd drive.
Any ideas what i am doing wrong?

The sound quality on those compared to the 4.57 standalone nvidia (that has its own version of the realtek AC97 codec and updated interface drivers) is not as good. Theres a long thread on here if you search for it for peoples opinions.
Quote from: charliemor45 on 29-May-05, 20:32:56
Shovon, the latest AC97 drivers from www.msicomputer.com will work perfectly for the K8N Neo2 Platinum
I currently have thwm running and have no problems
Go to that website, put the cursor over the 'Support' header and a drop down menu appears.
Click on Downloads.
Scroll down till you see the mother board K8N Neo2 Platinum(under the main heading Slot 939/K8)
Click on the link, and you'll come to the drivers page.
The Listed AC97 drivers that are the latest are there.

Nforce audio no rear channel

hello
im using the kn7420 mobo with a set of old 4.1 speakers in analog.
before my recent windows reinstall they worked perfectly i.e. sound out of all four speakers. now no matter which driver set i use or what options i set i cant get any sound out of the rear channel in applications. If i use the speaker test in the nforce control panel i can get it to work with certain settings but never with winamp or any games.
my speakers are creative fps 1600
any help would be appreciated
thank you
michael

Set cloning in the new audio drivers 4.31. In AC3 filter settings set 5.1 speakers. In WinAmp go preferences-Output-DirectSound-configure set Nvidia Audio and hardware accel. (Thanks to Wonkanoby)

NForce ethernet drivers and buildin firewall

I have the 7030 board, and I have some problems with the nForce Ethernet drivers and buildin firewall.
When I try to update the Network access manager with the latest v5.10 driver pack from Nvidia I get the following error.
"1: The installscript engine on this machine is older then the version required to run this setup. If available, please install the latest version of ISSCRIPT.MSI, or contact your support personnel for further assistance."
then I get this error
"1603 fatal error during installation"
I followed this link and installed a patch "IsScript9.zip" that did not work. Hope someone has a sollution to this problem.
My other problem is with the firewall, when I try to change the firewall settings to any setting, I get this error "Error in FwlProfiles Set : Unable to find profile." and the firewall setting does not change.
Extra question, does the audio driver that comes with the Nvidia/nForce driver pack not work with the onboard sound card?
As an extra bonus, and to my amusement I cant search this forum I get THIS ERROR!
"Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 35 bytes) in /var/www/web5/html/acp/lib/class_db_mysql.php on line 83"
Thank you for any help.

As a point of information, I also got that error message. To get it to work I had to uninstall the Nvidia Drivers, then I ran the isScript app, rebooted and re-installed the nforce drivers, it worked. On the manual installation, when you unzip the drivers to a location, make a note of the location. Then go into Device Manager, Network Adapters and Nvidia NForce. Locate the Update Driver tab and point to the location where you unzipped the files.

S5503w win7 64bit ethernet and audio drivers

I recently acquired a Pavilion Slimline (s5503w) desktop PC. For whatever reason the hard drive was blanked out when I recieved it and upon installing Windows 7 64-bit (Ultimate Ed) I've had quite some time locating the proper drivers. Attempting to use the recommended drivers from this website resulted in a 9996 error, you don't meet the requirments. Proper recommended installer for that version of windows, but no luck. I've also tried installing the Ethernet and Audio drivers recommended by Nividia's website. A 15.49 package, but though it recognizes the video card it doesn't notice the onboard Ethernet or Audio. Neither of these devices is listed in device manager as far as I can tell either. No typical yellow exclemation mark stating that the driver is missing.
Any help or a point in the right direction would be greatly apperciated.

Hi:
I don't think there is anything wrong with the hardware.
I would reinstall W7.
Then right afterward, install that nForce chipset driver first and reboot.
Then the video driver I posted and reboot.
Then the audio driver I posted and reboot.
If you still have issues, try a manual install.
Download the free 7-zip file utility and extract the files you downloaded into folders.
Then click on each device in the device manager that needs the drivers.
Click on the driver tab, click on update driver, select the Browse my computer for software and browse to the folders you extracted for each device.
Make sure the Include Subfolders box is checked and see if the drivers install that way.
There has to be a way to get these items installed.
If you stil can't get the drivers installed, please post the hardware ID's for each device needing drivers so I can confirm that they are what they are supposed to be according to the product specs for your PC.
If you don't know where to find the hardware ID, please read the info at the link below.
http://www.devicedriverfinder.com/blog/device-drivers/how-to-check-the-hardware-id-for-a-windows-dev...

A quick primer on audio drivers, devices, and latency

This information has come from Durin, Adobe staffer:
Hi everyone,
A common question that comes up in these forums over and over has to do with recording latency, audio drivers, and device formats. I'm going to provide a brief overview of the different types of devices, how they interface with the computer and Audition, and steps to maximize performance and minimize the latency inherent in computer audio.
First, a few definitions:
Monitoring: listening to existing audio while simultaneously recording new audio.
Sample: The value of each individual bit of audio digitized by the audio device. Typically, the audio device measures the incoming signal 44,100 or 48,000 times every second.
Buffer Size: The "bucket" where samples are placed before being passed to the destination. An audio application will collect a buffers-worth of samples before feeding it to the audio device for playback. An audio device will collect a buffers-worth of samples before feeding it to the audio device when recording. Buffers are typically measured in Samples (command values being 64, 128, 512, 1024, 2048...) or milliseconds which is simply a calculation based on the device sample rate and buffer size.
Latency: The time span that occurs between providing an input signal into an audio device (through a microphone, keyboard, guitar input, etc) and when each buffers-worth of that signal is provided to the audio application. It also refers to the other direction, where the output audio signal is sent from the audio application to the audio device for playback. When recording while monitoring, the overall perceived latency can often be double the device buffer size.
ASIO, MME, CoreAudio: These are audio driver models, which simply specify the manner in which an audio application and audio device communicate. Apple Mac systems use CoreAudio almost exclusively which provides for low buffer sizes and the ability to mix and match different devices (called an Aggregate Device.) MME and ASIO are mostly Windows-exclusive driver models, and provide different methods of communicating between application and device. MME drivers allow the operating system itself to act as a go-between and are generally slower as they rely upon higher buffer sizes and have to pass through multiple processes on the computer before being sent to the audio device. ASIO drivers provide an audio application direct communication with the hardware, bypassing the operating system. This allows for much lower latency while being limited in an applications ability to access multiple devices simultaneously, or share a device channel with another application.
Dropouts: Missing audio data as a result of being unable to process an audio stream fast enough to keep up with the buffer size. Generally, dropouts occur when an audio application cannot process effects and mix tracks together quickly enough to fill the device buffer, or when the audio device is trying to send audio data to the application more quickly than it can handle it. (Remember when Lucy and Ethel were working at the chocolate factory and the machine sped up to the point where they were dropping chocolates all over the place? Pretend the chocolates were samples, Lucy and Ethel were the audio application, and the chocolate machine is the audio device/driver, and you'll have a pretty good visualization of how this works.)
Typically, latency is not a problem if you're simply playing back existing audio (you might experience a very slight delay between pressing PLAY and when audio is heard through your speakers) or recording to disk without monitoring existing audio tracks since precise timing is not crucial in these conditions. However, when trying to play along with a drum track, or sing a harmony to an existing track, or overdub narration to a video, latency becomes a factor since our ears are far more sensitive to timing issues than our other senses.   If a bass guitar track is not precisely aligned with the drums, it quickly sounds sloppy. Therefore, we need to attempt to reduce latency as much as possible for these situations. If we simply set our Buffer Size parameter as low as it will go, we're likely to experience dropouts - especially if we have some tracks configured with audio effects which require additional processing and contribute their own latency to the chain. Dropouts are annoying but not destructive during playback, but if dropouts occur on the recording stream, it means you're losing data and your recording will never sound right - the data is simply lost.   Obviously, this is not good.
Latency under 40ms is generally considered within the range of reasonable for recording. Some folks can hear even this and it affects their ability to play, but most people find this unnoticeable or tolerable. We can calculate our approximate desired buffer size with this formula:
(Sample per second / 1000) * Desired Latency
So, if we are recording at 44,100 Hz and we are aiming for 20ms latency:   44100 / 1000 * 20 = 882 samples. Most audio devices do not allow arbitrary buffer sizes but offer an array of choices, so we would select the closest option. The device I'm using right now offers 512 and 1024 samples as the closest available buffer sizes, so I would select 512 first and see how this performs. If my session has a lot of tracks and/or several effects, I might need to bump this up to 1024 if I experience dropouts.
Now that we hopefully have a pretty firm understanding of what constitutes latency and under what circumstances it is undesirable, let's take a look at how we can reduce it for our needs. You may find that you continue to experience dropouts at a buffer size of 1024 but that raising it to larger options introduces too much latency for your needs. So we need to determine what we can do to reduce our overhead in order to have quality playback and recording at this buffer size.
Effects: A common cause of playback latency is the use of effects. As your audio stream passes through an effect, it takes time for the computer to perform the calculations to modify that signal. Each effect in a chain introduces its own amount of latency before the chunk of audio even reaches the point where the audio application passes it to the audio device and starts to fill up the buffer. Audition and other DAWs attempt to address this through "latency compensation" routines which introduce a bit more latency when you first press play as they process several seconds of audio ahead of time before beginning to stream those chunks to the audio driver. In some cases, however, the effects may be so intensive that the CPU simply isn't processing the math fast enough.   With Audition, you can "freeze" or pre-render these tracks by clicking the small lightning bolt button visible in the Effects Rack with that track selected. This performs a background render of that track, which automatically updates if you make any changes to the track or effect parameters, so that instead of calculating all those changes on-the-fly, it simply needs to stream back a plain old audio file which requires much fewer system resources. You may also choose to disable certain effects, or temporarily replace them with alternatives which may not sound exactly like what you want for your final mix, but which adequately simulate the desired effect for the purpose of recording.   (You might replace the CPU-intensive Full Reverb effect with the lightweight Studio Reverb effect, for example. Full Reverb effect is mathematically far more accurate and realistic, but Studio Reverb can provide that quick "body" you might want when monitoring vocals, for example.) You can also just disable the effects for a track or clip while recording, and turn them on later.
Device and Driver Options: Different devices may have wildly different performance at the same buffer size and with the same session. Audio devices designed primarily for gaming are less likely to perform well at low buffer sizes as those designed for music production, for example. Even if the hardware performs the same, the driver mode may be a source of latency. ASIO is almost always faster than MME, though many device manufacturers do not supply an ASIO driver. The use of third-party, device-agnostic drivers, such as ASIO4ALL (www.asio4all.com) allow you to wrap an MME-only device inside a faux-ASIO shell. The audio application believes it's speaking to an ASIO driver, and ASIO4ALL has been streamlined to work more quickly with the MME device, or even to allow you to use different inputs and outputs on separate devices which ASIO would otherwise prevent.
We also now see more USB microphone devices which are input-only audio devices that generally use a generic Windows driver and, with a few exceptions, rarely offer native ASIO support. USB microphones generally require a higher buffer size as they are primarily designed for recording in cases where monitoring is unimportant. When attempting to record via a USB microphone and monitor via a separate audio device, you're more likely to run into issues where the two devices are not synchronized or drift apart after some time. (The ugly secret of many device manufacturers is that they rarely operate at EXACTLY the sample rate specified. The difference between 44,100 and 44,118 Hz is negligible when listening to audio, but when trying to precisely synchronize to a track recorded AT 44,100, the difference adds up over time and what sounded in sync for the first minute will be wildly off-beat several minutes later.) You are almost always going to have better sync and performance with a standard microphone connected to the same device you're using for playback, and for serious recording, this is the best practice. If USB microphones are your only option, then I would recommend making certain you purchase a high-quality one and have an equally high-quality playback device. Attempt to match the buffer sizes and sample rates as closely as possible, and consider using a higher buffer size and correcting the latency post-recording. (One method of doing this is to have a click or clap at the beginning of your session and make sure this is recorded by your USB microphone. After you finish your recording, you can visually line up the click in the recorded track with the click in the original track by moving your clip backwards in the timeline. This is not the most efficient method, but this alignment is the reason you see the clapboards in behind-the-scenes filmmaking footage.)
Other Hardware: Other hardware in your computer plays a role in the ability to feed or store audio data quickly. CPUs are so fast, and with multiple cores, capable of spreading the load so often the bottleneck for good performance - especially at high sample rates - tends to be your hard drive or storage media. It is highly recommended that you configure your temporary files location, and session/recording location, to a physical drive that is NOT the same as you have your operating system installed. Audition and other DAWs have absolutely no control over what Windows or OS X may decide to do at any given time and if your antivirus software or system file indexer decides it's time to start churning away at your hard drive at the same time that you're recording your magnum opus, you raise the likelihood of losing some of that performance. (In fact, it's a good idea to disable all non-essential applications and internet connections while recording to reduce the likelihood of external interference.) If you're going to be recording multiple tracks at once, it's a good idea to purchase the fastest hard drive your budget allows. Most cheap drives spin around 5400 rpm, which is fine for general use cases but does not allow for the fast read, write, and seek operations the drive needs to do when recording and playing back from multiple files simultaneously. 7200 RPM drives perform much better, and even faster options are available. While fragmentation is less of a problem on OS X systems, you'll want to frequently defragment your drive on Windows frequently - this process realigns all the blocks of your files so they're grouped together. As you write and delete files, pieces of each tend to get placed in the first location that has room. This ends up creating lots of gaps or splitting files up all over the disk. The act of reading or writing to these spread out areas cause the operation to take significantly longer than it needs to and can contribute to glitches in playback or loss of data when recording.

There is one point in the above that needed a little clarification, relating to USB mics:
_durin_ wrote:
If USB microphones are your only option, then I would recommend making certain you purchase a high-quality one and have an equally high-quality playback device.
If you are going to spend that much, then you'd be better off putting a little more money into an external device with a proper mic pre, and a little less money by not bothering with a USB mic at all, and just getting a 'normal' condensor mic. It's true to say that over the years, the USB mic class of recording device has caused more trouble than any other, regardless.
You should also be aware that if you find a USB mic offering ASIO support, then unless it's got a headphone socket on it as well then you aren't going to be able to monitor what you record if you use it in its native ASIO mode. This is because your computer can only cope with one ASIO device in the system - that's all the spec allows. What you can do with most ASIO hardware though is share multiple streams (if the device has multiple inputs and outputs) between different software.
Seriously, USB mics are more trouble than they're worth.

MSI 785GM-E51 can't install audio drivers

Hey, I would be grateful if you could help me with this problem.
When I try to install the audio drivers of this mobo(785GM-E51), Windows 7 can't find them. It offers me another set of drivers - that of VIA's, but it should be Realtek's. Normally it wouldn't be a problem, but I have a an issue with front panel microphone jack(it's not working), so I want to install the proper drivers. I tried disabling auto-installing option of Windows 7, and then install the drivers that MSI offers officially , but still the computer acts as if I didn't install anything.
EDIT: It seems that I have a different motherboard - in the document I have(about the parts of PC), it says that the computer has MSI 785GM-E51, but now that I checked the informationa about motherboard in the Windows itself, it appaars that ASrock M3A770DE is in the case. So I guess the fact that I can't install the MSI's drivers is because of different mobo. I have no idea how this could've happened.

>>Posting Guide<<
Why don't you open up a case and read the model? Is the computer secured with some sort of sticker that voids warranty if opened?

Audio Drivers for an XP install of a dv7t-1200?

I had to reformat my laptop and since Vista is still a mediocre at best OS, I decided to switch back to XP. Unfortunately, it seems as though HP has no audio drivers for this operating system. Is there any known way to get audio working on a dv7t-1200 under windows XP? Thank you in advance

Have you tried driver in C:\swsetup\driver ?
Pavilion DV2922TX, XP-SP3 32bit, Intel T5750 2.0Ghz, Nvidia Geforce 8400M GS with 128MB, 4GB 667 DDR2, 250GB HDD

HT5628 How to fix track pad and audio drivers if we install windows 8 on macbook pro??

Can anyone help me how to install track pad and audio drivers for my MBP if i install windows 8 on it?

Run Boot Camp Assistant and select the menu option to download the Windows Support software, Then start Windows and install the Windows Support software. Follow the Boot Camp instructions which detail how to download and install the drivers (Windows Support software).

Audio drivers for Compaq C770LA for Win XP Pro / integrated mic not working

Hello. I have downgraded a Compaq C770LA to Win XP Pro SP3. Almost everything seem works perfect, but I have tried several audio drivers and still can´t get to control or use the integrated mic which this notebook has. I can hear audio and even record, etc, but there is no way to use or get to the integrated mic and some of the volumen controls I was used to (as "Record whats been listened") are lost. Does anybody knows wheter I have to change the driver or if it´s going to be any difference if I install for example the smartaudio add-on? I tried HP but they replied they don´t provide drivers for notebook for Operating Systems other than the one they gave the notebook with.
Thanks in advance for any clue!

Try XP downgrade guide, here
Your model is in Part 2.
Pavilion DV2922TX, XP-SP3 32bit, Intel T5750 2.0Ghz, Nvidia Geforce 8400M GS with 128MB, 4GB 667 DDR2, 250GB HDD

[SOLVED]Sound issue - xine was unable to initialize any audio drivers.

When I booted this morning the computer showed that arts died and blabla messages, and when I started Amarok I got this nasty error that I occasionally get when I am not in the 'audio' group:
xine was unable to initialize any audio drivers.
But I am in the audio group and everything used to work yesterday
I will post logs and versions later, just to see if it is some common issue or not.
Last edited by gemidjy (2007-11-13 09:37:56)

I just deleted ~/.xine and it fixed.

2869 nForce Audio Drivers on WindowsUpdate

Similar Messages

Maybe you are looking for