Abit VH6 + Aureal = head imprint in the wall

[slimborama]

I just got an Abit VH6 and I was all excited to get my celly from 566->850... everything's going great, and I'm about to get hooked up with Counter-Strike 1.0 and my sound craps out when I disable the onboard sound and install my Aureal. I've been reading around, and I know I'm not the only one with a VH6 and sound probs...

Now what I wanted to ask was, is it my Aureal? or am I just plain SOL with the VH6? Believe me I've tried every permutation of PCI slots, jumper pins, BIOS settings, and drivers...

Specific symptoms:
- after cold (re)boot, splash sound plays for < 1 second then craps out until next cold reboot. process repeats.
- sound works (through the splash sound) upon reinstallation of the win2k aureal drivers, plays MP3s fine... I load up Half-Life, and sound craps out immediately until next cold reboot.
- sound doesn't work period upon install of the latest Aureal beta drivers from vortexofsound.com

Is there any hope for this POS VH6? Can I go get an SB Live! Value or should I tape some M80s to both my Aureal and VH6 and celebrate Chinese New Year early this year?

thanks homies.

slim.

 

[HammondB3]

I can pretty much gaurantee you it's the Aureal. Incredibly lame stuff from them (for the most part)...ever see their modems? uuuuuugh

good luck

 

[HammondB3]

Oooooops..... read that too fast. I didn't catch you're disabling onboard audio.

Ok. HOW are you disabling the audio? It should be done through the BIOS.

If you didn't do this ... go into the BIOS and look for the soundcard set to disabled.


Love the title of this thread BTW.... hehehehahahh

 

[slimborama]

I disabled the &quot;Onboard Sound&quot; setting in the Advanced BIOS first, and when that didn't work, a little more reading revealed there were a couple jumper pins I could remove on the motherboard, but that didn't work either. Actually, lemme clarify, ENABLING works, but DISABLING and using my Aureal does NOT work... super sucky.

 

[damocles]

Which OS are you using? I had this problem with WinME, but moving to Win2k fixed it. Have you tried the 4 in 1 drivers from Via (latest version??)