ottoramsaig wrote on Feb 27
th, 2012 at 9:24pm:
Here is how i got around it, it may work then again maybe not. Windows 7 has FSX permission folders that need to be modified to full control. I am not sure which OP your using but on the search bar type in folders and it should take to the permissions page. WARNING! Doing this will allow you to change the aircraft.cfg. SAVE the original before doing anything.
I've never had to do that, and I think I would remember having done it. A lot has to do with where on you system FSX is installed.
philwhite100 wrote on Feb 28
th, 2012 at 11:54pm:
This gets more confusing all the time. Since i was getting nowhere further i just left things alone and all of a sudden some of the callsigns are working properly with ATC text and voice showing and reading aloud the callsigns.
I am still considering installing a new hard drive in my system and installing windows 7 on it purely for FSX and it's add ons.
When it comes to the installation of FSX when using Vista or Windows 7 (32bit and 64bit):
C:\Program Files\Microsoft Games\Microsoft Flight Simulator X and C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X = BAD
C:\FSX = GOOD
X:\FSX = BEST (
X = any drive other than the C: drive)
This has to do with the way that Vista and Win 7 secure the C: drive.
Especially Program Files and Program Files (x86).
With Vista and Windows 7, it is recommended that you DO NOT install FSX in its default location because of the restrictions by those Operating Systems.
If you have FSX installed in the default location, I think it would be a smart idea to make FSX always run with administrative rights by Right Mouse Click on
fsx.exe (in the FSX root folder) > select properties > Compatibility tab > checkmark
Run this program as an administrator (under Privilege Level) > click OK.
Then you need to make sure that you install
all your FSX 3rd party addons using
Run as administrator (Right Mouse Click on the installer and select Run as administrator from the list).
These things might help you get some things sorted out. I know that it is a real PITA to have to reinstall FSX after having gone through everything to get it where you want it, but the end result would be a lot less headaches. Hopefully the above should make FSX work with less problems.
NOTE: Installing FSX on a drive that is "owned" by you in a previous installation of Vista or Win 7 can end up giving you similar problems (and possibly Win XP, but to a lesser extent). So if, like me, you have other things stored (saved or backed up) on the drive that you install FSX
AFTER you have reinstalled the OS, you will have some problems because of the ownership of the drive. I did. I think if I get rid of everything on my J: drive, reformat it and then reinstall FSX, I would fix some minor issues that every now and then rear their ugly little heads in FSX. Somehow retaking ownership of the drive didn't quite fix it. I'm too lazy to do that right now.
And here is me telling you to do just that above
So now you know why I understand how much of a PITA it is!
Mark
Pages: 
ATC callsign problems (Read 9814 times)
