fsuipc 5 install problem

[niokilt]

hello pete,

 

here is a the report after intsall:

 

Installer for FSUIPC5.DLL version 5.15

Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=C:\Program Files\Lockheed Martin\Prepar3D v4\
===========================================================

INSTALLATION FOR Prepar3D v4:
AppPath="C:\Program Files\Lockheed Martin\Prepar3D v4\"
Checking version of the Prepar3D v4 EXE:
... Version 4.4.16.27077  (Need at least 4.1.0.0)
Checking if there's already a version of FSUIPC5 installed as:
       C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL
... Version 5.150 found.
C:\Program Files\Lockheed Martin\Prepar3D v4\Modules folder already exists.
Okay -- installed FSUIPC5 into "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\nico\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\nico\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\nico\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC5 section.
No previous FSUIPC5 entry found, so adding it now ...
Cannot edit the DLL.XML file to activate FSUIPC.

It is a new installation of p3d in a new computer with windows 10. I run the installer after running once p3d.

Could you help mùe with this issue?

 

thanks

 

 

I have fixed the problem, just remove the DLL.XML annd reload the intsll programm..

[Pete Dowson]

17 hours ago, niokilt said:

I have fixed the problem, just remove the DLL.XML annd reload the intsll programm..

But with a new install of P3D on a new PC, there shouldn't have been a DLL.XML.  Whatever was there in that name was evidently a corrupted file in any case.

Anyway, glad you fixed it. Otherwise I'd have asked to see the file.

Pete