Do a forum search. One of the forum members posted a method to correct this issue. There is another recently modified thread in which this fix is posted.

I'm using that motherboard without any audio problems. I'm running Vista 64, mind you and have installed the most recent RealTek drivers posted on the Asus site for the P5W DH Deluxe. This onboard audio worked with MC 3.0, 3.5 and now 4. I did not try it with MC 2.8.

I know this reply is of no help to you but I ran into exactly the same problem when I was upgrading to 4.0.2 and now I can't remember how I solved the problem. There's something in the readme file that talks about having to change a registry setting before installing BCC and/or Avid FX because the installer points to the wrong folder - something

With Vista you can hit F8 during the boot and select an option to allow unsigned drivers. I don't know if this is true for Windows 7. I have to agree with the spirit of Tomas' reply. This thread should have been 'Holy crap Windows 7 sort of works with a very contrained set of tests and limited hardware support... your mileage may vary'

Once you install 4.0.3 you'll lose the 182.65 driver (which is too bad because the latest nVidia driver shipping with 4.0.3 is a disaster for After Effects and various other OpenGL programs I use with my FX3700).

MC 3.5.4 is certified to work with BCC 5.0.4. Are you really using BCC 3.0?

I would say that audio is one of MCs weaknesses. I too would be interested in an answer to your question. IMHO, it should also be possible to apply multiple effects to audio clips and tracks (a feature request, but I'm not holding my breath). For any of you coming from Avid Liquid, you will appreciate the value of this missing functionality. I find

Was your placeholder clip progressive?

I have to keep using the 182 driver for 4.0.3 as I found that the newer driver completely destroyed the OpenGL shader 4 for one of my apps (Vue 8 Infinite). Admittedly, there are many settings that I could have tweaked in the display driver to (perhaps) sort this out but for now, the driver shipping with 4.0.2 seems to work just fine. Mind you, this

That's odd because MetaFuse installs and runs fine on Vista 64... perhaps it's checking for XP and Vista as prerequisites but simply reporting 'needs XP'. Were you trying MetaFuze 2.x?