ckaack
Jr. Member
Posts: 68
|
 |
« on: May 31, 2009, 10:00:40 AM » |
|
Every FSDreamTeam scenery I am installing causes the following error message:
Clicking on "yes" crashes the FSX to desktop.
I have re-installed many times and manually deleted the bglmanx.dll without success.
Any idea?
|
|
|
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #1 on: May 31, 2009, 01:20:44 PM » |
|
This has been answered many times:
This error comes from a known FSX bug that, sometimes, a newly installed module that has just been trusted, will not run on the first try.
The solution is, instead of uninstalling, to allow the module to run, and not worry if FSX doesn't start the first time. Just launch it another time and, if the error still comes out, reboot Windows and try again.
|
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #2 on: May 31, 2009, 04:48:21 PM » |
|
Whatever I do FSX CTD once I clicked on Yes.
|
|
|
|
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #3 on: May 31, 2009, 05:26:57 PM » |
|
Don't worry if FSX crashes, try launch it again and, eventually reboot Windows.
Another issue might be that if, for any reasons, your FSX wasn't closed properly when you were installing the scenery, some files weren't updated.
Try to do the following:
- Go to the FSX root folder, and manually remove the following files: bglmanx.dll, and all the bglmanx*.dat files (there should be 3 of them, remove all)
- Reinstall any scenery, and try again, as usual, allowing the module to run, even if it crashes and, eventually, reboot Windows before trying again.
|
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #4 on: May 31, 2009, 05:46:38 PM » |
|
1) I have deleted in the FSX root folder the following files:
bglmanx_fsdt
bglmanx_aerosoft
bglmanx.dll
bglmanx
2) I reinstalled KLAS in adminmode
3) CTD during boot of FSX
4) Reboot of Windows
5) CTD during boot of FSX
Remark:
KORD and KJFK were running on the system but after installing KLAS the problem occured for the first time. When the problemn occured I removed all FSDreamteam products and now it doesn't matter which product from FSDreamTeam I am trying to install as noone is working anymore
|
|
|
|
« Last Edit: May 31, 2009, 05:48:24 PM by ckaack »
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #5 on: May 31, 2009, 06:19:09 PM » |
|
Are you running some kind of antivirus software ?
If yes, can you try to explicitely exclude the FSX root folder from virus scanning in the antivirus options, and then trying the whole process ?
|
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #6 on: May 31, 2009, 06:22:08 PM » |
|
I disabled the whole Anti-Virus Scanner
|
|
|
|
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #7 on: May 31, 2009, 06:31:58 PM » |
|
Try to open your FSX.CFG with a text editor like Notepad, located at
%APPDATA%\Microsoft\FSX
search for all instance of bglmanx.dll, to be found under the [Trusted] section, and remove every line that has a bglmanx.dll inside. Remove the whole line.
Then, launch FSX and check if you see the Windows dialog about trusting the module, reply YES to BOTH questions, the one from Windows, and the one from FSX that will come immediately after the Windows one.
|
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #8 on: May 31, 2009, 08:12:34 PM » |
|
I did remove one line which contained bglmanx.dll in FSX.cfg
I started FSX and I replied with "yes" and a 2nd time with "yes" and after a CTD occured.
|
|
|
|
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #9 on: May 31, 2009, 08:21:26 PM » |
|
As I've said, have you allowed the module to run, and you tried rebooting Windows after it didn't run at the first try ?
|
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #10 on: May 31, 2009, 08:26:11 PM » |
|
I clicked "yes" to allow the module to run. Virus scan and firewall were disabled. Than I had a CTD and reboot with the same result.
|
|
|
|
|
Logged
|
|
|
|
|
virtuali
|
|
« Reply #11 on: May 31, 2009, 09:04:22 PM » |
|
Could you install this utility here ? http://code.kliu.org/hashcheck/downloads/HashCheckInstall-latest.exeIt's a small shell extension that can be used to verify file integrity. After installing it, can you check the MD5 checksum for the following files ? bglmanx.dll bglmanx.dat bglmanx_aerosoft.dat bglmanx_fsdt.dat You can check the checksum, by right-clicking on each file, and selecting "Properties", then the "Checksums" tab, with several checksums will be listed. Post here the md5 for all 4 files. This will, at least, verify your files are not corrupted on your machine. |
|
|
|
|
Logged
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #12 on: May 31, 2009, 09:11:11 PM » |
|
Datei: bglmanx.dat
CRC-32: b24a9139
MD4: 44477632a335a3291f7df8a206323a31
MD5: 7b2eb2ed47c48aec72f4685bc5340f65
SHA-1: 1ac744061fa2bccbb153a4418678032914d2f048
Datei: bglmanx.dll
CRC-32: 0e768d55
MD4: 1ec6a1c99a0aeafb2f9509892ebde334
MD5: bba4bf7ef6df864530ed15bfa0d9e446
SHA-1: 8005b9e774a2df65f8afc862b6df88adb1a57e1b#
Datei: bglmanx_aerosoft.dat
CRC-32: b40a2380
MD4: dae2d891554f7dfdd875e0fcea818792
MD5: 99be4537ba1cf64270ecee6ee151446b
SHA-1: 2de613cfaf0a17a787e15ff2eea2af1258fcd01a
Datei: bglmanx_fsdt.dat
CRC-32: 37f51ea1
MD4: f1b861a0a7363dc131015c3cf303d1c6
MD5: 60597c3e837bbced742f291d28e8fb0f
SHA-1: 9fd8ec88f27dd7a42d0ae13474facda24705bd29
|
|
|
|
|
Logged
|
|
|
|
|
|
ckaack
Jr. Member
Posts: 68
|
|
« Reply #14 on: June 01, 2009, 06:12:09 AM » |
|
Okay will try this after returning from a business trip on June/12
|
|
|
|
|
Logged
|
|
|
|
|
