Good morning,

 

I am having some major problems that hopefully you can help with.

 

Last night I purchased an addon (Wilco ERJ) and installed it. This morning, I went to fly (Level D was the aircraft of choice). That gave me all kinds of failures. So I started loading my other addons. My 747x, has a dll problem, cant find them according to the error messages, and my MD-11 just causes a fatal error (these have never happened before). The NGX loads fine, as well as the JS4100. I did a re-install of the 747x and it still gives me the .dll error. Any ideas on how I can fix this short of a full re-install of FSX? Thank you.

 

Brian A. Neuman

your FSX folder got infected with "Wilcoitis" :lol:. I would suggest a quick PM to Mr. FSX aka Word Not Allowed.

Good morning,

 

I am having some major problems that hopefully you can help with.

 

Last night I purchased an addon (Wilco ERJ) and installed it. This morning, I went to fly (Level D was the aircraft of choice). That gave me all kinds of failures. So I started loading my other addons. My 747x, has a dll problem, cant find them according to the error messages, and my MD-11 just causes a fatal error (these have never happened before). The NGX loads fine, as well as the JS4100. I did a re-install of the 747x and it still gives me the .dll error. Any ideas on how I can fix this short of a full re-install of FSX? Thank you.

 

Brian A. Neuman

 

Not sure if that's the one, there is at least one Wilco add-on that doesn't correctly edit the "dll.xml" file which lists all add-on dlls FSX should load on startup.

 

The results all sorts of spurious errors which aren't worth troubleshooting.

 

You can recover from it though.

 

Go to C:\Users\your_user_name\AppData\Roaming\Microsoft\FSX\ folder

 

Backup dll.xml file

 

Open it using Notepad.

 

Try removing references for the latest add-on you installed.

 

What you can safely remove is the part between <Launch.Addon> and </Launch.Addon> including these XML tags.

 

Example, to prevent FSX loading FSUIPC.dll, you would delete these

 

 

 

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

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

</Launch.Addon>

 

FSX will then be able to load the other dlls.

That did it Gerald. Thank you very much. I deleted the line on the bottom, so I am assuming the dll wont be available now. However, at the bottom of the file, there was a single letter 'i' that was just there. Could that have caused the problems?

That did it Gerald. Thank you very much. I deleted the line on the bottom, so I am assuming the dll wont be available now. However, at the bottom of the file, there was a single letter 'i' that was just there. Could that have caused the problems?

 

You're welcome.

 

Affirmative. All text should be encompassed between tags. Anything outside the tags delimiters is suspicious.

 

Example: an opening tag such as <Name> will encompass some text which is then validated by a closing tag </Name>

 

The last line in dll.xml should read

 

</SimBase.Document>

 

So maybe if you keep the info that references the Wilco dll, and just delete the suspicious "i", you'll have all your add-ons running fine including the Wilco.

Brian,

 

If this happens again just send the dll.xml to us in a ticket and I'll fix it for you. The Wilco products are notorious for trashing the file.

Thanks Ryan. I will keep that in mind in the future if this happens. Fortunatley, I think I am almost done with addons until the 777 and the revamped 744 come out, and I know your products wont mess up my files.

 

Thank you again for your support.