It was an error for me to install E-jets V2, onto my hard drive this past weekend for many reasons, but one inparticular.After installing E jets, and removing it, I had problems with FSX and I seriously contemplated rebuilding FSX files ( including a complete re install of add-ons etc) , I simply learned how to redo the DLL files. By the way i found out how to do that in the PMDG support wiki.But trust me, you do not want to have to do this. And I did have to end up reintalling PMDG planes only. This is by no means a bash of wilco - its purely for your protection !Cheers

Long standing problem - we've asked them numerous times to stop doing it and they never have. They change all the hidden newline characters in the file from the Windows formatting to the Unix/Linux formating - absolutely no idea why they do this, but that's what causes the problem.It's actually fairly easy to fix if you have a good text editor like UltraEdit.If anyone has this issue, just send me the dll.xml file via a support ticket and I'll fix it for you - no need to delete it and reinstall addons.

I installed the EMB and it wiped out my gates in KORD FSDT scenery. I finally figured out what it was and it sounds something like Ryan is talking about.Jack C

What saved my tail was that I happened to find a old copy of the DLL file that somehow managed to get backed up.

Could you guys be more specific as to what is happening and why and give examples or screen shots. I have the EMB V2 and have no problems, or at least none that I know of. I have some odd behavior of FSX from time to time but do not know if they are related to what you are talking about. What DLL files are being messed up? I'd definitely like to check my own files and see if anything is not as it should be. Any info would be appreciated. Michel.

I had installed my E-Jets, E-Jets v2 and Embraer Regional Jets without any problems. It did not change anything, and everything works as it did before. Regards

I am not aware of this issue, could someone please elaborate?I used to recommend the Erjs from them for a while but the more I fly them the more I feel they are utter crap.

One should always (that is always) backup your DLL.XML file before installing new addons for FSX. Anyone of them can potentially make changes to that file which is the achilles heel of FSX, stuff that and you stuff the whole shooting match!What some of the Wilco's do is add their entries to DLL.XML in a non-standard fashion. What you see when you open the file in Notepad is one long continuous line of entries rather than a sequence of short one-line entries. Doing that can stuff up other addons, there are several that will fail afterwards. It's possible to fix it if you know the layout of a correct DLL.XML file (hence the backup?!). Some addons insist that the entries in that file are in a specific order (i.e. this loads before that) but most will certainly expect the standard format which can be mucked up by some Wilcos. There is a sticky on this somewhere since PMDG spotted the problem some years ago.

Here's the technical answer on exactly what Wilco's installers do to the file:There's invisible formatting characters that make up what's called a "newline" in a text file. In Windows and a couple of other OSes, the newline sequence is "CR LF" - those stand for "carriage return" and "line feed" - they're terms that originated with mechanical typewriters. In Unix or Linux based OSes though, the standard is just an LF character. This is what Wilco/FeelThere is doing - they're stripping the CR characters out of the file and making it the *nix format with just LF. Notepad can't read Unix style newline formating, so you'll see just a string of text with no line breaks when you open one of these corrupted files with it.If you download a copy of Notepad++ here (which can read Unix text files), you can actually see these characters and fix them:http://notepad-plus-plus.org/downloadIn the program, go to View/Show Symbols/Show End of Line. You'll now see a bunch of boxed CR and LF characters at the end of each line in a good dll.xml file. If you see just LFs, the file's been corrupted.To fix the LFs, you can do one of two things:1. Go through manually, position the cursor before each LF and then press Ctrl+M, which inserts a Windows newline (CR LF)2. The much easier method is to go to Edit/EoL Conversion and Select "Windows Format". If Windows is greyed out, select Unix format first, and then move it back to Windows. It'll automatically convert all the LF to CR LF.With a lot of dll.xml files I've seen, this is only half the problem though, a lot of times the structure of the file is corrupted with sections of the header missing or truncated/fragmented. Those you have to fix manually by typing the correct info in.The correct header is:

<?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></SimBase.Document>

VERY IMPORTANT: Note here that the final closing tag for the SimBase.Document is the last thing in the entire file - your actual dll entries go between Launch.Manual.Load and it.If one of the actual dll entries is missing parts, the correct entry looks like this:

  <Launch.Addon>    <Name>FSUIPC 4</Name>    <Disabled>False</Disabled>    <Path>Modules\FSUIPC4.dll</Path>  </Launch.Addon>

This should be enough info for you to fix a corrupted dll.xml on your own now.

<<"CR LF" - those stand for "carriage return" and "line feed" - they're terms that originated with mechanical typewriters>>Actually these are from the Baudot code for teletype, think Western Union. On the old ASR-28 teletypes I used to use (blush) you could hit LF all day and the paper would zoom out of the machine (at 100 wpm!!) but the type block wouldn't return to the left position. That and the Bell character were used to get the attention of the DE (distant end).

<<"CR LF" - those stand for "carriage return" and "line feed" - they're terms that originated with mechanical typewriters>>Actually these are from the Baudot code for teletype, think Western Union. On the old ASR-28 teletypes I used to use (blush) you could hit LF all day and the paper would zoom out of the machine (at 100 wpm!!) but the type block wouldn't return to the left position. That and the Bell character were used to get the attention of the DE (distant end).

Cool, that makes sense - so it's even earlier than typewriters.

Cool, that makes sense - so it's even earlier than typewriters.

I'm currently just getting towards the end of a new Windows, FSX and all my addons installation.I've promised myself this time to NEVER install any of my Wilco addons again :( It REALLY hacks me off though, as of course, they already have my money.

I'm currently just getting towards the end of a new Windows, FSX and all my addons installation.I've promised myself this time to NEVER install any of my Wilco addons again :( It REALLY hacks me off though, as of course, they already have my money.

As long as you know how to fix the file, it's pretty easy to solve - a pain though in a general sense. What you could do is backup the dll.xml, install the feel there stuff, open up the new one in Notepad++, copy the new entries from the bottom, and then paste them into the back up - you'd only have to change a couple of LFs to CR LF that way.

Does this have anything to do with the 'fix registry' app that Flight 1 has??The connection in my mind is that after a wilco install I was having problemswith the ILS path being offset in the 747 or MD-11, forget which, and this appfixed it, just wondering now if this is some whole other thing they bork in asimilar way, or if the app was never really fixing the registry, but really thisdll config file???This is useful info though, I never knew exactly what was being messed up.As a long time Unix software engineer, all those DOS carriage returns gave mesome annoyance too, so it works both ways :(

Does this have anything to do with the 'fix registry' app that Flight 1 has??

No, two completely different issues.