Failure to register and sequent buffer overrun error **SOLVED**

[TheRedBadger]

I'm not sure what happened between now and months ago when I last used LAX. I flew into Burbank and I received a "trial period for LAX has started" message overhead, which was odd because I had already registered and installed the scenery.

Of course to my dismay I found out it was now de-registered for whatever reason, so I went to "register it" up top, which did nothing.

I restarted the simulator, loaded up LAX, same message, same tiral period ending.

I uninstalled LAX from FS9 which, for some reason also removed all the other FSDT products (even though I hadn't explicitly requested those be uninstalled. I did keep the addon manager when it asks me). Out of rage I re-entered the key twice in the same dialog window, hit enter, and then the simulator gave me a "buffer overrun" error, about the fs9 state being corrupted, and now I can't even use the simulator anymore, even after uninstalled LAX from the scenery..

First question is why I had experienced the initial trouble, second is how do I get myself out of this now even bigger problem without having to reinstall all of fs9 again.



EDIT: I have reinstalled the simulator (thankfully keeping addons this time). What would be the best way to reinstall all the FSDT sceneries? I recall hearing something about a different installer.

[virtuali]

About FS9, the only thing you need to do, is to install all the sceneries, and then, as the LAST thing you do, install the updated Stand-Alone Addon Manager for FS9.

The last step is required, otherwise there's no way to reactivate, because existing installers for FS9 still contains the old version that worked on Esellerate, which closed in 2019, the updated Addon Manager works with the new licensing system from QLM/Soraco. Just be sure you install it after all sceneries.

[TheRedBadger]

About FS9, the only thing you need to do, is to install all the sceneries, and then, as the LAST thing you do, install the updated Stand-Alone Addon Manager for FS9.

The last step is required, otherwise there's no way to reactivate, because existing installers for FS9 still contains the old version that worked on Esellerate, which closed in 2019, the updated Addon Manager works with the new licensing system from QLM/Soraco. Just be sure you install it after all sceneries.

Huh, that explains that. I suppose then the only solution would be a complete reinstall without the addon manager.

If I understand correctly, the addon manager is actually pretty old? I only see a 2007 program for it.

So I should "activate" the sceneries with the addon manager instead of through the normal way?



What if I choose to install a new FSDT scenery, hypothetically, and I already have the addon manager? Does something break or is it not allowed to install?

EDIT: oh I see its on the FSDT website by "fs2004".

[virtuali]

So I should "activate" the sceneries with the addon manager instead of through the normal way?

What do you mean ? The Addon Manager has ever been the only way to activate a scenery in FS9, it's just you need the updated version.

What if I choose to install a new FSDT scenery, hypothetically, and I already have the addon manager? Does something break or is it not allowed to install?

You'll have to reinstall the updated Stand-Alone Addon manager for FS9 again, after the scenery.

[TheRedBadger]

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)?

[virtuali]

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)?

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]

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.

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]

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.

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.

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]

Yup. I uninstalled using the uninstaller for each sim (using "unins000" or something for each).

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.

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.

Nowhere I said you should do that. In fact, I said exactly the opposite:

DO NOT start the sim,  DO NOT start the sim but, instead, install the Stand-Alone Addon Manager for FS9.

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.

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.

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.

[TheRedBadger]

Quote 2: that was me admitting I had no reason for doing so, not me asking you why I should be doing that.

Quote 3: no comment

Quote 4: FS9 has been added to exclusions. It was actually already there. I must have done that from a previous time.

Ok I looked at that thread and checked my registry under that same directory. Oddly enough I see something /different/. It references fs9.exe, and has under data "ignore free library": geartlk3.gau:runasadmin vistasetup One of the gauges I have installed in the sim.

We still know the bglman.dll is somehow problematic as referenced in the event viewer, but it doesn't appear to be the same exact case as this other fellow. I think there's multiple paths I can take here. I see you do mention fsdt live update to clear such a key, though that wouldn't address that bglman.dll

[virtuali]

Ok I looked at that thread and checked my registry under that same directory. Oddly enough I see something /different/. It references fs9.exe, and has under data "ignore free library": geartlk3.gau:runasadmin vistasetup One of the gauges I have installed in the sim.

That's the problem. In your case, it wasn't bglman.dll being set a wrong compatibility setting, it was the simulator *itself* which was forced to run in Windows Vista Compatibility mode, due to that gauge you installed, which made the sim crash and so Windows, trying to "help you", set the entire simulator to run in Vista  mode.

This will result in the same effect, so now every module will run in Vista mode, including our software, which doesn't probably work in Windows 7 either, so surely it won't work in Vista.

Remove the whole entry in the registry, so your FS9 will run as it should, with no Compatibility settings, which also have an effect on performances, since Video drivers underperform when using an older Windows Compatibility mode in Windows 10.

[TheRedBadger]

It still crashed after I deleted that entry :U . Event viewer still references the bglman.dll module (level: "error"). Everything has been installed in the correct order (scenery -> addon manager -> open fs9 -> crash on splash screen)

No new entries have appeared on the registry (meaning the deleted entry did not reappear)

[virtuali]

It still crashed after I deleted that entry :U . Event viewer still references the bglman.dll module (level: "error"). Everything has been installed in the correct order (scenery -> addon manager -> open fs9 -> crash on splash screen)

Try to use the new Universal Installer, it's not for FS9, but it *might* be able to fix some missing libraries in your Windows install that might fix this.

[TheRedBadger]

It still crashed after I deleted that entry :U . Event viewer still references the bglman.dll module (level: "error"). Everything has been installed in the correct order (scenery -> addon manager -> open fs9 -> crash on splash screen)

Try to use the new Universal Installer, it's not for FS9, but it *might* be able to fix some missing libraries in your Windows install that might fix this.

What you mean? Is this for windows 10 for installing any program? Not familiar with it but I’d think to look in flight sim.com for it when I can.

What’s you recommend after that?

I admit I had some trouble initially installing fs9.1 because it was “already installed” (it wasn’t) so I had to remove the BACKUP folder from the directory for the installer to work. I DID uninstall it before I reinstalled fs9, but the backup folder wasn’t removed when I had done that. Think this may be an issue with the modules? I don’t know if a complete reinstall would work, personally, as I’ve already done it a few times (albeit not in the right order). Just some thoughts for later