PMDG has an excellent help topic for the DLL.XML on their main website.

 

Reading this thread, it would seem that some folks have either had some bad or incomplete advice in the past, or something.  The Maddog solution of a reinstall for an DLL.XML file (if all the info was there) was really out there.

 

Covering this subject at the basic level, the DLL.XML file basically tells FSX what modules to load, and some of those will show up in the Addon Menu.  When we install SOME new software for FSX, it writes to and makes entries into the existing DLL.XML file (usually it iwll first back up the per-existing DLL.XML file in the same folder.

 

Now, sometimes (can be often depending on what and when you install software), the DLL.XML file becomes corrupted (the format goes to hell) when the newly installed software writes to the DLL.XML file. There is no way to prevent this.  On top of that, some modules (like FSINN and Active Sky Next's AS_Connect) like to be last in the DLL.XML file, so in some cases the format and the order of the listed modules (they load one at a time, top to bottom when FSX is started) is important.

 

What Jim is saying is that the format was likely munched when your software was installed.  It's nothing you did, FSX users have learned to deal with this.  Again, the PMDG website (not the forum on AVSIM) has a really good explanation on how to fix this.

 

As for Simconnect, if one installs FSX Acceleration, it sometimes does not correctly install Simconnect.  Short of that, DLL.XML problems are not typically related to DLL.XML file problems.

 

I've watched Jim's advice for a few years now, and he's an EXPERT. and one who gives of his time freely to help people. Follow his advice to the letter and he'll help you resolve your problem.

 

I sincerely hope I've helped to shed a little light on this subject, and that you find it helpful.

 

Take care.

What did you do to clean out the registry. I'm having trouble getting the Maddog to show up in the addon menu on my 2nd PC. I've tried everything. I even copied my simconnect files from my main PC (where the maddog works) into the winsxs folder on my client PC. All I have on the 2nd PC is FSX, FSUIPC, and the Maddog - no idea what's going on with it. 

 

Hello;

 

I used CCleaner to clear out my registry. Be warned you need to be comfortable with registry entries or you can mess things up in there. (If you're just uninstalling things REVO uninstaller does a good job of highlighting what can deleted safely).

 

When you say copied (simconnect), did you re-run the installer?

 

Also DaveCT (who walked me through my own issues with a ton of patience) mentioned checking out the PMDG site. Please do it!

 

Finally, I have had no issues with the Maddog and vPilot. Good riddance to FSInn and FSCopilot.

PMDG has an excellent help topic for the DLL.XML on their main website.

 

Reading this thread, it would seem that some folks have either had some bad or incomplete advice in the past, or something.  The Maddog solution of a reinstall for an DLL.XML file (if all the info was there) was really out there.

 

Covering this subject at the basic level, the DLL.XML file basically tells FSX what modules to load, and some of those will show up in the Addon Menu.  When we install SOME new software for FSX, it writes to and makes entries into the existing DLL.XML file (usually it iwll first back up the per-existing DLL.XML file in the same folder.

 

Now, sometimes (can be often depending on what and when you install software), the DLL.XML file becomes corrupted (the format goes to hell) when the newly installed software writes to the DLL.XML file. There is no way to prevent this.  On top of that, some modules (like FSINN and Active Sky Next's AS_Connect) like to be last in the DLL.XML file, so in some cases the format and the order of the listed modules (they load one at a time, top to bottom when FSX is started) is important.

 

What Jim is saying is that the format was likely munched when your software was installed.  It's nothing you did, FSX users have learned to deal with this.  Again, the PMDG website (not the forum on AVSIM) has a really good explanation on how to fix this.

 

As for Simconnect, if one installs FSX Acceleration, it sometimes does not correctly install Simconnect.  Short of that, DLL.XML problems are not typically related to DLL.XML file problems.

 

I've watched Jim's advice for a few years now, and he's an EXPERT. and one who gives of his time freely to help people. Follow his advice to the letter and he'll help you resolve your problem.

 

I sincerely hope I've helped to shed a little light on this subject, and that you find it helpful.

 

Take care.

 

I checked the DLL.XML file. It's identical to the one on my main FSX PC - except with only FSUIPC and the Maddog entries (not all of the other addons from the main PC). Here's the full description of my problem: http://forum.simflight.com/topic/77829-addon-menu/

 

 

Hello;

 

I used CCleaner to clear out my registry. Be warned you need to be comfortable with registry entries or you can mess things up in there. (If you're just uninstalling things REVO uninstaller does a good job of highlighting what can deleted safely).

 

When you say copied (simconnect), did you re-run the installer?

 

Also DaveCT (who walked me through my own issues with a ton of patience) mentioned checking out the PMDG site. Please do it!

 

Finally, I have had no issues with the Maddog and vPilot. Good riddance to FSInn and FSCopilot.

 

I ran CCleaner but it didn't fix the issue. First I ran the Simconnect installers. When that didn't work I just copied the actual Simconnect.dll files over. One thing I did notice is I have a lot more C++ 2005 and 2008 Redistributables under Control Panel -> Programs on my main FSX PC than the client. Unfortunately, I keep getting errors when trying to install them on the client PC. I think I may just do a reformat, install windows, install all of the redistributables available, then FSX etc..... Check out the link above for a full description of the problem.

 

Thank you both for the input.

Just taking a stab at this.  Did you completely register the Maddog software?  Are you attempting to run the same  copy/license on different computers at the same time?

 

Not sure if it's germane, but I'm pretty sure the Maddog software doesn't use SimConnect.