Media File Wizard: Installer Options

## Media File Wizard: Installer Options |

| In this step of the media file wizard you define options for the installer, most importantly the default installation directory.

| This step is different for installers and archives: Installers: Installation directory Enter a simple directory name (without backslashes). The standard location for applications will we prepended to this directory name. In other words: do not enter `C:\Program Files\MyApplication` but only `MyApplication` The installer will find out the correct equivalent for `C:\Program Files`, `/opt` or similar standard locations at runtime. By default, install4j will suggest the short name you have entered in the general application options. It is also possible to enter a composite relative directory like `My Corp\MyApplication`. Use custom installation base directory If you do not want to install your application to the standard application directory, you can enter a custom base directory here. This is useful for internal deployments with non-standard directory policies. The installation directory entered above will be appended to the custom base directory. For example, if the application should be installed in `D:\apps\MyApplication`, check the custom installation base option, enter `D:\apps` in the text field below it and enter `MyApplication` in the installation directory text field above. On Unix, if you want to suggest a directory below the user home directory, you can use ~ as the custom installation base directory. Archives: With the installation directory you determine the top level directory for the archive. All files will be contained in the top level directory. Enter a simple name without slashes, such as `myapp`. By default, install4j will suggest the short name you have entered in the general application options. For Mac OS X single bundle archives, it is not possible to set an installation directory since all files in a single bundle are in contained in a single directory whose name is determined by the name of the main launcher. The user can move the entire bundle somewhere else by dragging the displayed icon.

| For Windows installer media files, this step includes an option `Request admin privileges on Windows Vista` that allows you to compile the installer and uninstaller executables in such a way that Windows Vista will know up-front that the installer and uninstaller require admin privileges. If these privileges are not available, Windows Vista will present a dialog that allows the user to specify the credentials of an admin user. Select this option if your installer always requires admin rights on Windows Vista. This option does not replace the "Require admin user" action. Contrary to the cross-platform "Require admin user" action, this option is static and influences the way the installer executable is launched. When the "Require admin user" action is executed and the installer doesn't run with admin rights, the user is informed with a message box and the installer quits. If you do not select this option the execution level "Highest available" is used on Windows Vista. For a standard user the installer will run with the rights of this user. If the user is an Administrator with filtered rights, Windows Vista will ask him if the installer should be allowed to gain full administration rights.

| For Unix/Linux GUI installer media files, this step has a Installer custom script sub-step. If you specify a bourne shell custom script, the entered script fragement will be inserted into the launcher script immediately before the Java invocation of your installer takes place. This is a hook for experienced users to make custom changes in the environment. You can select one of: No custom script No custom script will be inserted. Custom script from file Specify a file from which the custom script will be read. If you enter a relative file, the file will be interpreted relative to the project file. Direct entry of custom script Enter your custom script in the text area below.

| For Linux RPM media files, this step has sub-steps where you can define scripts to run before and after installation or uninstallation by the rpm executable. The available hooks are: Pre-install script Post-install script Pre-uninstall script Post-uninstall script Please see http://www.rpm.org for more information. You can select one of: No custom script No custom script will be inserted. Custom script from file Specify a file from which the custom script will be read. If you enter a relative file, the file will be interpreted relative to the project file. Direct entry of custom script Enter your custom script in the text area below.