While I am enjoying how FSX Gold performs on my new system, I know I have started the wrong way when during installation I forgot to choose a different folder from the default "C:\Programs(x86)".

 

The sim itself installed OK, and some of the add-on aircraft to, as well as FSUIPC, but some configuration programs for add-on aircraft from Flight1 and Aerosoft are useless unless I run them as admin. This is really no problem and I can easily create a shortcut to do it, but I wonder if there are any other known problems with this type of installation in Windows 7.

 

I would like to read from other users with the same type of install. I really didn't want to go through the tedious task of redownloading from GFWL and installing again FSX to another folder. I can even disable UAC before playing FSX....

 

Any suggestions/opinions welcome!

Hello

Just start again and install to C:\FSX

You will save yourself a world of pain going forward. as you have found out many addons cannot write their data files with FSX installed in the default location.

Some folk are in denial about this, but that just means they haven't yet installed an addon that has issues with the extra security measures MS placed on Program Files (x86) folder

After you do this, follow Kostas guide to setting it up esp the part referring to uiautomationcore dll, that step alone will cure any issues switching from full screen to windowed or visiting the menu to many times.

You could just move the FSX directory and use the free registry path tool available at Flight1, you will then need to reinstall your addons to reflect the new path in the registry

mad dog, thx a lot!

 

I will search for that Flight1 registry tool - looks good!

Regarding the uninstall/reinstall of the add-ons, no problems since I just have FSUIPC, RealAirSF260, Aerosoft DiscusX, KatanaX and TwinOtterX installed :-)

 

So, the steps to follow will be:

 

1) Uninstall all add-ons, including FSUIPC

2) Move FSX under C:\

3) Run Flight1's registry tool

4) Read Word Not Allowed's guide (?)

 

Well I did use an online tweaker wich took my PC config + FSX.CFG and returned a massaged CFG file. It really had effect on my FPS! Don't remember the URL now...

 

Thx again for your help!

Hello

Sorry here is the link to Word Not Allowed's guide

http://forum.avsim.net/topic/370594-read-before-posting-software-hardware-guide-for-fsx/

 

This was the online tuning tool you used ?, it is good, Word Not Allowed's guide will explain some of the settings this tool alters and why.

http://www.venetubo.com/fsx.html

Exactly mad dog - Venetubo was the online tuning tool I used. It worked very well and I did notice the changes :-)

I will keep the modified FSC.CFG file and reuse it with my new install ;-)

With a Windows 64bit Operating System, my two cents worth is always place FSX on 'DriveLetter:\Program Files (x86)', preferably on another drive obviously!

Placing it in this folder allows the OS to know and optimize a 32bit application. Here is a link explaining it:

http://www.samlogic.net/articles/32-64-bit-windows-folder-x86-syswow64.htm

Hello

To the best of my knowledge this only applies to C:\Program Files(x86) as this folder is given special security measures by Windows 7.

The redirection of calls to SysWow64 will still occur where ever a 32 bit program is installed, the OS knows the bitness of an executable anyway.

Our issue with programs that generate data files and are installed under C:\Program Files(x86) and also installed for "only for me" is that apps will have their Cfg/Data files redirected to C:\Users\username\AppData\Local\VirtualStore\ So other programs that need to read these files will not be able to find them, getting FSX away from C:\Program Files(x86) and installed for "all users" solves this issue.

 

Here is how the Authors of FSCommander explain the situation

 

" For applications installed under C:\Program Files(X86) which generate files for the outside

world (= other applications), Vista and Windows 7 place these file into a virtual store

which other applications may know nothing about. Consequently, the other applications

may look for these files in a specific folder which, however, does not contain the

expected file.

If you install FSX under C:\program files (X86)\ and choose "only for me" instead of "for all

users", then FSX will write the scenery.cfg also into the virtual store instead of C:\ProgramData\Microsoft\FSX\ "

 

Since (older) external programs do not have access to the virtual store, any (older) program which needs to use scenery.cfg to generate a database will also fail. FSCommanders Database tool being one such program. "

 

But as you point out FSX will work fine from D:\program files (X86)\FSX

Question is, and since I do not have a [D:], will it run equally good from, say, an FSX folder directly placed on the Desktop ? Since Desktop has a lot of permitions for the owner then it looks like even better than in say C:\FSX ?

 

