FS9 support > Los Angeles support FS9
Failure to register and sequent buffer overrun error **SOLVED**
virtuali:
--- Quote from: TheRedBadger on April 06, 2022, 04:22:46 pm ---Ah sorry, I meant should I register the serials for the sceneries in the simulator and then install the new addon manager (and that's it)?
--- End quote ---
No, you must install the scenery first, THEN update the Addon Manager and THEN you can register.
TheRedBadger:
I'm not sure what's going on, but now everytime I install the scenery with the installer, fs9 boots but then crashes at the splash screen before I can even think about registering anything. Removing the sceneries manually from the scenery.cfg yields the same results. This has been a disaster.
I can reinstall the entire simulator and try again but the critical action is installing the dang scenery which results in a permanent boot-and-crash event of the simulator.
Observations:
-I will say uninstalling all the sceneries allowed the sim to run fine.
-WHen installing ORD or DFW, I get a buffet overrun error on boot... uninstalling it fixes the trick.
-When installing LAX, the splash screen loads, then quits.
I'm not even going to try JFK.
Doesn't seem like I'm allowed to use any of the FSDT sceneries right now.
I wonder if those uninstalls are as "clean" as they need to be to successfully be able to install them again. Maybe there's something conflicting I need to take care of?
virtuali:
--- Quote from: TheRedBadger on April 07, 2022, 07:23:47 am ---I'm not sure what's going on, but now everytime I install the scenery with the installer, fs9 boots but then crashes at the splash screen before I can even think about registering anything. Removing the sceneries manually from the scenery.cfg yields the same results. This has been a disaster.
--- End quote ---
You should NOT remove the sceneries manually, you are only making it worse. Undo everything you did, use ONLY the proper Uninstaller to uninstall ( which is not even required ) and don't touch anything manually.
There's only ONE method that works.
- Install the scenery using its own installer
- DO NOT start the sim but, instead, install the Stand-Alone Addon Manager for FS9.
- If you need to install another scenery, you MUST reinstall the Stand-Alone Addon Manager for FS9 AGAIN. That's why, as I've said in my first post, install the Stand-Alone Addon Manager for FS9 as the LAST thing you do, after all the sceneries you have, otherwise you'll have to reinstall it several times, because it must be always reinstalled after a scenery.
Also, you haven't said anything about your OS.
While the new Addon Manager for FS9 surely works, provided you follow the instructions of ALWAYS installing it last, there's no guaranteed it will work with older and unsupported OS, like Windows 7 or XP. We only tested it with Windows 10, although it's likely will work on Windows 8 but, since January 2020, when Windows 7 went completely out of any support, we can only guarantee support for Windows 8 and up, with a strong suggestion of using Windows 10, which is the only OS we test our software with.
TheRedBadger:
--- Quote from: virtuali on April 07, 2022, 11:14:01 am ---
--- Quote from: TheRedBadger on April 07, 2022, 07:23:47 am ---I'm not sure what's going on, but now everytime I install the scenery with the installer, fs9 boots but then crashes at the splash screen before I can even think about registering anything. Removing the sceneries manually from the scenery.cfg yields the same results. This has been a disaster.
--- End quote ---
You should NOT remove the sceneries manually, you are only making it worse. Undo everything you did, use ONLY the proper Uninstaller to uninstall ( which is not even required ) and don't touch anything manually.
There's only ONE method that works.
- Install the scenery using its own installer
- DO NOT start the sim but, instead, install the Stand-Alone Addon Manager for FS9.
- If you need to install another scenery, you MUST reinstall the Stand-Alone Addon Manager for FS9 AGAIN. That's why, as I've said in my first post, install the Stand-Alone Addon Manager for FS9 as the LAST thing you do, after all the sceneries you have, otherwise you'll have to reinstall it several times, because it must be always reinstalled after a scenery.
Also, you haven't said anything about your OS.
While the new Addon Manager for FS9 surely works, provided you follow the instructions of ALWAYS installing it last, there's no guaranteed it will work with older and unsupported OS, like Windows 7 or XP. We only tested it with Windows 10, although it's likely will work on Windows 8 but, since January 2020, when Windows 7 went completely out of any support, we can only guarantee support for Windows 8 and up, with a strong suggestion of using Windows 10, which is the only OS we test our software with.
--- End quote ---
Yup. I uninstalled using the uninstaller for each sim (using "unins000" or something for each). Only once did I do uninstall manually when I wasn't sure what to do. I haven't done it that way again.
I've a Windows 10.
Though I admit running the sim before installing the addon manager is redundant and perhaps troubling, not sure why that would cause a crash instead of simply keeping the scenery from loading. Just seems overkill.
I just followed the instructions provided. I tested only DFW by installing it with the installer.exe file, then I installed the addon manager using the given .exe file, and only then did I run the simulator.
It did its usual routine with any new scenery, and then it crashed again. Seems like regardless of what I do it crashes on boot. Not sure what's causing it but it is related to something fsdt. I checked programs and features and certainly there's no trace of any FSDT scenery installed.
Here's something: I checked the eventviewer and it spits this out:
Faulting application name: fs9.exe, version 9.1
Faulting modlue name: bglman.dll, version 1.9
and then some other stuff repeating the same stuff differently. Again this only happens when I have any of these sceneries installed. Could it be that module isn't compatible with them? I have fs9.1 installed. I'm not touching anything for now.
virtuali:
--- Quote from: TheRedBadger on April 08, 2022, 05:49:22 am ---Yup. I uninstalled using the uninstaller for each sim (using "unins000" or something for each).
--- End quote ---
The easiest way is, instead, uninstall from the Windows Control Panel, which always starts the correct uninstaller. Especially if you uninstalled manually once, those unins000 files might not doing anything, because they might be leftovers from previous installations which weren't uninstalled correctly.
--- Quote ---Though I admit running the sim before installing the addon manager is redundant and perhaps troubling, not sure why that would cause a crash instead of simply keeping the scenery from loading. Just seems overkill.
--- End quote ---
Nowhere I said you should do that. In fact, I said exactly the opposite:
--- Quote ---DO NOT start the sim, DO NOT start the sim but, instead, install the Stand-Alone Addon Manager for FS9.
--- End quote ---
There's always a reason why I post a suggestion and it's if a program crashes, sometimes Windows automatically set some keys in the registry to "help" you run it the 2nd time, like wrong compatibility options, and those are related to the filename. Since the filename of the file ( bglman.dll ) won't change, even if you update it, the wrong compatibility setting would still be in effect, even if the new version didn't require it. In fact, not even the old version required it, it's just Windows that silently set these keys without even asking, because you had a crash with the previous session.
--- Quote ---I just followed the instructions provided. I tested only DFW by installing it with the installer.exe file, then I installed the addon manager using the given .exe file, and only then did I run the simulator.
--- End quote ---
That's better but, because of that registry issue, it's possible that file won't run anymore, unless the key are cleared. Check this thread here:
http://www.fsdreamteam.com/forum/index.php/topic,16389.0.html
In your case, the name of the file would be bglman.dll, not bglmanx.dll, but it's otherwise the same.
Also, BEFORE you start the sim again, be sure you have the whole FS9 folder added to the antivirus EXCLUSIONS.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version