Jump to content
The simFlight Network Forums

tkellogg

Members
  • Posts

    6
  • Joined

  • Last visited

About tkellogg

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://www.creativesimulations.com

Profile Information

  • Location
    Snellville, Georgia
  • Interests
    Flying, sim building, skiiing, granddaugter

tkellogg's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I do not understand why you think I haven't referred to the installation manual. If I hadn't, I would not have known where to check on whether FSUIPC had successfully loaded in FSX. My problem was I was focusing on problems with the network. I spent hours working on this and even upgraded all of my computers from Vista and XP to Windows 7 and still had the problem. I was planning on updating anyway so now it is done. I then reread the installation guide as I was having problems locating the MSFS X modules folder. However, initially I was more focused on the problem being my network. I had problems finding the MSFS X module folder because it was not in the program files in Windows 7. I finally located the MSFS X folder under program files (x86). From here it was easy to find the FSUIPC documents folder where I found the FSUIPC User's guide where I easily found the solution to my problem. In your manual you write; For Windows Vista and Windows 7 If you have installed FSX or ESP in its default folder (or any folder within "Program Files" or "Program Files x86)", then Windows will be protecting the folders against normal user access. This applies even if you are the PC's administrator. The best and cleanest way out of this would have been never to allow FS to install into Program Files in the first place. Instead some nice easy folder like C:\FSX would be better, much better. However, assuming it is too late now, what can you do? First off, to be sure you can actually manipulate the real files in the FS folders, run Windows Explorer "as administrator". That means right clicking on it or its shortcut and selecting "run as administrator". That gives it elevated administrator privileges. Once I saw this I opened under administrator and my problem was solved. I would like to make a suggestion that may help future Users. Include this language in the installation guide in addition to the User's guide. God knows it would have saved me a lot of time and frustration. Thanks for all of the help.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.