Problem: When running WinXP, Microsoft Sidewinder Force Feedback Pro
Works - sort of - in FS2000.
Inop - totally - in FS2002.
Because Microsoft's Sidewinder 3.02 software for Microsoft's Force Feedback
Pro Hardware is not compatible with Microsoft's Windows XP, the FF Pro
joystick is only marginally operable in Windows XP. Forces cannot be
adjusted, and the "Shift Buttons" cannot be assigned. Conclusion: Microsoft'
s failure to support their hardware and software is DESPICABLE.
If your FF Pro works in FS2000 but not in FS2002, the likely reason is that
you've tried to install the Sidewinder 3.02 software in WinXP, which can
neither install or uninstall it successfully and completely. As a result,
the registries need to be edited.
Caution: Editing the registries can have dire consequences. If you are not
confident in the procedures below, go buy a FF 2 for about $100 and dump
more money down Microsoft's drain - exactly what they hope you will do.
Warning: If you have more than one joystick installed, the procedures below
may very well wipe out its registries also. Could require re-installing your
Warning: I tested these procedures twice, but I cannot attest that they will
work for everyone, nor can I help you if you get in trouble. I'll be flying!
1. Uninstall Sidewinder software (to the extent WinXP can)
a. In Control Panel, double-click Add/Remove Programs.
b. Uninstall all components of Sidewinder software.
NOTE: If you are prompted to remove "Shared" files, click No. Do not
remove shared files.
2. Delete the folder that the Sidewinder software was installed in. By
default, the Sidewinder software was installed in the following folder:
C:\Program Files\Microsoft Hardware
NOTE: Do not delete the Microsoft Hardware folder.
3. Delete any .inf files that may remain
a. Search for "sw*w98.*" (without the quotation marks)
b. Once search is complete, select all of the files that are found and
delete every last one of them. (I found only sw10w98.inf)
4. Find and rename any of the following files that may remain:
a. These, if present, should be in C:\Windows\System32 folder:
1) dinput.dll: rename to dinput.dll.old
2) dinput.vxd: rename to dinput.vxd.old
3) joyhid.vxd: rename to joyhid.vxd.old
4) joy.cpl: rename to joy.old
5) msjstick.drv: rename to msjstick.drv.old
6) vjoyd.vxd: rename to vjoyd.vxd.old
b. This, if present, should be in C:\Windows\System32\Drivers folder:
1) hidgame.sys: rename to Hidgame.sys.old
c. This file may be found in C:\Windows\Inf or C:\Windows\System\
1) joystick.inf: rename to joystick.inf.old
Not all files above will be found
Ignore files in CABS folders
5. Set a Restore point using Help & Support, then System Restore. This is
VERY IMPORTANT. If you screw up the next step, Restore may fix it back.
6. Remove Sidewinder software entries in the Registry:
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. There is no guarantee
that problems resulting from the incorrect use of Registry Editor can be
solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should BACK UP THE REGISTRY before you edit it.
IN OTHER WORDS, if you've never edited registries before, DON'T make this
your first time.
a. Click Start, and then click Run.
b. In the Open box, type "regedit" (without the quotation marks). Click
c. Back up the registry. To do this, follow these steps:
1) Click Registry, and then click Export Registry File.
2) In the "Save in" box, click Desktop.
3) In the "File name" box, type "regbackup" (without the quotation
marks). Click Save.
d. Remove the following registry keys, if they exist:
1) HKEY_LOCAL_MACHINE\Software\Microsoft\Gaming Input Devices
NOTE: In Edit, you can do a Find on "36FC9E60" and "745a17a0" to
quickly find 8) and 9) above.
Your Force Feedback Pro joystick will now be "seen" by FS2002. If it worked
in FS2000, it will work the same - not very well - in FS2002.
"Dave Wilkins" <Falc...@home.com> schreef in bericht