Well, that much is evident from your "poo-pooing" of many folks who are in fact "FS experts..." You represent at most a sample of 15, and most certainly cannot conclude from such a small sample to predict your "good experience" to encompass the universe of FS users, and plethora of hardware and operating system combinations.

 

Over the past twenty odd years I have helped literally hundreds of folks with FS problems, many of which have been solved by simply following the advice given to not use the "default folder" for FS. This has been especially true since the advent of Vista and has continued through into Win8.

 

The odds of having access problems only increase as one adds more and more advanced aircraft to their collection.

 

I have everything installed in the x86 folder and no crashes. It's called taking control of your OS instead of looking for a work around. I'm surprised as a developer your instructing folks to a work around instead of telling them how to install in win 7 default location. But you do what you want but don't decieve people by saying FSX won't work if you install in default location.

Lol, chill out guys, I stated clearly I'm not an FSX expert, even adding "not by a long shot" and was merely sharing my own experiences so far, with a bit of tongue in cheek humour...

 

Geeze...

 

I may not be an FSXpert, but I do know windows, and just like you, I have helped thousands of people in the last 20 years with all versions, and a crazy array of differing applications, so I know from experience what screws your OS and what doesn't... Just like FSX, a badly written app/add-on will cause you mayhem, or in the case of Vista, the OS will present certain challenges that will drive you nuts, but not so with Win7..

 

Even something simple like choosing the wrong security software can present you with never ending headaches in everything your computer does.

 

Are we not all here to share experience, and share a laugh once in a while....

Back to the scheduled program...

Bill (Bigmack), why do you think he 'deceives' folks? He was expressing that a lot the support items arise from picking that default location. Or, the other way around, could be solved by choosing another one.

 

So that's a statement which can't be right or wrong but clearly refers to his experience. And Rob from Realair doubles that impression. If there are folks around happily running with the default folder, even better. I also think that it may be easier to explain how to pick another folder instead of teaching folks how to make use of elevated user rights and stuff.

 

In general, your preference to solve things instead of working around them is correct though.

 

Since FSX develops some trouble with other Win7 and later character traits too, maybe it forms up an exception among 'modern' programs. So if we imagine a new user of FSX choosing the default folder, getting limited by the Win UAC and later DEP plus the trouble with the uiautomationcore.dll, we may first of all notice that FSX grew old.

 

To make it workable and stable, it may indeed need a few tips. The one on the C:\program files avoidance looks good to me. :smile:

There are basically two kinds of CTDs. One has a defined cause and a well-known fix that works. The other is totally random. The first is easy to deal with. With the second, nothing you do has any permanent effect.

 

While some change will seem to work for a flight or two, the crash frequency doesn't actually change. This leads to any number of voodoo solutions. If something seems to work as much as 53% of the time, it becomes a mandatory change. Research the problem a year later and people are saying that the mandatory change is what is causing the problems.

 

Work with someone for a few days or weeks, get reports that something works, then a couple of days later that they still have the problem, and you try something else. Eventually the person doesn't come back and you think you've solved the problem, but it's likely because he gave up and either quit using FSX or resolved himself to dealing with the crashes. I gave up and used to save my flights every half hour.

 

On my old computer, after installing SP2, FSX crashed about every third flight. On my new computer, FSX crashed about every third flight. When I got into the Microsoft Flight beta, Flight crashed about every third flight. I kept reporting these crashes, it was suspected that my computer was unstable, but eventually I was given a new loader program and the crashes mostly went away. I wasn't told what was changed. Did the new program actually fix my problem, or did it just shift it to somewhere that had less visible effect?

 

My best guess is that the random crashes are related to the order in which various programs load, or at least the order in which memory is allocated for them. Unfortunately, this is something we can't easily examine or control.

 

One thing I've noticed is that the crashes would seem to get less and less frequent, then after a Windows update they'd be back in full force. I stopped having crashes (at least during flights) in mid November. Right now I've got a notification that there are Windows updates available. I'm ignoring it. We'll see what happens.

 

Hook

I have had a few successful flights today which is good.

Just in case one thinks that we forgot about the OP. ^_^ Good news!

I left an 13 hour flight from WSSS-EGLL on overnight and FSX kept running

 

I'm going to try enabling REX to see if that works now fingers crossed!!.

I have everything installed in the x86 folder and no crashes. It's called taking control of your OS instead of looking for a work around. I'm surprised as a developer your instructing folks to a work around instead of telling them how to install in win 7 default location. But you do what you want but don't decieve people by saying FSX won't work if you install in default location.

Most folks are simply not knowledgable enough to "take control of (their) OS." Since there is a simple and totally achievable solution to >90% of the potential problems, why not advise taking those simple steps?

 

Instead of strolling down the middle of the railroad tracks every day on the way to work and hoping that a train never runs you down, why not simply walk on the bikepath that parallels the tracks?

 

That's not "deception" at all; it's called expediency...

 

On another note, since many of the utility programs that MS/ACES provided for developers to use are command prompt shell programs, not having to type in that rediculously L O N G path fifty times or more every day is a true blessing... :yahoo:

Never ever install your FSX stuff in C:\Program Files (x86) on a windows 7 and above computer........

I did and my FSX is working fine. I have never gotten any permission errors.

Most folks are simply not knowledgable enough to "take control of (their) OS." Since there is a simple and totally achievable solution to >90% of the potential problems, why not advise taking those simple steps?

 

Instead of strolling down the middle of the railroad tracks every day on the way to work and hoping that a train never runs you down, why not simply walk on the bikepath that parallels the tracks?

 

Knowledge and learning. The key to most acheivable things. Once you get clipped by that train a few times by walking down those tracks, you'll learned to move when the whistle blows. :lol:

Knowledge and learning. The key to most acheivable things. Once you get clipped by that train a few times by walking down those tracks, you'll learned to move when the whistle blows. :lol:

But you do what you want but don't decieve people by saying FSX won't work if you install in default location.

I forgot in my earlier reply to address this last sentence from your reply...

 

I have never once stated any such thing. I've only advised that there is a potential for problems arising at some future time. One guaranteed way to avoid such problems from ever being manifest is to use a simple path for FS installation that lies outside the protected areas.

 

Keep in mind also that the core of FS's program code remains mostly in the pre-windows domain, and ACES had to take some rather novel approaches to move as much as possible to non-protected paths in the USER folder structure. As a result, we now have the case of files being scattered all over the system's folders, rather than all being in one logical and centrally accessible location.

 

How many folks have fruitlessly tried to edit the cameras.cfg file located in the ..\FSX root folder, only to later discover that the real, working file is to be found here:

x:\Users\UserName\AppData\Roaming\Microsoft\FSX... only if their OS is Win7 that is...

 

I did and my FSX is working fine. I have never gotten any permission errors.

 

I have driven right through red lights a time or two. Does that mean its an ok thing to do or was I lucky? :-)

Hi all,

 

I've just run a 6 hr flight with by REX add-on running, so seems to be working well