I'm just trying to help you Umberto, if you don't want to believe me then not much I can do
I obviously believe it happened TO YOU, that doesn't mean there's a problem in the installer. As I've said, there might be other reason, depending what you did *outside* the installation, that might cause this, and it's not possible to say for sure, without having checked all the history of your file operations.
But frankly, the uninstaller should be able to detect other installed Virtuali products and simply NOT offer these two prompts as they could effective disable those products and that would be a situation that shouldn't be offered to an end user
The Uninstaller DOES the correct thing, which is ALERTING you that IF you reply YES to removing those modules you will lose your other installed products, but DOES offer you the choice to remove them anyway, because you might WANT to "clean up" your installation for many reasons. You will NOT lose the other installed product if you reply NO to both questions.
there is NO case where an end user would want to disable all their other Virtuali products when they are just uninstalling a single airport/product.
Every time you need a complete Uninstall, this should be accessible from any Uninstaller. Would you rather have an Uninstaller that doesn't even give you the CHOICE to remove modules that you might not want to run with FSX for any reason, with the only option to manually remove files ?
If the Uninstaller has the appropriate code/logic to determine how many products are already installed, it would know when it's uninstalling the last and final product and do the necessary code to remove those two key components.
That logic is ALREADY obviously there, and it works. If you reply NO to both questions, the Uninstaller KNOWS that the Addon Manager and the Couatl script engines are shared modules, and they are NOT removed "by default". "By default", means replying NO to both questions.
Now, it's obviously possible to use what you call "take the design logic one step further", which is a service offered by Windows and is called "Reference Counting", which is used by some Windows .DLL. Basically, every installer that needs to install a shared .DLL, will increase a counter for that file in the Windows registry, and every Uninstaller will decrease it. When the counter goes to zero, it means there's no need for that shared file, so it can be safely removed.
The obvious question would be "then why you don't use it ?" Because, of course, IT NEVER WORKS. Not in the real world. It works only in a perfect world of using never making any mistakes or never having any problems or never trying to fix problems themselves. It would be enough you remove this .DLL manually once, and the internal counter lose its sync and it's not reliable anymore. So, you will need a backup "cleaning" option anyway, which is what we have already...
But again, I'm just trying to help you avoid these types of support calls
It's for the exact precise reason to REDUCE support, that we have an option to make a complete removal, without having to rely to automatic methods which, as I've said, works only when everything is 100% perfect.
Fact that you believe the Uninstaller has a "bug", clearly proves this. There isn't one, you just ended up in some unusual situation that might have been caused by something made in the past.
As you can see many others have encountered the same issue, so it's not just me.
No, it's just you. You are suggesting there's an Uninstaller bug, but that's not the case. Don't confuse cause with the effect. There might be many reasons for losing a scenery, but they are not caused by a problem in the Uninstaller.
As I've said, I believe YOU had a problem during the Uninstall process but, again, it's not the Uninstaller that caused it, or that cause it under normal conditions, I can't say exactly why it happened to you, but I can't see many other reports of losing a product "just" by Uninstalling another one.
