I use CH Yoke and Pedals. I can place the usb-sticks in my PC and it will function. Next time I start my Yoke wont work. I have to take out the usb-stick and place it again. This was not an issue in FS9. Anybody have a solution?Best regardsLars

>I use CH Yoke and Pedals. I can place the usb-sticks in my PC>and it will function. Next time I start my Yoke wont work. I>have to take out the usb-stick and place it again. This was>not an issue in FS9. Anybody have a solution?>>Best regards>Lars >Hi Lars:It sounds like you are describing a problem with having to remove and re-insert the CH controller USB cable plugs to force the USB device drivers to re-initialize in FSX via the Windows "Hot-Swap" technology.It might prove to be important for us to know here if you are using FSX installed under WindowsXP, or Windows Vista!Possibly this might assist you in exploring/solving your problem.I helped my colleague set up the CH USB Yoke and Pedals a couple of years ago on his FS2004 (FS9) system, and noticed a couple of quirks similar to what you are describing.He wanted to use the CH controllers across the room in front of his big 36" Sony Wega screen running on the RGB (YPrPb) Component Video output of his ATI video card.We tried using no less than 3 different sets of booster extender cables, and 3 different USB hubs with auxiliary power supplies in an attempt to get the CH controllers to stay active and synchronized with the virtual system device that the CH driver creates in the Windows device manager; none worked... they all failed to resume or would suddenly stop working mid-flight.We ultimately got the CH Yoke and Pedals to work properly over extender cables from IOGEAR (I have no affiliation with them... just a satisfied end user!); those cables apparently have a specially manufactured inline circuit, powered off of the USB subsystem itself, which successfully maintains those devices active and synchronized.In case you or others are interested in this option - New part# is UE250:http://www.aten-usa.com/?product&cat=595&Item=UE250 The other possibility that might cause the problem you describe is power saving modes in Windows; if you allow the computer to "sleep" or "hibernate", some special purpose drivers do not successfully wake up when you attempt to power back up and resume normal operations.I would recommend turning off all power saving and either leave the computer running around the clock with no more than a screen saver in between turning your monitor on and off, or fully exit windows before turning off the computer and monitor power when you have no intention of using it again within 2 to 4 hours to save energy.Otherwise, contact CH technical support; I have talked with them a number of times over the years, and they have proven very friendly, helpful, and committed to customer satisfaction.http://www.chproducts.com/retail/tech_contact.aspHope this might help! :-) GaryGB

>The other possibility that might cause the problem you>describe is power saving modes in Windows; if you allow the>computer to "sleep" or "hibernate", some special purpose>drivers do not successfully wake up when you attempt to power>back up and resume normal operations.>>I would recommend turning off all power saving and either>leave the computer running around the clock with no more than>a screen saver in between turning your monitor on and off, or>fully exit windows before turning off the computer and monitor>power when you have no intention of using it again within 2 to>4 hours to save energy.Thank you Gary,The above "hibernation-thing was the problem. I have asked CH Controls if there is a solution to this (I'll be able to live with this minor porblem though...)BRLars