• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Installer pain

I generally avoid installers where I can, though sometimes they're unavoidable.

Far to many don't uninstal correctly and leave files and folders behind. If they can't uninstal those what's the likelihood of their uninstalling registry changes?
 
Two places to look, adds to the fun...

EDIT: I did discover NSIS Dialog Designer recently, and I will need to go back a press the 'donate' button, since it does most of the work.

I didn't consult the SDK, but simply checked in the Registry of the machine on which I've got Prepar3D installed... So, kudos for checking the 64bit entry!

There a TON of very useful plugins and scripts for NSIS. Almost too many, actually... :D
 
I generally avoid installers where I can, though sometimes they're unavoidable.

Far to many don't uninstal correctly and leave files and folders behind. If they can't uninstal those what's the likelihood of their uninstalling registry changes?

Gerry, that is nearly always the fault of the person using the installer package by failing to read the instructions...

On the other hand, that's the sheer beauty of NSIS. You can't possibly use NSIS to create an install package without RTFM'ing. :D

As a bonus feature, the developer has absolutely full control over how the installer behaves.

It would be trivial for example to ask the end user whether they wish to "auto-install" or "install to a \Temp folder..." Give control to the end user...
 
Having designed applications myself, I would never use registry entries to look up information. You only need to focus on one file that is specific to flight simulator, even an .ini or a configuration file....also installer add to the programs list which gets messy if you install a lot of FS add-ons, I wouldn't do this in any of my applications.

Take that as a lesson, been there done that.
 
Having designed applications myself, I would never use registry entries to look up information. You only need to focus on one file that is specific to flight simulator, even an .ini or a configuration file....also installer add to the programs list which gets messy if you install a lot of FS add-ons, I wouldn't do this in any of my applications.

Take that as a lesson, been there done that.

Did I not write that NSIS allows one FULL and unrestricted control? Normally an entry will be made in the "Programs List" only if you create an "Uninstaller.exe." If you don't create an uninstaller, then there's no listing.

Of course, it's also trivial with NSIS to spoof that "autolisting" and still have an uninstaller for your product.

As for using Registry lookups, most of my advanced gauges require that handy feature!
 
Gerry, that is nearly always the fault of the person using the installer package by failing to read the instructions...

If you mean the developer I'd agree. I've lost count of the times I've installed an interesting looking application, accepting the default options, only to find that when it wasn't what I wanted and uninstalled it there were still folders and files left behind.
 
If you mean the developer I'd agree. I've lost count of the times I've installed an interesting looking application, accepting the default options, only to find that when it wasn't what I wanted and uninstalled it there were still folders and files left behind.

That's the main problem with installers, not that they are inherently dangerous, but that those who use them don't always test them properly, or understand the problems they can cause when not fully de-bugged.
 
If you mean the developer I'd agree. I've lost count of the times I've installed an interesting looking application, accepting the default options, only to find that when it wasn't what I wanted and uninstalled it there were still folders and files left behind.

That is precisely the person I was meaning. I just wasn't clear enough. The biggest problem with the ClickTeam installer is that it is just too inflexible in many ways, and relying on the "defaults" when asking for it to "autocreate" an uninstaller is just begging for trouble!

Just as a very simple example, unless the developer says differently, every bloody uninstaller ClickTeam creates uses the default program name "uninstaller.exe" for heaven's sake. How stupid is that!

Many developers use the ubiquitous "GaugeSound.dll" to support their sound system, so their installer blindly installs a copy in the ..\FSX root folder. No such file should ever be installed without checking first to see if the user already has a specific file installed, then only overwrite the existing file if it is a newer version.

Similarly, when uninstalling, that same file should not be uninstalled if it was there previously! That means that one needs to have the ability to customize the uninstaller, which unfortunately "ClickTeam" doesn't allow... :mad:
 
I use INNO scripting language to create installers. It's actually not that hard since there is this 3rd party GUI for the compiler called InnoIDE.
 
The Pro version of Clickteam Install has added functions...
"Do not install if a higher version of the file is already installed" is actually included.
I definitely agree these installers can be very dangerous tools.
Still I don’t see a practical alternative.
If you can't find a user's 'custom' install path you'll get complaints too :)
 
