Microsoft Sidewinder Force Feedback Wheel 4.0
This is a discussion about Microsoft Sidewinder Force Feedback Wheel 4.0 in the Windows Games category; I have installed my Microsoft Force Feedback Sidewinder wheel in my computer - running Windows XP Pro. It wiil not let me assign a wheel button to a keyboard stroke ie: my talk button in Teamspeak is left control, I am trying to set my A button on the wheel to left control.
I have installed my Microsoft Force Feedback Sidewinder wheel in my computer - running Windows XP Pro. It wiil not let me assign a wheel button to a keyboard stroke ie: my talk button in Teamspeak is left control, I am trying to set my "A" button on the wheel to left control. Worked fine when I ran Windows 98SE, in XP Pro keeps giving me an error message{"An exception occured while trying to run"Shell32.dll, Control_RunDLL joy.cpl"} This thing has me baffled...any help would be greatly appreciated.
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Dec 5
Mar 25
0
1 minute
Responses to this topic
I've got the same problem - same message whenever I try to "record" action macros. So far I've got over it by copying the scheme files that I successfully recorded on my old system (running NT2000) to my new XP-Pro system. These can be found in "Program Files\Microsoft Hardware\Game Controller\Schemes".
However, I too would appreciate a proper solution - so am looking forward to learning whay I should be doing about it.
Incidently, there is a "shell32.dll" in the "WINDOWS\SYSTEM32" directory, so the message is a bit puzzling. I tried copying the NT2000 version onto my system (into SYSTEM, not SYSTEM32) but it made no difference.
However, I too would appreciate a proper solution - so am looking forward to learning whay I should be doing about it.
Incidently, there is a "shell32.dll" in the "WINDOWS\SYSTEM32" directory, so the message is a bit puzzling. I tried copying the NT2000 version onto my system (into SYSTEM, not SYSTEM32) but it made no difference.
I found that disabling buffer overrun detection for the CPU in the BIOS sorted this out. Weird but there ya go!
