strange Joystick problem...

[EvilKnevil]

Hi guys...

My system specs:

Duron 700 on a Soyo K7VTA Mobo
128MB RAM
3Dfx Voodoo3 2000
Am using the Integrated Audio Chip of the Mobo (and the game port too)

Running WIN98SE, patched up, DX7, installed the VIA 4-in-1's
Sound works fine.

Here's the clincher:

My joystick (Sidewinder 3dPro) refuses to be seen by the system- I can only use it when I set it to Generic 4 button, 3 Axis joystick in the Game Controllers Control Panel.

I downloaded the Sidewinder drivers (v.3.02) and still have the same behavior.

The joystick works fine as a generic type but I need the other features of the joystick (POV hat, extra buttons, etc)...

Anyone got an idea how to fix this?

Thanks! 🙂

 

[maddmax]

Is it correctly identified and status=OK in control panel, gaming options? Go to control panel, gaming options, properties, activator should= No profile is active. Good Luck

 

[EvilKnevil]

if its generic joystick status =OK

if its MS Sidewinder 3d pro status =not connected

strange...🙂

 

[WildDreamer]

Here are a few more things to try:

MS joystick support

also make sure you are running Dx7a and not Dx7

and if you can, test the joystick on a different machine

 

[maddmax]

In the sidewinder software profile activator, make sure no profiles are active. In control panel, gaming options delete the generic. Reboot and check gaming options again. And if that doesn't work, remove both from control panel/ gaming options. Remove and reinstall sidewinder software. If it still is not correctly identified and status=OK the problem most likely is 98SE. Sometimes 98 has some files missing. That info is not handy right now, post results and if you need it, I'll get it to you. One last question, are you using gameport or usb port?

 

[Vampire]

I could never get my Sidewinder 3D Pro to work right once I upgraded to a 650 Athlon Classic (and later 600 Duron). It's an older joystick, hardware version 1.0. Apparently there's a known problem with that and Atholns. Software updates have been no help at all. I've read that it has something to do with the Athlon's double pumped memory addressing.