I know we shouldn't download FSX into the Program (x86 ) file or the Program file, but what about an add on like Ezdoc or Rex?

That would be fine.

Rexe devs strongly advise users to install outside of  the default location being the (86)

Make a folder on c: drive for REX - ezdok no problem

The reason this gets done for FSX is because it's an old application that isn't "aware" of all the UAC protections and conventions that are used in the newer versions of Windows. As long as a program is newer and properly accounts for those things, it shouldn't have any trouble there.

Personally though, just to avoid any chance of problems I install everything like REX, Opus, PFPX etc to a D:\FSStuff folder where I know nothing can interfere with them.

Personally though, just to avoid any chance of problems I install everything like REX, Opus, PFPX etc to a D:\FSStuff folder where I know nothing can interfere with them.

Amen to that Ryan!

Personally though, just to avoid any chance of problems I install everything like REX, Opus, PFPX etc to a D:\FSStuff folder where I know nothing can interfere with them.

Ryan, that is an excellent rationale. Personally, I do it more for the sake of "organization" than anything else. If FSX is in it's own folder and perhaps even on its own hard drive, why not install everything else on the same drive or set of folders? B)

I've had FAR FAR few problems since ALL my FS software is installed to another drive.

When I bought my new PC the vendor pre installed it for me on a solid state  drive reserved only for FSX.

 

however the path is

 

E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X

 

I also have a C:\Program Files (x86)

 

Does this cause the same difficulties that sometimes occur, or does windows not recognise any special consideration of Program Files (x86) that's on the  E drive?

 

UAC is turned off,  and don't have any particular problems over the last 9 months?

 

However just noted both Air Hauler   and Saitek  have installed  to  C:\Program Files (x86)

 

Any issues anyone thinks I should be aware of?

 

Cheers

Steve

Ryan, that is an excellent rationale. Personally, I do it more for the sake of "organization" than anything else. If FSX is in it's own folder and perhaps even on its own hard drive, why not install everything else on the same drive or set of folders? B)

 

 

Ryan's way makes it easier to exclude all your FSX related stuff from your AV scans.

 

My mistake was to create separate folders like c:\REX, c:\ASE, c:\RC43 - took me a while to exclude them all from my AV ...

Well, actually FSX is properly written with respect to UAC, but in fact it is the way older addons have expected program folders to be writeable that have caused the issues, and that's not FSX's fault. Any changes to Program files folders should be done by the installer under Admin privileges.

Any changes to Program files folders should be done by the installer under Admin privileges.

That's precisely the reason I write all my installers to force admin priveleges prior to beginning the file extraction and placement.

That's precisely the reason I write all my installers to force admin priveleges prior to beginning the file extraction and placement.

Yes good practice. The installer could also check itself for tampering prior to restarting with admin rights to be properly secure, and would refuse to run in admin mode if it detected tampering.