nomadstop.blogg.se

1. THRUSTMASTER FIRMWARE UPDATER 3.1.9 DRIVERS
2. THRUSTMASTER FIRMWARE UPDATER 3.1.9 UPDATE
3. THRUSTMASTER FIRMWARE UPDATER 3.1.9 CODE
4. THRUSTMASTER FIRMWARE UPDATER 3.1.9 WINDOWS

Apparently, the new power arrangement turns power off to the device when Windows thinks it is sleeping or not active. Microsoft has acknowledged that the way Win 8.1 manages the ports has caused lots of compatibility y problems with USB devices. There was a work around in the TM message to me that dealt with apparent problems that this new power management arrangemnet of the USB ports that Win 8.1 used. The second thing I did related to the way Win 8.1 managed the power settings of the USB ports. I might point out here that I had it plugged into USB 3 ports putting it into the USB 2 ports did not help when it was playing up.

I then turned the xHCI back to enabled again, and the settings stayed, and the HOTAS was still ok.

My HOTAS was with firmware again, and recognised by the computer again, and working. So what I tried was to turn off in my BIOS the xHCI mode, then reloaded the Warthog drivers, following the prompts, and IT ALL WORKED! Especially, the firmware updated with no problems.

So the problem had something to do with peripherals, especially the Warthog HOTAS, being plugged into this Intel controlled xHCI USB 3 ports. Turn it off, and the ports reverted to USB 2. Upon doing research, I discovered that Intel xHCI controlled the USB ports: xHCI equalled having the USB ports active. The guy disabled the xHCI mode and it sorted the problem. The solution was to go into the BIOS to disable something called xHCI mode in the USB configuration settings. There was ONE post on the SimHQ website, just one, about a guy complaining about Win nit booting properly with a Warthog attached. I sent an email, in my despair, to TM support.

THRUSTMASTER FIRMWARE UPDATER 3.1.9 UPDATE

Did not work either the firmware update kept failing at step 2 with error 0x0000000c. Next, I tried setting up the Warthog on a seperate, older machine, with only USB 2 ports. I followed the instructions to the letter this did NOT work, no matter how many times I followed it. Then I followed the Thrustmaster advice on their website to 'wake up' Bootloader joysticks.

THRUSTMASTER FIRMWARE UPDATER 3.1.9 DRIVERS

I first unloaded everything to do with the Warthog, re downloaded all the latest drivers and tried to reload drivers. So.unstable computer that hung randomly on loading, and Warthog throttle and joystick not working. I ended up with both my joystick and throttle without any firmware at all, and always being listed as Bootloader when I attached the cables into the USB slots. In particular, Win would not recognise my Warthog joystick: it was listed as a 'Bootloader', and to make matters worse, when I tried to update the firmware, it would not load, and consistently failed at step 2 with the error message of 0x0000000c. The computer suddenly became unstable when it booted up with the USB peripherals attached. Both facts are relevant, as it turned out. As you may know, the new motherboard had predominantly USB 3 slots, and as you probably won't know, Win 8.1 introduced a new way of managing power to these USB ports. I also went from Win 7 to Win 8.1 64 bit. I upgraded to an Asus x99 Deluxe motherboard and SLI 980s ect. I want to outline what worked for me so any other poor bugger having the same problems has a head start in solving them. I now seem to have solved them, with the help of Thrustmaster Technical Department. I have been having real problems with my Warthog, and indeed my MFDs after a major computer update.

THRUSTMASTER FIRMWARE UPDATER 3.1.9 CODE

Nothing do far after three days.Ĭan anyone help a desperate simmer? The Warthog us too expensive for us to be a brick and not being used! What can I do? How can I get it working again? What is error code 0x0000000c? I gave finally Seng an email to Trustmaster support, hoping against hope they actually are helpful. In desperation, I searched the Internet none of the solutions to date have worked for me. It still would not update the firmware, continuing to fail at step 2. I tried to set up the stick on a seperate machine to no avail. I took the stick apart looking for a detached wire all appeared in order. I have done everything: followed the advice from the Thrustmaster website to 'wake up' sleeping joysticks from bootloader, but that consistently dud not work. Now, the system won't recognise the joystick, saying it is a 'bootloader' and consistently failing to update the firmware. It failed at step 2, with the big red cross and the error code of 0x0000000c. I upgraded to an Asus x99-deluxe motherboard and sli 980s, downloaded the latest drivers from the Thrustmaster nnected the joystick and throttle set the appropriate time, and then tried to update the firmware. My Warthog just became a very expensive brick.