MS FF usb problem

I have Win ME/Win XP dual boot MS FF usb works perfectly all the time. My mate has Win XP and MS FF usb. But he has a pig of a time. In games his throttle and brake are either on or off. I went over last night to try and help him but it is just so different when i went into Game Controllers and Calibrate. Easy to do the turn left turn right press a button bit. Then it asks for RZ rotation......nothing makes this change. Only pressing a button which moves you onto the Finish screen. Then in LFS which shows RZ rotation his brake is shown as half on. Seperate doesnt work and he has to settle for Combined and that leads back to the on or off syndrome,i tried driving with it and it was awful. So can anyone advise how we sort out the calibration or use another utlity to get his pedals acting progressively again. Many thanks. AD

Ms ff devices do not work with "via" usb controllers

"Conga" <[email hidden]> wrote in message news:ZFcp9.111763$[email hidden]... > Ms ff devices do not work with "via" usb controllers > Yes they do. He should install the software that came with the wheel. It works with W2k and XP despite the warning during install. He can then choose separate axis and probably calibrate the thing to work OK. Jone.

Shut the fuck up! "Yes they do" Who made you an expert?You guys are generalising. There are 3 versions of the sticks and 2 of the wheels and some MSFF devices have issues with VIA usb controllers, there are also issues with Santa Cruz and AC97 soundcards. Go there and you'll find everything you need to get an answer: http://support.microsoft.com/default.aspx?scid=/support/hardware/forcefeedba ck/faq/default.asp Windows 2000 May Hang with USB Devices on Older Via Chip Set The information in this article applies to: a.. Microsoft Windows 2000 Advanced Server b.. Microsoft Windows 2000 Professional c.. Microsoft Windows 2000 Server IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base: Q256986 Description of the Microsoft Windows Registry SYMPTOMS When you are using certain Universal Serial Bus (USB) devices on a motherboard with the Via chip set in Windows 2000, you may experience any of the following symptoms: a.. The computer stops responding (hangs) when you attempt to use or connect certain USB devices. b.. You receive a "STOP: 0x0000000A - IRQL_NOT_LESS_OR_EQUAL" error message. NOTE: This behavior may also occur when you attempt to shut down the computer with Advanced Configuration and Power Interface (ACPI) or Advanced Power Management (APM) features enabled. CAUSE This behavior can occur if Windows 2000 detects a Via chip set and loads the Intel/Via driver (Uhcd.sys) with an older version of the Via chip set. Via chip sets earlier than REV_05 are not supported in Windows 2000. RESOLUTION Via has updated the newer chip set revisions, which are supported in Windows 2000. If your Via chip set is earlier than REV_05, consult the motherboard manufacturer's Web site for updated drivers or additional information. As an alternative, add a PCI add-in Universal Serial Bus (USB) adapter rather than using the built-in Via chip set-based controller to attach USB devices. You should disable the built-in controller in the computer's BIOS and Device Manager. WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk. To determine the revision of your Via USB controller, locate the Vendor ID string in the registry. This is located under the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI The PCI registry key contains subkeys for each PCI Vendor ID. These are similar to the following sample: \VEN_1002&DEV_4742&SUBSYS_00000000&REV_5C\1&3A To locate the Vendor ID for the USB controller, examine the subkeys of each Vendor ID listed until you find the Class:REG_SZ:USB and Service:REG_SZ:uhcd values. Within this registry key there is a HardwareID value that contains the revision number. To verify that you have a Via chip set, note the DeviceDesc and/or Mfg values within the same subkey. This should state whether it is an Intel or Via chip set.

"Conga" <[email hidden]> wrote in message news:KUfp9.112325$[email hidden]... > Shut the **** up! "Yes they do" Who made you an expert?You guys are > generalising. There are 3 versions of the sticks and 2 of the wheels and > some MSFF devices have issues with VIA usb controllers, there are also > issues with Santa Cruz and AC97 soundcards. > There is absolutely NO NEED for that. Idiot Ash http://www.siroccoracing.com

"Conga" <[email hidden]> wrote in message news:KUfp9.112325$[email hidden]... > Shut the fuck up! "Yes they do" Who made you an expert?You guys are > generalising. There are 3 versions of the sticks and 2 of the wheels and Sorry if I offended you Conga, but your "statement" kind of begged for a reply like that. I don't think I'm generalizing more then you are. You said they don't work, period. Mine works. Dameon's worked. There would be a whole lotta complaining in here about the matter if people couldn't get them to work on VIA chipsets. The QB article you quote is about W2k not XP, it doesn't fit Aydee's description of the problem, and it says W2k is incompatible with older VIA chip sets, not "Ms ff devices do not work with "via" usb controllers". I think something else is the problem for Aydee's friend, but I could be wrong, and it won't be a problem for me if I am. (If you continue posting massive statements I'll come back and contradict you again though :) Jone.

**UPDATE** Been to see him tonight and removed the wheel from the Controllers list and started from scratch. Installed the MS FF Sidewinder 4.0 software(..and yes despite its warnings) Plugged the wheel in,was recognized etc etc Went to calibrate....still same problem. So unplugged the wheel and plugged it into his 2 port PCI usb card. Tried again..still the same. Really got me stumped now. AD "Dameon" <[email hidden]> wrote in message news:[email hidden]...

Quoted text (13 lines)

