FSDreamTeam forum
Products Support => Dallas FSX/P3D => Topic started by: marcanthonystorm on August 13, 2010, 06:11:47 am
-
has anyone experienced after downloading DFW, an issue where fSX stops opening and says there's a problem. The problem tells me that " FLight Simulator has detected a problem with third party software.
Name Bglmanx Dynamic Link library
Version: 2,7,0,29
File. bglmanx.dll
I cant seem to get the Addon Manager to operate in the upper tab, it's not visible as well as coault is not there to click on.
-
- Reboot Windows
- Uninstall the scenery, reply YES to the question "Do you want to remove the Addon Manager?"
- Disable the Antivirus
- Reinstall the scenery
- Configure the Antivirus to exclude the FSX\bglmanx.dll file
- Run FSX, authorize both files, if asked.
- If FSX crashes once, try it again without doing anything else. If it still crashes, reboot Windows another time and try again.
Be sure you are NOT using FSX in "XP compatibility mode", if you are running Vista or Windows 7.
-
Tried what you said and it didnt work. Also don't know how to tell AVG for Free to allow the bglmanx.dll Im lost here, my system never had any issue and after I installed the DFW and put in the registration key it all failed from there. My system has 4.2 ghz processor, 6 gbs of Dominator GT 2000mhz, 3 Solid state drives and adding one more. ATi Radeon 5970. Pretty much handles what ever fsx throws at it but this is a mess. It all happened right after I put in the registration key for DFW and I have all the other FSDreamTeam airports.
-
It all happened right after I put in the registration key for DFW and I have all the other FSDreamTeam airports.
Ok, so it means it DID worked when you first installed KDFW, otherwise you woldn't be able to open its menu to add the Serial Number, so it hasn't happened after downloading and installing.
Are you sure that you rebooted Windows BOTH as the initial step and also after trying a couple of times by allowing the module to run (even if FSX suggests against it ?) This might be important.
Try this:
- Open your FSX.CFG file, located at %APPDATA%\Microsoft\FSX, with Notepad.
- Look under the [Trusted] section, and remove ALL the lines that contains a reference to bglmanx.dll. The whole line. Save the file back, don't launch FSX yet.
- Launch FSX. At the request to Trust the Addon Manager, reply YES, to both question, the one by Windows and the one by FSX itself.
- If you get the error the 3rd party module can't be loaded, IGNORE IT, and ALLOW it to run, regardless of what it says. Don't worry if FSX crashes after having issued that message. It doens't matter.
- Keep trying and, allow 20-30 seconds between each tries. If after 3-4 times it's always the same, REBOOT Windows and try again. Yes, this IS important, do it please.
-
ok i did as you said and removed the bglmanx line from the FSX config and saved. There were several of them. I restart FSX and I get the 3rd Party error again but I press yes. Then the Coautle window comes up and I say yes and do I trust this software and Yes again. Then it looks like it will load but then I get thei warning that Flight Simulator has stopped working, check for solution. Each time I do this the bglmanx is sput back in the FSX Conf file..
-
Yes, of course, it's normal that when you allow the file to run, it will save that info in the FSX.CFG. I asked to reset it, not because it's not supposed to be there, but because there's a known bug in FSX that, sometimes, the trust system acts strange so, by removing the files and triggering a new trust question, it's reset.
Are you running FSX "Ad Administrator ?", if yes, turn it off.
Also, are you running FSX in the "XP Compatibility mode" ? If yes, turn if off.
To do this, go into the FSX folder, select the FSX.EXE, right click on it, select "Properties", then select the "Compatibility" tab and be sure NOTHING is checked there, which is how FSX defaults to.
-
well if I check on Compatibiltiy mode Windows XP (Service Pack 3) lights up. But if I dont check that spot then it's not highlighted. I didn t have it checked to begin with so what should I do. IM running windows 7 64 bit. And I tried over and over again. Im about to reinstall this thing because its been a day of nothing. No flying just messing around with a program that just doesnt want to be friendly anymore.
Marc
-
If nothing is checked, than it's ok, don't check anything.
Try to download this update from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en
Use the vcredist_x86.exe file, yes, use that one, even if you are on 64 bit OS.
Always reboot Windows before each try, please.
-
I installed the link you gave me and didnt work either. I have rebooted and started up and get the same thing each time and CTD.
-
I even took out the FSX.CFG folder and left it on the desk top and rebooted. Then start up FSX and it actually seemed to skip the error and went to Coautle and then asked permission so I said yes and then Boom the error came back. Not much else to do but uninstall my whole system because of one add on
-
Then start up FSX and it actually seemed to skip the error and went to Coautle and then asked permission so I said yes and then Boom the error came back.
It's not clear: you said you get an error after trusting Couatl but, which error ?
- An error related to Couatl
- The same as the first error about bglmanx.dll
- An FSX error without specifing any module, followed by a crash
-
The same as the first error about bglmanx.dll
-
Also, you said you didn't know how to exclude files and folder from scanning with AVG, have a look here:
http://forums.avg.com/ww-en/avg-free-forum?sec=thread&act=show&id=25943#post_25943
The correct procedure to fix any possible antivirus interference is:
- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.
- TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.
- Reinstall the scenery with the Antivirus TURNED OFF. Don't launch FSX yet.
- Configure the antivirus to exclude the following files from scanning:
YourFSXFolder\bglmanx.dll
YourFSXFolder\fsdreamteam\couatl.exe
YourFSXFolder it's usually C:\Program Files\Microsoft Games\Microsoft Flight Simulator X, if you installed it in the default folder.
- Now you can turn the antivirus back on, and launch FSX.
-
Another thing to try is enabling UAC, if you have it disabled, or disabled it, if you have it enabled. It will require a reboot each time you change the setting.
Have a look here how to disable/enabled UAC in Windows 7
http://www.blogsdna.com/1815/how-to-disable-uac-turn-off-uac-in-windows-7-beta-1-build-7000.htm
-
Honestly I could have rebuilt the FSX on my RIG by now. Im not sure why this happened but it did happen with FSDreamTeam. As big of a fan I am of there software, something went wrong and it happened with DFW when I installed it and tried to register the product. This is most unfortunate.
-
Honestly I could have rebuilt the FSX on my RIG by now.
It won't make any difference, it's not an FSX issue, is something that has gone wrong in the Windows trust mechanism.
Have you tried at least the antivirus step ? This is usually the most common cause of the problem.
-
This is how my addon manager looks on my C: drive, keep in mind that my FSX is on the D: drive
If there is something that needs correcting please let me know what I must do but I believe there is something out of place, just not sure what.
Controls
SimObjects
Substitutions
Cameras
dll
dll.xml.addonmanager
dll.xml_Before_Addon_Manager
exe
exe.xml_Before_Addon_Manager
fsx
LWcfg.SPB
navlog0
wxstationlist.BIN
-
I'm fairly sure it's not an FSX thing, it's related to the Windows trust system. Sorry to ask again but, have you tried my two previous suggestions, disabling or enabling UAC, and configure the antivirus to exclude our files ?
-
Also, you are kindly requested NOT to open another thread about this issue.
You have a problem with KDFW, this is the KDFW support area, there's already a thread opened for you, and you ARE getting support for it, and we'll not end up until this is fixed.
So, please, don't open another thread about the same issue elsewhere, because it only making more confusing to follow you.
-
Please, check your PM, I've sent you a message with other things to try.
-
Ok, and just know that Im doing everything you asked. Yes it has been allowed to pass through AVG, Excluded.
-
Im not able to use my Quality Wings, FSDreamTeam addons, or PMDG. The issue happened right as I clicked ok after inserting the registration code. Im with the Touch and Go Films staff. Right now the msg on the bottom right hand corner of my screen is saying. Microsoft Flight Simulator has stopped working... A problem caused the program to stop working correctly. Windows will close the program blah blah blah..
-
I did try the bglmanx that you sent to me but it didnt work. I have uninstalled everything again and that includes planes and scenery deletion from the control panel.
-
I completely uninstalled every existence of FSX from my computer. I reintalled fsx then installed acceleration. Tested it with an F18 hornet and it was fine with max settings. My security has been off for a day now. I also just installed REX V2.0 and it works just fine. But when Installed the KDFW and ran fsx, I got the error message that bglmanx.dll has an error and then the Microsoft Flight Simulator stopped working.
Dont know what to do or believe at this point. Everything works that doesnt us Coualt products but those that do will not work
-
I completely uninstalled every existence of FSX from my computer. I reintalled fsx then installed acceleration.
You shouldn't have done that, I told you twice:
it's not an FSX issue
I'm fairly sure it's not an FSX thing, it's related to the Windows trust system
This is not an FSX problem, it's something wrong in Windows. I've sent you exactly the same file you had by PM to this user:
http://www.fsdreamteam.com/forum/index.php?topic=3437.0
That had the same problem, and he told me that as soon as he installed the new file, the problem has gone. The only difference between the regular version and the one you got to test, it's only a different release of the VC++ runtimes it's linked with, which means (at least in case of the other user) the problem was 100% caused by a problem with that other library in his own system.
Are you really sure you installed this file from Microsoft:
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en
And rebooted Windows after installing and trying again ? The file I've sent you, won't run if this update is not installed.
You can try a different thing:
- Go in the Windows control panel, and Uninstall ALL the istances of the Visual Studio 2005 redistributable runtimes. You might have more than one version, remove them all.
- Then, after removing everything related to VS2005, reinstall again these 3 files:
http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en
One after the other one, in this order. Use always the vcredist_x86.exe, even if your OS is 64 bit, we are dealing with 32 bit apps, so they need a 32 bit runtime.
-
For the record I did everything you asked in your last post verbatim, unfortunately it came back with the same results. It all started when I put in the registration code for DFW. I have no use of my FSDT addons at all or my QW because of this. Im out of my best addons and a lot of money down the drain because there isnt a soul who knows how to fix this glitch. If my computer had this problem from the beginnig I would just say buy a new RIG. But I had almost all of the FSDT addons and then the second I put in DFW it ruined it. So does anyone know what really needs to be done. What was in that code that gave my PC a virus because thats what it is. Its really unfair that the makers of FSDT dont have a solution and my FSDT QW days are over because of it. I spend a lot of money on addons and make a ton of FSX videos that get a lot of attention. I hope someone here will do something and make a patch that works.
Marc Anthony Gonzalez
AKA
MARCANTHONYSTORM on YouTube
-
What was in that code that gave my PC a virus because thats what it is.
Sorry, but this is just not possible. The Serial Number it's just a text code that is stored in the registry, it can't create any problem to your system.
Its really unfair that the makers of FSDT dont have a solution and my FSDT QW days are over because of it.
Besides, I was WAITING for your report so, you can't just say we don't have a solution, because you have been constantly followed with PLENTY of solutions, I've sent you a special version of the Addon Manager which I've made just for that purpose and there was ANOTHER user that had the same problem that got the same file, and he reported it to me it was fixed.
In his case, it was most likely a problem with the Visual Studio 2005 runtimes that were probably broken on his system, the file you have received it's linked with a slightly different version, there were no other differences.
So, it's very likely that on your system, instead, the VS 2005 runtimes are all having a problem, that's why I've asked to to reinstall them all.
I made some research and, there is a chance the VS 2008 runtimes, instead, might create a conflict with the VS 2005. We use the 2005, because this is what FSX uses, but I know there are other FS developers that use the VS 2008 ones.
Can you try to check if you have the VS2008 runtimes on your system ? If yes, try the following:
- Uninstall ALL the Microsoft VS 2008 runtimes
- Uninstall ALL the Microsoft VS 2005 runtimes
- Reinstall ALL the Microsoft VS 2005 runtimes, using the links I've posted above.
- DO NOT Reinstall the VS 2008 ones, for the moment
- Reinstall KDFW and check if FSX starts now.
Don't think for a moment that WE will drop this problem, you WILL be supported until this is FIXED.
-
Ok, I will try it and thank you. I know that there has to be a solution. Is there any chance that the new FSrecorder 2.0 Beta could be interfering with it. I has put that on the night before which is the only other change to my rig. Sometimes I get the message after it crashes to desktop about Fsrecorder_0 something something and not sure what that has to do with anything
-
The easiest way to test if the problem is caused by a conflict with another module, is to disable them all in the DLL.XML, them re-enable one at a time, until the problem is found.
- Open you DLL.XML file with a text editor (eg. Notepad is fine), the file is located at %APPDATA%\Microsoft\FSX
- Look for all the <Disabled> tags, and change them to <Disabled>True</Disabled>
- Do this for ALL the <Launch.Addon> sections, EXCEPT for the Addon Manager one (bglmanx.dll) and the main section at the top of the file (which would disable the whole XML file so, you shouldn't change it)
- Save the file and exit.
- Do the same for the EXE.XML file, located in the same folder, disable all modules EXCEPT for Couatl (fsdreamteam\couatl.exe)
- Save the file and exit
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.
-
Here is my dll.XML file I hope you will see something in there that tells what the probelm might be
<?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>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Object Placement Tool</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Traffic Toolbox</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>Visual Effects Tool</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.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>VistaMare Core</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>VistaMare\ViMaCoreX.dll</Path>
</Launch.Addon>
<Launch.Addon>
<Name>FeelThere ERJX Helper</Name>
<Disabled>False</Disabled>
<Path>FeelThere\Erj\E145XH.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>FS Recorder Module</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>D:\Program Files (x86)\FS Recorder for FSX\RecorderFSX.dll</Path></Launch.Addon></SimBase.Document>
-
This is my exe.xml copy
<?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><Name>EZdok camera addon</Name><Disabled>False</Disabled><Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path></Launch.Addon><Launch.Addon><Name>Couatl</Name><Disabled>False</Disabled><ManualLoad>False</ManualLoad><Path>fsdreamteam\couatl\couatl.exe</Path></Launch.Addon></SimBase.Document>
-
You only posted your XML, but haven't done what I've asked to do in my previous message, which would allow you to find what is the conflicting module.
So, I'll repeat the last instructions:
- Open you DLL.XML file with a text editor (eg. Notepad is fine), the file is located at %APPDATA%\Microsoft\FSX
- Look for all the <Disabled> tags, and change them to <Disabled>True</Disabled>
- Do this for ALL the <Launch.Addon> sections, EXCEPT for the Addon Manager one (bglmanx.dll) and the main section at the top of the file (which would disable the whole XML file so, you shouldn't change it)
- Save the file and exit.
- Do the same for the EXE.XML file, located in the same folder, disable all modules EXCEPT for Couatl (fsdreamteam\couatl.exe)
- Save the file and exit
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.
-
Something doesn't add to your report:
- If you had the request to trust the 2 modules, it means there WAS a Addon Manager in DLL.XML file, and a Coutl entry in the EXE.XML, otherwise you wouldn't seen those requests.
- If you don't have the entries now, it means no software is loading. But, if FSX is crashing at 100% Loading, with no software loaded, it means the crash is NOT caused by anything related to our software, since it's not running at that point.
So, it seems you are having two entirely different issue:
1) No Addon Manager entries in the DLL.XML and no Couatl entries in the EXE.XML. Are you *really* sure about this ? Because this simply can't be happening. If your XML files were corrupted, the installer should have prompted you to recreate a correct XML from scratch so, it's just not possible you'd end up with no entries.
2) FSX crashing at 100%. This can't be caused by our modules or our scenery. It can't because, if it was an Addon Manager problem (not updated files, for example, or antivirus issues), FSX would quit right at the start, before reaching any menu. And, if your XML files don't have the entries, the modules are not loaded anyway so, they can't surely be the cause of the crash, if they are not loaded.
Try to MOVE your DLL.XML and your EXE.XML files to a different location (like, on your Desktop), then reinstall the scenery, the installer WILL create a new correct XML file with the entries. If not, then something is REALLY wrong with your system.
Just to be sure, the XML files are located at:
%APPDATA%\Microsoft\FSX
And, to be SURE you are looking at the correct files, turn on the option in Explorer to show the complete file name +file extension.
-
Just wondering, since Im not the only person this has happened too because it also happened Spencer from Touch and Go Films. What has the forum of Fsdt done to fix the problem. I have read outside of this forum people having this issue and you are telling me to find what program conflicts, but wouldn't you know the answer by now. It is unfair that Im being asked to find the culprit when everything else on my system works well with each other. The only program that is conflicting is Fsdt. So what are you guys doing to correct this problem. QW uses the same bglmanx.dll and it won't work either. Mind you it all happened the day I put the DFW on my rig and put the password, then it went bizzerk. Seriously, my system is fine but Fsdt should have used something other then Coautle to run their program. I have PMDG, Captain Sim all of the Aerosoft addons and UK 2000 too and no issue at all. Im frustrated because Im out of almost 400 dollars because of your product and I'd almost rather post on my YouTube page, not to use any Fsdt products and with 460 subscribers and counting and 160,000 views, I know it will make an impact really fast. I receive almost 1500 to 2000 views a day. I went up 60 subs in the past 3 weeks. So tell me how many more things should I change before I get a true answer, either I dont now Marc or this is the solution. Please choose your words carefully when you reply because it's been over 2 months and you havent given me an answer just pot luck solutions that don't work. I won't hesitate for a second to post on my Youtube page this problem with Fsdt. Yes I am very disappointed.
Respectfully
Marc
-
Just wondering, since Im not the only person this has happened too because it also happened Spencer from Touch and Go Films.
It happen to many other people as well but, of course, we always fixed it in the end.
What has the forum of Fsdt done to fix the problem.
Fixing all those that asked for help here, which what we always do, as can clearly seen from all the forum posts.
but wouldn't you know the answer by now.
No, because what you are seeing it's just a diagnostic message from FSX that it can't load our module FOR ANY REASON. It doesn't mean the module is at fault, it simply mean it wasn't able to load it, for some reason.
But the *reasons* might be several, from the antivirus (most common one) to a conflict with another module, from a problem in the Windows trust system, to a problem with some Windows sytem libraries.
All those reasons happened, all of them has been fixed, but ALL of them started with that message, and they were all fixed using entirely different methods, depening on what the cause was in that single case.
So, you shouldn't do the mistake of confusing the diagnostic message with the cause, becuase the causes can be many and, unless we follow a way to troubleshoot it, there's no an "universal" solution to it.
Note that, in ALL cases when the problem was eventually fixed, it was ALWAYS something system related, antivirus-related, or other modules in conflict-related.
It was NEVER fixed by "fixing" or replacing our module, becaue there wasn't nothing wrong with it to begin with: it was just a matter of finding WHAT is causing it to fail on THAT specific system and, as I've said, the causes are many.
It is unfair that Im being asked to find the culprit when everything else on my system works well with each other.
It might be in YOUR case nothing is conflicting, then we'll proceed with other troubleshooting methods, and your issue will be fixed, as it was fixed to anyone that went here asking from help.
The only program that is conflicting is Fsdt.
A program doesn't "conflicts" on its own. If there's is a conflict, it's with something else, otherwise it should fail on each and every system. Since it obviously doesn't, it's clear the conflict is something else, and it needs to be identified what is in your case, on your system.
So what are you guys doing to correct this problem.
As as I've said, fixing the problem to everyone that asked for help here, as clearly demonstrated by following all posts, to their eventual conclusion, which alwasy was the problem was solved in the end, but with different methods because the causes can be several.
QW uses the same bglmanx.dll and it won't work either.
That's normal. Since the file it's the same, if something on your system is causing it to fail, it won't change if it's installed with QW or with FSDT, it will still suffer from that "something else" on your system that is preventing to work.
Seriously, my system is fine but Fsdt should have used something other then Coautle to run their program
Now I don't understand: you are saying the error is coming from bglmanx.dll, now you are saying is coming from Couatl.exe ? Please, clarify better: do you see the error on bglmanx.dll only, on Couatl.exe only, or both ?
I won't hesitate for a second to post on my Youtube page this problem with Fsdt.
By posting all over the world about your problem, you will only show that your system had a problem, nothing more than that.
Since we have a Trial version of all our products, everyone can freely download them on his own system and 99.99% of the cases, he'll find they works just fine, and when they don't, he can come here and have the problem fixed.
Please choose your words carefully when you reply because it's been over 2 months and you havent given me an answer just pot luck solutions that don't work.
Your last message was on Sept. 4th, to that I replied in about 1 hour, asking to try something.
You are now replying 20 days later than what you have been asked to (trying to exclude any other modules to check for a problem) is "not fair".
It might be there's no conflct with another module, but before being sure of it, we need to test it so, please, do what you have been asked to because, if you have tried all the other usual solutions, like checking the antivirus and the trust system haven't worked, there might a chance there's another module in conflict.
Sometimes, it might be enough to change the module's loading *order*, and it migth do away but first, it needs to be identified if there is a conflict indeed, otherwise we don't have any way to know with *which* module we should exchange the loading order with.
So, we are now back to my last message, please try this:
- Open you DLL.XML file with a text editor (eg. Notepad is fine), the file is located at %APPDATA%\Microsoft\FSX
- Look for all the <Disabled> tags, and change them to <Disabled>True</Disabled>
- Do this for ALL the <Launch.Addon> sections, EXCEPT for the Addon Manager one (bglmanx.dll) and the main section at the top of the file (which would disable the whole XML file so, you shouldn't change it)
- Save the file and exit.
- Do the same for the EXE.XML file, located in the same folder, disable all modules EXCEPT for Couatl (fsdreamteam\couatl.exe)
- Save the file and exit
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.
-
I'm waiting from your report.
Your message here has been removed from the other section, because you posted two copies of it.
Posting twice the same message, doesn't make our job any easier, and doesn't give you a better chance to get a reply, considering all your previous messages have been replied to in a timely matter.
So, either you chose to continue here, or in the other thread in General section, please, continue in a single thread only, because it gets very easy replying to the same person about the same problem in two threads at the same time, which is why one of your identical messages has been removed.
-
I tried what you asked with changing the other addons to True and it didnt work. Anyway thought you might like to watch my latest video.
-
Have you tried to install the latest Stand-Alone Addon Manager ? We had a small update last week.
http://www.virtualisoftware.com/binaries/setup_addonmanagerX.exe
Try this, if it doesn't work, I'll contact you via email to try a different version that we use for debugging.
-
I opened this message and I did install new install you sent me in September as you requested. It didn't work. It looked like it would, it went through the motions of getting my permission to run the programs and then BAM, Microsoft Flight Simulator has stopped working window pops up. I am on Skype and my name is Marc Anthony Gonzalez, my email is Marcanthonystorm@hotmail.com and Im on Youtube Marcanthonystorm with 68 videos, over 690 subs and 225,763 views. The last part of the msg when flight Simulator shuts off is "FSX process not found. FSX_handle:0" inside of Ezdoc window. Please lets fix this problem I spent a lot of money on FSDT and Quality Wings. Im not reinstalling FSX one more time to repeat this whole scenery again.
-
I opened this message and I did install new install you sent me in September as you requested.
That is probably outdated by now. Try with the current Stand-Alone Addon Manager installer found on the website, the link is the same as the previous message above.
The last part of the msg when flight Simulator shuts off is "FSX process not found. FSX_handle:0" inside of Ezdoc window.
That kind of explain you are having issues: it's Ezdoc (don't know what it is, but it looks like an FSX addon) that has crashed. It's possible there's a conflict between the programs.
Try to remove this addon first, and use the current Addon Manager, not the one I've sent you in September.
If I recall correctly, you have been given a version which was linked with a different version of the C++ runtime.
If that fixed the issue back then, it clearly proves your problem is that your Windows installation has a corrupted install of the C++ runtimes we need to run. OR, it's possible another FSX addon you are using is trying to use that runtime in a wrong way, and triggers the conflict.
And besides, you still haven't reported back any results of the test I've asked you to do many times, which is of course the one and only way to know if there's a conflict with another addon.
I'll repeat the instructions here again:
- Open you DLL.XML file with a text editor (eg. Notepad is fine), the file is located at %APPDATA%\Microsoft\FSX
- Look for all the <Disabled> tags, and change them to <Disabled>True</Disabled>
- Do this for ALL the <Launch.Addon> sections, EXCEPT for the Addon Manager one (bglmanx.dll) and the main section at the top of the file (which would disable the whole XML file so, you shouldn't change it)
- Save the file and exit.
- Do the same for the EXE.XML file, located in the same folder, disable all modules EXCEPT for Couatl (fsdreamteam\couatl.exe)
- Save the file and exit
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.
-
Ezdoc Camera allows you to move the camera around the plane in any direction without restrictions. It also gives you camera shake so the flight looks more real. I had Ezdoc on here before with FSDT and it was fine. My problem started the day I installed the DFW scenery from FSDT. Ever since then its not worked with FSDT or Quality Wings either. That's a little over 350 dollars down the drain. Can you send me the link to the new addon Manager so Im getting the right one. Also I use Team Viewer too and I help others with there problems. Would it be too hard to do the same with me. thank you.
Marc
-
I had Ezdoc on here before with FSDT and it was fine
For the 4TH TIME: Can you PLEASE TRY to do what I've asked ? Just to be SURE it's not a conflict with it ?
Can you send me the link to the new addon Manager so Im getting the right one
As I've said in my previous message, the link hasn't changed from the message before.
Also I use Team Viewer too and I help others with there problems. Would it be too hard to do the same with me.
Try installing the latest Addon Manager, and if still doesn't work, I'll try to reach you with Team Viewer.
-
Ok i'll try to do it without the ez doc camera addon
-
Well I removed the Ezdoc camera from my entire computer, then I installed the latest addon Manager from FSDT. I started up FSX and it asked me about Coutle and permission,
which I gladly gave and then the infamous window Microsoft Flight Simulator has stopped working popped up. Seriously, does anyone have the answer. I have tried and tried and tried, I have
the PMDG working with everyone on my rig, Captain Sim works Ezdoc did work well, FS Recorder works, all of my UK 2000 scernery works, Aerosoft addons work. The only thing that doesnt work
is FSDT software and Quality wings of which both use the Coutal and Bglmanx.dll which is conflicting. HEEEEEEELLLLLLLLLLPPPPPPPP me.
-
Well I removed the Ezdoc camera from my entire computer, then I installed the latest addon Manager from FSDT. I started up FSX and it asked me about Coutle and permission,
I haven't asked to disable just one module. I've said to remove *everything* except the bglmanx.dll from the dll.xml, and then:
- Launch FSX and see if it works. If it does, re-enable every module, one by one, check if FSX works, enable another module, and so on, until you find the conflicting one.
So please, try this first.
I gladly gave and then the infamous window Microsoft Flight Simulator has stopped working popped up.
Have you rebooted Windows before trying it again, which I think was already suggested several posts ago ? Reboot Windows, try again and ALLOW the module to run, even if it crashes, and try a couple of times but please, REBOOT Windows at least once.
If still doesn't work, to this:
- Go in the Windows control panel, and Uninstall ALL the istances of the Visual Studio 2005 redistributable runtimes. You might have more than one version, remove them all.
- Then, after removing everything related to VS2005, reinstall again these 3 files:
http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en
One after the other one, in this order. Use always the vcredist_x86.exe, even if your OS is 64 bit, we are dealing with 32 bit apps, so they need a 32 bit runtime.
-
If I didnt tell you how this happened already, I will tell you. Perhaps it might shed some light. I am with a team called Touch and Go Films, and we make flight sim videos especially for FSDT. The vice president of TAGF offered me the program with a registration key. Now I already owned several other airports like JFK, KLAS, OHare, Ft Lauderdale etc.... When he gave me the key on skype for KDFW, I copied it and pasted it in the registration window. That is when it all went Bonkers and fsx shut off. I then removed KDFW and purchased it if that was a problem. But it didnt solve the problem. I believe that key had some type of virus in it and it's on my computer still since I didnt reformat the hard drives, I removed FSX and reinstalled it several times that week but its that key that is somewhere in my computer that needs to be removed. Now was I wrong to use Spencer's key which he claimed to be authorized to give out to me since Im part of Touch and Go Films. Thank you and I hope that info helps. Spencer had the same thing happen to him on his computer before if happened to me when installing KDFW. Thank you again
Marc
-
A Serial Number can't contain a "virus", this is just not possible. If you are using someone else's key, these are the ONLY possible outcomes:
- The original user hasn't used up all his activations yet. In this case, the scenery will just be reactivated normally.
- The original user has used all his activations. In this case, there will be just a message of having exceeded the available activations, and the scenery will work in Trial mode, without any problems, for 5 minutes at time.
As I've said, many times already, you HAVE to follow my initial suggestion (which was repeated 4 times, yet you keep ignoring it), to first disable every module in your DLL.XML except the Addon Manager, and check if it works. This might work or not, but at least we can check for potential conflicts caused by different versions of the VC++ runtimes used by different installed modules.
Or, as an alternative, to remove ALL the VC++ 2005 runtimes installed in your system, and reinstall them from the links provided in the previous message.
Your issue is that you can't accept the problem is NOT the scenery, but is something that has gone wrong in your Windows installation (not your FSX installation, that's why it's useless to reinstall FSX), and that is what you need to find out, and I've provided several resolution steps. If you are really sure it's not caused by the antivirus and you properly disable it, it's very likely is related to problems with your VC++ runtimes, which is why I'm suggestion the above methods.
You'll not going to fix anything if you continue to assume there was a problem with the activation, the key, or anything related to our software or that it might have been the *cause* of this, when in fact is the opposite way around, and it's something that has gone wrong in your system that has *caused* the software to stop working.
-
I have Microsoft Visual C++2005 Redistributable 2 of them and Microsoft Visual C++2008 ATL Update kb973924, Microsoft Visual C++2008 Redistributable 4 of these, and
Microsoft Visual C++2010 x64 Redistributable too. Do you want me to remove all of these and replace with the ones you told me to and wont it effect other programs on my FSX.
Thanks
Marc
I did try removing these before and it didnt work but perhaps I did something wrong.
-
Yes, remove them all, both 2005 and 2008, including the ATL update. Then reinstall only the 2005 versions FIRST, and test if it works. Then, add the 2008 version, and test.
There was a known bug in a version of VC++ 2008 runtime that, if installed, would create a conflict with the 2005 ones. We use the 2005 ones, because they are installed and required by FSX itself.
-
what about Microsoft SQL Server 2005 Compact Edition [ENU] and Microsoft Visual C++2010 x64 Redistributable. I removed C++2005's and 2008's and then installed what you asked me too and it didnt work yet. So the SQL and 2010 are the only ones left. Im trying, I really am. Thank you.
Marc
-
I don't know about the SQL redist of the VC++ 2010 redist, perhaps they also come with libraries that affect the 2005 redist.
You can try removing those as well but I think you have to do the whole process from scratch meaning, you have to remove *everything*, then start with the 3 2005 ones, and stop there, to test in FSX.
-
SOLVED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
This was solved with the help of Brad Robbinson from FrameFreaks88 on YouTube. In less then 3 minutes and going into the "Regedit" file under HKEY_CURRENT_USER and then SOFTWARE file. In there you will find the FSDreamteam Folder that is stored there from the time you original installed it. Inside it has all the records of what you purchase and all the bugs too if you happen to get one when registering. Well, he erased the fsdreamteam from there and said, "try it now, it should work" with his English accent, so I did. And it worked and so does Quality Wings. Brad is a Genius. Let's here it for FrameFreaks88. Brad your the best. Thank you to the team at FSDT for sticking with me in trying to figure this problem out. Brad should be made an honorary member because he deserves the credit. Thank you....
Marc
-
It would be interesting to know *what* exactly you had in the registry, possibly a strange/non-ascii/illegal character that you mis-typed when registering ?
Or, something too long (like thousand of characters) in place of the Serial Number, as if you pasted the whole email instead of just the Serial ? Knowing this would help us fixing this problem in the future.
-
that's what I was trying to tell you. When I copied the register that has been given to us at TAGF, I copied as the whole message by accident and just pasted it and then pressed enter. That's when everything went wrong because I believe it copied the entire post and not just the registration key. Anyway it is all solved now and Im happier than ever. Seriously you guys should make Brad Robbinson part of your team, this isnt the first time helped me with fsx and he is a wiz at it. Thank you again.
Marc
-
that's what I was trying to tell you. When I copied the register that has been given to us at TAGF, I copied as the whole message by accident and just pasted it and then pressed enter.
Well, you only said it happened when you copied the registration code, you haven't said anything about having copied the whole message, this might have helped. Perhaps it's a Skype issue, that insert strange characters which are not visible but create problems in the dialog screen.
In any case, nobody had this problem before (most of users either use the integrated purchase, which insert the code automatically, or they paste from *their* email, not from someone else's code on Skype), that's why we started with the usual diagnostic steps.
-
well thank you Umberto for sticking with me and trying to resolve it with me. I know it was difficult, I have to help friends too with their rigs when things go wrong with fsx and it is not always easy trying to figure out fsx. Thank you again.
Marc
-
Hello,
Finally I joined to nice FSDT sceneries(KJFK-KDFW-LSZH) and QW757 users this week. :)
But I have exactly this problem:
My EZDOK camera stop working and I receive this message "FSX process not found. FSX_handle:0" inside of Ezdoc window. :(
I didn’t understand how marc solve his problem , please advise me with simple words and step by step please if possible.
EZDOK camera by flight1 is “must have add-on for me”
many thanks
Bob
-
My EZDOK camera stop working and I receive this message "FSX process not found. FSX_handle:0" inside of Ezdoc window.
That's not really relevant to this or our products, that message is coming from EZDOK program which, apparently, can't find the FSX running process.
-
My EZDOK camera stop working and I receive this message "FSX process not found. FSX_handle:0" inside of Ezdoc window.
That's not really relevant to this or our products, that message is coming from EZDOK program which, apparently, can't find the FSX running process.
Yes , you are right but when I disable Bglmanx.dll in dll.xml this module (EZDOK) is working again! ???
-
Yes , you are right but when I disable Bglmanx.dll in dll.xml this module (EZDOK) is working again! ???
That doesn't mean it's a bglmanx.dll problem.
The most likely source of potential conflict between two modules, is the C++ runtime library that they were compiled with and how they signal to Windows this, by using an embedded manifest file. Our module use the VC++ 2005 (SP1) runtime, which is the same as used by FSX and of course includes a proper manifest file inside to tell Windows about this. Even if this info might not tell much to you, it might be helpful if you report it to EZDOK developers, maybe they'll have an idea what the problem could be.
Another thing you can try, is to rearrange the *order* of the modules in the DLL.XML, this could make a difference.
-
Yes , you are right but when I disable Bglmanx.dll in dll.xml this module (EZDOK) is working again! ???
That doesn't mean it's a bglmanx.dll problem.
The most likely source of potential conflict between two modules, is the C++ runtime library that they were compiled with and how they signal to Windows this, by using an embedded manifest file. Our module use the VC++ 2005 (SP1) runtime, which is the same as used by FSX and of course includes a proper manifest file inside to tell Windows about this. Even if this info might not tell much to you, it might be helpful if you report it to EZDOK developers, maybe they'll have an idea what the problem could be.
Another thing you can try, is to rearrange the *order* of the modules in the DLL.XML, this could make a difference.
Rearranging the order of the modules in the DLL.XML did not help.
I reported your advice to EZDOK developer.
But here are my Microsoft Visual C++ 2005 Redistributable status on "Programs and Features" Win7 64:
Microsoft Visual C++ 2005 ATL Update kb973923 – x86 8.0.50727.4053 (250KB)
Microsoft Visual C++ 2005 Redistributable (426KB)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 (2.52MB)
Microsoft Visual C++ 2008 Redistributable – x64 9.0.30729.4148 (788KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.21022 (3.51MB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148 (596KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.17 (238KB)
Regards
-
Rearranging the order of the modules in the DLL.XML did not help.
I reported your advice to EZDOK developer.
But here are my Microsoft Visual C++ 2005 Redistributable status on "Programs and Features" Win7 64:
The installed runtimes don't look wrong. However, just being installed, doesn't ensure all their files are in good order. Since you have the latest version of the 2005 runtime (4053), try this alternate bglmanx.dll, with is linked against that one, and see if it makes any difference:
www.fsdreamteam.com/download/setup/bglmanx/4053/bglmanx.dll
If it doesn't, it's very likely an issue with EZDOK.
-
I'm new here ... but I too have this same issue. I admit, I didn't read every page here in this thread but skipped to the last couple pages. I thought it would be best to keep all this in the same thread, but, I can make a new one if that is what I should do.
I have registered copies of your JFK, PHNL, and Hawaii 1 scenery's....they all work great, zero issues. KLAS is installed but still in trial version.
I'm interested in buying DFW but get the bglmanx.dll warning. What is different with this package compared to the others?....soon as I delete DFW things are great. I once had ezDok installed but didn't like the product so I uninstalled it. I see that there is a bglmanx.dll alternate, but I am unsure where to put it.
Specs: Win7 64, FSX only, tons and tons of addons
Thank you.
Mike
EDIT: Also...I don't have nor use any anti-virus software
-
...found where to put the file, but still have the same problem.
Mike
-
Can you contact me via email (address is on the "Contact Us" page ) ? I would like to run some tests.
-
Done
Mike