FSDreamTeam forum
FS9 support => Los Angeles support FS9 => Topic started by: TheRedBadger on April 05, 2022, 08:54:12 pm
-
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.
-
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.
-
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".
-
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.
-
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)?
-
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.
-
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?
-
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.
-
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.
-
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.
-
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
-
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.
-
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)
-
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.
-
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
-
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.
It's OUR Universal Installer, links to download it are on every page of our site, including the Home Page, 2nd line of the "News" section. As I've said, it's not made for FS9 but, just installing it might fix some things missing from your Windows install.
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
That seems to indicate some kind of problems. Have you upgraded to Windows 10 over an existing installation, or reinstalled everything from scratch ?
-
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.
It's OUR Universal Installer, links to download it are on every page of our site, including the Home Page, 2nd line of the "News" section. As I've said, it's not made for FS9 but, just installing it might fix some things missing from your Windows install.
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
That seems to indicate some kind of problems. Have you upgraded to Windows 10 over an existing installation, or reinstalled everything from scratch ?
Quote 1: I see it. Where should I install it? I have my FS9 directory outside of program files x86 (C:/Flight simulator 9 is the location). Should I let the installer install in prgram files x86 or
choose to install it in C:/Flight simulator 9? Does it matter?
Quote 2: If I understand you correctly, the computer was Windows 8 and upgraded to 10. However less than a year ago it had a major issue (I forget which one), so in the end Windows 10 was (likely, by the Dell technicians) installed from scratch.
I think doing a FULL reinstall of FS9 (as opposed to a partial one) might relieve some problems, even this one perhaps. I only did a partial uninstall to save all the copy/pasting of my large addons (taking close to an hour to transfer), though I may just rename my aircraft and scenery folders differently (Aaircraft and sscenery, for example) to keep the sim from deleting them. Thoughts? Would that work? I'll continue with your solutions for now but this is something simple I thought may work.
-
Quote 1: I see it. Where should I install it? I have my FS9 directory outside of program files x86 (C:/Flight simulator 9 is the location). Should I let the installer install in prgram files x86 or choose to install it in C:/Flight simulator 9? Does it matter?
In its own folder, even in the supported simulators ( FSX, P3D and MSFS ), it should always install in its own folder, which you can change, but shouldn't be "inside" the sim.
Quote 2: If I understand you correctly, the computer was Windows 8 and upgraded to 10. However less than a year ago it had a major issue (I forget which one), so in the end Windows 10 was (likely, by the Dell technicians) installed from scratch.
But do you recall running FS9 and FSDT products after reinstalling ?
I think doing a FULL reinstall of FS9 (as opposed to a partial one) might relieve some problems, even this one perhaps. I only did a partial uninstall to save all the copy/pasting of my large addons (taking close to an hour to transfer), though I may just rename my aircraft and scenery folders differently (Aaircraft and scenery, for example) to keep the sim from deleting them. Thoughts? Would that work? I'll continue with your solutions for now but this is something simple I thought may work.
Partial reinstall are always at risk, because you can't be sure what the original add-on installer did ( like replacing stock FS9 files ) and what their uninstallers were supposed to do ( restore them ) so, it might work sometime, that's why you might have read from some users that it worked for them, but you can't be sure it will always work for everybody.
That's why a proper reinstall, using all the add-on installers, is the safest way after an OS reinstall.
For example, one of the most common mistake FS9 users do when installing on a brand new PC, which usually comes without a DVD drive, is to install FS9, then upgrade to 9.1, and then install a "nocd" crack that was originally made for 9.0 onto their 9.1 install. This SEEMS to work, at a first sight, but mixing up all the 9.1 .DLLs with the 9.0 "nocd" .EXE will cause endless problems, in particular to our products, because the software needs to read directly in memory some data to create some effects like multi-seasonal objects, etc. because in FS9 there was no official API like Simconnect, and in-memory access was required, and that will fail if the .EXE and its associated .DLL are not exactly the same version, likely caused crashes.
-
Quote 1: Ok. I installed it but it still caused a crash during boot.
Quote 2: Oh yeah. I was able to use all the FSDT programs without an issue for months prior to some unexpected event. Like I said, I flew into Burbank and I noticed the "trial started for LAX", which was highly unusual as I had not made any changes AFAIK to LAX or FSDT recently.
Quote 3: Actually there's two patches; one for 9.0, one for 9.1. The flyawaysimulation site indicates installing 9.1 first before using the 9.1 patch. Unless you mean something different.
I think that's one of my last options. It /should/ work unless whatever damage is done is far more internal than fs9. If I do this, what sequence should I uninstall everything? I currently have all fsdt stuff installed including the addonmanager and fsdt update. I'd think uninstall the sceneries first (before the update and addon manager?), then 9.1, then fs9, and then reverse order.
EDIT: right now FS9 is uninstalled. No FS9.1, no FSDT, all my personal files are backed up. AFAIK everything's uninstalled correctly.
Side note, I noticed when fs9.1 is being installed, it references fs9.exe. Should the fs9.1 be installed /after/ the fs9.1nocd patch is installed?
Lastly, I know this is a lot of information, but, when and if I do install fs9 the first time, I get a "compatibility" issue. Should I just ignore this and say "fs9 was installed correctly"? I assume this is because I am just running fs9 on windows 10.
-
Side note, I noticed when fs9.1 is being installed, it references fs9.exe. Should the fs9.1 be installed /after/ the fs9.1nocd patch is installed?
The nocd patch should always be installed last, after the 9.1 update is installed. And, you must be absolutely sure it's a 9.1 NOCD patch. A nocd for 9.0 "seems" to work, but in fact it's not.
Lastly, I know this is a lot of information, but, when and if I do install fs9 the first time, I get a "compatibility" issue. Should I just ignore this and say "fs9 was installed correctly"? I assume this is because I am just running fs9 on windows 10.
I don't recall if I got that warning on install, but I assure you FS9 runs just fine with no Compatibility options set. In fact, it runs worse with such options enabled so, be sure Windows hasn't automatically set them for you.
-
It still crashes.... ugh.. I was hoping the nuclear option would just fix it as most solutions after that are tedious, high-difficulty and low success rate.
HOWEVER when I remove the bglman.dll file, the sim is able to load. But I know I can't just run without it since it does.... stuff. The event viewer still indicates that as the source of the crash, and there's nothing in the regedit referencing it either. I feel like there's nothing in my simulator that is causing the crash other than that one file.
I imagien without that file I can't run anything FSDT though.
-
I imagine without that file I can't run anything FSDT though.
No, you can't. I'm sorry but, other than saying it's supposed to work, I think I exhausted all solutions.
-
I imagine without that file I can't run anything FSDT though.
No, you can't. I'm sorry but, other than saying it's supposed to work, I think I exhausted all solutions.
No worries, I appreciate your help up to this point. I’m going to look elsewhere for potential leads. I will however post some other potentially important observations in case there’s anything overlooked later.
-
I imagine without that file I can't run anything FSDT though.
No, you can't. I'm sorry but, other than saying it's supposed to work, I think I exhausted all solutions.
Some more information prior to this mishap:
-I had been using JFK, LAX, and DFW FSDT for sometime without issues. Last time I appeared to have used LAX was in February (shockingly). DFW I use more often and I've had no issues with it.
-About a couple of days before the crash I had chosen to reinstall ORD and experienced no issues during installation. I think I did have to re-register it. I think.
-On that flight from DFW-BUR, DFW was working fine. It was then that LAX appeared to work in "trial period". Multiple attempts to re-register/activate it failed. Even after it had appeared on the drop-down menu to be already activated (I think), restarting the simulator would only result in the scenery buildings deactivating after a minute or two. That or entering the key did nothing.
Big issue here now that I think about it.
-Re-installing LAX from scratch to fix that trial period bug, I must have clicked on "remove addon manager" (out of haste) after the uninstall was complete, since the other sceneries appeared to have disappeared. LAX was the only one that was "re-installed", but again, it was in trial period again, even after seemingly having it registered again.
-The final blow was me pasting the activation key in the popup dialog /twice/, and then that's when the buffer overrun error hit, the sim crashed, and I was never able to get access back to those sceneries.
I may have mentioned that already, but I thought I'd explain it in more detail. Maybe one of those actions was fatally critical?
-
I had been using JFK, LAX, and DFW FSDT for sometime without issues. Last time I appeared to have used LAX was in February (shockingly)
The old Addon Manager might have worked and, if nothing happened in your system that would eventually triggered a reactivation (a Windows reinstall, a bios update, a major change of an hardware component ), you could foreseeably stay with the previous version "forever".
The problems would start if you had to reactivate for any of these reasons: THEN you MUST had the updated Addon Manager, since the Esellerate servers closed in 2019, so there would be nobody the old software could talk to, that's why you need the updated software, otherwise there would be no way to exit from Trial.
Since the new software is confirmed to work in Windows 10, I already listed all the the only possible reasons why it might not work for you, with all the known possible solutions:
- The Addon Manager MUST be installed last. If you reinstall any scenery for FS9, you MUST reinstall the Addon Manager again, because the installer might "downgrade" it to the Esellerate version, since we have updated the Stand-Alone Addon Manager for FS9, but not the single products installers, that's why the last thing you do must be installing the Stand-Alone Addon Manager for FS9.
- The antivirus might interfere, blocking the update or, even worse, blocking some files and let pass others, which will 100% result in a crash on start. This should be fixed by adding the WHOLE FS9 FOLDER to the antivirus Exclusions then THEN reinstall the Stand-Alone Addon Manager for FS9 again, to be sure the correct version is installed fully without antivirus interference
- You might miss some .NET libraries required by the new software to work. This shouldn't normally happen, since the Addon Manager installer will surely install them in FS9 and register them in Windows. That's why I said to try the new Uninversal Installer which, although the program itself is not used for FS9, it will install and register the same libraries, so maybe it would work, but that's not normally required.
You might try this last thing:
- Go in the Windows Control Panel, and UNINSTALL the Addon Manager for FS9 AND (important) reply YES to the question "Do you want to the remove the Addon Manager?"
- After the uninstall is complete, reinstall it again, maybe the previous uninstall manager to clean up some leftover files that needed to be removed.
-
The old add on manager (1.8?) is still under programs and features in windows 10. It may have been partially removed when I uninstalled LAX that one time but not correctly (saying “yes” to “remove the add on manager?”) . I do remember trying to remove it but IIRC I got some error along the lines of “the uninstaller ain’t here” or “already uninstalled”. I can’t remember, again I’ll reverify. Think that may be an issue?
-
As I've said:
- Go in the Windows Control Panel, and UNINSTALL the Addon Manager for FS9 AND (important) reply YES to the question "Do you want to the remove the Addon Manager?"
If you have multiple entries, uninstall them all.
-
As I've said:
- Go in the Windows Control Panel, and UNINSTALL the Addon Manager for FS9 AND (important) reply YES to the question "Do you want to the remove the Addon Manager?"
If you have multiple entries, uninstall them all.
When trying to uninstall the older version of the virtuali addon manager, it indicates it "cannot find unins001.exe. Make sure you typed the name correctly and try again". I did say "yes" to the addon manager question when uninstalling the newer, 1.9 version. I don't know if the older addon manager is actually still there.
A couple of scenarios: the older version is still lingering somewhere in my computer causing the crash and I have to find another way to remove it. Scenario 2 is that it is only listed in programs and features, but is actually not installed onto my computer anymore. Thoughts?
Actually did a search of "1.81" and found this (I know, only LAX is still installed but I can remove it if I need to next):
https://cdn.discordapp.com/attachments/852052198812549170/965094452534317187/unknown.png (https://cdn.discordapp.com/attachments/852052198812549170/965094452534317187/unknown.png)
I assume I should delete this? Won't do anything until your mark.
-
When trying to uninstall the older version of the virtuali addon manager, it indicates it "cannot find unins001.exe. Make sure you typed the name correctly and try again". I did say "yes" to the addon manager question when uninstalling the newer, 1.9 version. I don't know if the older addon manager is actually still there.
That's because you removed something manually, so you left the orphaned registry entry for the old uninstaller. You can remove the entry, so it won't appear on the Control Panel, but that's it.
My previous suggestions of installing the CURRENT Addon Manager once, uninstalling it by replying YES to the question "Do you want to the remove the Addon Manager?", then reinstalling it again, still stands to be sure nothing of the old version is left, the orphaned uninstaller won't cause any issues to the new files, once you do what I said to do. The most important part is:
- Only using the LATEST Addon Manager for FS9.
- Only installing AFTER all the sceneries.
- Do the double Uninstall/reinstall replying YES to the question "Do you want to the remove the Addon Manager?" THIS is what will trigger a clean up of all old files.
If that still doesn't work, then I'm afraid your problem is deeper into your Windows install, so we reached the end of the kind of support we could offer for a 19 years old simulator ( yes, FS9 came out in the Summer of 2003... )
-
When trying to uninstall the older version of the virtuali addon manager, it indicates it "cannot find unins001.exe. Make sure you typed the name correctly and try again". I did say "yes" to the addon manager question when uninstalling the newer, 1.9 version. I don't know if the older addon manager is actually still there.
That's because you removed something manually, so you left the orphaned registry entry for the old uninstaller. You can remove the entry, so it won't appear on the Control Panel, but that's it.
My previous suggestions of installing the CURRENT Addon Manager once, uninstalling it by replying YES to the question "Do you want to the remove the Addon Manager?", then reinstalling it again, still stands to be sure nothing of the old version is left, the orphaned uninstaller won't cause any issues to the new files, once you do what I said to do. The most important part is:
- Only using the LATEST Addon Manager for FS9.
- Only installing AFTER all the sceneries.
- Do the double Uninstall/reinstall replying YES to the question "Do you want to the remove the Addon Manager?" THIS is what will trigger a clean up of all old files.
If that still doesn't work, then I'm afraid your problem is deeper into your Windows install, so we reached the end of the kind of support we could offer for a 19 years old simulator ( yes, FS9 came out in the Summer of 2003... )
OK! So I did a factory reset of the computer (gosh that caused problems for 2 days..), installed the simulator before anything else, then 9.1, then the nocd patch, and then..
DFW, /then/ the addon manager, and finally the sim loaded without problems. I registered the simulator using the activation key I was provided and it quickly, without issue, successfully activated (even reading "activated" in the addon manager menu for DFW).
Question is (I may find out in a bit), do I need to re-register each scenery if I uninstall and then reinstall the addon manager?
Also, in the past when uninstalling the addon manager, it asks me after the fact "do I wish to remove the addon manager" even though I have already uninstalled it (didn't I?). Do I press "YES" everytime? Or does it not matter since I'll be reinstalling the addon manager anyways after I add a new scenery?
-
You can uninstall anything, your activation won't be lost. A new activation is required only if you change hardware.
Of course, if you uninstall the Addon Manager as well, no FSDT scenery will work, that's why there's a question about it when uninstalling a scenery, so you know if you do that, even *other* FSDT sceneries will stop working.
If you reinstall a scenery (they all come with an OLD Addon Manager that doesn't work anymore, since Esellerate closed in 2019 ) and try to run the sim without updating the Addon Manager, first not only the scenery will not work ( because the old Addon Manager cannot recognize the new QLM license, since it was made for Esellerate ), but it's possible you'll need to reactivate again, after you update the Addon Manager.
So, always update the Addon Manager last, whenever you need to reinstall a scenery.
-
You can uninstall anything, your activation won't be lost. A new activation is required only if you change hardware.
Of course, if you uninstall the Addon Manager as well, no FSDT scenery will work, that's why there's a question about it when uninstalling a scenery, so you know if you do that, even *other* FSDT sceneries will stop working.
If you reinstall a scenery (they all come with an OLD Addon Manager that doesn't work anymore, since Esellerate closed in 2019 ) and try to run the sim without updating the Addon Manager, first not only the scenery will not work ( because the old Addon Manager cannot recognize the new QLM license, since it was made for Esellerate ), but it's possible you'll need to reactivate again, after you update the Addon Manager.
So, always update the Addon Manager last, whenever you need to reinstall a scenery.
Aye I figured it out. Thanks for all your help