Simviation Forums

I've always allowed the Windows XP automatic update feature to keep my system current, and until 2 weeks ago, it never created any problems.  After updating a couple weeks ago, I found my CH FlightSim yoke was disabled.  It took a system restore to a point prior to the update to get the yoke operational again.  Last week, with a different update, the same thing happened again, so whatever the hangup is, is not related to any specific update.

Is anyone else having a similar problem or have any ideas what to do about it?  Thanks in advance.

-Scott

 I shut the automatic updates off:
start>control panel>system>automatic updates and uncheck the box.
If you don't want to disable the auto update I don't know what to tell you. Maybe you need to update your drivers for the flight yoke.  ???

Apparently the XP update pack (SP1) has been causing loads of problems with FS2k2. Nobody knows why, M$ are doing the great customer service thing and pretending there is nothing wrong :-/. The only solution is to reinstall XP and not take on any of the upgrades.

Sorry
Ozzy

Apparently the XP update pack (SP1) has been causing loads of problems with FS2k2. Nobody knows why, M$ are doing the great customer service thing and pretending there is nothing wrong

You have opened a large can of worms!  Let me relate my sad tale of woe concerning SP1.

I bought a new laptop computer last November.  The first one Dell sent had a sprung frame and shaped itself like a taco shell whenever I opened it up.  Dell immediately replaced it.  The replacement passed all my tests with flying colors so I started the week-long process of loading software and data to turn Dell's machine into MY machine.

After 3 days of feeding it CDs without a problem, it started not recognizing CDs until I tried a couple times.  The problem got worse until it would NEVER recognize a loaded CD.  Dell's tech support wasn't much help.  A search of Micro$oft's knowledge base revealed an interesting situation: Roxio CD Creator and Norton Systemworks hate each other when working under WindowsXP.  The only solution - re-load Windows WITH SP1.

I had to do a format-reinstall of Windows, add SP1, then go through the entire process again.  The machine has been stable ever since, but the idea of 2 mainstream programs that do different things and have no need to interact killing a computer is just too weird to think about.