Add uninstall information to Add/Remove Programs.This would be much more comfortable than writing all of the information on the command line. If your installer/uninstaller requires a lot of information and you want it to be able to be silent, you should allow the user to pass on a path to an answers file. Or: foo.exe /S /USERNAME="string with spaces" /D=C:\Program Files\Foo Or: foo.exe /S /USERNAME=string with spaces /D=C:\Program Files\Foo The user can use: foo.exe /S /USERNAME=Bar /D=C:\Program Files\Foo This allows the user to specify the required information on the command line instead of using the interactive user interface.
Removed Online Download feature due to domain being taken down.
Changed native loader code to reduce detections. Changed system calls to direct system calls thus reducing detections. The above example will copy the value the user passes on after /USERNAME= into $0. v1.5.1 () Added Process Killer feature that constantly checks for the 'Kill Targets' programs and kills them if found. If your installer/uninstaller requires some more information that can not be gathered when silent, you can allow the user to specify that information on the command line and process it in. To do that, the user uses the /D switch as in the following example: foo.exe /S /D=C:\Program Files\Foo Since the directory page is not shown in silent installers the user has an option to specify the installation directory on the command line (this also works on non-silent installers/uninstallers). The silent.nsi example demonstrates all aspects of this topic. All internal NSIS message boxes have defaults for silent installers. If you want your installer/uninstaller to be able to be completely silent you should use this switch. The MessageBox command, which is the most common culprit in silent installers, has the /SD switch to set a default answer for silent installers. To make sure your installer will be silent when it needs to, you should check with IfSilent before each command that might require user intervention or create a window. To check if the installer/uninstaller is silent use IfSilent. Passing /S on the command line (case sensitive).There are several methods to make an installer or an uninstaller silent: onGUIEnd, their uninstaller equivalents and any callback related to a specific page or page type will not be called. When an installer or an uninstaller is silent, not all callback functions are called.onGUIInit. NSIS installers and uninstallers can be both silent and not silent. It is also useful for other developers who wish to embed another installer in their own and collect all of the required information on their installer instead of showing two installers. This is useful for network administrators who wish to install or uninstall something without user intervention so they can perform the operation quickly over any number of computers. The user doesn't see any dialog and isn't asked any questions. Silent installers are installers which require no user intervention and have no user interface. Previous | Contents | Next 4.12 Silent Installers/Uninstallers