If you install into the Program Files folders, just don't come back to us when you start having problems accessing various FS files with some older utility programs...

@tgibson. With all due respect these forums used to be a bit more civil. Instead of telling people "don't come back to us with your problems" it would be more helpful if perhaps you explained to

the community what "problems" and or implications you are specifically talking about.

After literally dozens of help requests that I have fielded on this topic, I am simply trying to put it as strongly as possible to avoid future support requests. Sorry if I offended you, but I must make an impression over those posters that say "it works fine for me with everything in the Program Files folder" - it may indeed work just fine for them, but I have had too many people come to me for help, and the only thing that ended up working was to move all of their FS-related files outside of those folders. This can be a painful process, and I will do anything to avoid that for these new users. Many people just don't know how to reset their security options or their folder permissions, or something in their setup just doesn't allow that to work. Thus my emphatic response.

 

Again, I apologize for my strong words, but I just have to make an impression on these people to save them from problems later...

Good advice. If you don't understand windows file security or don't want to get involved install into \FS9 post WinXP. Although there is still a problem with some addons or planes you may come across, they try to write to a protected part of the registry. That's fine with the admin account, but there's no way round it with these other than to "run as admin". These problems originate from the applications not having been programmed for the User account, the programmers and test crew all were admins.

Scott. Do you think it might be helpful to tell everyone exactly what the Win 7 method is? I don't recall doing anything different on Win7 when installing FSX.

 

I wrote a large post in the Windows 7 form on getting everything to work properly in W7. Yes my post was mainly concerning migrating your add-ins but I have no problem stating that is the proper 'W7 Install Methode'.

 

Like what was already stated here DO NOT install in any of the Program Files folders. This can cause problems with certain add-ons, scenery, and utilities. I'm not going to dig through a list just take my word for it. As far as W8 I can offer no support on that OS and wouldn't use it unless I had a touch screen. For what we need an OS for it's 7 featured are almost identical. Now if you get FS9/FSX installed in W8 and find the touchscreen works flawless in VZ's 8 is hands down worth a look. Even the 2D guys could find a meaningful use for this feature. W7 offers TS support but W8 the whole OS is built around this technology.

 

Again read my install write up in the W7 forum and many of your questions will be answered.

 

Above Sent from my iPhone with spelling errors. Anyone know why I can't edit posts on my iPhone?

Anyone know why I can't edit posts on my iPhone?

It's Apple. Go figure. ^_^

For some reason my thread is no longer pinned but search for this title and you'll find it, "Migrating FS9 from XP 32Bit to Windows 7 64Bit".

Here's two pence worth for ya. I've installed every FS Version I've ever owned to default C:\Program Files/Program Files (X86) of the Windows XYZ 32 or 64 Bit OS.

To date I have NEVER had an OS/FS Issue present itself. The OS and the FS makers are one and the same. B)

Here's two pence worth for ya. I've installed every FS Version I've ever owned to default C:\Program Files/Program Files (X86) of the Windows XYZ 32 or 64 Bit OS.

To date I have NEVER had an OS/FS Issue present itself. The OS and the FS makers are one and the same. B)

 

Wow... I'm sure your not using every add-on combination out there. To play it safe it's best first not to have FS on the same drive as your OS and second not to install it in either W7 'Program Files' folder. During my first go around with migration I had to uninstall FS9 and re-install it after a conflict arose with a few add-ons. It's been so long I don't remember which ones. Again play it safe to be sure.

If it works for you and others then fine. Just saying that Program Files/Program Files(X86) ain't the culprit folks. B)

Just saying that Program Files/Program Files(X86) ain't the culprit folks. B)

 

Helo Ron

It is not just about the OS and FSX though, installing to Program Files(X86) creates problems for other addons such as FSCommander unless UAC is turned off and the application installed as adminisrator and always run as administrator.

 

 

From the FSCommander installation PDF

 

"For applications installed under C:\Program Files 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. "

 

Note, other applications in this instance means Pre Vista /W7

 

PMDG also advise installing FSX outside of Program Files (X86)

Correct, we wrote similar warnings ourselves at early FSX and the transition from XP/Vista/Win 7 and assume that folks understand that they rmust retake control of their OS. B)

This ain't a food fight, it's that blanket statments, whether mine or others. need to be considered.

Here's two pence worth for ya. I've installed every FS Version I've ever owned to default C:\Program Files/Program Files (X86) of the Windows XYZ 32 or 64 Bit OS.

To date I have NEVER had an OS/FS Issue present itself. The OS and the FS makers are one and the same. B)

 

I agree with Ron.I have everything installed in default (x86) folder. Haven't had problem with any install to date. But some folks aren't willing to learn how to take control of their OS. So the work around is to install some place else.

Precisely why MS created the Program Files/Program Files (X86) in the first place.....

Anyway, folks are going to do what they want. This was an attempt to provide "another side of the coin" viewpoint. :rolleyes:

And I'll let you take the support posts of the people that follow that advice...