;***********************************************
;***********************************************
; INFORMATION ABOUT AUTOMATED INSTALL
;
; Automated install is a feature that allows 
; users to run the Lotus Install program 
; without the user interface. This feature
; is particularly useful for system administrators
; who must manage installs and upgrades for 
; large groups of users.
;
; System administrators use this feature 
; by filling in the fields in this response 
; file (wordpro.rsp), and then making this 
; file available to end users. The information 
; you supply in this file provides input 
; to the Install program so it can run without 
; user intervention.
;
; NOTE: Only system administrators should edit 
; this file. Individual users should use the 
; response file provided to them by their system
; administrator.
; 
; 
; TO USE THE AUTOMATED INSTALL FEATURE:
;
; 1) Prepare the Response File:
;
;    a) Back up this file by copying it 
;       to a new name (wordpro.sav, for example)
;       so you can start fresh at any time.
;    b) In this file, provide the information 
;       for each field. Examine each default 
;       value to make sure it is the value you
;       want. Read the comments for each field
;       for information about legal values and
;       possible interactions with other fields.
;    c) Validate your response file by running 
;       an install that uses this file as input. 
;       (See the command line information below).
;       The Install program displays any errors 
;       that occur. Remember that if you are 
;       testing node installs, you must run a
;       server install first.
;
; 2) Make the Response File Available to 
;    End Users
; 
;    When your response file has no errors
;    and performs the install as you intended, 
;    make it available to your users with 
;    instructions about how to run the Install 
;    program. You might want to simply tell them
;    what command line to type from Program Manager,
;    or you might want to use the Object Packager
;    to create an icon they can click on. The best
;    distribution strategy depends on the tools 
;    you have available at your site.
; 
;
; TO RUN AN AUTOMATED INSTALL:
; Choose File Run from the Windows Program Manager,
; and type the install command:
;
; <path>\install /A <ResponseFilePath> [/U ["<UserName>"]] [/?]
;
; where:
;    path is the location of the install program
;         executable.
;    ResponseFilePath is the location of this file.
;         ALWAYS specify the full path to this file.
;    "<UserName>" is the name of the user to which
;         this copy of the program is registered.
;    /? brings up usage information.
;
;
; HINTS AND TIPS:
;
; Do not change the field names to the left 
; of the equal signs (=) in this file. 
; Changing the field names will cause errors.
;
; Do not remove fields from this
; file. Removing fields will
; cause errors.
;
;
;***********************************************
;***********************************************
; THE RESPONSE FILE STARTS HERE:
;
[User Registration]
; The [User Registration] section is for 
; information about the end user of this copy
; of the product. 
;
; Type the user's name in the "UserName" field. 
; Type the company's name in the "CompanyName"
; field. This information will become a 
; permanent part of the user's copy of this 
; program. If you do not supply this 
; information, the program will attempt 
; to find the user and company name from 
; a previously installed version 
; of this program (if there is one), or 
; from the Windows registration information.
;
;***********************************************
UserName = 
CompanyName = 
;***********************************************
;
[General Information]
; The [General Information] section specifies the
; type of install you want to perform, how to handle
; changes to the AUTOEXEC.BAT file, and the program 
; group to which you want to add the product icon.
;
; Use the "InstallType" field to specify the kind of install 
; you want to perform. 
;     1 Standalone Install
;     2 Server Install
;     3 Distribution Install
;     4 Node Install
;
;***********************************************
InstallType = 1
;***********************************************
;
; Use the "Autoexec" field to specify how 
; to handle changes that may be required 
; in the user's AUTOEXEC.BAT file.
;     1 Modifies the user's AUTOEXEC.BAT file 
;     2 Makes a copy of the user's AUTOEXEC.BAT file
;       that includes the changes the user must make to
;       the file
;     3 Makes no changes and no copy
;
;***********************************************
Autoexec = 1
;***********************************************
;
; Use the "ProgramGroup" field to name the program group
; to which you want to add this product's icon. 
; This field is used only if you are doing a standard, 
; server, or node install.
;
;***********************************************
ProgramGroup = Lotus Applications
;***********************************************
;
[Node Install]
; The [Node Install] section applies only 
; to node installs.
;
; Use the "NodeOptions" field to specify 
; whether the features selected by the 
; system administrator should be copied 
; to the node user's machine.
;      0 Do not copy the features to the user's 
;        machine
;      1 Copy the features to the user's machine
;
;***********************************************
NodeOptions = 1
;***********************************************
;
[Lotusapp]
; The [Lotusapp] section provides information 
; about Lotus shared components, such as the 
; Spell Checker.
; 
; Use the "Consolidation" field to specify 
; whether Lotus shared components that the
; Install program finds in different places 
; on the user's machine should be consolidated 
; into one directory.
;      0 Do not consolidate
;      1 Consolidate
;
;***********************************************
Consolidation = 1
;***********************************************
;
; Use the "LOTUSAPPDIR" field to specify the 
; location of the Lotus shared components.
; You may change the drive letter if 
; necessary, but we recommend that you 
; accept the default path \windows\lotusapp.
; 
; This field is normally used only if there
; has been no previous consolidation, or if
; the current consolidation location is 
; read-only or does not have enough room for
; all of the shared components. To confirm
; whether you have a consolidation location
; already, look for the "Common Directory"
; entry in your \windows\lotus.ini file.
;
;***********************************************
LOTUSAPPDIR = c:\windows\lotusapp
;***********************************************
;
[AMI]
; The [AMI] section provides information 
; specific to the Word Pro install.
; 
; Use the "SizeOfInstall" field to specify the
; size of the install:
;      1 Complete install
;      2 Minimum install 
;
;***********************************************
SizeOfInstall = 1
;***********************************************
;
; Use the fields in this section to select
; where you want to install Word Pro.
;    AMIDIR: Main product directory for Word Pro
;    AMIDOCSDIR: Document directory
;    AMISCRIPTSDIR: Scripts directory
;    AMIMASTERSDIR: SmartMasters directory
;    AMIICONDIR: SmartIcon directory
;    AMIDRAWSYMDIR: Drawing symbol directory
;
; For a server install, all directories listed 
; for Word Pro should be under one common root
; and should adhere to the following heirarchy,
; otherwise Node install will fail.
; 
;    AMIDIR        = \root
;    AMIDOCSDIR    = \root\docs
;    AMISCRIPTSDIR = \root\scripts
;    AMIMASTERSDIR = \root\smasters
;    AMIICONDIR    = \root\icons
;    AMIDRAWSYMDIR = \root\drawsym
;***********************************************
AMIDIR = c:\lotus\wordpro
AMIDOCSDIR = c:\lotus\wordpro\docs
AMISCRIPTSDIR = c:\lotus\wordpro\scripts
AMIMASTERSDIR = c:\lotus\wordpro\smasters
AMIICONDIR = c:\lotus\wordpro\icons
AMIDRAWSYMDIR = c:\lotus\wordpro\drawsym
;***********************************************
;***********************************************
;
;
;End of Response File
