If you use the Package and Deployment Wizard, the wizard creates the Setup.lst file automatically. You can edit the file manually after creation if you need to customize it.
The Setup.lst file describes all the files that must be installed on the user's machine for your application and contains crucial information for the setup process. For example, the Setup.lst file tells the system the name of each file, where to install it, and how it should be registered. There are five sections to the Setup.lst file:
For More Information See "Format of the Bootstrap and Setup1 Files Sections" for information on the syntax for these sections.
The BootStrap section contains all the information the setup.exe file needs to set up and launch the main installation program for your application.
Note Remember that there are two setup programs for your installation: setup.exe, which is a pre-installation program, and setup1.exe, which is compiled from the Setup Toolkit. The BootStrap section provides instructions to the setup.exe file.
The BootStrap section contains the following components:
| Component | Description |
| SetupTitle | The title to show in the dialog box that appears as setup.exe is copying files to your system. |
| SetupText | The text to show within the dialog box that appears as setup.exe is copying files to your system. |
| CabFile | The name of the .cab file for your application, or the name of the first .cab file for your application if your package has multiple .cab files. |
| Spawn | The name of the application to launch when setup.exe finishes processing. In most instances, this will be the setup1.exe file. |
| TmpDir | The location you wish to use for the temporary files generated during the installation process. |
| Uninstall | The name of the application to use as an uninstall program. In general, this is st6unst.exe, which is automatically packaged into all packages created with the wizard. |
The BootStrap Files section lists all the files that must be loaded on the user's machine before your application and dependency files can be loaded. These pre-install, or bootstrap, files include the core files required to run any Visual Basic application, such as the Visual Basic run-time DLL (Msvbvm60.dll). The setup program installs these files prior to installing and launching the main installation program.
The following example shows entries in a typical BootStrap Files section:
[Bootstrap Files]
File1=@Msvbvm60.dll,$(WinSysPathSysFile),$(DLLSelfRegister),1/23/98 9:43:25 AM,1457936,6.0.80.23
File2=@OleAut32.dll,$(WinSysPath),$(DLLSelfRegister),1/21/98 11:08:26 PM,571152,2.30.4248.1
File3=@OlePro32.dll,$(WinSysPathSysFile),$(DLLSelfRegister),1/21/98 11:08:27 PM,152336,5.0.4248.1
The Setup1 Files section contains all the other files required by your application, such as your .exe file, data, text, and dependencies. The setup program installs these files after it installs the core files listed in the Bootstrap Files section.
The following example shows entries in a typical Setup1 Files section:
[Setup1 Files]
File1=@LotsAControls.exe,$(AppPath),$(EXESelfRegister),,1/26/98 3:43:48 PM,7168,1.0.0.0
File2=@mscomctl.ocx,$(AppPath),$(DLLSelfRegister),,1/23/98 9:43:40 AM,1011472,6.0.80.23
The Setup section of the Setup.lst file is simply a list of information used by other parts of the installation process. The following table lists the information contained in the Setup section.
| Component | Description |
| Title | The name of the application as it will appear in the splash screen during installation, in the program groups on the Start menu, and in the program item name. |
| DefaultDir | The default installation directory. The user can specify a different directory during the installation process. |
| ForceUseDefDir | If left blank, the user is prompted for an installation directory. If set to 1, the application is automatically installed to the directory specified by "DefaultDir" in Setup.lst. |
| AppToUninstal | The name you wish to see as your application in the Add/Remove Programs utility in Control Panel. |
| AppExe | The name of your application's executable file, such as Myapp.exe. |
The IconGroups section contains information about the Start menu program groups created by the installation process. Each program group to be created is first listed in the IconGroups section, then assigned an individual section (Group0, Group1, Group2, etc.) that contains information about icons and titles for that group. Groups are numbered sequentially starting at zero.
The following example shows entries in a typical IconGroups section and related subsections:
[IconGroups]
Group0=MyTestEXE
Group1=Group1
[MyTestExe]
Icon1=my.exe
Title1=MyTestExe
[Group1]
Icon1=ReadMe.txt
Title1=ReadMe
Icon2=my.hlp
Title2=Help