> On Thu, 10 Oct 2002 11:12:06 -0300, "Conga" <[email hidden]> > wrote: > > >Shut the fuck up! "Yes they do" Who made you an expert?You guys are > >generalising. There are 3 versions of the sticks and 2 of the wheels and > >some MSFF devices have issues with VIA usb controllers, there are also > >issues with Santa Cruz and AC97 soundcards. > > Yo shut the fuck up. There is only one MSFF *USB* wheel avalable. I > had a Santa Cruz soundcard too. > > Oh, and it was an older via chipset. 686B. >

FIXED ITTTTTTTTTTTTTTT :) :) Heres how......greatttttttttttt http://f12002.relaygames.com/DLMiscDetail.asp?MiscID=64 Thankyou to all who tried to help. AD "Aydee" <[email hidden]> wrote in message news:ao4cvc$nop$[email hidden]... > **UPDATE** > > Been to see him tonight and removed the wheel from the Controllers listand > started from scratch. > > Installed the MS FF Sidewinder 4.0 software(..and yes despite itswarnings)

Quoted text (20 lines)

> > Plugged the wheel in,was recognized etc etc > > Went to calibrate....still same problem. > > So unplugged the wheel and plugged it into his 2 port PCI usb card. > > Tried again..still the same. > > Really got me stumped now. > > > AD > "Dameon" <[email hidden]> wrote in message > news:[email hidden]... > > On Thu, 10 Oct 2002 11:12:06 -0300, "Conga" <[email hidden]> > > wrote: > > > > >Shut the fuck up! "Yes they do" Who made you an expert?You guys are > > >generalising. There are 3 versions of the sticks and 2 of the wheels

and

Quoted text (10 lines)

> > >some MSFF devices have issues with VIA usb controllers, there are also > > >issues with Santa Cruz and AC97 soundcards. > > > > Yo shut the fuck up. There is only one MSFF *USB* wheel avalable. I > > had a Santa Cruz soundcard too. > > > > Oh, and it was an older via chipset. 686B. > > > >

What are you talking about? I've been using an MSFFW on VIA USB controllers for years. It helps if you download and install the VIA USB FilterDriver. -Larry "Conga" <[email hidden]> wrote in message news:ZFcp9.111763$[email hidden]... > Ms ff devices do not work with "via" usb controllers > >

Again, you are wrong. I've also used the TBSC on VIA based machines with NO issues whatsoever. -Larry "Conga" <[email hidden]> wrote in message news:KUfp9.112325$[email hidden]...

Quoted text (9 lines)

> Shut the fuck up! "Yes they do" Who made you an expert?You guys are > generalising. There are 3 versions of the sticks and 2 of the wheels and > some MSFF devices have issues with VIA usb controllers, there are also > issues with Santa Cruz and AC97 soundcards. > > Go there and you'll find everything you need to get an answer: > > >

http://support.microsoft.com/default.aspx?scid=/support/hardware/forcefeedba

Quoted text (12 lines)

> ck/faq/default.asp > > > Windows 2000 May Hang with USB Devices on Older Via Chip Set > The information in this article applies to: > a.. Microsoft Windows 2000 Advanced Server > b.. Microsoft Windows 2000 Professional > c.. Microsoft Windows 2000 Server > IMPORTANT: This article contains information about modifying the registry. > Before you modify the registry, make sure to back it up and make sure that > you understand how to restore the registry if a problem occurs. For > information about how to back up, restore, and edit the registry, click

the > following article number to view the article in the Microsoft Knowledge > Base: > Q256986 Description of the Microsoft Windows Registry > SYMPTOMS > When you are using certain Universal Serial Bus (USB) devices on a > motherboard with the Via chip set in Windows 2000, you may experience anyof

Quoted text (7 lines)

> the following symptoms: > a.. The computer stops responding (hangs) when you attempt to use or > connect certain USB devices. > b.. You receive a "STOP: 0x0000000A - IRQL_NOT_LESS_OR_EQUAL" error > message. > NOTE: This behavior may also occur when you attempt to shut down the > computer with Advanced Configuration and Power Interface (ACPI) or

Advanced > Power Management (APM) features enabled. > CAUSE > This behavior can occur if Windows 2000 detects a Via chip set and loadsthe > Intel/Via driver (Uhcd.sys) with an older version of the Via chip set. Via > chip sets earlier than REV_05 are not supported in Windows 2000. > RESOLUTION > Via has updated the newer chip set revisions, which are supported inWindows > 2000. If your Via chip set is earlier than REV_05, consult the motherboard > manufacturer's Web site for updated drivers or additional information. Asan > alternative, add a PCI add-in Universal Serial Bus (USB) adapter ratherthan > using the built-in Via chip set-based controller to attach USB devices.You > should disable the built-in controller in the computer's BIOS and Device > Manager. > > WARNING: If you use Registry Editor incorrectly, you may cause serious > problems that may require you to reinstall your operating system.Microsoft > cannot guarantee that you can solve problems that result from usingRegistry

Quoted text (9 lines)

> Editor incorrectly. Use Registry Editor at your own risk. > > To determine the revision of your Via USB controller, locate the Vendor ID > string in the registry. This is located under the following key: > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI > The PCI registry key contains subkeys for each PCI Vendor ID. These are > similar to the following sample: > \VEN_1002&DEV_4742&SUBSYS_00000000&REV_5C\1&3A > To locate the Vendor ID for the USB controller, examine the subkeys of

each > Vendor ID listed until you find the Class:REG_SZ:USB andService:REG_SZ:uhcd

Quoted text (8 lines)

> values. Within this registry key there is a HardwareID value that contains > the revision number. > > To verify that you have a Via chip set, note the DeviceDesc and/or Mfg > values within the same subkey. This should state whether it is an Intel or > Via chip set. > >