FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: JamesChams on January 22, 2010, 03:53:36 am
-
Virtuali,
As always, I backup 3 files before I install any addon sceneries to insure that nothing gets "missing"...
Although PHNL v1.0 installed correct, I noticed this one minor "issue" in the "dll.xml" file:
The "Issue":
I already had the Addon Manager statements there before from other scenery installs. However, the installer removed them from their original location closer to the top of the file's statements and replace them at the bottom of the file as one continues statement (string); ie. missing all the indents and carriage returns etc. So, I manually added them. Not a problem for me, but thought I should mention it in case its not suppose to be doing that.
Now off to try out my FIRST "NEW" FSX ADDON Sudo-MILITARY Airport. ;D
-
Thanks for the "heads-up" James. I am getting ready to purchase it, but I will make a copy of my .xml file first before installing. ;)
Bob
-
Your very welcome, Mr. Bob "signmanbob!" ;)
-
So is it suppose to be that way or what? I've dwnlded but have'nt installed yet bscause of this question.
-
So is it suppose to be that way or what? I've dwnlded but have'nt installed yet bscause of this question.
Mr. "skimmer,"
To be safe, just backup your "FSX.CFG," "EXE.XML," & "DLL.XML" files found in the " %AppData%\Microsoft\FSX " folder. Then, if anything isn't working or missing you've got your originals. :)
-
As always, I backup 3 files before I install any addon sceneries to insure that nothing gets "missing"...
Although PHNL v1.0 installed correct, I noticed this one minor "issue" in the "dll.xml" file:
There's no "issue", at all.
I really don't know why you continue to fear our installer might do something "wrong" to your XML files. The current version of the installer use the STANDARD, OFFICIAL Microsoft XML parser to check the syntax, and to remove and add sections.
It doesn't use any code of its own so, you can be 100% sure that, if your file wasn't corrupted before, it will NOT be corrupted after. If it was corrupted before, you'll get an error message about it. Again, the error will be generated by the official MS XML parser. In this case, the file will NOT be touched.
The result of this, is that the Addon Manager section will always end up last AND, there will be not "pretty formatting" like we use to do before because, they don't have any meaning, as per official XML specification. A file doesn't need indents or lined up space to be valid. This is how the official MS handler works.
This way, we shouldn't end up in issues like having problem when trying to modify an XML that OTHER addons have formatted strangely, or by users that hand edited it in strange (although legal) ways.
Does FSX recognize the file ? Of course it does, otherwise it wouldn't load ANY addon module.
as one continues statement (string); ie. missing all the indents and carriage returns etc. So, I manually added them. Not a problem for me, but thought I should mention it in case its not suppose to be doing that.
Doesn't happen here, of course. I see correct indentation and spacing just fine, before and after installation.
But it wouldn't make any difference in any case because, as I've said, these do not matter at all in an XML file. Formatting with or without spaces/carriage returns, doesn't make the slightest difference to an XML file, the only issue it might happen, is that OTHER addons installers might get confused by this (which, as I've said, doesn't happen here).
Our installer can't be confused anymore because, by using the official MS XML parser, it should be able to add the Addon Manager section to any XML file, regardless of how funky formatted it is, as long as it's a legal one.
Note that, this is NOT a modification we introduced with PHNL installer: it's has been online in ALL installers since start of this year, and nobody had any problems with it so far. In fact, it's exactly the opposite: I find far less XML problem reports, since we changed all the installers which, as I've said, was done before PHNL release.
-
Thanks for the "heads-up" James. I am getting ready to purchase it, but I will make a copy of my .xml file first before installing.
Not needed, because our installer ALREADY does a backup copy of both XML files at start, and it always did, since years...
-
@chams please stop with this attitude as you were important or helpful for other people....that's what you belive. >:( Also in other forum I could observe it. People are happy even without your help or just exactly then ;D. And I'm sure that most developer would be quiet happy whitout your comment like "it would be nice to implement this features, or to change this, it would make you product more sell-able". Do a step back and don't feel you have to leave always a comment.
-
Please, let's not start another one, or the whole topic will go away.
-
Thanks for the info Virtuali. I have never had to backup any files because of Fsdt and dont have any problem now . Im going ahead with install as always.
-
Virtuali,
I'm glad to hear that the installer is "doing more" for us and that my concern was not an issue after all...
Where might I find these backedup files? I ask because I created a batch file to do backups of them for me and I'd rather not have multiple duplicate backed-up files scattered on my HDD's (HD space in at a premium on my systems now). If I can use your installers backedup ones that should be good enough.
Grazie!
-
Where might I find these backedup files?
In the same folder as the DLL.XML, named "DLL.XML_Before_Addon_Manager", and the same for the EXE
-
I wanted this so badly. I installed it and now my FSX won't start. The COUTL program or something gives me grief all the time.
I went to exe.xml and disabled to TRUE and my FSX starts up.
Any ideas what I need to do?
I am running FSX Accel on Win XP 32bit
-
Check you don't have FSX running in XP Compatibility mode, which is not correct, and it's not how FSX is installed normally.
-
I am running good ole Win XP no compatibility mode
I saw you other thread..so I am going to try uninstalling PHNL and the Add on manager and then reinstall PHNL.
-
When It asked me if I wanted to remove the addon manager and the COUTL I said yes and it was unable to remove both of them. Hmmm!
-
It didn't said that it was unable to remove both of them. It said a file was missing because, it was already removed.
It's not error, it's just an confirmation the file that should be removed, was missing already so, no need to re-remove it again so, everything it's ok.
-
I reinstalled after I manuall;y removed the COUTL.EXE and its back to square 1. FSX wouldn't start up. It just hangs there....
-
The Couatl exe can't prevent FSX to run, because it's an external exe. What error, exactly, are you getting from it ?
-
There is no error message. all I see is the FSX start screen just sitting there. Nothing. Its like frozen
-
There is no error message. all I see is the FSX start screen just sitting there. Nothing. Its like frozen
Your previous message said you said something about Couatl.exe
Are you using FS Copilot ?
-
When I tried to uninstall PHNL it asked me if I wanted to remove COUTL as well and I said yes but it gave an error message saying that it was unable to.
Well anyway, I tried installing the Addon Manager and this time it ended with an error saying the bracket was not closed or something like that. I take some xml was not written properly.
error on line 0,position 0: The following tag were not closed Simbase.Document
-
sorry forthe long post
dll.xml
<?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>
<Launch.Addon>
<Name>AddonConverterX</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\FlightSimTools.com\Addon Converter X Free Demo\AddonConverterX.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>AFXModule</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\AFX\AFXModuleFSX.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Instant Scenery</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>E:\Program Files\Instant Scenery\InstantSceneryFSX.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Object Placement Tool</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Level-D Simulations</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\LVLD.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG Options</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGOptions.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG Events</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGEvents.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>PMDG Sounds</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDGSounds.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim Menu</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\Captain_Sim.b757.menu.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Captain Sim 727 Menu</Name>
<Disabled>False</Disabled>
<Path>Captain_Sim\727\Captain_Sim.p727.menu.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
</SimBase.Document>
exe.xml
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Disabled>False</Disabled>
<Name>GoFlight Hardware Interface</Name>
<Path>C:\Program Files\GoFlight\GFDevFSX.exe</Path>
<CommandLine/>
</Launch.Addon>
<Launch.Addon>
<Name>Jeppesen SIMCharts</Name>
<Disabled>False</Disabled>
<Path>c:\Jeppesen\SIMCharts4\SimCharts.exe</Path>
<CommandLine>/FSX</CommandLine>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>UT2</Name>
<Path>D:\FSX\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>
<NewConsole>True</NewConsole>
</Launch.Addon>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
/SimBase.Document>
-
I notice an error there.. on that last line. Let me fix it and try again
All right virtuali. That fixed it. <Embarassed> here :P
Please remove my posts here that I created today. so as not to confuse others. This is my error. I introduced it it looks like. But the fact remains, it didn;t work the first time which necessitated me to go mess with the xml files. for now to avoid confusion, you may want to remove my posts that I did today.
Thankx
-
When I tried to uninstall PHNL it asked me if I wanted to remove COUTL as well and I said yes but it gave an error message saying that it was unable to.
This might also due to the fact that the Couatl.exe was still closing, because you might have launched the unstaller too soon after FSX closed down and, depending on your system speed, it might take some additional time before it also close the additional programs ( like Couatl.exe ) that are launched by it.
A Windows reboot would surely have fixed this.
Well anyway, I tried installing the Addon Manager and this time it ended with an error saying the bracket was not closed or something like that. I take some xml was not written properly.
error on line 0,position 0: The following tag were not closed Simbase.Document
This means there's an error in your EXE.XML file (or it's DLL.XML ?), that of course is preventing everything to run. This might have been appeared when you edited to disable the Couatl exe. In any case, it should be possible to manually fix your XML file, by closing the missing ending tag.
OR, if you are not sure about how to fix it, if you simply remove it and run PHNL installer again, a new correct one will be remade from scratch.
-
All right virtuali. That fixed it. <Embarassed> here Tongue
Please remove my posts here that I created today. so as not to confuse others. This is my error. I introduced it it looks like. But the fact remains, it didn;t work the first time which necessitated me to go mess with the xml files. for now to avoid confusion, you may want to remove my posts that I did today.
Thankx
-
But the fact remains, it didn;t work the first time
Yes, that's the issue: we know that, a lot of times, newly trusted modules don't run the 1st time you trust them. Usually, a 2nd or 3rd FSX launch, or a Windows reboot, fixes the problem.
-
I've installed HNL on FSX/acc and no problems at all.Looking good!!! ;D ;D (Windows XP)
-
Trial seems fine on my system (amazing scenery!) and I purchased it on the web. The servers seem busy because it keeps telling me to wait 15 mins when I put the key in and after I do it says to wait again :D
Will try tommorow ;)
-
The servers seem busy because it keeps telling me to wait 15 mins when I put the key in and after I do it says to wait again
A "Serial not found" error might also simply due because the Serial number was typed wrong like, for example, exchanging the letter O with a 0 ( zero ), or something like that.
-
After I installed the PHNL the Game CTD.
I removed the dll.xml and no problem and off course no menus.
So when i removed the:
<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
From the xml file - FSX worked again.
What shall I do
All the best
Jens Michlas
DK
-
You could have simply use the following method to disable a module:
<Disabled>True</Disabled>
Your program is most likely the antivirus, that has blocked the complete update of files during the installation.
- Turn off your antivirus. Don't simply quit its interface, but turn off its realtime protection.
- Uninstall the Scenery from the Windows Control Panel
- Reply YES to the question "Do you want to remove the Addon Manager ?"
- Reply YES to the question "Do you want to remove the Couatl Engine ?"
- Configure your antivirus to ignore the FSX\fsdreamteam\couatl.exe file from scanning.
- Configure your antivirus to ignore the FSX\bglmanx.dll file from scanning.
- Reinstall the Scenery
- Turn the antivirus back on, then launch FSX
-
Thank you for your reply
I will do that
And thanks for wonderfull sceneries
Jens Michlas
DK
-
Ok Im still having issues. Im getting the:
error on line 0,position 0: The following tag were not closed Simbase.Document
your dll.xml was not modified error. I am currently uninstalling all of my FSDT scenerys to try and narrow down the problem. I started all of this because my LAS building would not show up for some reason. So when I try and reinstall them I get the error for the dll everytime I install a FSDT scenery. I also reverted back to my original dll and exe. dll files to see if the problem would go away.
I am unsure how to configure Norton Antivirus to ignore the mentioned files. If someone could tell me that would be great! When I turn off my AV the error message does not come up.
So here is some basic information about my pc
Windows 7 HP 64bit
Norton Antivirus 2010
FSX SP1 and 2
Is there anything else that I should be doing to maybe troubleshoot this prob any more?
-
That error means either your dll.xml or you exe.xml have an error.
If you use the current version of the installer that is online now, the installer will now propose automatically recreate a correct one, and will proceed.
-
So the current version of the installer is different the one from release?
-
Yes, but just the installer, the scenery files are the same.
-
Hi
I still have the same problem.
It is only that fsdt post in dll file that make the problems.
So I think wait until you solve it.
So no FSDT sceneries working just now.
All the best.
Jens Michlas
DK
-
I still have the same problem.
Which problem ? There are many problems discussed here, from antivirus, to fs copilot, to dll.xml problems.
So I think wait until you solve it.
With regard to the fs copilot problem, and issues with dll.xml (or exe.xml) not correctly formatted, the *current* installers are all able to deal with this so, there's nothing to solve, because it's already solved.
If, instead, the problem is the antivirus, there's nothing we can "solve", the only way to solve it is to correctly configure the antivirus, which has been explained several times, even in this thread.