a joystick puzzle for you...

[EvilKnevil]

(reposted from TechSupport forum..)

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!

 

[EvilKnevil]

any takers out there?

please? eheheh

 

[KidViciou$]

i thought i was the only one

i think ill pull mine out of the closet and give it another try

 

[AmdEmAll]

Heh, I have the same problem with mine. Only the generic drivers work but then I cant use all the buttons.

 

[MGMorden]

I think it has something to do with a joystick port trying to emulate a digital input for analog pads. I had heard a while back that this caused problems with many actual digital gamepads and caused them to be recognised as analog pads. This happened to me with my Logitech Thunderpad Digital and Diamond Monster Sound MX300. Had to download the newest Wingman software (CD version wouldn't work) from Logitech to fix the problem.

 

[EvilKnevil]

cool..thanks for the responses...

let's hope collectively we can solve it

are all of you using the on board audio of the motherboard? couldbe a problem with the implementation of that..

i still have my pci sound card..might hook that up to see if the problem persists...

thanks again!

 

[dkozloski]

I went through all this a while back and I found that there are severe conflicts in gameport driver software because several different outfits have released drivers with totally different functions but the same name. I finally got it all straightened out by going to the Microsoft Knowledge Base. There is more information on the subject than you can stand. What happens is that a new driver installation will overwrite other drivers with the same name but different functions that are supposed to be doing something else. I had to manually remove all the drivers and reinstall what I was sure was a correct set. I seem to recall that it was an MS vs. Creative conflict but there were others involved.