Last edited:
If you can't find a user's 'custom' install path you'll get complaints too :)

If I can't find the path from the Registry, then I fallback to the alternate scheme of searching all connected drives for the path to FS9.exe or FSX.exe as appropriate.

Over the past year or so, the biggest problem has been with those folks who have pre-built machines without a "C" drive at all. Why on earth any manufacturer would make "F" the system drive is beyond me! :yikes:
 
Over the past year or so, the biggest problem has been with those folks who have pre-built machines without a "C" drive at all. Why on earth any manufacturer would make "F" the system drive is beyond me! :yikes:

C: is a complete anachronism harking back to the days when A: and B: were 5in floppy drives and C: was a (very small) hard drive.

Keeping to the same principle, very few machines have floppy drives, so shouldn't the system drive be A:?

As the Bard said, "What is in a name?" :D

Edit. BTW, I abhor installers.
 
Last edited:
You have described me to a T. How far will I go to avoid an installer messing with my FSX folder? I rename my original FSX folder, create a dummy FSX folder to look like my original FSX folder, run the installer, then go through the renaming process in reverse. You can use a program like Regshot to take a before and after snapshot of your registry to see if the installer made any changes to that.

I use a somewhat similar approach to "fool" installers so that I can first "inspect" what is going to be installed. :idea:

I take an extra step of first temporarily changing the FS install path listing in Windows registry and setting it to the "dummy" FS install target folder chain.

However, one must remember to immediately go back and restore the FS install path to its actual location afterward, or that can cause other problems ! :o


I also put "dummy" text files renamed as FS9.exe" and/or "FSX.exe" (or just copies of the actual FS executables themselves) into the root folder of that dummy FS folder chain, as many installers first try to locate FS via the registry, and then check that the FS executable is present inside that root folder path .


Even when I already have first inspected ZIP-packaged FS add-ons, I use a very helpful freeware utility to install them, which actually writes on-the-fly, a convenient auto-un-installer for the "installed" ZIP contents : ;)

"ZipInstaller v1.21
Copyright (c) 2003 - 2004 Nir Sofer

The ZipInstaller utility installs and uninstalls applications and utilities that do not provide an internal installation program. It automatically extracts all files from the Zip file, copies them to the destination folder you select, creates shortcuts in the start menu and in your desktop, and adds an uninstall module to allow you to automatically remove the software in the future.

This utility was originally developed to install the utilities in NirSoft Web site, but you can use it for installing utilities and applications from other sources, like the utilities provided in SysInternal Web site, Funduc Software, and many others.
Generally, this utility can install properly almost any software compressed in Zip files that doesn't provide an install/uninstall module.
"

http://www.nirsoft.net/utils/zipinst.html


And when all else fails, Revo UnInstaller has the ability to "redirect" installs (if one reads the subtle inferences at a particular place in the documentation carefully !), and it can dig deeply throughout one's system and 'forcibly eradicate' all traces (including "hidden" traces !) of installed packages... and can almost always still do so even when packages were not first logged during installation: :p

http://www.revouninstaller.com/revo_uninstaller_free_download.html


Hope these ideas might help as well ! :)

GaryGB
 
Last edited:
After reading all these posts I'm getting concerned... maybe I should change.

I've used ClickTeam Pro for quite a few years and, yes, I have had a few bad events linked to not paying attention when including an installer. None of my later installers has ever had a problem locating FS9/FSX folder since I set it to look in the specific location in the registry, otherwise it defaults to a "Locate your main FS directory..."

I understand fully the desire to manually install things since my setup isn't the typical default format. I test my installers a few times before I release them on my WinXP and Win7 machines. So far nothing noteable has gone wrong. So far...

Mostly I create installers for my technologically challenged friends who understand not much more than turning on their PCs and starting their sim. I get so very tired of explaining the same simple installation proceedures over and over and over and over... But having both a zip-file and an installer is a great idea!

Anywho... guess I'll look into NSIS.
 
Back
Top