Jump to content
The simFlight Network Forums
Sign in to follow this  

Recommended Posts

Hi!

Sorry to be a bother but I'm having one hell of a time getting FSUIPC installed in my FSX Steam Edition. I've installed it fine on a previous install, which I had to kill because of scenery issues.
Specifically the issue I'm having is the installer runs fine, picks up the correct directory, looks like it's installing just fine.. but doesn't.
Here's my install log, I've not gone through it very thoroughly, but there doesn't seem to be anything major wrong.
 

Installer for FSUIPC4.DLL version 4.944a


Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************


Looking in registry for Prepar3D v1 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! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="D:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (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:
       D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.944a found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Jim\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default.migrated\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Jim\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path: 
... found as "C:\Users\Jim\AppData\Roaming"
Now finding \Microsoft\FSX-SE\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\Default.migrated\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Jim\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path: 
... found as "C:\Users\Jim\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\Default.migrated\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Jim\AppData\Roaming"
Found FSX.CFG in "C:\Users\Jim\AppData\Roaming\Microsoft\FSX\FSX.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay

Now the most interesting thing I think is I don't actually have the FSX\Modules folder. Which has me slightly worried I'm going to need to download another 10gigs.

I should probably mention that FSUIPC is not the only installer doing this same thing, the FTX scenery, some freeware planes and Captainsim's Xload all have the same issue worryingly.

I've tried to remember all of the saga that this is turning into, but if I remember something more I'll definitely edit it in.

Share this post


Link to post
Share on other sites

Specifically the issue I'm having is the installer runs fine, picks up the correct directory, looks like it's installing just fine.. but doesn't.

Here's my install log, I've not gone through it very thoroughly, but there doesn't seem to be anything major wrong.

 

That looks perfect. Nothing wrong at all. Why do you think it isn't istalled correctly?

 

Now the most interesting thing I think is I don't actually have the FSX\Modules folder.

 

Yes, you do have that folder. Where are you looking?  See this line:

 

Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"

 

and of course all of the documentation is in the subforlder, thus:

 

Now installing additional files into the "Modules\FSUIPC Documents" folder:

 

 Which has me slightly worried I'm going to need to download another 10gigs.

 

Where does 10gigs come into it? the Modules folder is created by FSUIPC's installer. It isn't part of the default FSX or FSX-SE.

 

I should probably mention that FSUIPC is not the only installer doing this same thing, the FTX scenery, some freeware planes and Captainsim's Xload all have the same issue worryingly.

 

You need to explain what this "issue" actually is. You haven't so far!

 

Pete

Share this post


Link to post
Share on other sites

Oh, I'm so sorry. I had to type it out twice, my firefox crashed, couldn't remember exactly what I'd put in there or not. I've been faffing around with this for days, I'm just so lost in it all now.

Okies, take two.. xD
So.. there aren't any files in my FSX directory that have anything to do with FSUIPC. Also I'm not getting the drop down in the addons & my VRS Superbug installer is agreeing that FSUIPC isn't installed. Everything is targeting the correct directory being D:\Steam\steamapps\common\FSX
I've also not yet had the popup upon launching FSX asking if I want to allow the .dll files & so forth.

The modules folder isn't showing in my explorer at least. All folders are most definitely unhidden, so why would the installer say it's there? & I'm definitely not being blind because even the search yields no ressults for modules. It's almost like it's being cleaned up by an anti virus sweep before it hits the hard drive, but I've made sure that comodo is not taking action against the installer.

http://i.imgur.com/Qfuncu4.png

The ten gigs I was refering to was a redownload of FSX if that might be necessary. 10 gigs at 2 mbps is ten hours at best. I didn't realize that the modules was something added by FSUIPC & not there by default, everyone I know has managed to get FSUIPC working fine, so they have the folder of course.

So all in all, the installer seems to be claiming to install things correctly, but doesn't seem to be placing them. & it's not the only one doing it. I've run several registry clean ups with several different programs, including the ones specifically for FSX, it's not yet made any difference. Registry issues tend to follow me around, so I know my way around these cleaner programs. I'm fairly confident that it's not a registry problem. I mean if it is, it's a bloody deep one.

Sorry for not being clearer in the first place.

Edited by Jim Williams

Share this post


Link to post
Share on other sites

So.. there aren't any files in my FSX directory that have anything to do with FSUIPC.

 

You cannot be looking in the right place, then. Please see my previous email for the full path.

 

Also I'm not getting the drop down in the addons

 

Possibly your DLL.XML file is corrupted.  There are some installers around which make a mess of that.

 

The modules folder isn't showing in my explorer at least. All folders are most definitely unhidden, so why would the installer say it's there? & I'm definitely not being blind because even the search yields no ressults for modules.

http://i.imgur.com/Qfuncu4.png

 

That picture also shows a "missions" folder. I have no "missions" folder for FSX-SE. How did that get there?

 

 everyone I know has managed to get FSUIPC working fine, so they have the folder of course.

 

The folder absolutely MUST be there, this section alone is proof:

 

