What should not happen, can be found sometimes. The audio driver stands after
run of the complete nForce driver of package still redly pretends as an unknown
hardware in the system control device manager.

The cause often lies with Windows XP and the severe manipulation of the driver's
signature marking.
For Windows the audio is a device a Realtek audiodevice and is of the opinion the
nForce audio driver do not fit or cannot work.

The Realtek audio chip sentences with an audio codex from ALC655 are concerned
mostly. With the older one audio codex ALC650 could not find out the problem.

How we go forward for the problem removal

Too first of all we go to the system control on system qualities and loosen the
"driver's signature marking" under Windows XP.
The point in "barriers" should not exist. Choose instead the option "Warn" or
"ignoring" and then as a system standard fix.


Then the audio should allow to use Audio driver and NV Mixer with manual driver's choice
about the system control / device manager.
How this will work manually, the following Guide web page shows:

In few cases the nForce audio does not let itself install driver, really.
Reason: No Realtek audio chip exists, but a C Media audio chip and chipset codex.
In this case, please, install the C Media audio driver of the Mainboard CD.
From experience I say to you, the attempt the nForce audiodriver with constraint runs
to install inclinedly. Do not try it.
E.g., Mainboards of the revision 2.1, EXoX are concerned 8rda3 + and EXoX 8rda3i

[Back to Driver Choice Page]

[Back to Main Page] [Home]