Gameport Troubles

I recently purchased a TSW wheel and pedal set. I am very happy with my purchase as I had begun to enjoy the wheel set, but I have been recently troubled by some problems I am having with my game port. In particular, calibrating my wheel with Win95 button "2" always stays "fired" (not physically stuck, but within the nether world of the computer button 2 stays lit).Thus, I cannot calibrate my wheel, nor can I run certain games, such as GP2. :-( OTOH, the sound on my system is just fine :-) My system: AMD K6-2 333 MHz processor Ensoniq SoundscapeVIVO90 PnP Original BIOS String: 1.00.06.CY1T with a Unicore BIOS upgrade. My attempts to fix the problem, so far: 1) Moved sound card to another slot on my motherboard- Everything works fine until I fire any button, then button "2" stays "fired." 2) Tried another wheel/pedal set- Same problem. 3) Tried a replacement Ensoniq SoundscapeVIVO90 Pnp- Everything works fine for a couple of hours until now; Button "2" stays fired, etc.. 4) I have tried an ACM Gamecard from Thurstmaster, but I cannot disable the gameport from my sound card within Win95, plus I just feel the problem would repeat itself. I am at a loss about what to do next. John

If you decide to disable the gameport, (for this problem or just so you can use the ACM Gamecard) here is what I did for my PCI soundcard (Diamond Sonic Impact), I went to Control Panel -> Multimedia -> Advanced -> Joystick devices -> Gameport/Joystick and clicked remove. When I rebooted, I installed my CH Gamecard III and it's software, then went to Control Panel -> Add Hardware and selected Choose from list. I selected Sound, Video and Game Controllers. I selected Microsoft in the left pane, Gameport Joystick in the right, and it installed drivers from my win95 cd and I rebooted and was able to use my gamecard. I hope this helps. Charlie

% 1) Moved sound card to another slot on my motherboard- Everything works fine % until I fire any button, then button "2" stays "fired." % 2) Tried another wheel/pedal set- Same problem. % 3) Tried a replacement Ensoniq SoundscapeVIVO90 Pnp- Everything works fine % for a couple of hours until now; Button "2" stays fired, etc.. % 4) I have tried an ACM Gamecard from Thurstmaster, but I cannot disable the % gameport from my sound card within Win95, plus I just feel the problem would % repeat itself. % I am at a loss about what to do next. For attempting to disable your soundcard's gameport, Thrustmaster has some excellent tips on doing this. You may have to try every single one of them until you hit the combination that does the trick. http://www.thrustmaster.com/support/rcs_acm/pnp.htm -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

>% 1) Moved sound card to another slot on my motherboard- Everything works fine >% until I fire any button, then button "2" stays "fired." >% 2) Tried another wheel/pedal set- Same problem. >% 3) Tried a replacement Ensoniq SoundscapeVIVO90 Pnp- Everything works fine >% for a couple of hours until now; Button "2" stays fired, etc.. >% 4) I have tried an ACM Gamecard from Thurstmaster, but I cannot disable the >% gameport from my sound card within Win95, plus I just feel the problem would

Quoted text (9 lines)

>% repeat itself. >% I am at a loss about what to do next. >For attempting to disable your soundcard's gameport, Thrustmaster has >some excellent tips on doing this. You may have to try every single one >of them until you hit the combination that does the trick. >http://www.thrustmaster.com/support/rcs_acm/pnp.htm

Michael, Thank you for your reply. One of the first things I did when I was having the troubles with my system acknowledging my ACM game card was visit Thrustmaster's site. From a combination of their tips, I was able have my system use the ACM game card as my sole gameport. (If anybody cares, this information is also available on their CD supplied with their steering products, and it's quite useful.) Whew. And for a couple of hours everything was fine. Regrettably though, The problem with button "2" has emerged again. Within my computer, it stays "fired" (or "lit," or whatever???) but physically the paddle/gear- change hasn't been fired at all. Thus, I can't calibrate, blah-blah-blah... Could this problem have come about because I upgraded my BIOS and CPU with third party products away from the Intel origins? Or is this problem with my motherboard? Or is this problem with TSW which somehow jolts my gameport into error? I haven't a clue. late, j-n ("Penguins is practically chicken...And I loves the taste of chicken!" -- A Hobo, discussing dinner plans with Bugs Bunny and a Penguin)

