First of all, what i ment with the "Aerosoft way" was that every scenery that I have bought from them works. I install a program (downloaded/boxed version), just insert the serial number and the program installs and WORKS. Never a question about BglManX.dll or any other file problem from FSX. Installs and runs.
This is not true for all products. ANY product that use a module to run, REQUIRES in FSX, that you TRUST the executable code, that's why there's the question about running a module or a gague.
This is exactly the same, and is valid for ALL products from ALL developers that use executable code, Aerosoft included, because you HAVE to Trust their modules as well (like the VistaMare.dll) otherwise their products will not work (not ALL, just the one requiring it, like AES), or you have to trust their gauges, and this is valid for ALL airplanes, regardless of the publisher.
So, it's not true that there are "no questions" about modules, because the question to trust an executable is valid for any executable that runs in FSX.
Also, about Aerosoft, it's not true either that "just insert the serial number and the program installs and WORKS" because, the very reason why I tried to help you on Aerosoft's forum, was because you wrote this:
When I start my FSX + Addpac I get an errormessage during the startup telling me that FSX is not compatible with a certain program/file and that the problem i Bglmanx.dll and also ViMacoreX.dll
To that, I replied trying to help you, pointing out that this is a known FSX problem that, as you wrote yourself, affected BOTH Aerosoft module (ViMacoreX.dll as I've told you already, VistaMare IS from Aerosoft) and ours as well (Bglmanx.dll) so, it's nothing specific to a module, it's a FSX problem. We think it's a combination of a FSX problem + a Windows issue with Trusting, because it's usually fixed after a reboot.
Now that we clearly pointed out that the problem is not specific to bglmanx.dll, but can affects any module, because as you said yourself, both modules were affected, let's try to understand why, on YOUR particular system, the usual solution that always works, which is to allow the module to run, and try again, and eventually reboot Windows, still doesn't work on our own module.
Try the following:
- If you are under Vista, try to disable UAC (User Account Control), you do that from the Control Panel, under the User Account settings.
- If you are under Vista, try to disable DEP as well, look here how to do it:
http://www.tech-recipes.com/rx/1261/vista_disable_dep_noexecute_protection_fix_explorer_crashing/- If you have an antivirus enabled, try to disable it, BOTH when installing AND when running FSX
- When you are installing the scenery, check that bglmanx.dll and .dat files ARE being downloaded with no errors.
