Just read this:P4 performance enhancementNot owning a P4 or a dual system I haven't been able to test this out but it should work.After starting FS, go into task manager (CTRL_ALT_DEL)Select Processes tabRight click on FS9.exe, select "Set Affinity"Disable one of the two check boxes so that FS9 only runs on one virtual CPU.Do the same on any other running utilities and select the other virtual processor.Users who run a lot of extra software report as much as a doubling in frame rates. This, of course, assumes that hyperthreading is supported and enabled on your motherboard and BIOS settings.An even better (permanent) way of constraining FS9 to run on a single virtual CPU is by using the Microsoft IMAGECFG utility (an older NT/2000 utility that works fine in XP -- do a google search). Command syntax (in a Command window):IMAGECFG -a 0x1 fs9.exeThis writes a processor affinity mask into the executable. 0x1 specifies virtual CPU 0, 0x2 specifies vCPU 1, and 0x3 uses both 0 & 1 (default). FS will always run on the specified virtual CPU(s) from that point on.Do the same with the other utilities but assign them to the other virtual CPU and you're all set. ---------------------------Anyone else try this? I just typed this in, in the command window, and this is what I got. Can anyone confirm is I did it right?F:Flight SimulatorsMicrosoft GamesFlight Simulator 9>imagecfg -a 0x1 fs9.exefs9.exe contains the following configuration information: Subsystem Version of 4.0 Stack Reserve Size: 0x100000 Stack Commit Size: 0x1000

I tried it, couldn't notice any real difference.Some say they notice, some like me don't. :)

>I tried it, couldn't notice any real difference.>>Some say they notice, some like me don't. :)The response I got when I typed in the command, is that what I'm suppose to see to ensure it worked?

>>I tried it, couldn't notice any real difference.>>>>Some say they notice, some like me don't. :)>>>The response I got when I typed in the command, is that what>I'm suppose to see to ensure it worked?>>bump

If it's worked then the last modified date of fs9.exe will have changed from the defualt which is somewhere mid 2003, I get the exact same as you when I type the command and it doesn't change anything, started fs, went to the taskmanager and it was still using 'both' processors

I dont think this is a Hyperthreading only tweak.I don't have HT technology, but heard its beneficial to do with a P4 in general.

Hi BoDean,FOr this tweak to work you need to have dual processors or Hyperthreading support (P4 3Ghz or greater). Without either one of those, the tweak won't work as the applications are all tagged for uni-processor operation.The first step in the tweak from that page you posted is to run IMAGECFG using the -U switch which will "fool" the application into thinking it's in a uniprocessor environment. Fact is, the application already knows it's in a uni-processor environment. The next step is to "assign" the application to a single processor but if you've only got one processor with no hyperthreading support, you'll get an error stating:"Image can only run in a uni-processor mode on a uni-processor system"P4's without hyperthreading support have no affinity settings in the task manager either.Sorry bud, looks like only those with hyperthreading may benefit from this tip.MIkehttp://www.members.shaw.ca/madamo/boeingsig.jpg

This was covered before, the performance increase was because of specific addon, Garmin 530XP which was 16bit. Not sure if other addons slow things down too...But in general disabling HT should not give one better performance.