Turtle beach Santa Cruz game port is having problems in win xp/nforce 2 mobo

[Magnakai]

I am running an MSi k7n2 delta nforce 2 mobo, and a turtle beach santa cruz. Theres no onboard gameport on my mobo and the santa cruz game port is showing up in device manager as having problems. i've tried uninstalling it and installing it over and over and I can't get it straightened out. It's giving me error code 12. Anyone know whatt he deal may be?

 

[McCarthy]

Yes, there's something goofy with the nForce2 that doesn't allow use of the resource range of the Santa Cruz's gameport.

From Turtle Beach:
Santa Cruz: Joystick Port not working - nForce2 motherboards


The Nvidia nForce2 chip cannot access the I/O addresses for the Santa Cruz
Joystick port.

--------------------------------------------------------------------------
This issue was addressed and resolved in the 4184 BETA drivers or higher.
--------------------------------------------------------------------------

If you motherboard has a built in game port then here is a work around. This
example was on an Epox motherboard.

1. Disable Santa Cruz Game Port in the Device Manager.

2. Enable BOTH onboard Game Port and Midi Port in Epox BIOS:
Default values are:
Game Port 201, Midi Port 330, Midi Port IRQ 10 (5works as well)
- this was specific to the Epox motherboard your motherboard may differ

3. Now connect your Game Pad to the onboard game port and use it instead
of the (disabled) sound card game port.



Too bad they never got around to posting anything higher than 4161 for 2k/XP. But for Win98se the 4184 drivers should fix your problem. Download here
Personally I gave up on it, got a gameport to USB adapter for $17 and haven't thought about it since. Don't know of any other fix under 2K/XP, but this should work for you for now.

 

[NesuD]

Too bad they never got around to posting anything higher than 4161 for 2k/XP.

Look again 4193's for win2k/XP have been up for over a month Driver Page. this is supposed to correct the gameport issue although it didn't for me. works for some butnot for others I guess. I would give these a try.

 

[Adul]

Originally posted by: McCarthy
Yes, there's something goofy with the nForce2 that doesn't allow use of the resource range of the Santa Cruz's gameport.

From Turtle Beach:
Santa Cruz: Joystick Port not working - nForce2 motherboards


The Nvidia nForce2 chip cannot access the I/O addresses for the Santa Cruz
Joystick port.

--------------------------------------------------------------------------
This issue was addressed and resolved in the 4184 BETA drivers or higher.
--------------------------------------------------------------------------

If you motherboard has a built in game port then here is a work around. This
example was on an Epox motherboard.

1. Disable Santa Cruz Game Port in the Device Manager.

2. Enable BOTH onboard Game Port and Midi Port in Epox BIOS:
Default values are:
Game Port 201, Midi Port 330, Midi Port IRQ 10 (5works as well)
- this was specific to the Epox motherboard your motherboard may differ

3. Now connect your Game Pad to the onboard game port and use it instead
of the (disabled) sound card game port.



Too bad they never got around to posting anything higher than 4161 for 2k/XP. But for Win98se the 4184 drivers should fix your problem. Download here
Personally I gave up on it, got a gameport to USB adapter for $17 and haven't thought about it since. Don't know of any other fix under 2K/XP, but this should work for you for now.

check your eyes.

sc_4193.exe 25255816 06-27-03 Windows 98se (not plain), Millennium,
| 2000, XP | Release Candidate (Unsigned)
| WDM Driver v. 4193 with 5.1 Gaming,
| WMA Pro, EAX 2.0 functionality |

They are new drivers for XP/2k as well 😉

 

[dragonlord2112]

I just did this same setup with all the latest drivers and still have that problem. I just disabled it. (aka just gave up) 🙂

 

[Gulzakar]

I had the same problem, tried everything to fix it...it's a conflict with the onboard lan.

 

[NesuD]

same problem here with 2 different nforce2 boards. never did get it fixed nno matter what i tried. just gave up and got a new usb game controller.