FSDreamTeam forum
FS9 support => JFK for FS9 => Topic started by: flyboy4165 on May 12, 2013, 04:12:49 am
-
Hello hello,
I recently had to do a reinstall of FS2004 with new cds, as my previous disc was scratched beyond any reasonable measure. Upon every attempt to reinstall FSDT sceneries - And I've purchased and enjoyed JFK, ORD, DFW, HNL, LAS, KOA/OGG, along with the Cloud9 LAX (which itself is having difficulty finding the eseller component) - FS2004 crashes with the cheery little note of "Microsoft Flight Simulator has stopped working; A problem has caused the program to stop working correctly." I've attempted to reinstall FS2004 and then the FSDT sceneries numerous times, only to find my efforts were in vain and leading me to break out a glass of wine.
Please help! :)
-
For some added context, I'm not using any active antivirus software that would interfere with the software installation process.
-
I'm assuming you installed the SP updates after the reinstall?
Jim
-
Indeed I did, yes.
-
Be sure you download the most current version of the installers. Don't use something old you might have downloaded in the past. And install the Stand-Alone Addon Manager for FS9 as the last thing you do, especially if you install also old Cloud9 stuff that doesn't have the installer made by FSDT.
-
I downloaded the most recent installers and still encounter that dreaded message :/
-
So to recap, I've installed and re-installed a clean version of fs2004 and then the 9.1 upgrade. Following that, I downloaded fresh installers for JFK / ORD / HNL, installed the files into FS9, and every time FS2004 has crashed.
Any ideas what may be going on here? Someone at work performing Santeria on me, perhaps?
-
If you saw the Windows crash message, it means your crash has been recorded by Windows Event Viewer. If you open it (under the Administrative Tools in the Control Panel), look for that crash and post crash details, we might have a clue what is causing it.
-
This is what was posted in the "friendly" view:
fs9.exe
9.1.0.40901
4135a208
unknown
0.0.0.0
00000000
c0000005
754bc9f1
197c
01ce5114d08b0723
D:\Flight Simulator 9\fs9.exe
unknown
158a20df-bd08-11e2-8e91-9439e5d04d6b
Now as friendly as that looks, I thought I'd post the XML version as well.
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-05-15T02:35:20.000000000Z" />
<EventRecordID>28740</EventRecordID>
<Channel>Application</Channel>
<Computer>RyanFoley</Computer>
<Security />
</System>
- <EventData>
<Data>fs9.exe</Data>
<Data>9.1.0.40901</Data>
<Data>4135a208</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>754bc9f1</Data>
<Data>197c</Data>
<Data>01ce5114d08b0723</Data>
<Data>D:\Flight Simulator 9\fs9.exe</Data>
<Data>unknown</Data>
<Data>158a20df-bd08-11e2-8e91-9439e5d04d6b</Data>
</EventData>
</Event>
The above-mentioned data was copy-and-pasted immediately after another fresh install, application of the service pack, and installation of a FSDT scenery (HNL in this case). :)
-
The crash detail doesn't tell much, it's just a generic access violation error by FS9.EXE. Does it goes away if you remove the MODULES\BGLMAN.DLL ? Only remove that file, don't change anything else.
-
It does stop the crash, however the installed scenery - in this case, HNL - doesn't properly function. Instead of seeing terminal buildings, maintenance facilities, and the ever-rich textures of the scenery, it is concrete slab that abounds throughout.
-
It does stop the crash, however the installed scenery - in this case, HNL - doesn't properly function
Well, of course, that file is needed to display the scenery.
Try the following:
- If you are under Vista/Win7, try to disable UAC (User Account Control), you do that from the Control Panel, under the User Account settings.
- Also, 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/
OR
- try to run FS9 as Administrator.
OR
- Be sure the antivirus is not interfering, download and install with the antivirus OFF, then configure it to exclude the following files from scanning:
yourFS9Folder\MODULES\bglman.dll
-
Well, of course, that file is needed to display the scenery.
Just goes to show you how much I know about how all these different files work together.
I did all three steps that you mentioned and am still encountering the issue. I've disabled the UAC (as well as DEP), ran FS9 as an Administrator, made sure my antivirus software was not interfering with the file, and did all those things in concert with each other. Is there any diagnostic information I'd be able to send that might help figure out this mystery?
-
Is there any diagnostic information I'd be able to send that might help figure out this mystery?
Unfortunately, FS9 doesn't have any of the diagnostic tools that FSX has, so we will have to proceed by guessing.
First, try to download the files manually and put them in the FS9 MODULES folder:
http://www.fsdreamteam.com/download/setup/bglman/release_mscd/bglman.dll
http://www.fsdreamteam.com/download/setup/bglman/bglman.dat
http://www.fsdreamteam.com/download/setup/bglman/bglman_fsdt.dat
http://www.fsdreamteam.com/download/setup/bglman/bglman_skymakers.dat
http://www.fsdreamteam.com/download/setup/bglman/bglman_qwings.dat
And see if it makes any difference.
-
I input the bglman.dll file prior into the modules folder and upon insertion - without installing any of the other files - the program crashed again. Removing it, the program was just fine. Even renaming the file to bglman1.dll had the same effect.
-
I input the bglman.dll file prior into the modules folder and upon insertion - without installing any of the other files - the program crashed again
I've pointed to both .DLL and .DAT files, to have you download and install ALL of them. The whole point of this test (which is only valid if you download and update ALL of them) is precisely being sure that the .DLL is used together with the .DAT files is supposed to be used with.
-
Right then. I downloaded all of the files and input them into the modules folder. I'm still receiving the same message.
-
Right then. I downloaded all of the files and input them into the modules folder. I'm still receiving the same message.
Ok, now check for an eventual corruption of the .dll on your system: right click on MODULES\Bglman.dll, select "Properties" and check you have a "Digital Signature" field and check if it's reported as valid in the Signature details.
-
It specifies that the digital signature is OK.
-
That seems to indicate the cause doesn't have anything to do with our .DLL, it's possible the problem lies in one of its dependencies.
Check for the following file:
Esellerateengine.dll
In the following locations:
1) Your FS9 root folder
2) The main C:\Windows folder ( if this is your Windows folder )
3) The C:\ProgramData\Esellerate folder
If you have this .DLL in your FS9 root folder or your C:\Windows folder, REMOVE IT, because it's the wrong location for Vista/Windows 7 and, also, it's probably the wrong (old) version of the .DLL that has been put there by another product that uses the Esellerate engine DLL.
You should have one and only one copy of that .DLL and, on a Vista/Windows 7 system, it should be located at C:\ProgramData\Esellerate, which is where our installer puts it.
When you removed all the versions, reinstall the scenery again.
-
I checked all three folders and it only appears (correctly) in the C:\ProgramData. The file is version 3.6.5.0 if that makes any difference.
-
Would backing up my entire hard drive on a cloud storage site - and then giving you the requisite access - be of any assistance? Can't say you'd find anything on there all that exciting, though please don't ask about Halloween Elton John pictures.
-
Would backing up my entire hard drive on a cloud storage site - and then giving you the requisite access - be of any assistance?
What makes you think you need to backup the whole hard drive *just* to get remote assistance ? Are you afraid I'm reformatting you remotely ??
I don't think your issue can be fixed remotely, if you already made all the previously suggested steps, it means the problem doesn't have anything to do with any of our software modules, but it's a problem of your Windows configuration, some system files are probably corrupted/missing or not updated and they are *affecting* our module.
However, if you want to try a remote session with Teamviewer we can arrange that, I'll send you a PM with details later.
-
Lol not afraid of that at all; just thought that you might be able to see something that I'm not able to given your expertise in these matters.
Will send a PM out later today and take you up on that offer.
-
So for whatever reason, I am unable to view any messages (two so far) that I have sent to you in my outbox. What would be a good time to set up a remote access? I'm free all day Friday and Saturday, and will happily wake up early due to the time zone difference (in Las Vegas).