Disk Spanning Rules

InstallShield 2018

You can elect to have the Release Wizard automatically span your installation across as many disks as required. The wizard adheres to the following rules, which all multi-disk installations must follow. If you plan to customize how your installation spans across multiple disks, follow these rules:

Setup.exe must be on disk one. This rule is applicable if you want to ship your installation on floppy disks and you need to ship Setup.exe. The size of Setup.exe—depending on whether you choose one for Windows 9x, Windows NT, or both—can be 1.31 MB to 2.58 MB in size. The installation file for the Windows Installer service is included in the build as well. This file—called InstMsiW.exe or InstMsiA.exe, depending on the platform you choose—must also reside on disk one.
The second file that must be included on disk one is the .msi file that you are building. The total combined size of the .msi file, Setup.exe, and the Windows Installer installation files exceeds the maximum capacity of a standard 1.4 MB floppy disk. You have two options if you plan to distribute your setup on floppy disks:
You can distribute your installation without Setup.exe. This option is not available if you are creating an InstallScript MSI project.
The second and most feasible option is to use a distribution medium other than floppy disks.
Any transforms included in your installation must reside on the first disk. For example, if you create an installation with multiple run-time languages, an .mst file is created for each of those languages. This file is applied to the installation database, and it provides the language selected in the Language Selection dialog.
Redistributables (including merge modules) included in your installation must be stored on the first disk. Redistributables are streamed into the installation database while the script is built. This process cannot be completed if the redistributables are located on another disk.