Good evening to the PMDG team from SwitzerlandFirst of all, your products are day by day cheapper, due the currency lost of the US$ :-)In different posts you recommended do not install the FSX in the program-folder of the harddisk, instead directly on C:/FSX.Since FS9 with PMDGs 737, 747-400 and MD11 and FSX with the 747-400 and MD11 my FSX runs in the program folder without any problems.I don't think I can remove the FSX without a reinstall to the C./FSX? I don't want a reinstall of FSX with the SP1 and 2, PMDGs 747-400 and MD11.Why before never it was an issue and now it is? For me it is this important for a go or no go with NGX.Thank you very much for your answer on this matter.Have a nice evening and best regardsMarcel

Hi, it is an issue since maybe Vista but Windows7 for sure, and is caused by problems with permissions. Generally you should be able to avid them by simply running FSX as administrator, which means to right click and select "Run as administrator" or permanently setting it in FSX.exe file properties.

Even when running as administrator we've seen issues - Windows Vista/7 does very strange things to older programs in the Program Files and Program Files (x86) folder. FSX was made before these OSes existed. You can try it in those folders but just be aware that this is our recommendation on Vista/7 - install outside the Program Files folder. Unfortunately this does require a reinstall of the sim - the registry entries for the sim addons aren't going to work because they're still referencing the old location. Follow this guide if you decide to do it:http://support.preci...nstall-fsx.aspx

Good evening RyanThanks. If I desire to do it, what about the re-installation of the 747 and MD11? Have to use the extendet download service by PMDG support or what?Thanks for quick reply.Regards Marcel

Marcel, PM me your store account info...

Hello RyanThank you very much. We've very close of midnihgt here in Switzerland and I've to get up very early in the sunday morning. I'll do it an other day with patient, because I think your re-downloads links with activation have a limit of expiry days, isn't it? Best regards and good night over the AtlanticMarcel

I am getting a crazy OOM error with FSX (has nothing to do with the NGX) and I wonder if it has something to do with the fact that I am running it in the Program Files(86) folder.I get a message that says to lower my settings in FSX and that my computer has run out of memory, yet if I click within the FSX window, the sim keeps on running. If I close the error window, then FSX will also close, but while the error window is open the sim keeps going, at least for a while.When I check my Task Manager under Performance, it looks like I have plenty of memory available.I have Windows7 Ultimate 64bit on and i7 with 12Gigs of ram and a nVidia GTX480 video card.Do you think if I re-install FSX into C:\Microsoft Games\Microsoft Flightsimulator X, and take it out of the Program Files (86) folder, it would make a difference? Thank you,Bob

Hoi BobOnly a short input: As I understood Ryan even out of "MS Games/...."Direckt C:/FSX.Regards Marcel

It really doesn't matter where you put it as long as it's out of Program Files or Program Files (x86) - C:\Games\FSX is fine, D:\Simulators\Flight Simulator X is fine etc... it just needs to not be in one of these folders that the OS "protects".

Mine is in C:\Microsoft Games\Flight Simulator X\ and C:\Microsoft Games\Flight Simulator 9\ but unfortunately with my McAfee anti-virus I am unable to exclude MSFS from being scanned. Apparently it's a safeguard that McAfee built into their software to stop unsuspecting users from exempting files from scans that shouldn't be exempted. Very frustrating, but I don't know what I can do besides get a different anti-virus product.

It really doesn't matter where you put it as long as it's out of Program Files or Program Files (x86) - C:\Games\FSX is fine, D:\Simulators\Flight Simulator X is fine etc... it just needs to not be in one of these folders that the OS "protects".

Well, I'm going to be uninstalling my FSX tomorrow and re-installing it in C folder. I'm finding that I can go on a long flight, but when I get into the approach I get the OOM error.I went over 1200 miles today without any problem. Then I got into the approach for KDFW and my graphics started to get a little weard, then I got an OOM error. I clicked back on the FSX window and continued the landing, moving the error behind FSX, but things were falling apart graphically and getting choppy. After I landed, the airport had no detail.We'll see after I get everything re-installed, I guess. Bob

Bob, what about .cfg tweaks, do you use any? If you do, then try with default .cfg.

Bob, what about .cfg tweaks, do you use any? If you do, then try with default .cfg.

Yes. I will once I get it re-installed in the C folder. This is something that I have wanted to try. I have done all of Bohote's tweaks, nVidia inspector and FPS Limiter and my FSX runs beautifully with great graphics, but when I approach the destination airport (no matter how long the trip) I run out of memory.If putting FSX on C folder doesn't work, I going to put a new i5 or i7 Sandybridge processor and see if that helps, because my i7 looks like it is pegging out on six of the eight cores whenever I get the OOM error.