HardwareHeaven.com

HardwareHeaven.com

Looking for the skin chooser?
 
 
  • Home

  • Hardware reviews

  • Articles

  • News

  • Tools

  • Gaming at HardwareHeaven

  • Forums

 

Go Back   HardwareHeaven.com > Forums > Hardware and Related Topics > Audio General and Technical Discussion


Audio General and Technical Discussion Having problems or wishing to share information? check this out.

Reply
 
Thread Tools
Old Mar 13, 2004, 09:42 PM   #1
DriverHeaven Lover
 
Join Date: Oct 2003
Location: Dothan, Alabama USA
Posts: 224
Rep Power: 0
Wildman95gs-t is on a distinguished road

Game port conflict

I have a Turtle Beach Santa Cruz sound and after installing it on my Biostar nForce2 M7NCG400 motherboard, i get a conflict on the game port, it says this devise cannot find enough free resorces that it can use (Code 12). When you open resorces and configure manualy Input / Output 0200 - 0207 is being used. When i viewed all resorces by type, i couldnot find anything using that i/o. I have the onboard sound and game port disabled in the bios and there is no douplicate hardware. i would like to correct this conflict as it might be the cause of my poor gaming performance
__________________
AMD Athlon XP3000+
Biostar nForce2 M7NCG 400
Windows XP Home Edition SP3
Albatron 6800GT 256mb
2x1gb G.Skill NS 400DDR in DC
Creative X-Fi Xtreme Gamer
WD 100Gb 7200 HD
Samsung 16x/48x DVD Drive
Samsung 40x/12x/40x CDRW Drive
ENlight 420 Watt PSU
Wildman95gs-t is offline   Reply With Quote


Old Mar 18, 2004, 04:17 PM   #2
DriverHeaven Junior Member
 
Join Date: Nov 2002
Posts: 55
Rep Power: 0
Brian48 is on a distinguished road

No, it's not effecting your gaming performance, but it's still annoying nevertheless. Welcome to the wonderful, quirky world of nForce2. Just disable the device under Device Manager and use the on-board gameport if you really need it. It's an issue with sound card drivers, but Voyetra has never really corrected it (even with their beta release 4193). Supposedly it was addressed in the 4186 beta, but the fix doesn't work for everyone. Just learn to live with it as it shouldn't cause a problem once it's disabled.

FYI, this problem effected the Audigy2 early on as well, but Creative fixed it last year starting with their 11 Feb 03 driver release.
Brian48 is offline   Reply With Quote
Reply

Thread Tools