Logged In: NO The previous two commenters are only thinking of options available to developers. It's not that developers are unable to create installers with flexible silent options, it's that they don't bother to. This feature request is aimed at making silent installations easier for USERS, not giving NSIS script writers more scripting options.
Nullsoft Scriptable Install System (NSIS) is a script-driven Installer authoring tool for Microsoft Windows with minimal overhead backed by Nullsoft, the creators of Winamp. NSIS is released under a combination of free software licenses, primarily the zlib license. It has become a widely used alternative to commercial proprietary products. Silent Install Builder v5.1.4 + Crack What is the Silent Install Builder? The Silent Install Builder is a great tool if you need to quickly install a set of software on a multiple computers. Build silent installation packages The Silent Install Builder allows you to easily install multiple programs with one.
I'm talking about administrators that need to easily deploy an application to many desktops with absolutely no user interaction, or people that want to quickly install all of their favorite programs at once, such as from an unattended Windows install disk (see ). Currently, if an application's installer does not allow you to silently set the options you require, it has to be 'repackaged' instead, which means you lose all the logic/checking that was in the installer and just know what files/registries were changed.
![Version Version](http://makemsi-manual.dennisbareis.com/nullsoftinstaller.gif)
![Nullsoft nsis silent install Nullsoft nsis silent install](http://rsload.net/images4/Silent.Install.Helper.1.8.0.02.png)
There is currently no way I know of to decompile NSIS installers and set the options I want, therefore being able to add these options with NSIS script is useless. Some NSIS installers don't even obey the single /D=C: Bla parameter for the install directory! I know this is the developer's fault, and usually they just wrecked that functionality accidentally.
But seriously, when would NSIS script authors EVER need to disable command line options? I understand that you do not want to add any more feature bloat to NSIS, which I admire. So instead of adding commandline options that are embedded in every NSIS installer, my recommendation is this: create a tool that can be downloaded separately and allows administrators/users to silently set the options in an NSIS installer.
This tool would allow users to run the installer once and generate an options file, then later run the installer by way of the commandline tool, passing in the location of the options file. So it might work like this. To create an options file: silentNSIStool.exe /src='C: Installs Setup.exe' The tool would execute the NSIS installer and capture all the options entered by the user, then prompt the user where to save the options file. To run the installer silently: silentNSIStool.exe /src='C: Installs Setup.exe' /optionfile='C: Installs options.txt' /silent This would obviously require that the tool can parse the Setup.exe code or hook into it as it is running. I would expect that parsing the exe would work. Even if the tool can only create a list of all the input elements available to a user, that would be better than nothing. InnoSetup allows a good amount of options to be set on the commandline, such as install directory, whether to create start menu entries and where, which components to install, etc.
InstallShield works like this: Record a response file: Installer.exe -a -r Produces this file: c: Windows Setup.iss Install silently using the responses: Installer.exe -a -s -f1' MSI installers can sometimes be difficult to modify, but it's possible. There are some tools that allow you read all the public properties from an MSI file, which you can then set on the commandline during installation. Other tools let you run a fake installation and store the settings you enter into an MST transform file that can then be passed to msiexec.exe during installation.
As far as I am aware, NSIS has no features comparable to those other major install systems, which is why I am recommending this feature.
The CMake Win32 installer is built with NSIS, and as such, it supports some of the standard command line arguments that all such NSIS built installers do. If you build Windows installers for your project using NSIS and CPack, you can use this information with your installers, too.