I hate the EXE.xml. Everytime I try to mess with it, it always ends up screwing up somehow. Right now I have entries for both WinchX and AiCarriers in there and they both work fine. I am trying to add an entry for FSRecorder but when I do, all three end up not working. What am I doing wrong here? I will attach a copy of my EXE.xml so you guys can take a look.
-
There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.
The Staff of SOH
EXE.xml problems
- Thread starter Rezabrya
- Start date
N
NoNewMessages
Guest
There are no entries for FSRecorder in there, so there's no way of telling what the error may be.
Hello:
You might wish to use [FONT=verdana, sans-serif]the excellent freeware "ModuleToolX 0.4" to do those edits[/FONT] of EXE.XML and DLL.XML.
http://library.avsim.net/esearch.php?CatID=fsxutil&DLID=117187
BTW: There have been rare reports of edits to the active "Standard.XML" failing to be retained, and users have further edited both the working copy:
C:\Documents and Settings\[current user account or profile name]\Application Data\Microsoft\FSX\Controls\Standard.XML
(Windows XP 32-bit path shown)
...as well as the "template copy" in the [FSX install path] root folder to be sure the edits were kept.
But, I don't think you should have to do anything so drastic if you get the XML correct in the EXE.XML for *.EXE files, and get the XML correct in the DLL.XML (for *DLL modules in FSX root or \Modules sub-folder).
You'll likely also need to fix something in FSX.CFG to resolve this; and you should NOT have to rebuild your FSX.CFG from scratch to be successful.
To fix an already malfunctioning configuration for an executable FSX add-on that needs to be re-approved to run as a "Trusted" app, you may have to go into the active working copy of FSX.CFG, and "comment out" the problematic app to make sure you are presented with another opportunity to "re-approve" it the next time FSX loads up.
FYI: To "comment out" a Trusted app statement in FSX.CFG, place a double slash "//" followed by a space at the beginning of the line for the problematic app in the [Trusted] section near the bottom of FSX.CFG.
That, in conjunction with doing your edits of the configuration XML files above with [FONT=verdana, sans-serif]ModuleToolX 0.4[/FONT] may have you running a bit easier.
PS: Be sure in your XML files that the app has "Disabled" set to FALSE, and "Manual Load" set to "TRUE" so it will load and trigger the approval prompt at FSX startup.
Hope this helps ! :mixedsmi:
GaryGB
You might wish to use [FONT=verdana, sans-serif]the excellent freeware "ModuleToolX 0.4" to do those edits[/FONT] of EXE.XML and DLL.XML.
http://library.avsim.net/esearch.php?CatID=fsxutil&DLID=117187
BTW: There have been rare reports of edits to the active "Standard.XML" failing to be retained, and users have further edited both the working copy:
C:\Documents and Settings\[current user account or profile name]\Application Data\Microsoft\FSX\Controls\Standard.XML
(Windows XP 32-bit path shown)
...as well as the "template copy" in the [FSX install path] root folder to be sure the edits were kept.
But, I don't think you should have to do anything so drastic if you get the XML correct in the EXE.XML for *.EXE files, and get the XML correct in the DLL.XML (for *DLL modules in FSX root or \Modules sub-folder).
You'll likely also need to fix something in FSX.CFG to resolve this; and you should NOT have to rebuild your FSX.CFG from scratch to be successful.
To fix an already malfunctioning configuration for an executable FSX add-on that needs to be re-approved to run as a "Trusted" app, you may have to go into the active working copy of FSX.CFG, and "comment out" the problematic app to make sure you are presented with another opportunity to "re-approve" it the next time FSX loads up.
FYI: To "comment out" a Trusted app statement in FSX.CFG, place a double slash "//" followed by a space at the beginning of the line for the problematic app in the [Trusted] section near the bottom of FSX.CFG.
That, in conjunction with doing your edits of the configuration XML files above with [FONT=verdana, sans-serif]ModuleToolX 0.4[/FONT] may have you running a bit easier.
PS: Be sure in your XML files that the app has "Disabled" set to FALSE, and "Manual Load" set to "TRUE" so it will load and trigger the approval prompt at FSX startup.
Hope this helps ! :mixedsmi:
GaryGB
