DLL.exe

S

smoky942

Members +
When first installing FSUIPC into P3Dv3 it creates a Dll.exe in C:\username\myname\Appdata\Roaming\Lockheed Martin\P3Dv3 which is headed like this...
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>

In C:\Programdata\Lockheed Martin there's another Dll.exe headed like this... in fact, that is all it says.

<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="AceXML" version="3,0" id="dll">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
</SimBase.Document>


Are you supposed to just leave the one in Program data alone...or make entries to it ?

/Russell.
 
As to my understanding it just calls the dll.xml in C:\username\myname\Appdata\Roaming\Lockheed Martin\P3Dv3 .

This is apparent in the lines

<Descr>Launch</Descr>
<Filename>dll.xml</Filename>


These files are not created by default, as you implied, but are created the first time when an application wants a component to be started during the initiation of the simulation.

If you want to manually add other startups to the dll.xml, this is the file that needs to be edited.


HTH,
Mark
 
What about the dll.xml that resides here: C:\ProgramData\Lockheed Martin\Prepar3D v3

Why is there two?
 
dougal95, not sure why the dll.xml file is in Program Data but the date on mine is the day I installed P3D v.3. It could be a template for folks to use in the App Data location. I have no dll.xml file at that location in P3D v2.5. Anyone have more information?
 
Good thinking, Tom. If it is a template, it should be a bare version without any entries and it should stay that way.

Can't check from where I am in the moment, but I'll have a look tonight.


[Edit: the dll.xml in the C:\ProgramData\Lockheed Martin\Prepar3D v3 seems to be a bare template or reference. The active version is in C:\username\myname\Appdata\Roaming\Lockheed Martin\P3Dv3 , as it is supposed to be.

Ahh, and the dll.exe does not exist, I suppose the OP meant dll.xml or exe.xml. If it did it would be a binary file anyhow, nothing to edit there and you would not find it in the locations mentioned.

]

Cheers,
Mark
 
Mark, there are no entries essentially. It is the base entry only. Again it never changes is why I thought it was just a template. Interesting there is and never was a dll.xml file at this location for P3D v2.5 and below on my setup. The entry in this file is below.

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="AceXML" version="3,0" id="dll">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
</SimBase.Document>
 
You're absolutely right Mark...I did mean DLL.XML. No idea why I put .EXE. A senior moment I suppose. Sorry for the confusion.

/Russell.
 
I decided to bite the bullet and read the manual, which at some point is a good thing to do, especially when dealing with the new folder structure of P3D.

The manual says:

--> snip

The priority for how add-on library and executable configuration files differs from content and is initialized as follows:

ProgramData: Configuration files named dll.xml or exe.xml found at: %PROGRAMDATA%\Lockheed Martin\Prepar3D v3
Roaming: Configuration files named dll.xml or exe.xml found at: %APPDATA%\Lockheed Martin\Prepar3D v3

[... locations and priority...]

Local - AppData - %LOCALAPPDATA%\Lockheed Martin\Prepar3D v3 User account specific and system specific.
Roaming - AppData - %APPDATA%\Lockheed Martin\Prepar3D v3 User account specific and system independent.
ProgramData - %PROGRAMDATA%\Lockheed Martin\Prepar3D v3 User account independent and system specific. Default location.


--> snip

Quite logical - and note the priority. E.g. an entry in %APPDATA%Roaming overrides anything found in %PROGRAMDATA% (the way I read it the list of locations is checked bottom up, and the first entry (Local-AppData) has the highest priority). That mimicry is present with all multiple entries in these locations, as well as some cfg files like the scenery.cfg.

So the dll.xml calls libraries, the exe.xml calls executables. Note that dlls are unloaded automatically upon P3D shutdown, executables are expected to handle the shutdown on their own.

By reading the rest of the manual, it occurs to me that I probably structured my installation not the way I should have and I might reinstall my P3D version and follow the LM guide. The problems are older addons that I tricked to work somehow with V3, but now reside in places that are outside the scope described in the manual.

Cheers,
Mark
 
Hi Mark and thanks for that.
When you refer to 'the manual', are you meaning the HTML document, or have I by chance, missed a nice PDF file residing somewhere;-)

roger-wilco-66 said:
I decided to bite the bullet and read the manual, which at some point is a good thing to do, especially when dealing with the new folder structure of P3D.

The manual says:

--> snip

The priority for how add-on library and executable configuration files differs from content and is initialized as follows:

ProgramData: Configuration files named dll.xml or exe.xml found at: %PROGRAMDATA%\Lockheed Martin\Prepar3D v3
Roaming: Configuration files named dll.xml or exe.xml found at: %APPDATA%\Lockheed Martin\Prepar3D v3

[... locations and priority...]

Local - AppData - %LOCALAPPDATA%\Lockheed Martin\Prepar3D v3 User account specific and system specific.
Roaming - AppData - %APPDATA%\Lockheed Martin\Prepar3D v3 User account specific and system independent.
ProgramData - %PROGRAMDATA%\Lockheed Martin\Prepar3D v3 User account independent and system specific. Default location.


--> snip

Quite logical - and note the priority. E.g. an entry in %APPDATA%Roaming overrides anything found in %PROGRAMDATA% (the way I read it the list of locations is checked bottom up, and the first entry (Local-AppData) has the highest priority). That mimicry is present with all multiple entries in these locations, as well as some cfg files like the scenery.cfg.

So the dll.xml calls libraries, the exe.xml calls executable. Note that dlls are unloaded automatically upon P3D shutdown, executables are expected to handle the shutdown on their own.

By reading the rest of the manual, it occurs to me that I probably structured my installation not the way I should have and I might reinstall my P3D version and follow the LM guide. The problems are older addons that I tricked to work somehow with V3, but now reside in places that are outside the scope described in the manual.

Cheers,
Mark
Click to expand...
 
You must log in or register to reply here.
Back
Top