Category : Recently Uploaded Files
Archive   : VBHW18.ZIP
Filename : APPSETUP.INF
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
;
; Sample Installation Script -- 052094
;
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; About This File
; ===============
;
; This file, APPSETUP.INF, contains information that InstallWare uses to
; install applications. This file must be in the same directory as the
; program files IW.EXE(if used) and INSTALL.EXE. The two files can be on
; a floppy disk, a hard disk, or a network disk drive.
;
; The information in this file determines
;
; * The names of the disks and directories from which, and to which,
; InstallWare copies files.
;
; * The name of the group that InstallWare creates in Program Manager's
; window, and the names of program items that InstallWare adds to that
; group.
;
; You can create your own InstallWare program by changing some of the
; information in this file.
;
; The Parts of APPSETUP.INF
; -------------------------
;
; APPSETUP.INF is similar in format to a Windows initialization (.INI) file.
;
; Sections: APPSETUP.INF is divided into sections. Each section is identified
; by a name enclosed in square brackets.
;
; Most section names are "hard-coded". However, some section names
; are defined within other sections, and are therefore easily
; customizable.
;
; Comments: A comment begins with a semicolon. You can include a comment
; on the same line as syntax, as long as it comes after the syntax.
;
; Spaces: Spaces are ignored, except when between double quotes.
; Blank lines are also ignored.
;
; Sections in This File
; ---------------------
;
; The rest of this file contains the actual sections and statements
; that make up the working file. It also includes comments that
; explain each section and statement.
;
;
;
;
;
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; INFOFILE
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; The [infofile] section describes various miscellaneous aspects
; of the installation. The FILENAME label indicates the name of
; the text file that is shown to the user when the program starts
; up. The APPNAME label is used to refer to the name of the
; application being installed.
;
; The EXEFILE label is used to tell InstallWare that you would
; like to run a file after the installation is complete. This
; is useful for showing a readme file, unpacking some archives,
; or just starting up the program that was just installed. In
; the example below, note that the filename starts with a backslash.
; This indicates that the program is in the PATH. Otherwise,
; it is assumed to be located relative to the installation
; directory. The MESSAGE label denotes the text that will be
; displayed in the message box that prompts the user just before
; the EXEFILE is run. If there is no MESSAGE, then the EXEFILE
; is run without prompting the user.
; -------------------------------------------------------------
[infofile]
filename = Install.txt
appname = "VB HelpWriter"
exefile = "\notepad.exe readme.txt"
message = "Do you want to view the readme file?"
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; DIALOG
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; The [dialog caption] section is used to define the caption
; of the windows that shown in the INSTALL program.
; -------------------------------------------------------------
[dialog]
caption = "VB HelpWriter Installation"
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; DATA
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; The [data defdir] section defines the default directory. This
; directory is placed in the Install location editbox when the
; program starts. If the user does not change it, then this
; will be the base directory of the installation.
; -------------------------------------------------------------
[data]
defdir = C:\HelpWrit
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; DISKS
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
;
; The [disks] section defines the distribution disks that contain the
; application files. InstallWare uses this information to tell the user to
; insert the correct disk.
;
; Elsewhere within this .INF file, the distribution disks are normally
; referred to by a single-character disk ID. This section defines those
; disk IDs, and includes information about the disk to which each disk ID
; refers.
;
; The disk ID '0' is reserved; it represents the installation directory --
; the directory in which the user is installing the application.
;
; The format of each disk definition is:
;
; n = path, title
;
; where
; n is the disk ID (a single character from 1-9 or A-Z).
;
; path the path of the source directory from which InstallWare should
; copy the files to the disk. The path can be relative to the
; source directory (see examples below).
;
; title is a descriptive name for the disk. The title should match
; the disk's printed or written label exactly.
;
; The following statements would define two distribution disks.
;
; 1 =., "Demo Application Disk 1"
; 2 =.\files, "Demo Application Disk 2"
;
; The first statement tells InstallWare to refer to Disk 1 as "Demo Application
; Disk 1". Because the period (.) denotes the current directory, the files
; on that disk will be copied from the root directory of the
; distribution disk.
;
; The second statement tells InstallWare to refer to Disk 2 as "Demo
; Application Disk 2"; the files that Disk 2 contains will be copied
; from the \FILES directory of the distribution disk.
;
; You can include as many disk-definition statements as necessary. Every
; distribution disk should have a corresponding disk-definition statement;
; otherwise, InstallWare cannot tell the user to insert the appropriate disk.
;
; For the purposes of this file we will use this disk definition line:
[disks]
1 =., "INSTALL DISK"
2 =., "DICTIONARY DISK"
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; NEEDED.SPACE
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; This section tells INSTALL how much space is needed on the
; target disk to do a successful installation. The user will
; get an error message if they try to install to a disk that
; has less space.
; -------------------------------------------------------------
[needed.space]
minspace = 1000000
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; DEST.DIRECTORIES
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; The [dest.directories] section contains section-definition statements.
; Each statement defines a section that lists application files to be
; copied as part of installation. The sections are organized by file
; destination; you should define a separate section for each destination
; directory.
;
; Each section definition has the following form:
;
; #section_name, 0:dest_pathname
;
; where
;
; #section_name defines the name of the .INF section that lists the
; files to be copied.
; 0 is the disk ID that represents the installation directory.
; (0 is a reserved disk ID, and always represents the
; installation directory -- the directory the user specified
; when asked where to install the application.)
; dest_pathname is the pathname of the destination directory, relative
; to the installation directory. For example, "0:FILES"
; represents the FILES subdirectory of the installation
; directory.
;
; -------------------------------------------------------------
; In the example below, the first two entries define application
; specific directories. The #app.main directory will be the
; base directory defined by the user (or the default as
; described above). The #app.sub directory will cause a
; directory called sub to be created off of the base directory.
;
; The third and fourth entries refer to the two Windows
; specific directories: \WINDOWS and \WINDOWS\SYSTEM.
; INSTALL will find these directories and copy the specified
; files into them.
; -------------------------------------------------------------
[dest.directories]
#app.main, 0:
#app.SETUPSYSDIR, 0:SETUPSYSDIR
#app.SETUPWINDIR, 0:SETUPWINDIR
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; USER-DEFINED SECTION
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; This section is a user-defined section that lists files to be copied to a
; particular destination directory. The [dest.directories] section defines.
; the name of this section and the destination directory of the files.
;
; In each section like this one, you should list all files that you want copied
; to the same destination. (For example, all the files in this section,
; [app.user], will be copied to the installation directory.)
;
; InstallWare copies the files listed in this section in the order in which they
; are listed.
;
; The syntax of each file listing is
;
; N:FILENAME, "Description"
;
; where
;
; N: is the disk ID of the disk that contains the file. (Disk
; IDs are defined in the [disks] section.) If the specified
; disk is not in the disk drive, InstallWare prompts the
; user to insert it.
;
; FILENAME is the name of the file, including any filename extension.
;
; Description is descriptive text that InstallWare displays as it is
; copying the file or group of files. If you leave the
; description blank, InstallWare will continue displaying
; the descriptive text from the previous file. This lets
; you use a general name for a group of files.
;
;
; -------------------------------------------------------------
; This is the file list for the base directory.
; -------------------------------------------------------------
[app.main]
1:APPSETUP.INF, "APPSETUP.INF - Configuration File"
1:HELPWRIT.EXE ,"HELPWRIT.EXE - VB HelpWriter"
1:BUTTON3.DLL , "BUTTON3.DLL - Highedit v.2"
1:HEDLG.DLL , "HEDLG.DLL - Highedit v.2"
1:HEICON.DLL , "HEICON.DLL - Highedit v.2"
1:HEIMGMAN.DLL ,"HEIMGMAN.DLL - Highedit v.2"
1:HERTF.DLL , "HERTF.DLL - Highedit v.2"
1:HIGHEDIT.DLL ,"HIGHEDIT.DLL - Highedit v.2"
1:HETOOLS.DLL , "HETOOLS.DLL - Highedit v.2"
1:RTF.DLL , "RTF.DLL - Highedit v.2"
1:RULER.DLL , "RULER.DLL - Highedit v.2"
1:STATUS.DLL , "STATUS.DLL - Highedit v.2"
1:TAB.DLL , "TAB.DLL - Highedit v.2"
1:HE_BMP.DIL , "HE_BMP.DIL - Highedit v.2"
; 1:HECMDLG.VBX , "HECMDLG.VBX - Highedit v.2"
1:HEVB.VBX , "HEVB.VBX - Highedit v.2"
1:KEYWORDS.DAT ,"KEYWORDS.DAT - HelpGen table"
1:HCP.PIF , "HCP.PIF - PIF file for HC31"
1:TUTOR.HLP, "TUTOR.HLP - HelpWriter Tutorial"
1:HELPMAKR.ICO, "HELPMAKR.ICO - HelpWriter Icon"
1:ICON1.ICO , "ICON1.ICO - Sample Icon"
1:HEXCALC.BMP , "HEXCALC.BMP - Sample VB app"
1:HEXCALC.FRM , "HEXCALC.FRM - Sample VB app"
1:HEXCALC.MAK , "HEXCALC.MAK - Sample VB app"
1:GLOSSARY.SHG ,"GLOSSARY.SHG - Hypergraphic"
1:BULLET.BMP , "BULLET.BMP - Bullet lists"
1:README.TXT , "README.TXT - Latest info..."
1:TEST.DHP , "TEST.DHP - Test help compiler"
1:HELPWRIT.HLP ,"HELPWRIT.HLP - HelpWriter help file"
1:FILE_ID.DIZ, "FILE_ID.ZIP - Description file."
1:MACRO.LST, "Help Macros"
; -------------------------------------------------------------
; This is the file list for the \WINDOWS\SYSTEM directory.
; -------------------------------------------------------------
[app.SETUPSYSDIR]
1:MSGHOOK.VBX, "MSGHOOK.VBX"
1:VSVBX.VBX, "Videosoft's ELASTIC"
1:VSVBX.LIC, "Videosoft's ELASTIC"
1:MLIST.VBX, "Mabry's Listbox VBX"
1:CMDIALOG.VBX, "CMDIALOG.VBX - Windows common dialog vbx"
1:COMMDLG.DLL, "COMMDLG.DLL - Windows commond dialog dll"
1:THREED.VBX, "THREED.VBX - VB's 3D control VBX"
1:MMSYSTEM.DLL, "MMSYSTEM.DLL - Multimedia support dll"
1:CTL3DV2.DLL, "CTL3DV2.DLL - 3D support DLL"
1:VTSPELL.VBX, "VTSPELL.VBX - Spell Checking DLL."
; -------------------------------------------------------------
; This is the file list for the \WINDOWS\SYSTEM directory.
; -------------------------------------------------------------
[app.SETUPWINDIR]
; -------------------------------------------------------------
; This is the file list for the sub directory located off of
; the base directory.
; -------------------------------------------------------------
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; PROGMAN.GROUPS
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; The [progman.groups] section (optional) tells InstallWare to create Program
; Manager groups for your application. (InstallWare then uses DDE to
; communicate with Program Manager.)
;
; The section lists the names of the groups you want to create. You then
; define additional sections in this file; those sections list the program
; items you want in each group.
;
; The syntax for each group name is:
;
; groupname, [groupfile.grp]
;
; where
;
; groupname is the title you want Program Manager to display
; under the icon that represents the group. (The
; groupname will also be the name of the section
; that defines the contents of the group.)
;
; groupfile.grp is the filename of the file in which Program Manager
; will save information about the group. (You must include
; the .GRP filename extension.) This parameter is optional;
; if you omit it, InstallWare uses a default name for the
; group file.
;
; The following group-definition statement tells InstallWare to create a
; group named "Bob Dolan Shareware", and store its information in a file
; named BOBDOLAN.GRP.
[progman.groups]
VB HelpWriter, HELPWRIT.GRP
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; USER-DEFINED PROGMAN.GROUPS
; -------------------------------------------------------------
; *************************************************************
; -------------------------------------------------------------
; This section describes the Program Item Icon to add to the
; Program Group defined in the section heading.
;
; In each section like this one, you should list all items that you want
; InstallWare to add to the group.
;
; The syntax for item-definition statements is:
;
; "Description", APPFILE.EXE, [ICONFILE.EXE[, N]]
;
;where
;
; Description is the text that will appear below the program icon
; when displayed in the Program Manager group.
;
; APPFILE.EXE is the command line that starts the application.
;
; ICONFILE.EXE is the application file that contains the icon you
; want to represent the application. Typically, this is
; the executable application file, but it could be a
; different file. (You can also specify a .ICO file, created
; using the SDKPaint tool.) This parameter is optional; if
; you omit it, InstallWare will use the first icon it finds in
; APPFILE.EXE.
;
; N is the offset of the icon you want to use within the file
; ICONFILE.EXE. This parameter is optional; if you omit it,
; InstallWare uses the first icon it finds in ICONFILE.EXE.
; You must include this parameter if the file you specify
; contains more than one icon, and you want to use an icon
; other than the first icon.
;
; To use the Nth icon, specify the number N-1. For example,
; to use the third icon, specify 2.
;
; For example, the following item-definition statement tells InstallWare to add
; an item titled "Install" to Program Manager. The application command line is
; a file named INSTALL.EXE which is located in the SUB subdirectory off of the
; installation directory.
[VB HelpWriter]
"VB HelpWriter", helpwrit.EXE
"VB HelpWriter Help",HELPWRIT.HLP
; -------------------------------------------------------------
; -------------------------------------------------------------
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/