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.

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


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.
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.

If you can't find a user's 'custom' install path you'll get complaints too![]()


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!![]()
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.

