Re: Intel DG33BU motherboard and Vista Ultimate - audio driver iss

On Wed, 11 Jun 2008 07:43:02 -0700, sand
<sand@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Nonny, you've been so helpful - gee, thanks!

WTF! You want me to wave a freakin' magic wand for you?

OK... here's a DEFINITE fix, that you won't like: BUY A NEW AUDIO CARD
and disable onboard sound.

Realtek doesn't appear to have a very good Vista track record - and I
speak from personal experience. Buying a new sound card was my fix.

"Nonny" wrote:

On Tue, 10 Jun 2008 11:03:04 -0700, sand
<sand@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

There are several problems. First, Intel claims there is no driver issue
when there is a KNOWN issue to someone (Microsoft I assume) and two, I would
prefer to have the custom control application that usually comes with the
board's driver bundle.

Doesn't look like that's gonna happen soon.

"Nonny" wrote:

On Tue, 10 Jun 2008 08:36:00 -0700, sand
<sand@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

I just built a new PC with the DG33BU (made for Vista) board running Vista
Ultimate. It has the latest BIOS and drivers from Intel except for the audio
driver. Sound works using the native OS driver, but when I try to install
the Intel driver filename: AUD_allOS_5605_PV_Realktek.exe the Windows Program
Compatibility Assistant pops up and says "This program has known
compatibility issues" and "Intel Audio Controller - Realtek Codec is
incompatible with this version of Windows."

If the audio works with the native driver, what then is the problem???

Calling Intel has done little to help (yet) - I've gotten troubleshooting
suggestions like "remove the board from the chassis" to "reinstall the OS"
and on my last round - they think there might be a hardware problem and are
suggesting the RMA route.

Given the nature of the error messages and the fact that my audio does work
(although without the Intel driver or associated control app) I don't really
think the issue is faulty hardware. Any suggestions?

Your board works as promised with Vista.

The new driver/software apparently doesn't. It's a driver problem.