Hi,Ok, if you have a Intel HT CPU, and either the NEW GNS530/430 or the a36 do me a little favour.Run FS and take a note of your FPS reading, alt-tab out of FS and open the taskmanager, then fond the process/processes "ntvdm.exe" not how much CPU time its taking, and kill the process, then re-enter FS and see what has happened to the FPS?ThanksDan.

Couldn't RealityXP assist you when they asked a direct contact by mail?Jos

Well, I have posted on there forum yesterday, but have yet to get a satisfactory reply.I would just like to know if this is a general thing, or confined to my system.Dan.

I just tried it with two aircraft and the RXP GNS530.Killed ntvdm.exe like you asked and I saw no change in FPS. I keep mine locked at 35 though.P4 3.2HT 800FSB, 2GM Ram, 6800GT 256mb

Just checked and Ntvdm uses 8.6 mb and 3-5% cpu proccesses and when killed I can't see a gain or loss off cpu cycles. I have FS9 Exe set on Cpu affinnity O only though. Hope this helps.

Hmmm.....must just be me then, wonder why that is.Dan.

I have the A36. My pro is 3gig and HT. My video card is ATI 300. Cheap card. When doing the check you asked I found it to be using 80%. Now I am curious. After killing the process I was able to increse my FPS by 6.

hmm....I dont know why, but on my system, and seemingly yours, this process causes big cpu drain.I have written to RXP support and hopefully they will be able to fix itDan.

Dan, try turning off HT and see what happens.

Tried with it on and off, makes no difference.Dan.

I run my system with HT disabled. Funny thing. I have read hundreds of threads on here and elsewhere about how intensive FS9 is with the CPU usage. My FS9 is smooth, and runs great except with clouds. FPS are in the 19-21 range. I need a new VC and will get one soon but the more I read about FS9 the less I understand. I have the US coverd in 38m mesh from FSGenesis and their landclass. I have 3 payware aircraft. The Flight 1 172, A36, and Piaggio 180. The 172 kills my frame rates, 14 to 16 FPS, but I love it and it is the only plane I can as of yet fly in realistic mode. I read, and read some more but not much seems to work for the same person as it did the other one. I have even read where two people have the same system and their performance is vastly different. If you figure something out let me know. Thanks. R. Goad

That is basically a virutal machine. I beleive it has been noted before that it does not run well if HT is enabled.Don't know why it would be loaded if the program is 32 bit. You could use FSAutostart to kill the ntvdm if it running before start Flight Sim, but I guess it would get restarted.

Yes Ken, its the DOS virtual environment, the new GNS's seem to run in a different way now, and just call the virtual DOS environment, instead of before when they use to call the program direct.If you do a google for "ntvdm.exe high cpu usage" you will see that this is quite a common problem with the virtual DOS environment in multi-CPU environments, one of the cures was to use a small app called "tameDOS" this is supposed to cure this problem, and it does to a point, I get excellent FPS in the a36, 45fps, back to normal but the flipside of this is that the GNS becomes very sluggish, I guess because tameDOS is throttling the usage of the DOS program.So basically as it stands I can either not use tameDOS, have 15fps in FS with a responsive GNS, or run tameDOS get 45fps in FS but have a sluggish GNS.I have tried disabling HT in the BIOS, but it doesnt make any difference, maybe because when you install XP on a multi CPU machine it uses a different HAL layer?.I am really stuck now, can't understand why it works on some and not on others, any help anyone can give, I would greatly appreciate it.You never know, maybe Garmin will re-write the trainer apps as a 32-bit app one day :-lol.Dan.

As far I know the reason why the trainer is 16 bit is only one: The Garmin is based in a 16 bit processor. It's not rare to have 16 or even 8 bit in embedded systems.Jos

Have you tried using task manager to set the priority of the ntvdm process to something a little lower?