And why D:\program files (X86)\FSX instead of simply D:\FSX ?

Hello

Anywhere but C:\Program files(x86)

Although desktop is a bit untidy and quite a long path to point other addons to

Roger! Wilco!

 

BTW: downloading my good old Wilco Airbus Collection for FSX :-)

Would it not be possible to move the flight Simulator X file out of the programs directory and run the F1 registry repair tool?

 

I have FSX installed on a dedicated 180gb SSD . Created a folder on the SSD named "Flight Simulator X" and everything is installed to it. E:\Flight Simulator X, On occasion it is neccessary to point installers to it but that beats the heck out of all that UAC windows defender stuff! Also have P3D on a separate 150g WD Raptor drive. Works excellent.

With a Windows 64bit Operating System, my two cents worth is always place FSX on 'DriveLetter:\Program Files (x86)', preferably on another drive obviously!

Placing it in this folder allows the OS to know and optimize a 32bit application. Here is a link explaining it:

http://www.samlogic....86-syswow64.htm

 

From the link:

 

It is very important that a binary file compiled to a specific bitness (32 or 64) is installed to the correct system folder. Otherwise the program that needs the file will not be able to load the file and will probably not work as expected.

 

Really - why do do all my 32 bit applications in C:\ run with no problems?

Would it not be possible to move the flight Simulator X file out of the programs directory and run the F1 registry repair tool?

 

Isn't that what I said in post #2 ?

 

You could just move the FSX directory and use the free registry path tool available at Flight1, you will then need to reinstall your addons to reflect the new path in the registry

 

the Addons only need reinstalling as some of their paths may be relative to the FSX directory

With a Windows 64bit Operating System, my two cents worth is always place FSX on 'DriveLetter:\Program Files (x86)', preferably on another drive obviously!

Placing it in this folder allows the OS to know and optimize a 32bit application. Here is a link explaining it:

http://www.samlogic....86-syswow64.htm

This does not, however mean that the OS will not know the address of a 32 or a 64-bit program installed outside of those two default folders. As soon as one enters the newly created "D:\FSX" or "E:\MySim" - and hits Enter - the registry is updated - and that's the entry the os uses as a pointer to it's physical address on disk. The OS will read the exe's header and apply whatever memory area restrictions or parameters it needs, dependent upon 32 or 64-bit.

Just as there are endless liberal or conservative viewpoints - there are adherents to Mr. Sexton's "safe" viewpoint, but, while it may be true for Adobe's PhotoShop - FSX has far fewer issues with both operational and addon management when one installs it outside these two folders. We want as much control over a typical development environment as we possibly can, with no intrusion from the operating system, and as soon as we start changing "the Shaders files" or adding on REX, and the other thirty-odd chunks of OrbX scenery, we effectively have a fully-fledged development environment, and as we all experience from time to time - it doesn't always go the way we think it'll go! Windows 7-64 was not written for FSX, nor the other way around - in fact - I reckon we are darned lucky it works at all.

I have never experienced the issues the OP had installing FSX addons in Windows 7 64 bit. I installed FSX/Acceleration to the default folder too but have put many of my addons on another harddrive. The only problems I had was the g3d.dll error and a few BSOD's cus' I didn't setup my memory in the BIOS correctly and did not set my virtual memory to System Managed Size. I do have UAC disabled and I don't use an anti-virus program so maybe that's the solution - NOT! I have never had to run any program as an administrator, even during the installation. I just wanted to mention my successes with FSX and FSX addons and Windows 7, 64 bit as I don't want many to believe FSX won't work properly in the default location. I think everyone should make sure they have at least the MS Visual C++ Redistributable 2005 with SP1 installed. This is the MSV used by FSX/Acceleration to properly install FSX/Acceleration and many of the addons, especially some addons made for FS9 and ported into FSX. MSV 2005 is installed with FSX/Acceleration but SP1 was released after Acceleration and needs to be installed too. You also need Version 1 of Microsoft dotnet framework installed. Some addons, like Orbx, required later versions, but Version 1 is needed for FSX/Acceleration. It should have been installed when you installed FSX/Acceleration. That's my 2 cents worth....

 

Best regards,

Jim