Jump to content
The simFlight Network Forums

Cannot install FSUIPC4 into FSX:SE


Recommended Posts

Hi!

 

I have downloaded the latest FSUIPC4 that should work in FSX:SE but when I try to install it it says that cannot edit FSX DLL.XML file to active FSUIPC. I have run FSX:SE before running the FSUIPC installer.

 

 

Intaller says:

 

Installer for FSUIPC4.DLL version 4.938f
 
Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX
Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... >>>  OK! FOUND FSX-SE!  <<< ...
     AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\
Looking in registry for Prepar3D install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...
===========================================================
 
INSTALLATION FOR FSX:
SetupPath="C:\Program Files (x86)\Steam\steamapps\common\FSX"
Checking version of the FSX EXE:
... Version 10.0.62608.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62608 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.938f found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Lauri\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Lauri\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Cannot edit the DLL.XML file to activate FSUIPC.
 
Greetings from Finland
 
Lauri Aho
Link to comment
Share on other sites

Can you find the FSX.CFG file, please? It should be in 

 

C:\Users\Lauri\AppData\Roaming\Microsoft\FSX

 

or, just possibly

 

C:\Users\All Users\AppData\Roaming\Microsoft\FSX

 

However, the installer found it in neither place.

 

It is just possible that DoveTail have changed the installation method since build 632608 was released, but it worked fine here with the same paths as FSX. In fact I thought that was the main idea -- to make it look like FSX so most installers would work fine. As you see from FSUIPC's install log, it is treating it just like FSX.

 

Maybe they are now using "DoveTailGames" or "Steam" instead of "Microsoft"?

 

Let me know, please. If they have changed it I can deal with it with a new installer version, but it would be rather annoying for them to have done this.

 

Regards

Pete

Link to comment
Share on other sites

With a side-by-side installation (i.e. where you have both a DVD and Steam version installed) then the paths become "FSX - SE" for the Steam Edition installation.

 

So, as I have both, I have two paths:

 

c:\users\username\AppData\Roaming\Microsoft\FSX : DVD version

 

c:\users\username\AppData\Roaming\Microsoft\FSX - SE : Steam Edition.

 

Apparently there have been instances where it has thought that FSX was installed (e.g. a previous installation that has not been fully removed) and it has installed the "FSX - SE" paths, even though the equivalent "FSX" ones don't exist.

 

Hope that helps.

 

Ian P.

Link to comment
Share on other sites

With a side-by-side installation (i.e. where you have both a DVD and Steam version installed) then the paths become "FSX - SE" for the Steam Edition installation.

 

So, as I have both, I have two paths:

 

c:\users\username\AppData\Roaming\Microsoft\FSX : DVD version

 

c:\users\username\AppData\Roaming\Microsoft\FSX - SE : Steam Edition.

 

Yes, the current FSUIPC4 installer does cope with that.

 

 

 

Apparently there have been instances where it has thought that FSX was installed (e.g. a previous installation that has not been fully removed) and it has installed the "FSX - SE" paths, even though the equivalent "FSX" ones don't exist.

 

Yes, but then the registered path to the FSX.EXE would be as for a parallel FSX-SE, and the Installer would class it as FSX-SE, but in this user's case the path is in the usual FSX registry entry.

 

Puzzling. Until the user finds the CFG file I won't know what is happening here.

 

Pete

Link to comment
Share on other sites

I have both the boxed and steam version. After I had installed FSX:SE I uninstalled the boxed version and manually deleted FSX file (there was my boxed version`s FSX.CFG file) 

 

c:\users\username\AppData\Roaming\Microsoft\FSX

 

I had installed FSX:SE so my new FSX_SE.CFG file for FSX:SE is located 

 

c:\users\username\AppData\Roaming\Microsoft\FSX - SE

 

There is no CFG file named FSX.CFG since I uninstalled the boxed version. 

Link to comment
Share on other sites

I have both the boxed and steam version. After I had installed FSX:SE I uninstalled the boxed version and manually deleted FSX file (there was my boxed version`s FSX.CFG file)  

 

Well, the uninstall action failed to remove the Registry entries for FSX. Your registry is now in a bit of a mess as it includes entries for both FSX and FSX-SE, but both pointing to FSX-SE..

 

I think that either you have not shown me the whole installer log, or you aborted the install when you got the error for FSX! You should have let it carry on. It is only failing on the FSX part, not on the FSX-SE part!

 

Your registry still contains the entry for FSX, which now points to FSX-SE, thus:

 

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=C:\Program Files (x86)\Steam\steamapps\common\FSX
 
and it also contains the pointer for FSX-SE:
 
Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... >>>  OK! FOUND FSX-SE!  <<< ...
     AppPath=C:\Program Files (x86)\Steam\steamapps\common\FSX\

 

If you had let the Installer continue it would have worked fine. You are aborting after it says it can't edit the DLL.XML for FSX, NOT for FSX-SE! Why do you care about FSX if you have deleted it?

 

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.