Checking if there's already a version of FSUIPC4 installed in:

D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL

... Version 4.944a found.

FSX-SE Modules folder already exists.

 

You simply MUST be looking in the wrong place!

 

Pete

Share this post


Link to post
Share on other sites

Steam installs & launches things from a very specific place, & I've only got one install of FSX. Even running a search of every single hard drive that exists on this computer doesn't show anything for FSUIPC bar the .exe & .zip archives. So that suggest I have major issues, but FSX is the only thing effected.

I obviously have no idea how to explain it. I'll try uninstalling & running registry cleaners & letting the computer download through the night again but idk if that's going to solve anything.


 

Share this post


Link to post
Share on other sites

Steam installs & launches things from a very specific place, & I've only got one install of FSX. Even running a search of every single hard drive that exists on this computer doesn't show anything for FSUIPC bar the .exe & .zip archives. So that suggest I have major issues, but FSX is the only thing effected.

I obviously have no idea how to explain it. I'll try uninstalling & running registry cleaners & letting the computer download through the night again but idk if that's going to solve anything.

 

Well I can't imagine why the folder is hiding from you, but honestly there's no way the installer could find the existing copy of the DLL in the folder in which it should reside unless it is really there.

 

You do know there's a "repair" optionin the FSX-SE options. Right click on FSX-SE on the left in Steam, and check the drop down options offered. Not sure what it does, but I doubt you'd need a full re-install.

 

Also you could try actually CREATING the Modules folder in your Steam FSX folder. If it refuses then you'll know there's one there.

 

When you run FSX do you use the Steam window to select it?  What happens if you go to the D:\Steam\SteamApps\Commom\FSX folder and double-click the FSX-EXE file there? Does it load?

 

Also, check your DLL.XML file, found here:

 

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

 

Despite the name it can be viewed as a normal text file. In case it is corrupt, so stopping FSUIPC4 loading, try renaming it or saving it elsewhere, and re-running the FSUIPC4 installer. It will create a fresh one. If this gets you an Add-Ons menu entry, then the original DLL.XML was bad. You could paste it into a message here for checking if you wish.

 

Pete

Share this post


Link to post
Share on other sites

Found my issue.

 

The modules folder isn't showing in my explorer at least. All folders are most definitely unhidden, so why would the installer say it's there? & I'm definitely not being blind because even the search yields no ressults for modules. It's almost like it's being cleaned up by an anti virus sweep before it hits the hard drive, but I've made sure that comodo is not taking action against the installer.

I did some more digging & it turns out Comodo was indeed sandboxing it. I felt lucky & decided I'd test the installer with Comodo still active, then again with the process terminated. It worked.
I don't know where the files ended up or why none of it even showed on a complete search of the entire computer... but it must have been the sandbox. Even though I specifically told Comodo to trust all of these installers, I find it far too much of a coincidence that the second I completely shut Comodo down, things all start installing correctly. But it does seem odd that it has only been sandboxing Flight Sim stuff.

But it's definitely all worked, I'm getting the addons drop down, the VRS installer has detected it & the modules folder is now in the FSX Directory. Hopefully someone else has had this same issue & finds all of this of use.

Thanks for the quick responding, Pete.

Edited by Jim Williams

Share this post


Link to post
Share on other sites

I did some more digging & it turns out Comodo was indeed sandboxing it

 

Hmm. I've never heard of "Comodo" or "sandboxing" I'm afraid. Some sort of "stop the user doing what he wants" program?

 

I don't know where the files ended up or why none of it even showed on a complete search of the entire computer... but it must have been the sandbox.

 

Well, the Installer program actually found the files where it knew they should be, as this shows:

 

Checking if there's already a version of FSUIPC4 installed in:

D:\Steam\steamapps\common\FSX\

Modules\FSUIPC4.DLL

... 

Version 4.944a found.

FSX-SE Modules folder already exists.

 

So it seems all this "sandboxing" does is prevent YOU seeing them, but other programs can? Strange.

 

 

But it's definitely all worked, I'm getting the addons drop down, the VRS installer has detected it & the modules folder is now in the FSX Directory. Hopefully someone else has had this same issue & finds all of this of use.

 

 

Yes, thanks for getting back with the answer. Glad it is resolved.

 

Pete

Share this post


Link to post
Share on other sites

Comodo is a Firewall package, Pete.

What a lot of security software does now, rather than just blacklisting software that it doesn't recognise, is runs it in a "sandbox", where you can execute the application (e.g. an installer) to, basically, a virtual machine - it "extracts" it to a temporary store, rather than allowing it to write to the live Windows file system, Registry, etc. During this process it scans for "undesirable activity" and if it doesn't find any, it usually offers the user a choice to run the application 'properly'.

 

Norton and Symantec both do it, as well, now. Like with all the hysterical, sorry, "heuristic", detections, I've never heard of one actually catching a piece of zero-day malware, but no-one has come up with a better method yet! To be honest, sandboxing is  lot better than just blacklisting.

 

Ian P.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • 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.