<snip> % Whew. And for a couple of hours everything was fine. Regrettably though, The % problem with button "2" has emerged again. Within my computer, it stays % "fired" (or "lit," or whatever???) but physically the paddle/gear- change % hasn't been fired at all. Thus, I can't calibrate, blah-blah-blah... % Could this problem have come about because I upgraded my BIOS and CPU with % third party products away from the Intel origins? Or is this problem with my % motherboard? Or is this problem with TSW which somehow jolts my gameport % into error? It is beginning to sound like a problem with your TSW and the wiring. It sounds as if there maybe a short in the switch in question or the wiring harness somewhere. The only other thing I can think of is that the entry for the "wheel" you select in the Games Controller is messed up in the Registry. Does paddle show "fired" in TMScope as well? If so, I am beginning to think it is a short in the TSW. -- **************************** Michael E. Carver ************************* Upside out, or inside down...False alarm the only game in town. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

You could try it on another pc and see if the problem travels along with the wheel or stays in your own pc. Then you know where to look further. Bart Westra ><snip> >% Whew. And for a couple of hours everything was fine. Regrettably though, The >% problem with button "2" has emerged again. Within my computer, it stays >% "fired" (or "lit," or whatever???) but physically the paddle/gear- change >% hasn't been fired at all. Thus, I can't calibrate, blah-blah-blah... >% Could this problem have come about because I upgraded my BIOS and CPU with >% third party products away from the Intel origins? Or is this problem with my

Quoted text (17 lines)

>% motherboard? Or is this problem with TSW which somehow jolts my gameport >% into error? >It is beginning to sound like a problem with your TSW and the wiring. >It sounds as if there maybe a short in the switch in question or the >wiring harness somewhere. >The only other thing I can think of is that the entry for the "wheel" >you select in the Games Controller is messed up in the Registry. Does >paddle show "fired" in TMScope as well? If so, I am beginning to think >it is a short in the TSW. >-- >**************************** Michael E. Carver ************************* > Upside out, or inside down...False alarm the only game in town. >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=<[ /./. [- < ]>=-=-=-=-=-=-=-=-=-=-=-=-=-=

><snip> >% Whew. And for a couple of hours everything was fine. Regrettably though, The >% problem with button "2" has emerged again. Within my computer, it stays >% "fired" (or "lit," or whatever???) but physically the paddle/gear- change >% hasn't been fired at all. Thus, I can't calibrate, blah-blah-blah... >% Could this problem have come about because I upgraded my BIOS and CPU with >% third party products away from the Intel origins? Or is this problem with my

Quoted text (11 lines)

>% motherboard? Or is this problem with TSW which somehow jolts my gameport >% into error? >It is beginning to sound like a problem with your TSW and the wiring. >It sounds as if there maybe a short in the switch in question or the >wiring harness somewhere. >The only other thing I can think of is that the entry for the "wheel" >you select in the Games Controller is messed up in the Registry. Does >paddle show "fired" in TMScope as well? If so, I am beginning to think >it is a short in the TSW.

<snip> Michael, Thanks again for your attention. Yes, the paddle is shown as fired in theTMScope as well. After the problem has appeared with the TSW, I have tried another SW (which worked just fine before with the exact same system configuration) and the problem remained. Could a problem with the Thomas SW create a problem that persists regardless of the remedy, such as corrupting the Registry? Thanks again for your help. late, john ("Look, Maggie, that driver has a red boot and a blue boot.")