- After an SFX installation, the installer will always delete all the files it has unarchived while leaving any files that were pre-existing intact.
- Because of the nature of the self-extracting installer and it's clean up of temporary files, the user will not be allowed to install into a directory that the installer is started from. There will be a message to that effect if the situation arises but it might be something that you mention in your readme.
- The SFX Installer will check free space on the current hard drive when it is about to unarchive and if it is marginal will ask for a new drive to place temporary files in. It will keep asking if the followup drives are marginal also. You can force it to try anyways by using the F parameter. We are considering whether to find space automatically instead of asking which drive to use but a decision has not been made relating to that yet.
- Previously you could not use the same name on an SFX Installer archive as a file inside your archive may have had. For example, if your widget program was called "Widget.exe" you could not use "Widget.exe" for the archive name. We have added an automatic renaming scheme but it needs a thorough workout to be sure it is mistake free so please make sure your archive works properly before you send it out.
There are some reserved names that are not allowed as they will conflict with names used by the installer. That should not be a problem for the most part though. They are:
- Install.exe
- Install.dat
- Install.log
- UnInstal.cmd
These files are deleted (if they already exist) and are rewritten each time an archive is built or when it is installed depending on the files usage.