Sound Blaster not listed in control panel, No Audio Device Listed, Another application is record

[size="3" face="Times New Roman">Sound Recorder can not record sound because another application is recording, stop recording on this application and try again. <
[size="3" face="Times New Roman">Sound device installed ok in device manager but when I go to sounds in Control Panel it reports that there is no audio device it only list a modem device line?<
[size="3" face="Times New Roman">?<p class="MsoNormal">[size="3" face="Times New Roman">I have tried everything that I can think of (uninstalling and reinstalling in normal windows and safe windows mode, even after doing a full clean of the registry).
<p class="MsoNormal">[size="3" face="Times New Roman">I thought that the sound card must have developed a fault so bought a new one - but alas the same problem!
[size="3" face="Times New Roman">?<p class="MsoNormal">[size="3" face="Times New Roman">I even tried uninstalling and reinstalling windows component software for the multimedia but still the same problems.
[size="3" face="Times New Roman">?<p class="MsoNormal">[size="3" face="Times New Roman">A question that I have thought of ?pertains to the relationship of the applications involved along with the relationship between the kernel , the CPU memory , and the sound devices.
[size="3" face="Times New Roman">?<p class="MsoNormal">[size="3" face="Times New Roman">Can you clear the memory or perform a memory dump along with a kernel clear or refresh? to free up any potential hangs?
<p class="MsoNormal">[size="3" face="Times New Roman">Also is there a way to manually point the sounds & audio app. in the Control Panel to the proper sound device in the device manager?
[size="3" face="Times New Roman">?see my posts and replies on here
http://forums.creative.com/creativel....id=5683#M5683
http://forums.creative.com/creativel....id=5682#M5682
http://forums.creative.com/creativel....id=5684#M5684
http://forums.creative.com/creativel....id=5680#M5680
Advertisement
Reply

Wow,
Talk about picking the hardest solution to an easy problem.  You guys were right, it wasn't driver related at all.  It simply wasn't enabled in the system BIOS.  I never imagined that it would be disabled as a default.  I conceptualized this is Plug and Play (Which was wrong).  
Thanks for the hand.  BTW, MSI help desk was clueless about this (which was surprising).  
Now where was I (Starting Warcraft III),
Scott