Program, Setup Execution¶

This page lets you open a document file or launch an application's executable file after a successful extraction, or specify the loader (executable file) of your Setup routine. For a standard package, this is the document file you wish to be opened when the package closes (optional).

Program/Document Filename (for Standard Package type)¶

Use this text box to enter the full path to the file you would like to execute after the extraction. If this is a document file like a text or help file, the associated application will be executed to view it. You may also enter an Internet address: for instance https://www.mycompany.com will open the default user's Web browser to the specified page.

Example: %DESTPATH%\Readme.txt will open the readme text file that was extracted to the default destination folder.

Setup Launcher Filename (for Package for a Setup routine type)¶

Enter the full path to the program file that will initialize your setup routine. The package will run in the background and wait until the end of the installation. After that it will remove all temporary files. It must be an executable file (extension .exe).

If you want to run a Microsoft Windows Installer package (MSI) or patch (MSP), enable the "Install a Windows Installer package" option. See installing Windows Installer packages with Paquet Builder.

Other options¶

These options are specific to a package type, unless it is noted "common".

Display an "additional task" check box on the final screen¶

(standard package only) You can optionally let your end users decide whether the document file specified above should be actually opened or not. If you do so, a check box will be displayed by the package on the final screen. If end users disable it, the document file will not be opened.

Such a check box is commonly called "additional task". Paquet Builder allows you to put such a task on the final screen, but if you need more additional tasks, you can also use custom actions to prompt users.

Properties of the check box include its caption: you can set the latter by entering the text in the "Task Description" field.

Run program as un-elevated process (with standard and not admin user rights)¶

(standard package only) If your package runs with administrative rights (defined by the manifest), any executable started by the package will also be run with administrative rights. To avoid this, you can turn this option "Run program as un-elevated process" on. Then, the application started by the package will be run with standard user rights.

Remove Setup files only at Windows startup (in case of a reboot)¶

(for Package for a Setup routine type) For advanced users only. Use this option if your Setup routine may require a computer reboot at the end (files in use that need to be replaced for instance).

If you enable this option, the package will still extract its files to a temporary folder and launch your Setup procedure, but it will also leave the temporary files even after the Setup loader ends (or at least until Windows restarts): an uninstaller is actually created in order to remove the Setup files and Windows is configured to run the latter at its next startup. Once it is run by Windows, the uninstaller will silently remove any temporary Setup files and folder. It will not however remove your installed application files!

Command Line Switches¶

If you would like to pass switches or any command to the executed file, please use this field. You may use variables which encapsulate the standard system or shell folders.

Use a fixed name for the temporary folder¶

(for Package for a Setup routine type) Some Setup routines may require their files to be in the same place. For instance, if you distribute a Windows Installer MSI package, Windows Installer will remember the original location of the .MSI file when running in Repair mode for instance.

If you want the package to unpack the temporary files always in the same temporary folder, please enter a unique name for the folder, such as "MyCompanyProgramSetupFiles". This ensures the setup files (MSI, CAB...) will always be available in the same location.