From: Bill Hileman on
http://support.microsoft.com/kb/937378/en-us

SYMPTOMS

Consider the following scenario: (Okay!)

..You upgrade a computer to Windows Vista. (Uh huh)
..The computer uses a SigmaTel HD audio driver. (Uh huh)

In this scenario, audio playback no longer works on the computer.
Additionally, you receive the following message when you position the
pointer over the speaker icon in the notification area:

No audio output device is installed. (Yupper!)

This problem occurs even if all the audio cables are connected correctly,
and the sound driver appears to be working correctly in Device Manager.
(That's right!)

CAUSE

This problem occurs because of the proprietary way in which the SigmaTel
unified driver supports custom OEM configurations. Instead of using
different .inf files, SigmaTel uses an .ini file-referenced system that does
not function correctly when you upgrade the computer to Windows Vista.
(Well, damb)

RESOLUTION

To resolve this problem, download the latest SigmaTel HD audio driver from
your OEM support Web site, and then install this driver.

Um, I tried that, Sherlock. More than once. In fact, after reading about
similar problems, I also downloaded and installed the latest chipset
drivers. I went to Sigmatel's web site. They emphatically state that they
DO NOT SUPPORT THEIR OWN PRODUCTS and you have to go to the OEM for help.
Seems to me that DELL NEEDS TO CREATE THE FRIGGIN .INF FILES LIKE NOW.

I think it's things like this that lead people to do crazy things.

FIX MY DAMB COMPEWTER!

Bill "Don't make me angry" Hileman


From: Tony Harding on
Bill Hileman wrote:
> http://support.microsoft.com/kb/937378/en-us
>
> SYMPTOMS
>
> Consider the following scenario: (Okay!)
>
> .You upgrade a computer to Windows Vista. (Uh huh)
> .The computer uses a SigmaTel HD audio driver. (Uh huh)
>
> In this scenario, audio playback no longer works on the computer.
> Additionally, you receive the following message when you position the
> pointer over the speaker icon in the notification area:
>
> No audio output device is installed. (Yupper!)
>
> This problem occurs even if all the audio cables are connected correctly,
> and the sound driver appears to be working correctly in Device Manager.
> (That's right!)
>
> CAUSE
>
> This problem occurs because of the proprietary way in which the SigmaTel
> unified driver supports custom OEM configurations. Instead of using
> different .inf files, SigmaTel uses an .ini file-referenced system that does
> not function correctly when you upgrade the computer to Windows Vista.
> (Well, damb)
>
> RESOLUTION
>
> To resolve this problem, download the latest SigmaTel HD audio driver from
> your OEM support Web site, and then install this driver.
>
> Um, I tried that, Sherlock. More than once. In fact, after reading about
> similar problems, I also downloaded and installed the latest chipset
> drivers. I went to Sigmatel's web site. They emphatically state that they
> DO NOT SUPPORT THEIR OWN PRODUCTS and you have to go to the OEM for help.
> Seems to me that DELL NEEDS TO CREATE THE FRIGGIN .INF FILES LIKE NOW.
>
> I think it's things like this that lead people to do crazy things.
>
> FIX MY DAMB COMPEWTER!
>
> Bill "Don't make me angry" Hileman

Sounds like the audio problem I had when I upgraded my computer to XP
Pro x64. I had to download a hotfix from MSFT, install the correct fix
(English IIRC), then install the Dell audio drivers.

The filename is:

KB888111_Supported_OS_All_Languages.zip

I'd take a look at MSFT's KB for 888111.

HTH
From: Bill Hileman on
"Tony Harding" <ToHard(a)nowhere.org> wrote in message
news:4805a035$0$11621$607ed4bc(a)cv.net...
> Bill Hileman wrote:
>> http://support.microsoft.com/kb/937378/en-us
>>
>> SYMPTOMS
>>
>> Consider the following scenario: (Okay!)
>>
>> .You upgrade a computer to Windows Vista. (Uh huh)
>> .The computer uses a SigmaTel HD audio driver. (Uh huh)
>>
>> In this scenario, audio playback no longer works on the computer.
>> Additionally, you receive the following message when you position the
>> pointer over the speaker icon in the notification area:
>>
>> No audio output device is installed. (Yupper!)
>>
>> This problem occurs even if all the audio cables are connected correctly,
>> and the sound driver appears to be working correctly in Device Manager.
>> (That's right!)
>>
>> CAUSE
>>
>> This problem occurs because of the proprietary way in which the SigmaTel
>> unified driver supports custom OEM configurations. Instead of using
>> different .inf files, SigmaTel uses an .ini file-referenced system that
>> does
>> not function correctly when you upgrade the computer to Windows Vista.
>> (Well, damb)
>>
>> RESOLUTION
>>
>> To resolve this problem, download the latest SigmaTel HD audio driver
>> from
>> your OEM support Web site, and then install this driver.
>>
>> Um, I tried that, Sherlock. More than once. In fact, after reading
>> about
>> similar problems, I also downloaded and installed the latest chipset
>> drivers. I went to Sigmatel's web site. They emphatically state that
>> they
>> DO NOT SUPPORT THEIR OWN PRODUCTS and you have to go to the OEM for help.
>> Seems to me that DELL NEEDS TO CREATE THE FRIGGIN .INF FILES LIKE NOW.
>>
>> I think it's things like this that lead people to do crazy things.
>>
>> FIX MY DAMB COMPEWTER!
>>
>> Bill "Don't make me angry" Hileman
>
> Sounds like the audio problem I had when I upgraded my computer to XP Pro
> x64. I had to download a hotfix from MSFT, install the correct fix
> (English IIRC), then install the Dell audio drivers.
>
> The filename is:
>
> KB888111_Supported_OS_All_Languages.zip
>
> I'd take a look at MSFT's KB for 888111.

Thanks, Tony. I did finally figure out the solution. I had downloaded and
installed the updated drivers from Dell directly, but it didn't work.
However it would appear that the reason it didn't work was because I'd
uninstalled the original device driver via Device Manager (as one would
think one should). Instead, the solution was to remove the driver via
Add/Remove Programs, then installing the replacement drivers worked.
Probably had something to do with the .Ini vs. .Inf file issue, who knows.