
Configure extraction of files

This page allows you to decide how your files are extracted (unpacked) by the package onto the user's computer.

File Overwriting Mode

When an existing file is found, your package allows your end users to:

overwrite this file. Please note that Paquet Builder packages do not overwrite files that are write-protected by Windows. For example, running .exe, .dll files cannot be edited or removed. If an error occurs when the package tries to get a write-access handle to the output file, the corresponding message will be displayed to users.
ask end users for what they wish to do. This option is highly recommended if you use a standard package. If you choose this option, a dialog will prompt end users whether the given file should be overwritten or not (they can also decide whether the package should overwrite or skip all future existing files). See the screen shot below.
only overwrite older existing files. This option will cause the package to compare the file dates when an existing file is found. If the packaged file is more recent, then the package will replace the existing file. Otherwise it will skip this file.
skip existing files. No existing files will be overwritten if you choose this option, even if the packaged file is more recent.

Note: you can also check version information of executable files using the custom actions, and then determine whether a file should be overwritten or not using the file custom properties.

Miscellaneous Options

Overwrite files with read-only attribute: if the package has to overwrite an existing file and the latter is marked read-only (file attribute), then if you had enabled this option, Paquet Builder will remove the read-only attribute of the file and then replace it.
Replace in-use (locked) files at Windows startup: if the package has to overwrite an existing file and the latter is in use (locked) by another running process, then the package will display an error message (because the file cannot be replaced) unless you enable this option. In that case, the new file is stored in a temporary location and will replace the old version the next time Windows is started.

Notes:
- if a file needs to be replaced at startup, the package will set the %NEEDREBOOT% variable to "1". With custom actions, you can check the value of that variable at the end and then reboot the computer if required.
- This option also requires that the user runs the package with administrative rights.

Create a silent package: this will hide all dialog boxes including the progress indicator. All files will immediately be extracted to the folder you specified. Please note that the package would still display prompt messages and other user-defined dialogs (especially with the custom actions). This actually hides only common dialogs.
You can also enable/disable the silent mode at runtime thanks to the %SILENT% variable (for example, if you want to use the %PARAMS% variable which holds the command line parameters).

Allow end users to stop the extraction process: this will show a Stop button on the Progress indicator. If end users click on this button, a prompt will ask them if they really want to stop the extraction process. If they answer No, the extraction will continue. Otherwise it is immediately aborted and the package closes without removing the extracted files (no rollback feature is available: that's why the button is labeled "Stop" and not "Cancel"). This option also enables the system "Close" button of the dialog box.