Joystick Port Problems

Problem: Windows would not "see" Thrustmaster T2 using Sound Blaster 16 PCI game port. Installed a CH gamecard GC3 and disabled Blaster game port. CH GC3 shows as uninstalled during boot screen. Device manager shows Blaster game port disabled and new game port enabled with no conflicts. All instructions followed closely. System: Asus P2B motherboard Bios version 4.12 Celeron 300 overclocked to 450 128 megs of Cas2 ram Soundblaster 16 PCI soundcard Question: Am I missing something easy here or has someone else run into this problem. I have tried other joysticks on Blaster game port, they did not load under windows either. I'm assuming the Blaster game port is not fully disabled somehow even though device manager shows it as such. Any pointers would be greatly appreciated. Steve

I'm going thru a similar problem with a little bit different hardware. I use the gameport on SBLive. The only controller Windows will recognize is a Sidewinder gamepad of mine. What I'm guessing is that DirectX7 caused this. DirectX6.1 never gave me any problems. My point is, which version of DirectX is installed?

Are you using WinNt? Winnt have only MS Sidewinder driver installed. If you have another analog joystick you have to inastall those drives from your winnt CD. Borut

I am using Windows 98.

I am using DirectX 7, yikes! > > Problem: Windows would not "see" Thrustmaster T2 using Sound Blaster 16 > PCI > > game port. Installed a CH gamecard GC3 and disabled Blaster game port. > CH > > GC3 shows as uninstalled during boot screen. Device manager shows Blaster

Quoted text (11 lines)

> > game port disabled and new game port enabled with no conflicts. All > > instructions followed closely. > > System: > > Asus P2B motherboard Bios version 4.12 > > Celeron 300 overclocked to 450 > > 128 megs of Cas2 ram > > Soundblaster 16 PCI soundcard > > Question: Am I missing something easy here or has someone else run into > > this problem. I have tried other joysticks on Blaster game port, they

did > > not load under windows either. I'm assuming the Blaster game port is not > > fully disabled somehow even though device manager shows it as such. Any > > pointers would be greatly appreciated. > > Steve > I'm going thru a similar problem with a little bit different hardware. I use > the gameport on SBLive. The only controller Windows will recognize is a > Sidewinder gamepad of mine. What I'm guessing is that DirectX7 caused this. > DirectX6.1 never gave me any problems. My point is, which version of DirectX > is installed?