Error 129

InstallShield 2019

Message

Media too small. Could not fit filename on disk number.

Troubleshooting Information

This error can occur for any of the following reasons:

Total size of files required to be on one disk is greater than selected disk size.
An installation requires that certain files reside on the first disk, including the files placed in the Support Files view (such as Setup.bmp and License.txt) and Data1.cab. Also, an installation requires that certain files be compressed in Data1.cab, including the following:
files needed by the objects you have included in your setup
resource files for each language your installation supports
the file for the dialog box skin you selected

If your installation includes a large skin, setup files, or objects—or a large number of support files, objects, or languages—the total size of files required to be on the first disk can be greater than the disk size you selected in the Release Wizard’s Media Type panel.

To avoid this error and complete the build successfully, you must either remove the skin or some support files or objects from your project, reduce the size of some support files or choose a skin with a smaller file, or select a larger disk size.

If the error message specifies a disk other than disk 1, some of the files in your components may be too large to fit on the disk even when they have been compressed. In this case, you must either remove the large files, reduce their size, or select a larger disk size.

There is not enough space on your drives.

To create the installation’s cabinet files, the release builder requires space in the system’s temporary folder and in the build location. To avoid this error, make sure you have enough free space on the drive on which the system’s temporary folder resides and the drive on which you have specified the build location.

You can find the system’s temporary folder by typing in the word "set" at a DOS prompt. The temporary folder is identified by the value of the environment variable TEMP. You can find the build location by looking at the Release Wizard’s General Options panel’s Advanced dialog box or the Release view’s Release Location property.

There is not enough virtual memory.

On Windows NT, this error can be caused by a lack of free virtual memory rather than a lack of free hard disk space. For information, visit Knowledge Base article Q102757.