Annotation of mstools/mssetup/filedesc.wri, revision 1.1.1.1
1.1 root 1: 1� � � P [ [ [ [ [ \
2: FILEDESC.WRI
3:
4: This file contains a list of the files included in the Windows 3.1 SDK release of the Setup Toolkit and a short description of each file and its purpose.
5:
6:
7: ROOT directory.
8: Files comprising the Setup Program and Samples.
9:
10: Setup Executables.
11:
12: ...\SETUP.EXE Setup bootstrapper - DO NOT COMPRESS - copies setup .dlls, incs and _mstest.exe from a: to a temporary directory on the local hard-drive for execution. This avoids the problem of code segment discarding/ reloading after the original floppy has already been swapped out. The list of files to copy is contained in the SETUP.LST file (see next). The name of the temporary directory may also be specified in the SETUP.LST file. This .exe should NOT be compressed as it will be run by the end-user when installing YOUR program. This file must be on disk 1.
13:
14: ...\SETUP.LST Bootstrapper data file - DO NOT COMPRESS - contains a list of setup files to copy over to the tmp directory and other information. This file must be on disk 1. All files listed in SETUP.LST must be on disk 1.
15:
16: ...\_MSTEST.EXE Limited run-time version of MS-Test for Windows. This is the .EXE that runs the setup script (the .MST file), reads data from the .INF file and makes calls to the MS???STF.DLL libraries. This file needs to be listed in the SETUP.LST file and must be on disk 1.
17:
18: ...\_MSSETUP.EXE This is a special MS-DOS only program which is executed if Windows is restarted. This is only used when files marked as SYSTEM files need to be updated at Setup time AND they are locked by Windows, preventing this operation from succeeding without restarting Windows. If you have no files marked SYSTEM in your INF then you do not need to ship this file otherwise it needs to be listed in the SETUP.LST file and must be on disk 1.
19:
20:
21:
22: Setup DLLs. These files contain the code for the routines being called in your Setup Script. They are needed by _MSTEST.EXE. They need to be listed in the SETUP.LST file and shipped on disk 1.
23:
24: ...\MSCOMSTF.DLL Common Library DLL
25: ...\MSCUISTF.DLL Custom UI DLL - this should be customized using the SDK's Dialog Editor and the BLDCUI directory.
26: ...\MSDETSTF.DLL Detection Routines DLL
27: ...\MSINSSTF.DLL Install Routines DLL
28: ...\MSSHLSTF.DLL MS-Setup Shell Library DLL
29: ...\MSUILSTF.DLL UI - Library DLL
30:
31:
32:
33: Associated Include Files. These files may be included in your SETUP.MST script. If they are then they need to be listed in the SETUP.LST file and shipped on disk 1.
34:
35: ...\SETUPAPI.INC API definitions include file - contains prototype declarations for most Setup functions (required)
36: ...\MSDETECT.INC Detection API include file (optional but very useful)
37: ...\MSREGDB.INC MS-Windows 3.1 Registration Database Include File (optional)
38: ...\MSSHARED.INC MS-Shared Application Include File (optional)
39:
40:
41: Sample Files. Setup scripts and related .INF files. Only one set is necessary. They need to be listed in the SETUP.LST file and shipped on disk 1.
42:
43: ...\SAMPLE1.MST Sample setup script for a simple installation
44: ...\SAMPLE1.INF INF file for use with SAMPLE1.MST
45: ...\SAMPLE2.MST Sample setup script with a complicated Options Dialog
46: ...\SAMPLE2.INF INF file for use with SAMPLE2.MST
47: ...\SAMPLE3.MST Sample setup script for installing shared application files
48: ...\SAMPLE3.INF INF file for use with SAMPLE3.MST
49:
50:
51:
52: Help Files.
53:
54: ...\TESTDRVR.HLP Windows Help file containing descriptions of the Statements and Intrinsic Functions supplied by MS-Test for Windows. (Do not ship)
55: ...\FILEDESC.WRI This file. (Do not ship)
56: ...\README.WRI File containing extra information about the product and any last-minute change information. (Do not ship)
57:
58:
59:
60:
61: The BLDCUI sub-directory.
62: Files needed to build the MSCUISTF.DLL. Do not ship these - only ship the
63: resulting DLL built from them.
64:
65:
66: ...\DIALOGS.DLG The text file containing the Dialog Templates definitions used in the samples.
67: ...\DIALOGS.H The Header file containing the Constant declarations used in the Dialogs Template definitions.
68: ...\DIALOGS.RC The RC file used by the Resource Compiler to create the MSCUISTF.DLL. It includes DIALOGS.DLG and DIALOGS.H.
69: ...\DIALOGS.RES A version of DIALOGS.RC that has been compiled with the Resource Compiler. This file may be loaded directly into the SDK Dialog Editor.
70: ...\BLDVER.H Resource include file containing the Version Resource information. It gets included into DIALOGS.RC.
71:
72:
73: ...\DLGPROCS.C The C-File containing the Dialog Procedure code.
74: ...\CUI.H C-Language header file which contains prototypes for the functions contained in other MS-Setup DLLs, used in DLGPROCS.C and described in Chapter 2 of the Manual.
75:
76:
77: ...\SETUP.ICO The Setup Icon file which can be included in dialogs.
78: ...\BITMAP.DIB The "Microsoft Setup" logo painted on the background blue screen. You can replace this with a different .DIB file but it must be white on black.
79:
80:
81: ...\MAKEFILE A makefile to build the MSCUISTF.DLL using files in this directory. Contains a setting which determines whether a debug or ship version will be built.
82: ...\MSCUISTF.DEF DEF file for declaring library exports for the dialog procedures defined in DLGPROCS.C.
83: ...\CUISTF.LNK The ship-version link file
84: ...\CUISTFD.LNK The debug-version link file with CodeView information
85: ...\MSCOMSTF.LIB Import libraries for APIs in CUI.H
86: ...\MSSHLSTF.LIB Import libraries for APIs in CUI.H
87: ...\MSUILSTF.LIB Import libraries for APIs in CUI.H
88:
89:
90: The DISKLAY sub-directory.
91: Files comprising the Disk-Layout Utility. Do not ship these files - they are used
92: to generate one or more disk images and associoted .INF files.
93:
94: ...\DSKLAYT.EXE Disk Layout Front-End. This is a Windows/VB application that allows you to specify restrictions and attributes of the files you will ship with your product.
95: ...\DSKLAYT2.EXE Disk-Layout Back-End. This is a MS-DOS application which uses the information generated by DSKLAYT.EXE and creates compressed versions of your files, with a corresponding disk image of each disk copied to differently named directory.
96: ...\COLORLST.VBX VB Run-time Custom library. Required by DSKLAYT.EXE.
97: ...\VBRUN100.DLL VB Run-Time library. Required by DSKLAYT.EXE.
98:
99:
100: The INTLDLL sub-directory.
101: Files in the INTLDLL subdirectory are needed to translate the strings in
102: the DLL resources to localize a product for another country. Do not ship
103: these files -- they are used to generate localized versions of shipping .DLLs.
104:
105:
106: ...\MSCOMSTF.DLL Linked version of the Common Library which has not had its resources compiled in yet.
107: ...\MSCOMSTF.RC Uncompiled resource file for the Common Library.
108: ...\MSDETSTF.DLL Linked version of the Detect Library which has not had its resources compiled in yet.
109: ...\MSDETSTF.RC Uncompiled resource file for the Detect Library.
110: ...\MSINSSTF.DLL Linked version of the Install Library which has not had its resources compiled in yet.
111: ...\MSINSSTF.RC Uncompiled resource file for the Install Library.
112: ...\MSSHLSTF.DLL Linked version of the Shell (Frame) Library which has not had its resources compiled in yet.
113: ...\MSSHLSTF.RC Uncompiled resource file for the Shell (Frame) Library.
114: ...\MSUILSTF.DLL Linked version of the UI Library which has not had ts resources compiled in yet.
115: ...\MSUILSTF.RC Uncompiled resource file for the UI Library.
116:
117: ...\GAUGE.DLG Copy Files Progress Indicator dialog template used in MSINSSTF.RC.
118:
119: ...\BLDVER.H Resource include file containing the Version Resource information. It gets included each resource file. This is the same file as in BLDCUI.
120: ...\GAUGE.H Include file.
121: ...\IDS.H Include file.
122: ...\IDS_INST.H Include file.
123: ...\LOGIDS.H Include file.
124:
125: the MSCUISTF.DLL. Do not ship these - only ship the
126: resulting DLL built from them� � w � s � o � k .&