I am testing several FSX addons and have my dll.xml set up for manual loading of each one

 

When I start FSX I get the desired message asking if I want to run the addon? - I reply YES

 

Then I get the desired message that asks if I want to make this a trusted addon? - I reply NO

 

After FSX crashes due to the addon - I find the addon is listed in the [TRUSTED] section of fsx.cfg

 

I then have to delete the multiple lines in [TRUSTED] so I can start FSX without the addon

 

HOW do I prevent fsx from adding the UNTRUSTWORTHY addon to the [TRUSTED] section of fsx.cfg?

 

This problem occurs with some but not all addons. This problem also occurs with older addons that I have used for years with no problem but as a test I setup for manual loading. Some of them get added the [TRUSTED] section if I tell FSX not to add them

 

Any ideas?

I think it is adding them there, and making them as NOT-TRUSTED.

 

Think of [TRUSTED] as being "Trust State" rather than "These are Trusted"

 

See the 1, or 2 or -1 at the end of each entry.

Yes - there is a -1 after each entry that I said not to TRUST

 

BUT

 

each DLL that has a -1 at the end of the line in [TRUSTED] runs automatically the next time I start FSX and, since they are being tested, they cause FSX to crash. The only way I can make them not run is by removing them from the [TRUSTED] section

 

 

<?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>True</Launch.ManualLoad>

<Launch.Addon>

<Name>A2A Feel</Name>

<Disabled>False</Disabled>

<ManualLoad>True</ManualLoad>

<Path>Modules\A2A_Feel.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>AccuFeelMenu</Name>

<Disabled>False</Disabled>

<ManualLoad>True</ManualLoad>

<Path>Modules\AccuFeelMenu.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>A2A Service</Name>

<Disabled>False</Disabled>

<ManualLoad>True</ManualLoad>

<Path>A2A\Shared\A2A_Service.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

</SimBase.Document>

After <Launch.Addon>

 

Change

<Disabled>False</Disabled>

to

<Disabled>TRUE</Disabled>

 

for any you do want to be DISABLED.

 

If you want to Disable them ALL at once, you need only edit the 1st <Disabled>

ie , the one BEFORE <Launch.Addon>

 

 

 

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>True</Launch.ManualLoad>

<Launch.Addon>

I do not want to disable them - I want to selectively run them

 

I want to see the question "Do you want to run xxx.dll?" - I thought that was the purpose of Manual Load

OK .. sorry -- I re-read your original Post.

 

This problem occurs with some but not all addons. This problem also occurs with older addons that I have used for years with no problem but as a test I setup for manual loading. Some of them get added the [TRUSTED] section if I tell FSX not to add them

 

NO IDEA ... I can only assume that those addons were written (incorrectly ?) to not support the MANUAL load functionality of FSX.

 

Do you have a FREEWARE example of one that does not respond to being told to only load manually ?

thumbnails.dll - sometimes I find a value of =-1 at the end and other times I find a =-4 at the end - after I respond no to the trusted question