rodzilla

i have an older MS force feedback pro joystick,gameport version...i know a lot of people seem to have trouble getting this stick to work in win2k/xp...i don't have that problem... it works just fine.but i have no control over the force feedback unless the game itself allows it...but most games don't go beyond a simple on/off option for FF...and the default setting when turned on seems to be "high" which means i have to literally fight this stick for control...it's stiff,it's tiring and it makes it very difficult to use decently... in win98 these settings were/are controlled by the stick's software via the control panel.but the software control is not available to me for win2k... does anyone have any ideas on how to control just the overall level of force feedback...i don't know of any drivers other than the OEM versions that come with the OS,are there any others?does anyone know of a registry hack possibly?this doesn't have to be easy,but it would seem simple enough...there must be a way!

alecstaar- i was actually the one that advised stoffer about this hotfix issue at the other board,as i had experienced it as well.your advice is good, however can i assume you haven't had this problem?setting the pagefile to autoclear on shutdown has nothing on this pause..affected machines literally sit there with no activity whatsoever for well over a minute,it's extremely annoying. as for better safe than sorry,well maybe so,but this update really doesn't seem to even apply to the average single pc or home network user unless you plan on hacking your own security settings.microsoft themselves say in order to expoit the vulnurability the attacker needs to be logged on and have access already,from what i've read this may be a problem in a larger network with multiple users,some who may want to change their own or someone elses security settings,but i really think for the average user this can be safely forgone until microsoft realizes the error and "fixes the fix" XP they say has this fix incorporated into SP1...well on my dual boot xp/2k system my XP with sp1 doesn't have this problem shutting down so obviously there is something slightly wrong with whatever this update does to win 2000....