Modifying the Install.cfg File
You can control the DOS-based install program (install.exe) by modifying the install.cfg file. If you plan on Installing with ACU or Installing from the Network you should take the time to modify install.cfg for your networking environment. A Sample Install.cfg File is provided.
If you have several different groups of users who need to be upgraded, you might consider maintaining several different .ini files. See Using a Configuration File Other Than Install.cfg
IMPORTANT: If you are planning to install from Windows*, you must modify the setup.ini instead of the install.cfg. See Modifying the Setup.ini File
-
Set up a network install directory.
For more information, see Setting Up a Network Install Directory
-
Make sure you have a backup copy of install.cfg.
-
Open install.cfg (or the file you want to use for install information) in a text editor.
Install.cfg is in the NLS\language directory.
-
In the [SETUP] section, specify the InstallType for the install.
Basic allows users to make configuration changes. Auto requires no user intervention. For more information, see [SETUP] Options
-
(Conditional) If you specified Auto for the InstallType, configure default values for the protocols you want to install.
Make sure to set the Install parameter to True for each protocol you want to install.
-
In the [REQUESTER] section, enter default values for the preferred tree or server and add any defaults you want to include for this section of each workstation's net.cfg file.
For more information, see [REQUESTER] Options
-
(Conditional) If necessary, make changes to the [NIOS], [Protocol IPX], [Protocol TCPIP], [Link Support], [TCP/IP], [NWIP], [SNMP], [HOSTMIB], and [TSA] sections.
For more information, see Configuring Protocol and Management Support
Additional information about the install.cfg file is also available. See [driverTranslationTable] Section and Installation Files and Destination Directories
-
Save the file to the network install directory and exit the editor.
[SETUP] Options
The [Setup] section of the install.cfg maintains information for the DOS-based install. For example, you can configure the installation to run without displaying installation choices to the user.
Check the following table to make sure the options are set correctly for the installation you want to perform. (Note: Bold indicates default options.)
InstallType |
BASIC | AUTO BASIC is an attended installation that requires some user input. AUTO is an unattended installation that provides no user interface. |
TargetPath |
AUTO | path AUTO allows Setup to determine the target directories. Or you can enter a specific path after the equal (=) sign. |
InstallWindows |
TRUE | FALSE | AUTO Determines whether files marked with a W in the [Files] section are installed. TRUE installs Windows utilities and drivers. It requires a Windows user path (WindowsUserPath). FALSE does not install Windows utilities and drivers. AUTO installs Windows support if Setup detects win.com on the workstation. |
WindowsUserPath |
path The drive and directory of C:\ Windows where the files will be installed. A path is needed only if InstallWindows is set to TRUE. |
UpdateDOSSystemFiles |
TRUE | FALSE TRUE changes autoexec.bat and config.sys and backs up the older files with a .bnw extension. FALSE creates autoexec.new and config.new that you can use to make changes to the workstation's system files. |
OverwriteStartnetBat |
TRUE | FALSE TRUE overwrites startnet.bat. FALSE creates a startnet.new file that you can use to update the workstation's startnet.bat file. |
DoInstallIfLowSpace |
TRUE | FALSE TRUE continues to install the client, even if low disk space is detected. FALSE stops the installation if disk space is low and records an error in the nwcinst.log file, located in the directory where lsl.com was loaded. |
CopyAllUnicodeFiles |
TRUE | FALSE TRUE installs Unicode* files for all country codes. FALSE installs Unicode files only for the country specified in Windows. |
OverwriteNewerFiles |
TRUE | FALSE TRUE installs files to the destination directory even if a newer version of the file exists in the directory. FALSE does not install a file if a newer version exists in the destination directory. |
OverwriteNewerINIFiles |
TRUE | FALSE TRUE overwrites any modifications made to the nwadmin.ini file by copying over the file with the original nwadmin.ini file. This is not recommended. FALSE does not overwrite a modified nwadmin.ini file. |
OverwriteReadOnlyFiles |
TRUE | FALSE TRUE overwrites files marked Read Only. FALSE does not replace files marked Read Only. |
OverWriteReadOnlySYSFiles |
TRUE | FALSE TRUE updates or modifies DOS and Windows system configuration files that are marked Read Only. FALSE does not modify DOS and Windows system configuration files that are marked Read Only. |
CopyWinSysFiles |
TRUE | FALSE TRUE copies necessary files to the Windows system directory. This must be set to TRUE for all Windows installations except installations on workstations that access Windows from the network. FALSE must be set for all Windows installations on workstations that access Windows from the network. |
Use32BitDrivers |
TRUE | FALSE TRUE sets up the client to use a 32-bit ODITM LAN driver if one is available for the network board. FALSE sets up the client to use a 16-bit ODI LAN driver. |
InstallWorkstationManager |
TRUE | FALSE TRUE sets up the client so that administrators can use workstation management functions from NetWare Administrator. FALSE does not set up the client so that administrators can use workstation management functions from NetWare® Administrator. |
UseNWIP |
TRUE | FALSE TRUE sets up the client to access NWIP servers. This should be set to TRUE only if you have an NWIP server. This setting does not configure the NWIP domain name. FALSE does not set up the client to access NWIP servers. |
UseTCPIP |
TRUE | FALSE TRUE sets up the client to access the Internet and use a browser. FALSE does not set up the client to access the Internet and use a browser. |
[REQUESTER] Options
The [Requester] section of the install.cfg contains basic network client configuration information and uses the same syntax and options as the NetWare DOS RequesterTM section in net.cfg. The basic parameters are listed below and additional parameters are explained in the NetWare DOS Requester section of the net.cfg parameter library.
- OverrideLocalSettings = true | false
- First Network Drive =
drive_letter
- Preferred Tree =
tree_name
- Preferred Server =
server_name
- Name Context =
context
NOTE: If you want to use ACU to install the client without user intervention, you must include a setting for each of the basic parameters.
Configuring Protocol and Management Support
The protocol and management sections in install.cfg are [NIOS], [Protocol IPX], [Protocol TCPIP], [TCP/IP], [Link Support], [NWIP], [SNMP], [HOSTMIB], and [TSA].
The lines in each section supply default values for protocol settings. Install.exe uses these values if the settings are not in the workstation's net.cfg file, or to overwrite the values in net.cfg if the OverrideLocalSettings=True for the protocol you are installing.
[driverTranslationTable] Section
This section equates the long driver name of a16-bit ODITM LAN driver with the driver description of the driver's 32-bit version.
Some 32-bit ODI LAN drivers have descriptions that do not match the long driver name listed in the 16-bit driver's .com file. If Install does not upgrade a 16-bit driver to the correct 32-bit driver, you should make an entry in the [driverTranslationTable] section of install.cfg that equates the 16-bit ODI LAN driver's long driver name with the 32-bit ODI LAN driver's description.
-
Open install.cfg in a text editor.
-
(Conditional) If you do not know the long driver name, contact the network board manufacturer or search for the information by doing the following:
-
Open the 16-bit driver's .com file in a text editor.
For example, open ne2000.com in notepad.exe.
-
Search for the Long Driver Name.
There is no consistent way to find the Long Driver Name in a .com file. Usually, the Long Driver Name includes the manufacturer's name or the driver type. For example, search for Novell or Nov or Ethernet.
The long driver name is not the string listed after VeRsIoN=.
-
Record the long driver name for the 16-bit ODI LAN driver.
-
Close the .com file.
-
(Conditional) If you do not know the description, contact the network board manufacturer or search for the information by doing the following:
-
Open the 32-bit driver's .ldi file in a text editor.
The .ldi file has the same name as the driver. For example, ne2000.ldi.
-
Search for a reference to the manufacturer or type of driver.
For example, search for NE2000 or Ethernet.
-
Record the description for the 32-bit driver.
-
Close the .ldi file.
-
Under [driverTranslationTable], enter the long driver name for the 16-bit driver followed by an equal (=) sign and the 32-bit driver's description.
For example, the following line equates the long driver name of a Novell® 16-bit ODI LAN driver with the description for the 32-bit LAN driver:
Novell NE2 Ethernet = Novell Ethernet NE/2
-
Save install.cfg in the network install directory and close the text editor.
Installation Files and Destination Directories
Install.cfg contains several sections that control installation files and target directories. The [AUTOEXEC], [WINDELETE], [WINGROUP], [TITLES], and [FILES] sections also control files during client installation. The most important of these is the [FILES] section.
[AUTOEXEC] Section
Contains the line that Install adds to the end of autoexec.bat files to call startnet.bat.
[WINDELETE] Section
Lists the files that the installation removes from the Windows directory if the InstallWindows= line is set to True. Files listed after the \System line are removed from the Windows\System directory.
[WINGROUP] Section
Assigns the names of the Program Manager program group and icons that Install creates on Windows workstations.
[TITLES] Section
Assigns the names that Install uses to prompt for diskettes.
[FILES] Section
Contains a list of all files that install.exe copies to the workstation's hard drive and the target directory for each file. Information for each file is specified on the same line using four keywords separated by semicolons.
The four types of keywords indicate the source diskette, the target directory, the operating system or protocol the file is installed for, and the source directory, in that order.
For example, the following line appears in the [FILES] section of install.cfg:
The following tables list and describe the various keywords.
Source Diskette Keywords
DISK1DOS |
The first installation source diskette for the DOS install program (install.exe). |
DISK# |
The source diskette for the file. |
Destination Directory Keywords
CLIENT |
Client working directory. |
CLIENTNLS |
The client NLS directory, located in the client working directory. |
CLIENTLANG |
The NLS\nwlanguage directory in the client working directory. |
WINDOWS |
The working directory for Microsoft* Windows. |
WINSYS |
The Windows system directory. |
WINNLS |
The Windows nls directory in the Windows working directory. |
WINLANG |
The language directory for Windows located in the Windows system\nls directory. |
OS and Protocol Keywords
D |
Marks a file as necessary for NetWare DOS support. Install copies the file only if the UpdateDOSSystemFiles= line is set to True. |
W |
Marks a file as necessary for Windows support. Install copies the file only if the InstallWindows= line is set to True. |
DW |
Marks a file as necessary for a DOS or Windows installation (or both). Install copies the file if either the InstallWindows= line or the UpdateDOSSystemFiles= line is set to True. |
M |
Marks a file as necessary for SNMP support. |
T |
Marks a file as necessary for TCP/IP support. |
H |
Marks a file as necessary for HostMIB support. |
S |
Marks a file as necessary for TSA SMSTM support. |
G |
Marks a file as necessary for IPX/IP Gateway support. |
N |
Marks a file as necessary for NDPSTM support. |
The final section of each line contains the name of the file to copy preceded by the subdirectory of the install directory it is located in. For example, nios\cmsm.msg means that the file cmsm.msg is located in the nios directory of the install directory.
Sample Install.cfg File
See also Modifying the Install.cfg File for additional information.
- [
SETUP ]
- InstallType = BASIC
- TargetPath = *AUTO
- InstallWindows = AUTO
- WindowsUserPath = c:\windows
- UpdateDOSSystemFiles = true
- OverwriteStartnetBat = TRUE
- DoInstallIfLowSpace = true
- CopyAllUnicodeFiles = False
- OverwriteNewerFiles = false
- OverwriteNewerINIFiles = False
- OverwriteReadOnlyFiles = False
- OverwriteReadOnlySYSFiles = False
- CopyWinSysFiles = True
- Use32BitDrivers = True
- InstallWorkstationManager = False
- UseTCPIP = FALSE
- [REQUESTER]
- OverrideLocalSettings = false
- ; FIRST NETWORK DRIVE = F
- NETWARE PROTOCOL = NDS BIND
- ; PREFERRED SERVER =
- ; SHORT MACHINE TYPE =
- ; NAME CONTEXT =
- [NIOS]
- OverrideLocalSettings = false
- ; LINE DRAW CHARS = "Ú[iquest]ÀÙÄ"
- [TCP/IP]
- OverrideLocalSettings = false
- ; Set ip_server = DHCP, BOOTP or RARP
- ip_server = DHCP
- ip_address =
- ip_router =
- ip_netmask =
- DNS_domain =
- NameServerAddress =
- [PROTOCOLIPX]
- OverrideLocalSettings = false
- [LINK SUPPORT]
- OverrideLocalSettings = false
- ; MAX BUFFER SIZE 1024
- [NWIP]
- InstallNWIP = False
- OverrideLocalSettings = False
- ;configurable options
- NWIP_Domain_Name =
- [SNMP]
- InstallSNMP = False
- OverrideLocalSettings = False
- ;configurable options
- EnableMonitorCommunity = specified
- MonitorCommunity = public
- EnableControlCommunity = off
- ControlCommunity = public
- EnableTrapCommunity = specified
- TrapCommunity = public
- sysName = Suzanne Morley x893
- sysLocation = Building 2
- sysContact = suzanne@company.com
- snmpEnableAuthenTraps = off
- [HOSTMIB]
- OverrideLocalSettings = False
- InstallHOSTMIB = False
- ;configurable options
- PRINTER =
- MODEM =
- TAPEDRIVE =
- SWDirectorySearchDepth =
- SWDirectorySearch =
- [TSA]
- InstallTSA = False
- OverrideLocalSettings = false
- ;configurable options
- ServerName = ServerName
- WorkstationName = WorkstationName
- Password = password
- SelectedDrives = C
- DiskBuffers = 10
- StackSize = 2048
- [TIMEZONE]
- ; SET TZ=JST-9
- [TITLES]
- DISK1DOS:'Novell Client for DOS and Windows 3.1x Disk 1-DOS Install'
- DISK2:'Novell Client for DOS and Windows 3.1x Disk 2'
- DISK3:'Novell Client for DOS and Windows 3.1x Disk 3'
- DISK4:'Novell Client for DOS and Windows 3.1x Disk 4'
- DISK5:'Novell Client for DOS and Windows 3.1x Disk 5'
- DRIVER32:'Novell Client for DOS and Windows 3.1x 32 Bit LAN Driver'
- DRIVER16:'Novell Client for DOS and Windows 3.1x 16 Bit LAN Driver'
- [DISKSPACE]
- lowSpace = 5500
- installDosSpace = 1330
- installWinSpace = 3380
- [WINGROUP]
- group=NW.grp:Novell Client
- icon=nwuser.exe:W:winsys:NetWare User Tools
- icon=loginw31.exe:W:client:NetWare Login
- icon=setup.hlp:W:clientlang:Novell Client Help
- icon=gwsw16.exe:G:client:IP Gateway Switcher
- icon=winping.exe:G:client:IP Gateway WinPing
- [READMEFILE]
- LANGCLIENT:D:DOSWIN.txt
- [FILES]
- ; readme file for DOS
- DISK2:LANGCLIENT:D:DOSWIN.TXT
Using a Configuration File Other Than Install.cfg
You can specify a configuration file other than install.cfg for the DOS-based installation. This enables you to rename the edited version or to create multiple versions of install.cfg and specify the one you want to use on a command line. See Modifying the Install.cfg File for specifics about what must be in this file.
On the install.exe command line, enter
/C=path\filename
For example, to specify c32sales.cfg, enter
INSTALL /C=C:\NOVELL\CLIENT32\C32SALES.CFG
Additional Links
- Setting Up DOS-based ACU for DOS Login
- Installing from the Network
