FSDreamTeam forum
Products Support => JFK for FSX/P3D => Topic started by: pamvdam on September 19, 2008, 07:55:29 pm
-
After I've installed KJFK and said yes for the modules to be trusted every time I startup FSX I get the same error/warning.
Flightsimulator has detected a problem with a third-party software program (add-on)
Name: bglmanx (dynamic ...)
Version: 2, 5 , 0 8
Company: Virtuali s.a.s.
File: bglmax.dll
Do you want to run this software (not recommended)?
If I say yes, FSX will crash. If I no, FSX will continue but no fdaddon menu will be accessible and I'm not able to use my earlier bought
Zürich and O'hare airports. I'm not happy about that.
My config:
FSX with Acceleration
Vista 64 with SP1
I've reinstalled the fsadoon package, with and without UAC, manually deleted the files and reinstalled. Nothing works till now :(
I'm open for any suggestions. Not being able to use the new KJFK is one thing, not being able to use the things I already purchased is another one.
Thanks in advance!
Best regards,
Pascal van Dam
-
During testing we found a reason for this crash might be a corrupted scenery.cfg file, if you could mail me your scenery.cfg file, I can check it and verify if this was your case.
If not, try manually delete all bglmanx*.* files in the FSX root folder (*.dll and the *.dat), REBOOT, then run again the JFK installer.
-
Thanks I will.
Where can I find this scenery.cfg file? In FSX root dir?
Best regards,
Pascal van Dam
-
Yes.
-
Ok. Here it is. (Renamed to .dat so I'm able to upload it)
[attachment deleted by admin]
-
Yes.
Nope.
The scenery.cfg file in use is not in the root dir. That one is just a backup copy of the original (without any addons), in case it needs to be restored.
The scenery.cfg in use is here:
%ALLUSERSPROFILE%\Microsoft\FSX
pamvdam, please check you are sending the right scenery.cfg file.
-
Ok. As I have my roots in UNIX/Linux probaby we've different understandings of the concept rootdir.. ;)
No problem. This must be the one you need.
Thanks in advance!
[attachment deleted by admin]
-
No problem. This must be the one you need.
GOT IT...
That's the scenery.cfg corruption in action. I've fixed it, now I bet the Addon Manager will run. As you can see, the file is now much shorter, look below for an explanation.
To everybody having the same problem:
There must be some 3rd party addon around that is corrupting the scenery.cfg. The affected lines are (how hironical) the scenery Titles for Cloud9 products. It's not a problem of Cloud9 products or our products, somehow, this installer is not able to properly deal with .INI files with characters outside the standard ASCII range. Because Cloud9 used the standard (c) Copyright symbol in the title, an installer should be aware of the correct encoding, not blindly parse it as if it were an ASCII text.
What happens is that, the (c) symbol for Cloud9 sceneries in the scenery.cfg, gets replaced by this faulty installer, with a *very* long (more than a thousand chars) string of random text.
Since our Addon Manager *also* parses the scenery.cfg at start, but does it in the "correct" way, with the official Windows API call to read INI sections, that long random string of texture that used to be the (c) symbol for Cloud9 areas, creates a BUFFER OVERFLOW, not in our code, but into the Windows API call itself, making the Addon Manager, and the whole FSX crashing with it.
There's no way we can fix it in the Addon Manager, because it's the Windows API call that gets confused, but we might be able to fix it in our installer.
For the time being, until we fix it in the installer, if you run into this issue, try to edit your scenery.cfg file, look for Cloud9, and change the area title to anything you like, removing the 1400+ characters long string that was created by an unknown installer of something else (it's surely a scenery).
If you are not comfortable with editing the scenery.cfg, just post it here, I've modified the forum config to accept .cfg files without renaming.
[attachment deleted by admin]
-
Also make sure you dont have Microsoft Visual C++ 2008 installed.
I had to reinstall Zurich and my Cloud9 sceneries and got the same message that you and others get with the new addon manager .
Tried all the suggestions from the FSDreamteam and it seemed that I was the only one who couldnt get it to work...........I reinstalled Visual 2005 and noticed 2008 below it.
Decided to get rid of it since I didnt remember installing it and its a trial/ beta.
Finally FSX loaded normally . Now I wouldnt have to reinstall FSX and my 110 Gigs of Addons just to get rid of that annoying message.......lol lol
Hope my lucky guess saves anyone else with the same problem from having thoughts of an FSX reinstall to get rid of that message .
Chris
-
Yep. Works here now.
Thanks! I'm going to buy the scenery!
Best regards,
Pascal van Dam
-
Hey, i'm new here...
I installed the FS9 version of JFK and it worked beautifully, so I bought it, then I proceed to install the FSX version and get a bunch of weird messages (see pic)
ALSO while installing the program AVG seems to identify a virus in the software... (no pic yet)
IDK if this has anything to do with it... Finally I checked my scenery.cfg (no cloud 9 sceneries and no random text strings)
I only have Visual C++ 2005 installed so thats not it either...
Any ideas???
[attachment deleted by admin]
-
I installed the FS9 version of JFK and it worked beautifully, so I bought it, then I proceed to install the FSX version and get a bunch of weird messages (see pic)
ALSO while installing the program AVG seems to identify a virus in the software... (no pic yet)
These two might be related. AVG is interfering with it.
Try this:
- Exclude the FSX folder from scanning in the AVG options.
- Uninstall JFK, reply YES to the question about removing the Addon Manager and the Couatl engine.
- Reboot
- Reinstall JFK
Finally I checked my scenery.cfg (no cloud 9 sceneries and no random text strings)
The current version that is online now, is now able to defend itself agains that kind of corruption, it will not crash even in that case
-
I installed the FS9 version of JFK and it worked beautifully, so I bought it, then I proceed to install the FSX version and get a bunch of weird messages (see pic)
ALSO while installing the program AVG seems to identify a virus in the software... (no pic yet)
These two might be related. AVG is interfering with it.
Try this:
- Exclude the FSX folder from scanning in the AVG options.
- Uninstall JFK, reply YES to the question about removing the Addon Manager and the Couatl engine.
- Reboot
- Reinstall JFK
Finally I checked my scenery.cfg (no cloud 9 sceneries and no random text strings)
The current version that is online now, is now able to defend itself agains that kind of corruption, it will not crash even in that case
I am having the same AVG Virus warning problem, it stated Threat detected - Virus found Win/32Heur
then under hidden details it shows this path C:\Users\USERNAME\AppData\Local\Temp\is-EMHAR.temp\jfk_fsx_setup.tmp
Process ID: 3976
I tried to ask AVG to stop watching FSX, but do i also need to ask it to stop watching hidden fsx folders.
I did your Fix ref Cloud9 Copyright logo, but am still unable to get JFK to install, but that could be the AVG issue?
Please help
Thanks
Jason
-
then under hidden details it shows this path C:\Users\USERNAME\AppData\Local\Temp\is-EMHAR.temp\jfk_fsx_setup.tmp
Process ID: 3976
I tried to ask AVG to stop watching FSX, but do i also need to ask it to stop watching hidden fsx folders
Not FSX hidden folders, it's the temporary folders that need to be excluded. If you see the AVG path, is not referring to the anything related to FSX, it's trying to block our installer even BEFORE it goes into FSX, when is still in the temporary folder, which is located at %TMP%
However, excluding the %TMP% folder might not be a good idea.
As you can see from the message about the supposed "virus", AVG calls it "Win/32Heur". Heur stands for Heuristic.
Which simply means "I don't have any evidence this is a virus, but it might be because it uses cryptography and other anti-tampering methods". Heruristic search means that, instead of looking in a database of virus, the program tries to make a wild guess.
I'd start by disabling Heuristic detection of viruses, if possible.
OR, try INSTALLING with the Antivirus entirely off, then exclude the FSX folder, and then reactivate it.
-
Somehow it just decided to work weird, maybe AVG just had to update or something???
-
Somehow it just decided to work weird, maybe AVG just had to update or something??
Yes. It happens everytime, especially with AVG live updates. One day they insert new heuristic voodoos searches, hundreds of legit applications probably stop working, people and developers complain, they fix it after a few days...
-
Sorry for taking so long to reply,
I sorted it, I turned of AVG then back on. Happy Days,
Great airport, Thanks
-
Installed O'Hare - started FSX and loaded scenery - everything was fine (and KORD looked awesome!)
Installed JFK - started FSX and loaded scenery - everything was fine (and again a beautiful scenery!)
Installed ZurichX - started FSX but got error
This means you have used an old installer for Zurich. The current installer for Zurich doens't contain any different Addon Manager that the other two. In fact, it doesn't contain *any* Addon Manager files, it gets them from the internet when it starts so, they are exactly the same files that KORD and KJFK used because, even their installers gets the same files from the same place.
Researched threads in this forum - Inspected scenery.cfg file - no characters at the cloud9 scenery entry
All information in the forum about that issue is now obsolete. The Addon Manager gets constantly updated, and it's now able to defends itself against a corrupted scenery.cfg
To fix the issue:
- Uninstall JFK, reply "YES" to the question about removing BOTH the Addon Manager and the Coual engine.
- Reinstall JFK. Verify that it works. It should, because you already know that it worked before.
- Download the current Zurich installer and install. You will notice that it will download exactly the same Addon Manager files as the JFK installer at start.
-
Beautiful!!! I am at work right now, but will do as you instructed as soon as I get home. I can't wait!
Thank You so much for the prompt reply. I knew it was just something you would be able to recognize right away.
From looking around these forums it's obvious you work hard to offer top notch support for your products. That makes me a lot more comfortable spending my money with you. You also must work hard to produce beautiful, accurate sceneries and it shows.
When I get this error resolved at home this evening I will be purchasing your current sceneries and most likely all future releases. When I find a company that consistantly produces quality scenery products for Flight Sim I end up buying everything they make. This way I end up flying to places I never would have thought to fly to!
Thank You again for the quick help and nice products,
Kail
P.S.: Sorry for all the @ss kissing, I'm just in Flight Sim nirvana right now. I went straight from FS2002 with almost no scenery add-ons to FSX with lots of scenery add-ons from you and the other Top Shelf design teams currently producing.
-
I have done as you instructed but I'm still getting the third party software warning about bglman.
I also re-downloaded the JFK and O'Hare installers in case one of them was corrupted when I downloaded previously. I uninstalled all three sceneries, made sure there were no bglman files in FSX root directory, then reinstalled with new installers and no luck. At this time I can not use my Orlando scenery as well.
What should I do next.
Thank You,
Kail
-
I have done as you instructed but I'm still getting the third party software warning about bglman.
This can happen when there's a mismatch between files from different versions.
Try to Uninstall JUST JFK, and (important) reply Yes to the question about removing the Addon Manager and the Couatl engine.
Then, reboot and, just to be sure, check there aren't any bglmanx.dll and bglmanx*.dat files in the FSX root folder.
Then run JFK installer again. Don't install any Cloud9 product after JFK. It's best if you install Cloud9 products before anything else, and before making the above clean up.
-
Ok, actually I just couldn't figure why this shouldn't work so I uninstalled, made sure there were no bglman files anywhere, then installed JFK. Started FSX, got the error, but this time when I hit yes to run it anyway FSX did not crash, it loaded. So I exited FSX, re-booted computer, started FSX, no error, all working. So then I installed Zurich, loaded, no problem, installed O'Hare, no problem. Now all is well!!!
So I purchased O'Hare and then JFK and I'll be sending you an email with my order numbers for the Zurich promotion.
Thank You so much for all of your help. I'm really going to enjoy these airports.
Kail
-
Started FSX, got the error, but this time when I hit yes to run it anyway FSX did not crash, it loaded. So I exited FSX, re-booted computer, started FSX, no error, all working. So then I installed Zurich, loaded, no problem, installed O'Hare, no problem. Now all is well!!!
Yes, unfortunately, FSX sometimes gets confused when a new module is ran for the first time. Exiting from FSX cleanly, the launching it again, usually works.
-
Hi
Last week the error showed up again out of the blue, so i uninstalled the add-on manager then re-installed your latest version.
The Error dissapeared then a week later it was back again. But I have a USB problem and bsod keyboard and joystick buttons stop functioning so I am going to do a full re-install over the next week(THIS IS NOTHING TO DO WITH THE YOUR PRODUCTS). So when i re-install how can i be assured that i wont have this problem again, Shall i avoid my cloud 9 products and Aerosoft florence until they are Sp2 updated.
Basically i want to avoid the BGLmanx add on error, if something is corrupting my cfg files i would rather avoid the product all together, as re-install take forever.
Would appreciate your help
Lastly shall i uninstall your products before I reboot and do i need to back up any FSdreamteam files, i normally just wipe the hard drive but i believe there is a backup file needed for your products
thanks in advance,
Jason
-
So when i re-install how can i be assured that i wont have this problem again, Shall i avoid my cloud 9 products and Aerosoft florence until they are Sp2 updated.
Basically i want to avoid the BGLmanx add on error, if something is corrupting my cfg files i would rather avoid the product all together, as re-install take forever.
As explained already in that post, nothing is "corrupting" anything. You don't need to uninstall antything, you don't need to reinstall anything. Unless you want to reinstall for other reasons.
This error sometimes appears when a new module is trusted, and only the first time FSX starts with the new module. You simply ignore the error, close FSX and it will work the next time FSX is run. This, of course, provided your FSX is updated to SP2 or Acceleration, and you don't have *other* system problems.
Also, I don't understand the comment about having to wait Cloud9 products or Aereosoft Florence to be "updated" to SP2. They are already compatible with SP2. The current version of the Addon Manager, that works only with SP2, is compatible with both, you don't need to wait for updates.
Lastly shall i uninstall your products before I reboot and do i need to back up any FSdreamteam files, i normally just wipe the hard drive but i believe there is a backup file needed for your products
As explained on the fsdt_install_guide.pdf, and of the sticky thread on the General section of this forum about "Reinstalling after a system reinstall or crash", you can use the "Backup RegKey" option, but it's not mandatory: as long as you have your email with your serial number, you can simply type the serial number using the "Register Serial" button. Note, this one is available only with FSDT products. Cloud9 and Aerosoft must use the "Backup RegKey" option.
-
I have just switched OS's from XP to Vista Ultimate. The same BGLMANX error is ocuring, but I can not find the scenery.cfg. Should I uninstall all OhareX and JKFX. I have the .reg backup files stores on a separate drive.
FSX SP2
Vista Ultimate
Sophos Antivirus
4GB RAM
Rich Friedlaender
-
I have just switched OS's from XP to Vista Ultimate. The same BGLMANX error is ocuring, but I can not find the scenery.cfg
The current version of the Addon Manager is able to defend itself against corrupted scenery.cfg created by others. So, anything you might have read on the forum about the scenery.cfg, no longer applies to the current version.
Just install the stand-alone Addon Manager that will update it to the current version. Also, it might be your antivirus that is interfering with it. You might try to configure the antivirus to exclude the FSX folder from scanning.
-
I too am having problems with just JFK. :-\
I downloaded the newest files from your website.
I installed the app and then started FS X. Error message. I uninstalled and then rebooted. I then checked the scenery.cfg, dll.xml and fsx.cfg files to make sure all was back to normal.
Started FS X, runs fine.
I 've installed and uninstalled JFK three times and with each install, I get the same error message.
Running Vista x64 Ultimate with SP1 and Acceleration. Running ESET for my firewall and virus protection.
I believe I've read and performed all items within this thread. Any new suggestions?
PatB
Quadcore Intel Core 2 Extreme QX9650, 3GHZ | Intel DX38BT | 4GB RAM | NVidia GeForce 8800 GT |
-
I too am having problems with just JFK
It's not possible the problem is JFK, since all products now use the same installer, which downloads just the SAME bglmanx.dll from the net, as soon as it starts. Please, verify this happens.
And, check that your firewall is granting online access to the installer, otherwise it wouldn't be able to download the most updated files.
I installed the app and then started FS X. Error message. I uninstalled and then rebooted. I then checked the scenery.cfg, dll.xml and fsx.cfg files to make sure all was back to normal.
As I've said, many times, uninstalling IT'S NOT the way to solve the issue! This error message is *temporary*, FSX sometimes BELIEVES a module has problem, but just the first time it launches it. If you simply ignore the error, ALLOW the module to run and try again, possibly after a reboot, it usually works on subsequent launches.
Running ESET for my firewall and virus protection.
If you still are having the issue, even after a reboot, and if you are sure the installer WAS able to downloads the current files from the internet when it started, try to exclude the FSX main folder from scanning in your A/V config, and try again.
Also, you might try INSTALLING with the A/V off because, if the A/V mistakenly identified the dll as a virus, it might have blocked the *udpate*, so you are still running the old version, or perhaps a mix-match of versions, which might create a crash.
Just for your info, the current version of the bglmanx.dll file, that you can check by right clicking to it and selecting "Properties->Details", is 2.5.1.2
-
I tried it again. Disabled my firewall and virus checker during installation and it downloaded all the files from your site. Started FS X (without fw and virus turned on). Accepted the addon(s) as a trusted app and bam, error message. Version of bmmanx.dll is 2.5.1.2. Have a nice screenshot if you want to see it.
I have FS X on another pc running Vista x32 Ultimate. This version does NOT have any other addons added at this time. I decided to try and install on this pc to see if app would run or crash. It crashed with same error message. :-\
Not sure as to what's going on. I've spent way too long on this to try and get it to work. I've decided to de-install for now and maybe, just maybe in the near future to try it again.
If you can think of anything else, let me know.
Thanks.
PatB
-
I tried it again. Disabled my firewall and virus checker during installation and it downloaded all the files from your site. Started FS X (without fw and virus turned on). Accepted the addon(s) as a trusted app and bam, error message.
You probably haven't read my last message carefully.
The first time a newly trusted module is launched, the message might show up. However, if you simply IGNORE the warning, let the module run anyway, the exit, and launch FSX again, the error will usually go away, sometimes it might require a reboot.
Instead, you are keeping uninstalling, when I've said that you don't need to uninstall anything, you simply need to run FSX at least twice.
-
What's the conflict with visual studio 2008? I use it all the time for dev work?
-
I don't think there should be a conflict with Visual Studio 2008 because, if there was any conflict, it would have been with the 2005 and 2008 C++ runtimes but, if the runtimes themselves were a problem, even FSX ITSELF would conflict with Visual Studio 2008, because FSX is using 2005 C++ runtimes. We use instead the 2005 SP1 runtimes, because they are much safer.
On a properly configured Windows system, thanks with the WinSxS loading system, all different runtimes should work without any problems.