I bought ORBX KJAC (Jackson Hole) tonight...and when installing it...(to what was a working FSX:MS to that point), at the last of the installation, the installer stopped, and gave me a message that my dll.xml file 'seemed' to be corrupted, and that it could not write the module to a corrupted file. WTH!?!?!?!?

 

It would only write, if I agreed to have the installer program erase, and write a new clean dll.xml...but of course, any modules in the prior one...would be bye-bye...  Yes..yes..I know about cut 'n paste entries...but in some cases...it doesn't seem to work.  I backed up my old one before I let the ORBX KJAC installer wipe the file..and install its single module.

 

I have just spent a better part of three hours rebuilding (for some reason, just cut and pasting did not 'parse' out as a verified x.dll file...and so had to rebuild by reinstalling the stuff that placed modules (what a PITA!) to the file.  I have FSX:MS back up and running...and have placed, and will place a back-up of the most current dll.xml file into a back-up folder that I have created.

 

Now..I have done my share of cut and paste to get a few programs running either in FSX, or P3D..and have had them come up working...but for some reason...when FSX ran..or AS.Next ran, they could not 'verify' (I guess program-speak for successfully reading) the dll.xml file.

 

So...before this might happen to you, right out of the blue...make your backup, as soon as you finish reading this (yes, yes..even if you have had prior success with cut 'n paste from one dll.xml file to another...we all have)...as a 'whew' protection.  If there is any nonsense happening in the writing to the dll.xml (as in installing new software with modules of any kind....Object Flow...etc) you will have the most current back up to overwrite..and get right back to running FSX, and figuring out what happened in that most current install attempt.

 

I would suggest pulling a working copy of the dll.xml file into your new dll.xml back up folder...before you install another and subsequent products.  That way...no bad module writing can bring up the FSX has had a fatal error box..and CTD.

 

Just sayin...

 

 

I bought ORBX KJAC (Jackson Hole) tonight...and when installing it...(to what was a working FSX:MS to that point), at the last of the installation, the installer stopped, and gave me a message that my dll.xml file 'seemed' to be corrupted, and that it could not write the module to a corrupted file. WTH!?!?!?!?

 

It would only write, if I agreed to have the installer program erase, and write a new clean dll.xml...but of course, any modules in the prior one...would be bye-bye...  Yes..yes..I know about cut 'n paste entries...but in some cases...it doesn't seem to work.  I backed up my old one before I let the ORBX KJAC installer wipe the file..and install its single module.

 

I have just spent a better part of three hours rebuilding (for some reason, just cut and pasting did not 'parse' out as a verified x.dll file...and so had to rebuild by reinstalling the stuff that placed modules (what a PITA!) to the file.  I have FSX:MS back up and running...and have placed, and will place a back-up of the most current dll.xml file into a back-up folder that I have created.

 

Now..I have done my share of cut and paste to get a few programs running either in FSX, or P3D..and have had them come up working...but for some reason...when FSX ran..or AS.Next ran, they could not 'verify' (I guess program-speak for successfully reading) the dll.xml file.

 

So...before this might happen to you, right out of the blue...make your backup, as soon as you finish reading this (yes, yes..even if you have had prior success with cut 'n paste from one dll.xml file to another...we all have)...as a 'whew' protection.  If there is any nonsense happening in the writing to the dll.xml (as in installing new software with modules of any kind....Object Flow...etc) you will have the most current back up to overwrite..and get right back to running FSX, and figuring out what happened in that most current install attempt.

 

I would suggest pulling a working copy of the dll.xml file into your new dll.xml back up folder...before you install another and subsequent products.  That way...no bad module writing can bring up the FSX has had a fatal error box..and CTD.

 

Just sayin...

Very good Idea, a similar incident happened to me, but fortunately ASN made a back up for me. 

Also pays to read the warning box a bit more carefully. I does say it will create a new one and all other apps that use dll.xml will not work.

Very good Idea, a similar incident happened to me, but fortunately ASN made a back up for me.

 

Also fsdt  does  a back up of  your ddl.xml , another  way if most of  us  have made a back up copy of  our hard  drive  to a external  for  these types of  issues  that arise

Also pays to read the warning box a bit more carefully. I does say it will create a new one and all other apps that use dll.xml will not work.

Yes...read that...and made a back up...but something had already corrupted...and I had to hand feed...

 

 

Very good Idea, a similar incident happened to me, but fortunately ASN made a back up for me.

 

Yes it does...but only upon update/installation. This happened to me, where no other program backed up.  I only read about this er...corruption, from the end routine of the KJAC install. Before that...the sim was just shut down, from non-problematic use. What I am now doing...as this is the first time in all my years as a flight sim'er...to have a corrupted dll.xml file...is now just before I install any new purchased scenery,...is to drop by my user's/AppData/Roaming/Microsoft/FSX/...and make a copy of the dll.xml file to the folder called Latest working dll.xml file that now resides dormant in the same root folder where the working and, and FSX- read file is.  Good insurance, now that I see that this file can be corrupted by an installation module routine attempt.

Before I install or uninstall anything to FSX I make a folder called FSX BACKUP 5-30-15 (use current date), and in that folder I put a copy of my current:

 

FSX.cfg

EXE.xml

DLL.xml

Scenery.cfg

 

I know a lot of programs can alter anyone of or all of these file when you install or uninstall anything from FSX and keeping a copy of these 4 key files has served me well over the past 7 years of using FSX. Although some programs make backup copies of some of these files, I dont trust any installer/uninstaller to properly back up or rewrite these files and choose to keep the last good working copy myself. Doing so, I have had to only install FSX two times in 7 years and both of those installs were to new computers.

there's a free tool just for that - SIMconfigBackup
http://aviation.pero-online.de/wordpress/?page_id=551

 

 

 

 

there's a free tool just for that - SIMconfigBackup

 

Chris...thank you...thank you...thank you....x300!

 

Just downloaded and created my first back-up..>WOW...just what the Dr. ordered.

 

Here's a virtual beer...heck...here's a 36 pack (enter brand here..)!!!\

 

 

Mitch

Also pays to read the warning box a bit more carefully. I does say it will create a new one and all other apps that use dll.xml will not work.

 

Is that actually the case and all other application will fail?

Chris...thank you...thank you...thank you....x300!

 

Just downloaded and created my first back-up..>WOW...just what the Dr. ordered.

 

Here's a virtual beer...heck...here's a 36 pack (enter brand here..)!!!\

 

 

Mitch

lol 

you’re very welcome Mitch, but I’m just the messenger

all credit goes to the very talented Developer behind this great tool and many other, Peter Rosendhal.

Chris, just downloaded but the AV is throwing up a message that there is an infection on the download.It seems the .EXE is triggering the AV, but not the .ZIP. Anyone else getting that?

Hi Rick,

never heard of this before;

you probably have sensitive AV settings;

by nature the tool opens files and makes copies etc...

it's completely safe; try to loosen up security for the main exe

 

can you run a scan and post the report pls

Hi Chris

 

Thanks for that bit now when I click on the link for the EXE download, I get a 'Problem Loading page ' error  connection re-set. Managed to get the ZIP no problem.

very strange, just downloaded both installer and archive with no issues!

I cleared the cache and tried again and this screenshot is what I got first go, bottom right