As just mentioned, Package and Deployment Wizard creates a special text file
named SETUP.LST for each application that you set up. SETUP.LST looks a lot like
an INI file (see the example in Listing 21.2). It has named sections with headers
surrounded by brackets. Each section, in turn, contains entries of the form:
ItemName=value
The entries under the [Bootstrap Files] and
[Setup1] sections are the names of files to be copied to the user’s
system. Each file entry contains a long comma-delimited list detailing the file’s
compressed and uncompressed names as well as installation instructions and version
information.
SETUP.LST’s [BootStrap] and [Bootstrap Files] sections contain information
about actions that SETUP.EXE must perform on the user’s system before the
main setup routine can run.
If the main setup routine is a VB program (as it always is if you have created
it with Package and Deployment Wizard), for instance, users may not have the necessary
files installed on their workstations to run a VB application of the appropriate
version. SETUP.EXE must copy and register the VB runtime libraries on the user’s
system before the main setup routine (written in VB) can run.
The Spawn entry under the [Bootstrap] section gives
the name of the main Setup routine. By default, it is SETUP1.EXE. The
[Bootstrap] section also gives other information about the setup environment
in general, including the initial dialog box title and prompt as well as CAB file
and uninstall information.
The [Bootstrap Files] section lists the files that
SETUP.EXE must copy to and register on the end user’s system before the
main setup routine can run.
A couple of other groups may exist ([Icon Groups] and
a section named with your application’s title) if you chose to create an
entry or a group for your application on the Windows Start Menu/Programs menu.
The [Setup] section contains general information
needed during the setup process, such as screen captions and install directories.
The [Setup1] section lists other files that the
main setup routine must copy to and register on the user’s system.
LISTING 21.2
CONTENTS OF A TYPICAL SETUP.LST FILE
[Bootstrap]
SetupTitle=Install
SetupText=Copying Files, please stand by.
CabFile=Project2.CAB
Spawn=Setup1.exe
Uninstal=st6unst.exe
TmpDir=msftqws.Package and Deployment Wizard
Cabs=1
[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,5/20/98 11:00:00 PM,102400,6.0.81.41
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),, 11/18/97 12:00:00
AM,22288,4.71.1441.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),,,5/21/98 12:00:00 AM,17920,2.30.4260.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,5/21/98 12:00:00 AM,147728,2.30.4260.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),, 5/21/98 12:00:00
AM,164112,5.0.4260.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),, 5/21/98 12:00:00
AM,598288,2.30.4260.1
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),, 5/21/98 12:00:00
AM,1417216,6.0.81.41
[IconGroups]
Group0=My Standalone
PrivateGroup0=True
Parent0=$(Programs)
[My Standalone]
Icon1=Project2.exe
Title1=My Standalone
StartIn1=$(AppPath)
[Setup]
Title=My Standalone
DefaultDir=$(ProgramFiles)\Project1
AppExe=Project2.exe
AppToUninstall=Project2.exe
[Setup1 Files]
File1=@Project2.exe,$(AppPath),,,11/14/98 10:42:55 PM,16384,1.0.0.0
; The following lines may be deleted in order to obtain extra
; space for customizing this file on a full installation diskette.
;
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
; XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
The developer may customize the setup process by changing the information in
this file with a text editor.
