Copyright: Copyright © Novell, Inc.


16-bit ODI Drivers

16-bit ODI* drivers require two modules (N16ODI.COM and PC32MLID.LAN) that enable the 32-bit NIOS to communicate with the 16-bit ODI LAN driver. The modules are loaded in STARTNET.BAT after LSL.COM. The following example illustrates a typical load order of modules in STARTNET.BAT for a computer that runs a 16-bit ODI LAN driver with Client 32* software:

NIOS.EXE

LH LSL.COM

LH N16ODI.COM

LH NESL.COM

LH 16-bit ODI LAN driver .COM

LOAD LSLC32.NLM

LOAD PC32MLID.LAN

LOAD IPX.NLM

LOAD CLIENT32.NLM

Note: Unlike the 32-bit ODI LAN drivers, 16-bit ODI LAN drivers access NET.CFG when loading to find configuration information.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


32-bit LAN Driver Parameters

32-bit ODI* LAN drivers do not use NET.CFG for configuration parameters. Type configuration parameters on the load line. Most ISA drivers require at least the following parameters:

FRAME=frame_type

IRQ=interrupt

PORT=number

Example: LOAD CNE2000.LAN FRAME=Ethernet_802.2 IRQ=3 PORT=300

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Adding Search Paths

Use the Add Search Path dialog box to specify the path to a directory you want included in Host MIB inventory scans. You need to type a specific path only if the directory you want to scan is deeper in the directory structure than the number indicated in the Directory Levels to Search from Root field.

1.	In the New Search Path box, type the path to the directory you want the Host MIB agent to inventory.

Note: You can search all subdirectories by typing "\*.*" after the directory name. For example, the path "C:\WINDOWS\*.*" makes the Host MIB agent search all subdirectories below the WINDOWS directory.

2.	Click OK.


Changes Setup Makes to All Clients

New Files and Directories

Setup creates a directory (by default, NOVELL\CLIENT32) for Client 32* files and copies core Client 32 files and NLM* programs to this directory.

Setup creates an NLS\language directory in the Client 32 working directory and copies language-specific files to these directories.

Changes to the AUTOEXEC.BAT File

Setup adds a line to the end of the AUTOEXEC.BAT file to run STARTNET.BAT:

@CALL drive:\client32_home_dir\STARTNET.BAT

Setup adds the Client 32 working directory to the PATH variable in the AUTOEXEC.BAT file.

Changes to the NET.CFG File

If the computer has a NET.CFG file, Setup copies the NET.CFG to the CLIENT32 working directory and makes the following changes:

If the computer uses a 16-bit driver, Setup adds or edits the Link Driver section of the NET.CFG file.

Setup adds the following two lines to the NetWare DOS Requester section:

FIRST NETWORK DRIVE = F

NETWARE PROTOCOL = NDS BIND

Setup adds or edits sections in NET.CFG based on the configuration information the user supplies during Setup.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to Clients

Overview

Overview

Changes to All Clients

Changes Based on User Input

Changes to Windows Clients

Changes to TCP/IP Clients

Changes to SNMP Clients

Changes to TSA Clients


Changes Setup Makes to SNMP Clients

Changes to System Files

Setup adds or edits a Desktop SNMP section to NET.CFG. If the computer also runs support for Host MIB, Setup adds a Host MIB section to NET.CFG.

Setup adds the following lines in STARTNET.BAT to load the SNMP NLM* programs:

LOAD drive:  \client32_home_dir   \SNMP.NLM

LOAD drive:  \client32_home_dir  \SNMPIPX.NLM

LOAD drive:  \client32_home_dir  \SNMPUDP.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to TCP/IP Clients

File Changes

Setup renames all instances of WINSOCK.DLL and WLIBSOCK.DLL in the Windows** root and Windows SYSTEM directories by changing the .DLL extension to .OLD.

Setup installs WINSOCK.DLL and WLIBSOCK.DLL to the Client 32* working directory (by default, NOVELL\CLIENT32).

Changes to System Files

Setup adds or edits a Protocol TCPIP section to the NET.CFG file.

Setup adds the following lines to the RESOLV.CFG file:

DOMAIN domain_name_entered

NAMESERVER address_entered

Note: If RESOLV.CFG is not already on the computer, Setup creates the file in the TCP directory of the Client 32 working directory.

Setup adds the following line in STARTNET.BAT to load the TCP/IP NLM:

LOAD drive:\client32_home_dir\TCPIP.NLM

Changes for NetWare/IP

Setup adds the following line to STARTNET.BAT that loads the NetWare*/IP* NLM* program:

LOAD drive:\client32_home_dir\NWIP.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to TSA Clients

Changes to System Files

Setup adds or edits a NetWare* DOS TSA section to NET.CFG and includes the following parameters:

TSA Server Name, Password, Disk Buffers, Drives

Setup adds the following line in STARTNET.BAT to loads the workstation TSA:

drive:  \client32_home_dir  \TSASMS.COM

Note: This line loads a TSR (under 10 KB, depending on the Disk Buffers parameter) that communicates with SBACKUP.NLM on the SMS* server.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Changes Setup Makes to Windows Clients

Changes to Files and Directories

Setup copies files to the Windows** SYSTEM directory (normally C:\WINDOWS\SYSTEM). You can configure the DOS-based Setup to overwrite or keep files that are newer than those provided by Setup.

Setup deletes NetWare* files from the Windows root directory.

Setup copies unicode tables to the winroot  \NLS directory.

Changes to Program Manager

Setup creates a group file (NW.GRP) called NetWare Tools that contains icons for NetWare User Tools and NetWare Login, and adds the following line to PROGMAN.INI:

GROUP# =C:\WINDOWS\NW.GRP

Changes to WIN.INI

Setup adds the following line to the [Windows] section of the computer's WIN.INI file:

Load=NWPOPUP.EXE

Changes to SYSTEM.INI

Setup removes all instances of "*DOSNET," "VTCPIP.386," and "VIPX.386" from the Network= line of the [386 Enh] section.

Setup removes all instances of "Device = VTCPIP.386" from the [386 Enh] section.

Setup appends the Network= line in the [386 Enh] section to include "VNETWARE.386."

When installing a 16-bit ODI LAN driver, Setup adds the following line to the [386 Enh] section:

device = VLANINT.386

Setup makes the following changes to Windows for Workgroups 3.11 clients:

Setup adds the following line to the [boot] section:

secondnet.drv = netware.drv

Setup adds the following line to the [boot.description] section:

secondnet.drv = Novell NetWare (v4.0)

Setup makes the following changes to clients running Windows 3.1 (not WFW 3.11):

Setup adds the following line to the [boot] section:

network.drv = netware.drv

Setup adds the following line to the [boot.description] section:

network.drv = Novell NetWare (v4.0)

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Choosing a Hardware Interrupt

In most cases, you can use IRQ3 or IRQ5 for your network board if these are not already used by COM2 and LPT2. If neither IRQ3 nor IRQ5 is available, see the manufacturer’s documentation.

Note: If you specify an interrupt for the network board that is already being used by another device, you can still install the network board but the network software will not run successfully.

The following table shows the IRQ settings that are commonly used by other devices, and the settings that might be available.

IRQ	Device
0	Timer output 0
1	Keyboard
2	EGA/VGA
3	COM2
4	COM1
5	LPT2
6	Diskette
7	LPT1
8	Real time clock
9	Available
10	Available
11	Available
12	Available
13	Co-processor
14	Hard disk
15	Available


Choosing an Input/Output Port

The base input/output port is a channel used by the network board to transfer information to the CPU. Each hardware device included in your client workstation must have a different base I/O port setting. For more information, see the manufacturer’s documentation.

The following table shows a list of standard I/O ports and the devices that commonly use them. If a workstation does not have any one of these devices, the I/O port given in the table for that device might be available for other use.

I/O Port	Device
1F0	AT disk controller
200	Game controller/joystick (200-20F)
220	Novell network keycard
240	Available
260	LPT2 (278-27F)
280	LCD display on WYSE* 2108 PC
2A0	Available
2C0	Available
2E0	COM4 GPIB-Adapter 0 (2E1); COM2 Information collection from external devices
300	Available
320	XT hard disk interface
340	Available
360	LPT1 (378-37F)
380	SLDC/Sec BiSync interface (380-38C)
3A0	Primary BiSync interface (3A03A9); Monochrome display (3B0-3BB)
3C0	EGA display control (3C0-3CF); CGA display control (3D0-3DF)
3E0	COM3 (3E8-3EF); Diskette controller (3F0-3F7); COM1 (3F8-3FF)


Choosing an ODI Driver

Use the ODI Driver Selection dialog box to specify the ODI* LAN driver your network board uses.

To specify an ODI LAN driver

1.	Select 32-bit or 16-bit to specify the type of driver you want to use.

32-bit drivers improve the client's speed and reliability over 16-bit drivers. You should use the 32-bit driver if one is available for your LAN board.

2.	Choose the driver you want to use.

If the name of the driver you want to use appears in the Board list, select the driver name from the list.

If the driver does not appear in the list, select a different driver type (16-bit or 32-bit) and look again for the driver.

If the board you want to set up is not listed in the Board list and you have a copy of the driver, click Other Boards and install the driver from a local or network drive.

3.	(Optional) Click Driver Settings to configure the LAN board.

4.	Click Next when you are finished.

To reset values to the driver

Select Reset to Detected Driver.

Note: Setup discovers the current network boards and and LAN driver settings by requesting the information from LSL.COM or NIOS.EXE. Setup does not display information for an installed network board if LSL.COM or NIOS.EXE is not loaded.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Client 32 Utilities and Modules

Utilities

Overview of Client 32 Utilities

ENABLE/DISABLE

LOAD/UNLOAD

MODULES

Client 32 Modules

Overview of Client 32 Modules

Core Modules

ODI LAN Driver Modules

Optional Protocols


Completing Setup

Restart Computer (Recommended)

This option will remove any existing client from memory, reboot the computer, and load Client 32* if you chose to modify AUTOEXEC.BAT. To load Client 32 manually, run STARTNET.BAT in the Client 32 working directory.

Return to Windows

This option will return you to Windows**. Client 32 will not be loaded until you reboot the workstation. If you chose to modify AUTOEXEC.BAT, Client 32 is loaded automatically when the computer boots. To load Client32 manually, run STARTNET.BAT from the Client 32 working directory.

Exit to DOS

This option ends your Windows session and exits to DOS. Client 32 will not be loaded until you reboot the computer. If you chose to modify AUTOEXEC.BAT, Client 32 is loaded automatically when the computer boots. To load Client 32 manually, run STARTNET.BAT in the Client 32 working directory.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Additional Options

Update AUTOEXEC.BAT

Modifies the AUTOEXEC.BAT file to load the client each time the computer boots. If you do not want to load the client every time the computer boots, or if you want to edit these files yourself, uncheck Update AUTOEXEC.BAT to load NetWare Client 32.

TCP/IP

Installs support for connecting to Transmission Control Protocol/Internet Protocol (TCP/IP) networks. You should install support for TCP/IP if you want to connect to the internet or if you use TCP/IP or NetWare*/IP* on your network.

NetWare/IP

Installs support for NetWare/IP. You should install NetWare/IP only if you use applications that require IPX* across a network that requires IP.

SNMP and Host MIB

Installs Simple Network Management Protocol (SNMP), a cross-protocol language that allows administrators to manage computers across diverse network platforms.

If the management console supports Management Information Base (MIB) files, you might also want to load Host Resources MIB support on the client. Host Resources MIB support enables the management console to poll the client for inventory information.

TSA for SMS

Installs NetWare Target Service Agent (TSA) support for Storage Management Services* (SMS*). TSA software enables SMS to back up clients on diverse operating systems. If you have an SMS server, you can back up information on the client to the SMS server by installing the TSA for SMS support.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring LAN Driver in Windows_p
Configuring the ODI LAN Driver in Windows

2a.	Remove any existing LAN drivers from the dialog box by selecting a LAN driver and choosing Remove.

When prompted to make sure you want to remove the selected LAN drivers, choose Yes.

2b.	Choose Add Adapter.

2c.	From the Add Network Adapter dialog box, select the appropriate ODI* LAN driver for your network board.

The Setup program might prompt you to direct it to the location of the correct ODI LAN driver. The LAN driver should exist in the directory you used when installing Client 32*.

2d.	Click OK.


Configuring NetWare/IP

Enter the following information in the NetWare/IP Configuration dialog box.

NetWare*/IP* Domain Name

Enter the NetWare/IP domain name (for example, NWIP.ATLANTIC.COM).

Preferred DSS

(Optional) Enter the names or addresses of preferred domain servers running Service Advertising Protocol (SAP) or Router Information Protocol (RIP). For example: 222.33.0.0 DSSSERV.ALTANTIC.COM

You can enter up to five servers by separating the names or addresses by a space.

Nearest NWIP Server

(Optional) Type the name or address of the server you want NetWare/IP to communicate with first (for example, SERV1.ATLANTIC.COM).

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Protocol Support

Overview

The protocol sections set default values for optional software included with Client 32* software.

The first line of each section indicates whether Client 32 Setup installs support for the protocol when the InstallType in the [Setup] section is set to Auto. If the InstallType is set to Basic, the user selects what protocols Setup installs on the computer.

The remaining lines in each section supply default values for protocol settings. Setup uses these values if the settings are not in the computer’s NET.CFG. You can set the default values listed in INSTALL.CFG to override the computer's NET.CFG values by setting the OverwriteLocalSettings line to TRUE.

Making Changes

Editing INSTALL.CFG

Sections

[TCP/ IP]

[NWIP]

[SNMP]

[HOSTMIB]

[TSA]

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Protocols in Windows

3a.	 To add a protocol, click Add Protocol, select the protocol you want to use, and then click OK.

You can use the following protocols with Client 32*:

IPX*/SPX* Compatible Transport

IPX/SPX Compatible Transport with NetBIOS

Microsoft** NetBEUI

3b.	To remove a protocol, select the protocol and click Remove.

3c.	If you load more than one protocol, select the protocol you want to use as default and click Set As Default Protocol.


Configuring SNMP

You can set up the computer's SNMP environment to report the following optional parameters:

Parameter	Description
Workstation Name	A label that identifies the computer.
Workstation Location	A description of the location of the computer. You can place any information in this field, up to 255 characters.
Contact Name	The name of the person responsible for supporting the computer. For example, you may want to type the manufacturer's name and phone number.
Trap Target Address	The network addresses of SNMP management consoles. The SNMP agent on the client computer sends SNMP information to the network addresses listed. IPX* addresses are two hexadecimal numbers separated by a colon (9FA:C01). IP addresses are four numbers from 1 to 255 separated by periods (111.222.33.44).
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring Startup Files in Windows

8a.	From Program Manager, click the File menu and click Run.

8b.	Type "SYSEDIT" and click OK.

8c.	In the AUTOEXEC.BAT window, highlight the line that loads ODIHLP.EXE.

8d.	From the Edit menu, click Cut.

8e.	From the File menu in Program Manager click Run.

8f.	Type "NOTEPAD" and the path to the STARTNET.BAT file. For example:

      NOTEPAD C:\NOVELL\CLIENT32\STARTNET.BAT

8g.	Click OK.

8h. In the STARTNET.BAT file, paste the ODIHLP.EXE line above the line that loads PC32MLID.LAN.

8i.	Save your changes and close NOTEPAD and SYSEDIT.


Configuring Support for SMS

Enter the following information to install support for backing up files on the computer to an SMS* server:

Field	Description
TSA Server Name	The name of the server that backs up the computer.
Workstation Name	A 1-10 character description of the computer for SMS services.
Password	A 1-10 character password that a network supervisor must provide before backing up the computer's local drives.
Local Drives to Back Up	The drive letters of the drives the TSA server backs up.
Transfer Buffers	The amount of memory reserved for storing data before it is sent over the network.
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring TCP/IP

The TCP/IP protocol stack requires information that defines the computer's network environment. If you do not know the information for some of the fields, accept the defaults and continue with Setup. You can edit these parameters in the NET.CFG and RESOLV.CFG files after Setup completes or by running Setup again.

Setup requires the following information to install support for TCP/IP:

Client IP Address

Default Router Address

DNS Domain Name

Domain Name Server Address

Subnetwork Mask


Configuring Windows Components

To set up support for multiple country codes in Windows

1.	Select the country codes field and press Enter.

2.	Press the Y key.

To set up support for a networked Windows directory

1.	Select the shared Windows** directory field and press Enter.

2.	Press the Y key.

3.	Press Enter.

4.	Type the path to the shared Windows directory.

5.	Press Enter.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Configuring the LAN Driver

The Driver Settings dialog box lists the parameters for the driver you are installing. Most drivers require values for the interrupt request line (IRQ), the frame type, and the the number of retries. Other possible parameters include base I/O port and node address.

All of the configurable parameters for the driver are listed. Default values listed are determined in this order: from NET.CFG, from the LSL* module, or from the defaults specified by the driver.

Note: You should accept the default driver settings unless you are aware of settings that will increase the performance of your LAN board.

To change driver settings

1.	Double-click the parameter you want to change.

2.	Set the value of the parameter.

3.	Click OK.

4.	Click OK to exit the Driver Settings dialog box.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contacting Novell

Technical support direct from Novell* is a fee-based service.  To purchase support on a pay-as-you-go basis call 1-800-NETWARE or 1-801-429-5588 in the Americas, +49-211-5277-744 in Europe and the Middle East, and +61-2-925-3133 in Asia Pacific.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contacting a Novell Partner

Novell’s PartnerNet* program allows customers to contact Novell Partners that can assist them with their service needs.  PartnerNet* integrates key Novell* programs sales, consulting, and technical service enabling Novell Partners to provide quality solutions. Novell Platinum Partner* representatives provide enterprise solutions and Novell Gold Partner* representatives specialize in specific product areas.  Novell authorizes partners who are committed to providing quality service and support to customers.

To find a Novell Partner in your area, call 1-800-338-6272 in the United States or Canada.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Contents
Client 32 Setup

Overview

What is Client 32

What's New?

Installing Client 32

Overview

Preparing to Install Client 32

Setting Up Client 32

Setting Up Additional Software

Changes Setup Makes to Clients

Uninstalling Client 32

Optimizing Client 32

Overview

Increasing Speed

Minimizing Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Optimizing STARTNET.BAT

Using Client 32

Overview

Logging In to a NetWare Network

Using Network Resources

Reference

Client 32 NET.CFG Parameters

Client 32 Utilities and Modules

System Messages

Support


ControlCommunity

Specifies the name of the SNMP community that has rights to control the computer when the EnableControlCommunity parameter is set to SPECIFIED.

Syntax: ControlCommunity = name

Default: public

Example:

[SNMP]

ControlCommunity = public


Controlling Installation Files and Target Directories

Overview

INSTALL.CFG contains several sections that control installation files and target directories. The most important of these is the [Files] section. The [AUTOEXEC], [WINDELETE], [wingroup], and [titles] sections also control files during Client 32* installation.

Making Changes

Editing INSTALL.CFG

Sections

[Files]

[AUTOEXEC]

[WINDELETE]

[wingroup]

[titles]

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Controlling the DOS-based Setup

Editing the Setup Configuration File

Overview

Editing INSTALL.CFG

Using a Setup File Other Than INSTALL.CFG

Setting Installation Parameters

Selecting Setup Options

Setting Default Parameters for Client 32

Configuring Protocol Support

Controlling Installation Files and Target Directories


CopyAllUnicodeFiles

This line of INSTALL.CFG specifies whether Setup installs unicode files for all country codes or only for the country specified in Windows**.

Syntax: CopyAllUnicodeFiles = TRUE | FALSE

Default: FALSE

Example:

[Setup]

CopyAllUnicodeFiles = TRUE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Core Modules

Overview

The core modules are the modules that a computer must load to connect to a network. These modules must be loaded in the following order

Modules

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

NIOS.EXE

Examples

Example of 32-bit ODI LAN Driver

Example of 16-bit ODI LAN Driver


Creating User Groups for ACU
Consider the following rules when creating a user group for ACU:

The computers should have similar memory configurations and TSRs.

All computers in a group should use the same path naming conventions for NetWare* and Windows** software.

The computers should be running the same version of NetWare Client* software.


Creating a Network Install Directory

To run Client 32* Setup from the network, you must set up a network directory where users can access the Setup files. The way you set up the directory depends on the way you received Client 32.

Click the line that describes the way you received Client 32 software:

Client 32 CD-ROM

Downloaded Client 32 Files

NetWare 4.11 Server

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DNS_domain Option

Syntax: DNS_domain = DOMAIN_NAME

Default: none

Example: DNS_domain = company.com


Deleted Windows Files

Setup deletes these files from the Windows** root directory (normally C:\WINDOWS). Setup replaces some of these files in the Windows SYSTEM directory.

NWPOPUP.EXE	NETWARE.DRV
NWCALLS.DLL	NWLOCALE.DLL
NWNET.DLL	NWPSRV.DLL
NWPSERV.DLL	NWIPXSPX.DLL
VIPX.386	VNETWARE.386
NETWARE.HLP	TASKID.COM
TBMI2.COM	NWGDI.DLL
PNW.DLL


Destination Directory Keywords

Each destination directory keyword represents the path from the Client 32* source disks to the computer's hard drive.

Keyword	Description
CLIENT	Client 32 working directory.
CLIENTNLS	The Client 32 NLS directory, located in the Client 32 working directory.
CLIENTLANG	The language directory in the Client 32 NLS nwlanguage directory.
LANGCLIENT	From NLS nwlanguage to the Client 32 working directory.
WINSYS	The Windows SYSTEM directory.
WINNLS	The Windows** NLS directory, located in the Windows working directory.
WINLANG	The language directory for Windows located in the Windows SYSTEM\NLS directory.
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DiskBuffers

Specifies the amount of memory TSA reserves for transferring data to the SMS* server.

Syntax: DiskBuffers = number_kilobytes

Default: 10

Example:

[TSA]

DiskBuffers = 20

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


DoInstallIfLowSpace

This line of INSTALL.CFG specifiess whether Setup continues if low disk space is detected.

Syntax: DoInstallIfLowSpace = TRUE | FALSE

Default: TRUE

Example:

[Setup]

DoInstallIfLowSpace = TRUE


Downloading Client 32

If you have an internet connection on the computer, you can download disk images of Client 32* Setup and run it from the computer's local drive. You can also copy the downloaded files to the network so other clients can run Setup from the network.

To download disk images

1.	Launch your internet browser.

2.	Point the browser to a Novell* NetWire* location.

3.	Locate the DOS/Windows Client download area.

4.	Download the Client 32 software to your computer or a network drive.

You can download a Network Installation that provides all Setup files in a common directory. The network installation is faster to execute and does not prompt for disks, but it cannot be copied easily to floppy disks.

You can also download a Diskette Installation. The diskette installation gives you 8 disk images that you can use to install the client from floppy disk. You should download the disk installation if you have a slow or unreliable internet connection. You can copy the diskettes into a common directory to improve the speed of the installation.

5.	Close your browser and run Client 32 Setup on the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


ENABLE/DISABLE

Switches Client 32 functions on or off.

Syntax: ENABLE | DISABLE function

Example: ENABLE LOGGING

Notes

Currently, LOGGING is the only parameter available to use with ENABLE/DISABLE.

Enabling LOGGING creates or appends a NIOS.LOG file in the Client 32* working directory. The log file contains information about Client 32 events.

You can specify another name and path for the log file in the computer's NET.CFG file.

You can also enable LOGGING by adding a /L to the NIOS.EXE command line.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Editing INSTALL.CFG

To edit INSTALL.CFG

1.	Make sure you have a backup copy of INSTALL.CFG.

2.	Open INSTALL.CFG or the file you want to use for setup information in a text editor.

INTALL.CFG is on the root directory of DISK1DOS or the network install directory.

3.	In the [Files] section, make any changes to the destination directories.

4.	In the [Files] section, make changes to the files you want to copy.

5.	In the [REQUESTER] section, enter default values for the preferred tree or server.

6.	(Conditional) If you are using ACU, choose the protocols you want to install and set the options you want to use in the [Setup] section.

7.	Save the file to the install directory and exit the editor.


EnableControlCommunity

Specifies which SNMP communities can access the computer.

Syntax: EnableControlCommunity = specified | any | off

Default: off

Example:

[SNMP]

EnableControlCommunity = any


EnableMonitorCommunity

Specifies which SNMP communities can query the computer for inventory information.

Syntax: EnableMonitorCommunity = specified | any | off

Default: SPECIFIED

Example:

[SNMP]

EnableMonitorCommunity = any


EnableTrapCommunity

Specifies which SNMP communities can caputure alerts from the computer.

Syntax: EnableTrapCommunity = specified | off

Default: specified

Example:

[SNMP]

EnableTrapCommunity = off


Ensuring Data Integrity

If the users on your network require maximum data integrity, you can set several Client 32* parameters to avoid data loss. Client 32 functions more slowly when it is maximized for data integrity than it does when maximized for speed.

To increase data integrity of Client 32

1.	Open the computer's NET.CFG in a text editor.

NET.CFG is located in the Client 32 working directory (NOVELL\CLIENT32, by default).

2.	Set the following parameters to specified values, using NET.CFG syntax.

Parameter	Value
Auto-reconnect Level	4 or 5
Checksum	2 or 3
Close Behind Ticks	0
True Commit	on
3.	Save your changes and exit the editor.

4.	Unload and reload Client 32 software or reboot the computer to make the changes effective.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Finding the Driver Description

To find the description for a 32-bit LAN driver

1.	Open the 32-bit driver’s .LDI file in a text editor.
The .LDI file has the same name as the driver. For example, CNE2000.LDI.

2.	Search for a reference to the manufacturer or type of driver.
For example, search for "CNE2000" or "Ethernet." The Description can sometimes be found after "Des:" or "Description:."

3.	Make a note of the Description for the 32-bit driver.

4.	Close the .LDI file.


Finding the Long Driver Name

You can find the Long Driver Name and the Description by contacting the manufacturer of the network board or by searching for the information in the drivers' .COM and .LDI files.

To find the Long Driver Name for a 16-bit LAN driver

1.	Open the 16-bit driver’s .COM file in a text editor.
For example, open NE2000.COM in NOTEPAD.EXE.

2.	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."

Note: The Long Driver Name is not defined by the "VeRsIoN=" line, even though the version and Long Driver Name may be the same.

3.	Make a note of the Long Driver Name for the 16-bit driver.

4.	Close the .COM file.


Getting Information from NetWire

NetWire*, Novell’s technical information forum, gives you access to the most up-to-date technical information about Novell products and technologies.  When logged on to NetWire, you can search for and download information or troubleshoot your questions with help from other experienced users.  Novell* system operators (Sysops) monitor the CompuServe forums and have direct access to Novell support engineers when necessary.  The only fee for NetWire is the standard connect charge of the online service you use.

NetWire includes:

Downloadable files, patches and drivers

Thousands of Technical Information Documents (TIDs)

Product documentation

NetWare Application Notes*

GroupWare Professional’s Guide

Novell Labs* certification bulletins

You can visit NetWire at one of the following locations:

Service	Location
World Wide Web	http://netwire.novell.com or http://netwire.de
FTP	ftp://ftp.novell.com or ftp://ftp.novell.de
Gopher	gopher://gopher.novell.com or  gopher://gopher.novell.de
CompuServe**	Enter GO NETWIRE at the CompuServe prompt
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


INSTALL.EXE

The execution file for DOS-based Client 32* Setup. INSTALL.EXE is located on the root of DISK1DOS.

Syntax:  INSTALL [ /C=path\filename | /I=path\locale_file]

Example:  INSTALL /C=F:\C32\ACCTG.CFG

Notes

Use the /C option to specify a Setup configuration file other than the INSTALL.CFG file in the same directory as INSTALL.EXE.

Use the /I option to specify the path and file name to LOCALE.CFG.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


IP Address (definition)
IP Address

The IP address of the computer. The IP address is a set of four numbers from 1 to 255 separated by periods. For example, 111.222.233.24.


Increasing the Speed of Client 32

By default, Client 32* is configured for optimum speed with good data integrity. You can modify the following parameters in the computer's NET.CFG to maximize the speed at which Client 32 performs network operations.

To increase the speed of Client 32

1.	Open the computer's NET.CFG in a text editor.

NET.CFG is located in the Client 32 working directory (NOVELL\CLIENT32, by default).

2.	Set the parameters to specified values, using NET.CFG syntax.

3.	Save your changes and exit the editor.

4.	Unload and reload Client 32 software or reboot the computer to make the changes effective.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Install Options for DOS

NetWare* Client* 32* for DOS

Installs the files necessary to run Client 32 in DOS.

NetWare Client 32 for Windows**

Installs support for Microsoft** Windows 3.1x and DOS. Also installs User Tools. If you choose this option, you need to specify any country codes the computer uses other than the ones listed in the computer's WIN.INI file. Also, if the computer runs Windows from the network, you need to specify the path to the shared Windows directory.

NetWare TCP/IP

Installs support for connecting to Transmission Control Protocol/Internet Protocol (TCP/IP) networks. You should install support for TCP/IP if you want the computer to connect to the internet or if your network requires TCP/IP or NetWare/IP*.

NetWare/IP

NetWare/IP sends and receives IPX* packets in an IP format. NetWare/IP enables networked applications that use only IPX to run over TCP/IP-based networks. It also provides a way for separate IPX networks to communicate across IP connections.

Desktop SNMP

Simple Network Management Protocol (SNMP) is a cross-protocol language that allows administrators to manage computers across diverse network platforms. If the management console supports Management Information Base (MIB) files, you can load Host Resources MIB support on the client. Host Resources MIB support enables the management console to poll SNMP clients for inventory information.

NetWare TSA for SMS

Target Service Agent for Storage Management Services* enables SMS* servers to back up files on client computers.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Install<protocol>
Installprotocol

Specifies whether Setup adds support for the protocol listed.

Syntax: Install[TCPIP | NWIP | SNMP | HOSTMIB | TSA] = TRUE | FALSE

Default: FALSE

Example:

[TCP/IP]

InstallTCP = True


InstallType

This line of INSTALL.CFG specifies the amount of user input during a DOS installation.

Syntax: InstallType = BASIC | AUTO

Default: AUTO

Example: InstallType = AUTO

Notes

BASIC is an attended installation that requires some user input.

AUTO is an unattended installation--errors are written to NWCINST.LOG.


InstallWindows

This line of INSTALL.CFG specifies whether files marked with W in the [FILES] section are installed.

Syntax: InstallWindows = TRUE | FALSE | AUTO

Default: TRUE

Example:

[Setup]

InstallWindows = TRUE

AUTO installs Windows** support if Setup detects WIN.COM on the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Client 32 from DOS

Purpose

To install Client 32* software using a DOS-based install program. The DOS-based install program can install support for Windows** 3.x as well as for DOS.

To install Client 32 from DOS

1.	From a DOS prompt, switch to the local or network drive where the Client 32 install program is located.

2.	Type "INSTALL" and press Enter.

3.	Press Enter to accept the License Agreement.

4.	Select the components you want to install on the computer.

5.	Press F10 to continue.

Note: Press the Esc key at any time before Install begins copying files to return to the previous screen or to cancel the installation.

6.	Configure the components you are installing. Use the arrow keys to move to a new field and press Enter to edit the field.

7.	Press F10 save your changes and continue.

8.	Choose to allow Setup to change the AUTOEXEC.BAT and CONFIG.SYS files.

9.	Set the Client directory to the directory where you want to install Client 32 files.

10.	If you are installing support for Windows, set the Windows directory to the directory where the computer runs Windows.

11.	Select 16-bit or 32-bit LAN driver type.

12.	Select the LAN driver your computer uses.

13.	Press F10 to continue.

Install copies the appropriate files to your computer and sets up the computer to run Client 32.

14.	Exit Install by pressing Enter to return to DOS or by pressing Ctrl+Alt+Del to reboot the computer.

Client 32 cannot load until the computer restarts.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Client 32 from Windows

Purpose

To install Client 32* software using a Windows** interface. The Windows-based Setup program installs support for both DOS and Windows.

To install Client 32 from Windows

1.	From Windows, close all other programs running on the computer.

2.	From the File menu in Program Manager, choose Run.

3.	Type the drive letter and path to SETUP.EXE for Client 32.

4.	Click OK.

5.	Click Continue in the Welcome dialog box and then click Yes to accept the Software License Agreement.

6.	In the Target Directory field, type the path to the directory where you want to install Client 32. The default is C:\NOVELL\CLIENT32.

7.	In the Windows Directory field, type the path to the directory where the computer runs Windows.

If the computer runs Windows from the network, quit Setup and run INSTALL.EXE from DOS.

8.	Click Next.

9.	Select the 32-bit or 16-bit option to specify the type of ODI LAN driver you want the computer's network board to use.

Note: You should use a 32-bit LAN driver if one is available for your network board.

10.	Make sure the board setting specifies the correct ODI LAN driver for your network board.

Click the drop-down box to select another board.

If no 32-bit LAN driver is listed for your network board, click 16-bit and select the appropriate 16-bit LAN driver from the list.

If your network board is not listed, you can load the driver from a local or network drive by clicking Other Boards.

11.	(Optional) To configure the settings for the network board, click Driver Settings.

12.	Click Next.

13.	Choose to allow Setup to change the computer's AUTOEXEC.BAT.

14.	Select any additional software you want to install.

15.	Click Next and then supply information for the additional software you are installing.

16.	When Setup completes, reboot the computer or return to Windows.

Note: If you want to use Windows for Workgroups peer-to-peer networking, exit to Windows and make the necessary changes before restarting the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing From Floppy Disks
Installing from a Floppy Drive

If you have a computer that does not have a CD-ROM drive and is not connected to the network, you can create a set of Client 32* installation diskettes. You can then install Client 32 from a floppy drive using the DOS or Windows** Client 32 Setup program.

To create Client 32 setup diskettes

1.	Prepare 8 blank formatted diskettes to use as setup diskettes.

2.	Do one of the following:

On a computer with a CD-ROM drive, insert the Client 32 CD-ROM.

On a computer with an internet connection, download Client 32 files to the computer.

Run INSTALL.BAT from the root of the NetWare* 4.11 CD-ROM and follow the instructions provided. After creating the diskettes, go to step 9.

3.	Change to the root of the Client 32 directory.

4.	From a DOS prompt, type "MAKEDISK" driveletter: and press Enter.

The driveletter is the letter of the disk drive where you will insert the diskettes.

5.	Insert a blank formatted diskette into the drive you indicated.

6.	Press any key to begin copying files to the disk.

7.	Place additional diskettes in the disk drive as you are prompted.

8.	Label the diskettes as directed.

9.	When you are finished making setup diskettes, run Setup by doing one of the following:

Place DISK1DOS into the computer's floppy drive and run the DOS Client 32 Setup program.

Or

Place DISK1WIN into the computer's floppy drive and run the Windows Client 32 Setup program.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing Support for Host MIB
Installing Support for Host Resources MIB

Note: All settings in this dialog box are optional.

To set up support for Host Resources MIB

1.	If your computer has a local device such as a printer, tape drive, or modem that you want to record in the Host Resources MIB inventory database, click Add.

2.	Type any information you want to record for the printer, modem, or tape drive connected to your computer.

3.	Click OK.

4.	Enter the number of directories away from the root directory that you want the Host MIB agent to scan for installed software.

5.	List the paths to any directories you want to include in the inventory scan that are more levels away from the root than number entered in Step 4.

5a.	Click Add in the Additional Search Paths box.

5b.	Type the path to the directory you want Host MIB to inventory.

5c.	Click OK.

Note: You can search all subdirectories by typing "\*.*" after the directory name. For example, the path "C:\WINDOWS\*.*" makes the Host MIB agent search C:\WINDOWS and all subdirectories below the WINDOWS directory.


Installing Unlisted ODI LAN Drivers

You can install a LAN driver that is not included with Client 32* Setup by providing the driver and the .LDI or .INS files on disk or on a network drive.

To use an unlisted driver

1.	In the ODI* Driver Path dialog box, type the path to the directory containing the unlisted driver.

Drivers with a .LAN extension are 32-bit. Drivers with .COM extension are 16-bit.

2.	Click OK.

3.	Select the name of the network board your computer uses.

4.	Click OK.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Installing from CD-ROM

To install Client 32* from a local CD-ROM drive

1.	Insert the CD into the CD-ROM drive.

2.	Change to root of the Client 32 CD-ROM.

3.	Choose to run Setup from Windows** or from DOS.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


LOAD/UNLOAD

Loads a Client 32* module onto the NIOS core.

Syntax: LOAD | UNLOAD module_name

Example: UNLOAD CLIENT32.NLM

Note

STARTNET.BAT uses LOAD commands to load NLM software on the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


LOCALE.CFG

LOCALE.CFG is a companion file to INSTALL.CFG used for internationalization. Countries that use a LOCALE.CFG file run INSTALL.EXE from a batch file that that specifies the proper file to use.

LOCALE.CFG files are subsets of INSTALL.CFG and use the same syntax for the sections it supports. You should not edit any LOCALE.CFG file.


Listing Devices for Host MIB

The Host MIB agent reports inventory information for the computer to an SNMP management console. Because DOS does not keep track of local devices such as printers, modems, and tape drives, the Host MIB agent relies on user input to describe these items.

Enter the name of the printer, modem, or tape drive physically attached to your computer. Settings are kept in the Host MIB section of NET.CFG.


Loading 32-bit ODI Drivers

The following example illustrates the load order of modules in STARTNET.BAT for a computer using a 32-bit ODI* LAN driver:

NIOS.EXE

LOAD LSLC32.NLM

LOAD CMSM.NLM

LOAD [ether  | token  | fddi]TSM.NLM

LOAD 32-bit ODI_driver .LAN [configuration parameters ]

LOAD IPX.NLM

LOAD CLIENT32.NLM

Note: If you use more than one frame type, repeat the ODI LAN driver load line for each frame type. Specify the frame type and other required parameters on the load line. For example:

LOAD CNE2000.LAN FRAME=802.2 IRQ=3 RETRIES=5

LOAD CNE2000.LAN FRAME=802.3 IRQ=3 RETRIES=5

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Loading LAN Drivers

Overview

Loading 32-bit ODI Drivers

Loading 16-bit ODI Drivers

Using 16-bit Protocol Stacks with Client 32

Adjusting Driver Settings


Logging In to a NetWare Network

You can log in to a NetWare* network from a DOS prompt or from Windows**. If you want to log in every time you boot the computer, you can add the LOGIN command line in the AUTOEXEC.BAT or, for Windows computers, you can place the Login icon in the Startup group or add LOGIN.EXE to the load line in the WIN.INI file.

For more information on Windows login, see LOGINW31.HLP, in the WINDOWS\NLS\ENGLISH directory.

Prerequisites

An account on a NetWare server or Directory tree

Client 32* software is running on the computer

Preferred Tree or Preferred Server setting in NET.CFG (if you have not done this, make the change in NET.CFG and reboot the computer)

To log in to a NetWare network from DOS

1.	At the DOS pompt, change to the first network drive (usually F:) by typing the drive letter and pressing Enter.

2.	Type "LOGIN" username  and press Enter.

For example, to log in to context "sales.corp" as user "User_1," type:

LOGIN user_1.sales.corp <Enter>

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


MODULES

Lists and displays information about the Client 32* modules loaded on the computer.

Syntax: MODULES

Example: MODULES

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Minimizing Memory Usage

You can limit the amount of memory Client 32* uses by adjusting several Client 32 parameters. The following table describes the effect that changing memory parameters will have on the client.

To decrease memory usage of Client 32

1.	Open the computer's NET.CFG in a text editor.

NET.CFG is located in the Client 32 working directory (NOVELL\CLIENT32, by default).

2.	Set the following parameters to specified values, using NET.CFG syntax.

Parameter	Value
Max Cache Size	0 - 1000
Cache Writes	off
Max Buffer Size	If your network board uses bus-mastering, increasing this setting increases system memory usage. Otherwise, system memory usage is usually unaffected by this setting. See the online help for more information.
3.	Save your changes and exit the editor.

4.	Unload and reload Client 32 software or reboot the computer to make the changes effective.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Modifying Driver Settings

Setup uses the driver settings from the computer's current driver as the defaults for the driver you are installing. You can edit these settings in the Driver Settings dialog box. Driver settings vary, but most drivers include settings for the following:

Parameter	Description
Hardware Interrupt (IRQ)	The hardware interrupt the driver uses to access the processor. Network boards typically use interrupt 3, but if you have multiple LAN boards or if you have other boards installed, you may need to change this number to avoid interrupt conflicts.
Base I/O Port	The address of the Input/Output port.
Frame Type	The frame type or types the network is using.
Retries	The number of times the LAN driver attempts to attach to the network before sending an error code to NIOS.
Node Address	The address of the LAN board uses on the network.


MonitorCommunity

Specifies the name of the SNMP community that has rights to query the computer for inventory information. This parameter is used only if EnableMonitorCommunity is set to SPECIFIED.

Syntax: MonitorCommunity = name

Default: public

Example:

[SNMP]

MonitorCommunity = private


Mounting a CD-ROM Volume

If you have a CD-ROM drive attached to a NetWare* server, you can mount the Client 32* CD-ROM as a server volume. Mounting a CD-ROM volume is the fastest way to create a network install directory if you plan to use the Windows**-based Setup for user-initated installations,

Note: If you plan to use ACU to upgrade clients on the network, you should run Client Setup from a network directory instead of from a CD-ROM volume.

To run Client 32 Setup from a CD-ROM volume

1.	At a NetWare server with a CD-ROM attached, mount the Client 32 CD-ROM as a volume of the server.

For example, to mount a CD-ROM volume labeled C32SETUP, enter the following at the server console:

CD MOUNT C32SETUP

2.	Grant the users that need to install Client 32 Read and File Scan rights to the root directory of the CD-ROM.

For example, to grant the group "Upgrade" access to the C32SETUP volume, change to the root of the volume and enter the following at a DOS prompt:

RIGHTS C32SETUP: RF /NAME=Upgrade

3.	Run SETUP.EXE or INSTALL.EXE from the root of the CD-ROM volume.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NET.CFG Parameters Affecting Speed

The following NET.CFG parameters affect the speed of Client 32* software:

Parameter	Value
Cache Writes	on
Close Behind Ticks	>18
Delay Writes	on
File Cache Level	3 or 4
Large Internet Packets	on
LIP Start Size	576 for WAN connectivity or 65535 for LAN connectivity
Max Cache Size	Depends on RAM free memory available
Opportunistic Locking	on
PB Buffers	1-10
Pburst Read Window Size	24 for most networks
Pburst Write Window Size	24 for most networks. 64 for small LANs
Signature Level	0 or 1 (Before changing this setting, make sure your users do not require high security)
True Commit	off (unless you require a high level of data integrity)
Use Video BIOS	off
IPX Frame Types	Bind only to the necessary frame types (Note that 32-bit drivers do not use NET.CFG--the frame type must be specified on the driver's load line)
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NWDETECT.EXE

NWDETECT.EXE compares the version stamp and the client type on the client computer with the version information listed on the NWDETECT.EXE command line.

Syntax: NWDETECT [options]

Example: NWDETECT C32 1.1.2

Exit Codes:

0 =	No error. The versions matched.

1 =	Error. The versions did not match or the install stamp was not found.


NWDETECT.EXE Exit Codes

NWDETECT.EXE returns an exit code of "0" in the following circumstances:

The "Name=" line in the Install Stamp section of the client’s NET.CFG does not match the [name] option on the command line.

The major, minor, and revision versions in the Install Stamp section do not match the [version] option on the command line.

The client type (VLM, NETX, NIOS) does not match the [/T(client type)] option on the command line.

An Install Stamp does not exist on the client computer.

Any combination of the above.


NWDETECT.EXE Options

The following table describes the options available for NWDETECT.EXE.

Option	Description
name	A string NWDETECT.EXE compares with the string listed on the NAME = line.
version1	Specifies the major, minor, and revision version in #.#.# format. If you use the [version2] option, this number represents the starting version.
version2	Specifies the ending version in #.#.# format. You can use this option to test for a version range.
/T client_type	Detects the type of client loaded. Valid client types are NETX, VLM, and NIOS (Client 32).
/P "prompt text"	Prompts the user if other options return "True." The user must be able to answer the prompt with a "Y" or "N." A "Y" returns an exit code of 0. An "N" returns an exit code of 1.
/C path\filename	Specifies the path and filename where NWDETECT.EXE reads the Install Stamp. NET.CFG is the default file if no file is specified.
/NS	Detects the presence of the Install Stamp in the NET.CFG file.


NWIP_Domain_Name

Syntax: NWIP_Domain_Name = domain_name

Default: none

Example:

[NWIP]

NWIP_Domain_Name = sales_domain


NWLOG.EXE

NWLOG.EXE writes the date, time, and network information for the computer that runs the program to the file specified on the command line. You can use NWLOG.EXE to record the status of the Client 32* upgrade.

Syntax: NWLOG [/F path\filename] [/M "message"] [/R #]

Example: NWLOG /F C:\NOVELL\CLIENT32\LOG

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


NWLOG.EXE Options

The following table describes the options available for NWLOG.EXE.

Option	Description
[/F path\filename ]	Path and filename to the log file where NWLOG.EXE writes the log entry.
[/M "message" ]	Additional message to include in the log entry. The message must be in quotes. The total amount of alphanumeric characters allowed for the message and NWLOG command line syntax is 125.
[/R number_retries ]	The number of times NWLOG.EXE tries to open the log file. The default number is 5.


NWSTAMP.EXE

NWSTAMP.EXE writes version information specified on the command line to the computer's NET.CFG file (or to the file you specify) in the Install Stamp section.

Syntax: NWSTAMP name version [/B] [/C path]

Example: NWSTAMP C32 1.2.a

Notes

The Install Stamp section contains the following four lines:

Name = name
Major Version = number
Minor Version = number
Revision Version = number

NWDETECT.EXE compares the values in the Install Stamp section with those listed on the NWDETECT.EXE command line.


NWSTAMP.EXE Options

The following table describes the options available for NWSTAMP.EXE.

Parameter	Description
name	Specifies the word NWSTAMP.EXE places on the "Name=" line. The name cannot contain spaces.
version	Specifies the major, minor, and revision versions NWSTAMP.EXE uses to write version information. Use the #.#.# format to specify the version. For example, NWSTAMP.EXE writes "4.1.0" to the NET.CFG as follows: Major Version = 4  Minor Version = 1 Revision Version = 0
[/B (path\filename)]	Backs up NET.CFG using the path and filename specified.
[/C path\filename]	Writes the stamp information to the file specified.


NameServerAddress Option

Syntax: NameServerAddress = IP_ADDRESS

Default: 000.000.000.000

Example:

NameServerAddress = 1.2.3.4


ODI LAN Driver Modules

Overview

You can use 32-bit ODI* or 16-bit ODI MLID modules with Client 32*. MLID software controls the network board and 32-bit ODI and 16-bit ODI protocols.

Note: ODI LAN drivers (Hardware Specific Modules) are supplied by network board vendors and are not included in this list.

32-bit Support Modules

LSLC32.NLM

CMSM.NLM

ETHERTSM.NLM

TOKENTSM.NLM

FDDITSM.NLM

PC32MLID.LAN

PDOSMLID.NLM

SROUTE.NLM

16-bit Support Modules

LSL.COM

N16ODI.COM

NESL.COM

PDOSETH.COM

PDOSFDDI.COM

PDOSTOK.COM

ROUTE.COM

Examples

Example of 32-bit ODI LAN Driver

Example of 16-bit ODI LAN Driver

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Operating System and Protocol Keywords

The following table describes the keywords for operating systems and protocols used in INSTALL.CFG.

Keyword	Description
D	Marks a file as necessary for Client 32* DOS support. Setup copies the file only if the "UpdateDOSSystemFiles=" line is set to "True."
W	Marks a file as necessary for Windows support. Setup 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. Setup copies the file if either the "Install Windows=" 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 SMS support.
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Optimizing STARTNET.BAT

STARTNET.BAT groups commands that load the programs necessary to attach to a Novell* NetWare* network. Setup can edit a computer's AUTOEXEC.BAT to call STARTNET.BAT so that the network loads automatically each time the computer boots.

You can edit the STARTNET.BAT to load only the network drivers and programs you want to use or to optimize the way the programs load. Use the following rules when editing STARTNET.BAT to determine the load order for the networking software:

NIOS.EXE should load before any 16-bit TSRs and must load before any NLM programs.

If you are loading 32-bit ODI* LAN drivers, make sure to specify the interrupt, port, and frame type on the load line for each driver.

If you are using more than one frame type, make a separate LAN driver load line for each frame type.

IPX.NLM binds to all LAN adapters installed at the time it loads.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Optional Protocols

Overview

You can install support for protocols by loading the appropriate module on your computer.

TCP/IP

Overview of TCP/IP and NetWare/IP

TCPIP.NLM

NWIP.NLM

SPX_SKTS.NLM

Network Management

SNMP.NLM

SNMPIPX.NLM

SNMPUDP.NLM

HOSTMIB.NLM

NMR.NLM

TSASMS.COM

Token Ring Source Routing

Overview of Setting Up Source Routing

SROUTE.NLM

ROUTE.COM


OverWriteReadOnlySYSFiles

This line of INSTALL.CFG specifies whether Client 32* Setup overwrites system files that are flagged read only.

Syntax: OverWriteReadOnlySYSFiles = TRUE | FALSE

Default: FALSE

Example:

[Setup]

OverWriteReadOnlySYSFiles = TRUE | FALSE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


OverrideLocalSettings

Syntax: OverrideLocalSettings = TRUE | FALSE

Default: FALSE

Example:

[TCP/IP]

OverrideLocalSettings = False

Notes

TRUE makes Setup use the values listed in the section rather than information in a computer's NET.CFG.

FALSE makes Setup use the settings in this section only if they are not specified in the computer's NET.CFG.

This setting is valid for the [TCP/IP], [NWIP], [SNMP], [HOSTMIB], and [TSA] sections.


Overview NWIP.NLM

Description

NWIP.NLM provides NetWare/IP suport on the computer. NetWare/IP enables IPX-based applications to communicate over Internet Protocol (IP) on the network.

Dependencies

Core Modules

TCPIP.NLM

NET.CFG Section

NWIP


Overview of Automatic Client Upgrade

To run Automatic Client Upgrade, you need to edit the system, container, or personal login script for the users you want to upgrade. Because the login script executes in DOS, you can use only the DOS-based Setup program (INSTALL.EXE) to upgrade clients automatically. The Windows**-based Setup program (SETUP.EXE) will not run from a login script.

ACU consists of four programs that run from a login script. Three programs ensure that computers run Client 32* Setup only when an update is required. A fourth program reboots client computers from a login script. These programs have options you can use to customize ACU for your network.

Important: Refer to ACU.TXT in the \ADMIN1 directory of the Client 32 software for more detailed information about ACU.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of CLIENT32.NLM

Description

CLIENT32.NLM extends DOS to include network resources, similar to NetWare DOS Requester* (VLM*) software and the NETX shell.

Dependencies

LSLC32.NLM

ODI* LAN driver modules

IPX.NLM

NET.CFG Section

NetWare DOS Requester

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of CMSM.NLM

Description

CMSM.NLM is the Media Support Module (MSM) for the ODI* LAN driver. The MSM standardizes and manages primary details of interfacing ODI MLID* software to LSL* and the operating system.

The MSM contains initialization and runtime functions common to all drivers. This module also enables the Hardware Specific Module (HSM), the ODI LAN driver, to be used on various platforms.

For more information see "Open Data-Link Interface" in the Concepts  manual.

Dependencies

LSLC32.NLM

[ether | token | fddi]TSM.NLM

Configuration Settings

None

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Changes Setup Makes to Clients

Depending on the software you choose to install, Setup makes the following changes on a computer:

Creates a new directory for Client 32* files.

Creates NET.CFG and STARTNET.BAT in the Client 32 directory based on existing versions of these files, if available.

Makes changes to AUTOEXEC.BAT and CONFIG.SYS. Setup also makes changes to the WIN.INI and SYSTEM.INI files when installing support for Windows**.

Adds a group file and copies several .DLL files to the WINDOWS directory for Windows clients.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Client 32 Modules

What Is a Client 32 Module?

Client 32* functionality that is divided into separate pieces of software, or modules. A module can be a LAN driver for a network board, a protocol driver, or a driver for other network functions, such network backup.

The Client 32 architecture uses the NetWare Input/Output Subsystem (NIOS) to manage Client 32 modules, so NIOS.EXE must be loaded before you can load any other modules.

What Types of Modules Are There?

Client 32 requires certain core modules to be loaded on the computer, regardless of the computer's configuration. These modules are NIOS.EXE, LSLC32.NLM, IPX.NLM, and CLIENT32.NLM.

You load other modules depending on the computer's network board and network environment.

How Do I Use Modules?

Use the LOAD utility to add modules to NIOS. You should place commands in the STARTNET.BAT file for modules you want to load each time the computer boots. Many Client 32 modules require other modules to be loaded before the module can load. Check the information on the modules you want to use for information on load order.

You can remove modules from NIOS by using the UNLOAD utility.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Client 32 Utilities

Utilities are internal programs in NIOS that help you manage Client 32. For example, you can use the LOAD utility to add Client 32 modules to NIOS.

Client 32 utilities run from a DOS prompt. You must have NIOS.EXE loaded on the computer to run the utilities.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of ETHERTSM.NLM

Description

ETHERTSM.NLM is the Topology Specific Module (TSM) for Ethernet networks. TSM software manages operations unique to a specific media type, such as Ethernet, token ring, and Fiber Distributed Data Interface (FDDI). ETHERTSM.NLM provides support for all Ethernet frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM

Configuration Settings

None


Overview of FDDITSM.NLM

Overview

FDDITSM.NLM is the Topology Specific Module (TSM) for Fiber Distributed Data Interface (FDDI) networks. TSM software manages operations unique to a specific media type, such as Ethernet, token ring, and Fiber Distributed Data Interface (FDDI). FDDITSM.NLM provides support for all FDDI frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM


Overview of HOSTMIB.NLM

Description

HOSTMIB.NLM is an agent that enables the computer to be manged over SNMP using the Host Resources MIB database format.

Dependencies

SNMP.NLM

NET.CFG Section

Host MIB


Overview of Host Resources MIB

The Host Resources MIB agent (HOSTMIB.NLM) can inventory a computer's hardware and software configuration and send the data to the SNMP management console.

Because the Host MIB agent cannot detect printers, modems, or tape drives, you can type the name of any of these devices you have connected to the computer. Setup saves these values to NET.CFG. During an inventory scan, the agent reads the NET.CFG file for information on these devices. If you do not have any devices to report, leave this field blank.

The Host MIB agent can also scan for software programs on the computer by searching for .EXE, .COM, and .BAT files. You can increase the speed of this scan by limiting the depth of the search. For example, if you know that the computer does not have any application executable deeper than three directories from the root directory, you can limit the scan to 3.

If there are a few directories that have applications at a deeper level, you can specify these directories individually.


Overview of IPX.NLM

Description

IPX.NLM transports data using the Internetwork Packet Exchange* (IPX*) and Sequenced Packet Exchange* (SPX*) protocols.

Dependencies

NIOS.EXE

LSLC32.NLM

NET.CFG Section

Protocol IPX

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Installing Client 32

There are several ways to install Client 32* software, so you should determine which installation method works best for you before you run the Setup program.

If you want to upgrade several existing clients, installing Client 32 from the network is the easiest way to install. You can edit the INSTALL.CFG file so users do not need to supply configuration information.

If you only need to install Client 32 on a few computers or if the computers are not yet connected to a network, you can install Client 32 from a local drive.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Installing from a Local Drive
Overview of Running Setup from a Local Drive

If you need to install Client 32* on only one or two computers, or if the computers are not yet connected to a network, you can install Client 32 from a local drive.

You can run Setup from a local CD-ROM drive or floppy drive. If the computer has an internet connection, you can download Client 32 from NetWire* and run Setup from the computer's hard drive.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LAN Drivers

Client 32* supports 16-bit and 32-bit ODI* LAN drivers. For increased performance and stability, you should use a 32-bit ODI LAN driver when one is available for your computer's network board.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LSL.COM

Description

LSL.COM is the 16-bit Link Support Layer* (LSL*) for Client 32*. LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.

For more information on LSL, see the Concepts  manual.

Configuration Settings

Link Support

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of LSLC32.NLM

Desciption

LSLC32.NLM is the 32-bit Link Support Layer* (LSL*), for Client 32*. LSL allows one network board to service several communications protocol stacks. It also allows several network boards to service the same protocol stack.

For more information on LSL, see the Concepts manual.

Dependencies

NIOS.EXE

NET.CFG Settings

Link Support

Note: LSLC32.NLM uses only the Max Buffer Size parameter in the Link Support section of NET.CFG.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of N16ODI.COM

Description

N16ODI.COM coordinates memory access between NIOS and the 16-bit LSL.COM module. This module prevents NIOS from running foreground events while LSL.COM is using real mode interrupts.

Dependencies

NIOS.EXE (can load before or after)

LSL.COM

Note: N16ODI.COM enables you to load the following modules:

PDOS[eth | tok | fddi].COM

PDOSMLID.NLM

PC32MLID.LAN


Overview of NESL.COM

Description

NESL.COM manages events for the 16-bit real mode environment. Its function is similar to LSL.COM but it directs event objects instead of data objects.

Dependencies

LSL.COM (can load before of after)


Overview of NIOS.EXE

Description

The NetWare Input/Output Subsystem (NIOS.EXE) is the first Client 32* module loaded. NIOS.EXE creates the flat memory environment needed to load other components and controls the loading and unloading of other Client 32 modules. NIOS.EXE also serves as the interface between the operating system and Client 32.

NET.CFG Section

NIOS

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of NMR.NLM

Description

The Network Management Responder module (NMR.NLM) provides information about a computer to network management utilities such as ManageWise*.

Dependencies

IPX.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of NetWare TSA for SMS

The workstation Target Service Agent (TSA) is a terminate-and-stay-resident program called TSASMS.COM that processes data moving between the client computer and a Storage Management Server Services* (SMS*) server. The agent makes it possible for an SMS server to back up and restore files on the client computer.

To install TSA for SMS support, you need to supply some information about the SMS environment on the client computer. The client maintains this information in the "NetWare* DOS TSA" section of the NET.CFG file.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of ODI

The Open Data-Link Interface* (ODI*) specifiction sets standards for developing Multiple Link Interface Driver (MLID) software and media independent protocol stacks.

The MLID architecture decouples device drivers from protocol stacks. This architecture requires three modules that make up the MLID architecture: the Media Support Module (MSM), the Topology Specific Module (TSM), and the Hardware Specific Module (HSM).

For Client 32, these modules are loaded in the following order after NIOS.EXE:

LSLC32.NLM

CMSM.NLM

[ether | token | fddi]TSM.NLM

32-bit_LAN_Driver.LAN

For more information, see "Open Data-Link Interface" in Concepts.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Optimizing Client 32

You can optimize Client 32* software for your networking environment.  By default, Client 32 is configured for high speed with moderate use of memory and data protection. You can adjust Client 32 to optimize its performance in any of these areas. Be aware that optimizing the client in one area can mean a performance cost in other areas, as the following table indicates:

Optimize for	Cost
Speed	Memory, Data Integrity
Data Integrity	Speed
Memory	Speed
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PC32MLID.LAN

Description

PC32MLID.LAN enables 32-bit ODI* stacks to communicate with 16-bit ODI LAN drivers.

Dependencies

NIOS.EXE

LSL.COM

N16ODI.COM

NESL.COM

LSLC32.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSETH.COM

Description

This module enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

NIOS.EXE

LSL.COM

N16ODI.COM

LSLC32.NLM

PDOSMLID.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSFDDI.COM

Description

This module enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

NIOS.EXE

LSL.COM

N16ODI.COM

LSLC32.NLM

PDOSMLID.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSMLID.NLM

Description

PDOSMLID.NLM helps enable the 32-bit ODI* modules to communicate with 16-bit protocol stacks.

Dependencies

NIOS.EXE

LSL.COM

LSLC32.NLM

PDOS[eth | tok | fddi].COM

N16ODI.COM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of PDOSTOK.COM

Description

PDOSTOK.COM enables 16-bit ODI* protocol stacks to use 32-bit ODI LAN drivers.

Dependencies

NIOS.EXE

LSL.COM

N16ODI.COM

LSLC32.NLM

PDOSMLID.NLM

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of ROUTE.COM

Description

ROUTE.COM enables the computer to communicate with network resources across IBM** token ring network bridges. ROUTE.COM supports 16-bit ODI* LAN drivers.

Dependencies

Core Modules

Token ring ODI LAN driver

Settings

Configure ROUTE.COM using options on the command line.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Removing Client 32

Client 32* does not have an uninstall program, so you must edit system files and delete directories if you want to remove the installation.

If you remove Client 32 files from the computer, you must run Client 32 Setup to replace the client software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Running Setup from the Network

Installing from the network is the most efficient way to upgrade several existing clients. Installing from the network also enables you to control the amount of user input Setup requires.

There are 3 methods for runing Client 32* setup over the network:

Automatic Client Upgrade (ACU)--DOS-based Setup only

Network Application Manager (NAM)--Windows-based Setup only

User-Initated install--DOS or Windows-based Setup

Use the following table to detemine which method is appropriate for the clients on your network.

Client	Method of Install
Windows** 3.x NDS*	NAM or ACU
DOS or Windows bindery	ACU
Any supported client	User-Initiated
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of SNMP

Simple network management protocol (SNMP) is a language that makes it possible to manage different types of computers over a network. When you load the SNMP agent on your computer, management consoles that use SNMP can perform the following types of management tasks on the computer.

Configure software settings

Gather information about the computer

Monitor computer events

You can control the type of access SNMP management consoles have to a computer by specifying community names in the NET.CFG file.


Overview of SNMP.NLM

Description

SNMP.NLM enables the computer to be monitored and controlled by management consoles over Simple Network Management Protocol. It also implements the "system," "interfaces," and "snmp" groups of MIB-II.

This module is an implementation of an extensible SNMP 1.0 agent.

Dependencies

Core modules

NET.CFG Section

Desktop SNMP


Overview of SNMPIPX.NLM

Description

SNMPIPX.NLM implements an IPX transport provider for SNMP. It monitors the SNMP well-known IPX socket to receive SNMP request PDUs and to send out the SNMP reply PDUs.

Dependencies

IPX.NLM

SNMP.NLM

NET.CFG Section

SNMP Transport Provider IPX


Overview of SNMPUDP.NLM

Description

SNMPUDP.NLM implements a UDP transport provider for SNMP. It monitors the SNMP well-known port to receive SNMP request PDUs and to send out the SNMP reply PDUs.

Dependencies

SNMP.NLM

TCPIP.NLM

Note: Load SNMP.NLM first, then TCPIP.NLM, and then SNMPUDP.NLM.

NET.CFG Section

SNMP Transport Provider UDP


Overview of SPX_SKTS.NLM
SPX_SKTS.NLM

Description

This module enables the IPX*/SPX* protocols under Novell's WINSOCK.DLL.

Dependencies

IPX.NLM

Configuration Settings

None

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of SROUTE.NLM

Overview

SROUTE.NLM enables communication across IBM** token ring network bridges. SROUTE.NLM supports 32-bit ODI LAN drivers.

Dependencies

Core modules

Configuration

Configure SROUTE.NLM using options on the module's LOAD line.


Overview of Setting Up Named Pipes

The Named Pipes protocol is the basis for communication between the client and advanced client-server applications such as Microsoft** SQL Server and Microsoft Comm Server software.

To set up support for Named Pipes on a computer, you must install Client 32 and then edit the STARTNET.BAT file to run DOSNP.EXE. The Setup programs copy DOSNP.EXE to the Client 32* working directory, but they do not setup a computer to run Named Pipes.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up NetBIOS

NetBIOS (Network Basic Input/Output System) is the IBM** standard protocol for applications developed to run peer-to-peer communications on the IBM PC Network and the IBM Token Ring Network. NetBIOS has become widely accepted as a standard for network interfacing.

Client 32* provides a NetBIOS driver that emulates the NetBIOS protocol. This emulator allows the NetWare* IPX* to interface with the NetBIOS Interrupt 5Ch and an alternate interface, Interrupt 2Ah.

The NetBIOS software provided by Novell* is an emulator because it does not transmit NetBIOS packets. Instead, NetBIOS packets are encapsulated in IPX packets, and the IPX packets are transmitted.

The NetBIOS protocol was designed for small-scale networks. While Novell has added functionality to the original specification, the NetBIOS emulation still works most effectively with small-scale networks.

If your network contains several thousand workstations and your LAN segments are interconnected with more than one router, use SPX* instead of NetBIOS if your applications support SPX.

To set up support for NetBIOS on a computer, you must install Client 32 and then edit the STARTNET.BAT file to run the NetBIOS driver, NETBIOS.EXE. The Setup programs copy NETBIOS.EXE to the Client 32 working directory, but they do not setup a computer to run NetBIOS.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Setting Up Source Routing

The NetWare* source-routing drivers (SROUTE.NLM and ROUTE.COM) enable communication across IBM** token ring network bridges. SROUTE.NLM supports 32-bit ODI* LAN drivers. ROUTE.COM supports 16-bit ODI LAN drivers.

To set up support for source routing on a computer, you must install Client 32* and then edit the STARTNET.BAT file to load SROUTE.NLM. The Setup programs copy SROUTE.NLM to the Client 32 working directory, but they do not setup a computer to run source routing. You also need to load source routing on a NetWare server.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Support for Windows for Workgroups

You can install support for peer-to-peer networking in Windows** for Workgroups 3.11. Peer-to-peer networking enables you to share and access printers and disk drives attached to a workstation over the network.

You can use the following protocols for Microsoft** peer-to-peer networking with Client 32*:

NetBEUI

IPX*/SPX* Compatible Transport with NetBIOS

IPX/SPX Compatible Transport

Note: You must set up Client 32 to use 16-bit ODI* LAN drivers if you want to use peer-to-peer networking. The peer-to-peer networking software included with Windows for Workgroups does not support 32-bit ODI LAN drivers.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of TCPIP.NLM

Description

TCPIP.NLM enables Transmission Control Protocol/Internet Protocol on client computers.

Dependencies

Core Modules

Note: Load TCPIP.NLM before loading CLIENT32.NLM.

NET.CFG Section

Protocol TCPIP


Overview of TOKENTSM.NLM

Description

TOKENTSM.NLM is the Topology Specific Module (TSM) for token ring networks. TSM software manages operations unique to a specific media type, such as Ethernet, token ring, and Fiber Distributed Data Interface (FDDI). TOKENTSM.NLM provides support for all token ring frame types.

Dependencies

NIOS.EXE

LSLC32.NLM

CMSM.NLM

Configuration Settings

None


Overview of TSASMS.COM

Description

TSASMS.COM is the Target Service Agent that provides workstation support for NetWare* Storage Management Services* (SMS*). You can use TSA.NLM and SMS to create backup copies of local files on a network storage device.

NET.CFG Section

NetWare DOS TSA

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Turning Off Client 32

Client 32* software does not have an uninstall program, so you must edit system files and delete directories if you want to remove the installation.

If you plan to use Client 32 again on the computer, you can "turn off" Client 32 by commenting out the line in the AUTOEXEC.BAT that calls STARTNET.BAT in the CLIENT32 directory.

Client 32 does not replace the VLM* or NETX client so you can revert to these clients simply by specifying the STARTNET.BAT file in the NWCLIENT directory.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of Using Client 32

Client 32* software extends the capabilities of DOS and Windows** programs by adding extra drives to the computer's environment and redirecting print jobs to network printers.

In Windows, you can access network files through File Manager. Also, you can use Netware User Tools in Windows for mapping drives, capturing printer ports to network printers, and sending network broadcast messages.

In DOS, you can use command line utilites such as MAP, CAPTURE, and SEND to perform these funtions. Type "/?" on the command line for syntax information on each of these commands.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of the DOS-based Install

You can control the DOS-based setup program (INSTALL.EXE) by editing INSTALL.CFG. If you plan to use ACU or run user-initiated DOS-based installations from the network, you should take the time to modify INSTALL.CFG for your networking environment.

Note: The Windows-based setup program (SETUP.EXE) does not use INSTALL.CFG.

You can edit INSTALL.CFG to control the following aspects of the DOS-based Client 32* Setup:

Installation files and target directories

Default parameters for Client 32

Setup options

Protocol support

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Overview of the Setup Programs

You can install Client 32* software from DOS or from Windows. Both setup programs support the same installation options and both programs can run from network or local drives, with the following restrictions:

If you want to install Client 32 using Automatic Client Upgrade (ACU), you must run the DOS-based installation, because the Windows setup program cannot run from a login script.

If you want to install Client 32 using Network Application Manager (NAM), you must run the Windows-based installation.

If you are using a networked version of Windows**, you must run the DOS installation.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


OverwriteNewerFiles

This line of INSTALL.CFG specifies whether Client 32* Setup replaces files that have a later time and date stamp than comparable files on the source disk.

Syntax: OverwriteNewerFiles = TRUE | FALSE

Default: FALSE

Example:

[Setup]

OverwriteNewerFiles = TRUE | FALSE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


OverwriteReadOnlyFiles

This line of INSTALL.CFG specifies whether Client 32* Setup overwrites files flagged as read only.

Syntax: OverwriteReadOnlyFiles = TRUE | FALSE

Default: FALSE

Example:

[Setup]

OverwriteReadOnlyFiles = TRUE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


OverwriteStartnetBat

This line of INSTALL.CFG specifies whether Client 32* Setup overwrites STARTNET.BAT in the Client 32 working directory.

Sytnax: OverwriteStarnetBat = TRUE | FALSE

Default: TRUE

Example:

[Setup]

OverwriteStarnetBat = TRUE

TRUE overwrites STARTNET.BAT in the Client 32 working directory.

FALSE creates a STARTNET.NEW file.

The default working directory for Client 32 is NOVELL\CLIENT32. VLM* and NETX clients should not be affected by this parameter.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Password

Sets a password that a network supervisor must provide before SMS* can back up the client's local drives.

Syntax: Password = 1-10_character _word

Default: none

Example:

[TSA]

Password = b@Kup

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Preparing to Install Client 32

Make sure the the client has the following configuration before installing NetWare* Client* 32* software.

Installed Components

386 processor or better

At least 3 MB of free disk space

At least 4 MB of RAM

At least 500 KB of free lower memory (to run the Setup program only)

A memory manager such as HIMEM.SYS, EMM386.EXE, QEMM, or 386MAX

A network board with the appropriate LAN driver

A physical connection to a NetWare network

A supported operating system

Supported Operating Systems

Novell* DOS* 7

MS-DOS** 5.x or 6.x

PC-DOS 5.x , 6.x , or 7.0

Windows** 3.1x  or Windows for Workgroups 3.11

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Product Overview

What is Client 32

Client 32* is 32-bit software that enables computers running DOS and Windows** 3.1x to access resources on a Novell* NetWare* network.

Stable Network Connections

Client 32 is provides DOS and Windows computers a stable connection to NetWare networks. The requester runs in protected mode, so other programs running on a computer cannot interfere with memory reserved for the Client 32. If network services fail, Client 32 can automatically reconnect to the services when they become available again. Client 32 can also use multiple network boards on a computer, so if one board fails, the computer can continue to access the network from another board.

Full NDS Support

Client 32 is enables full support of NetWare Directory Services* (NDS). Using Client 32, you can browse for network services across multiple trees and use network services such as printing and running applications.

Protocol Support

Client 32 includes native support for IPX*/SPX*, TCP/IP, NetWare/IP, and SNMP (including Host Resources MIB).

TSA Support for Storage Management Services

Client 32 Setup can install a Target Service Agent (TSA) on workstations that enables a NetWare server to back up the workstation's local drives.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Protocol Sections in NET.CFG

Section	Protocol
Protocol TCPIP	TCP/IP support
NWIP	NetWare/IP*
Desktop SNMP	SNMP support
Host MIB	Host Resources MIB support
NetWare* DOS TSA	TSA for SMS*


REBOOT.COM

REBOOT.COM is a program that reboots a computer. REBOOT.COM has no command line options.

Syntax: REBOOT

Example:

REM Login Script Example

PAUSE

#G:REBOOT


ROUTE.COM Options

Adds functionality to the ODI LAN driver to support source routing among token ring networks.

Syntax: ROUTE [option1, option2,...]

Example: ROUTE BOARD=2, DEF

You can use any of the following command line options with ROUTE.COM.

Option	Explanation
BOARD = number	Specifies the number for the network board that ROUTE.COM binds to. The board number is determined by the order in which the LAN drivers are loaded, starting with board number 1. If you do not specify a board number, ROUTE.COM binds to board 1.
DEF	Prevents frames that have unknown destination addresses from being sent across single-route IBM bridges.
GBR	Sends General Broadcast frames to All Routes Broadcast frames.
MBR	Sends Multicast Broadcast frames to All Routes Broadcast frames.
NODES=number	Specifies number of table entries (between 8 and 255) in source routing table. The default value is 16.
HOPS=number	Specifies the number of bridges (up to 13) a packed can traverse. The default is 7.
TIME=number	The number of seconds (between 1 and 3640) the source router waits for a response before timing out a known route. The default is 10. Enter "0" to disable routing timeouts.
CLEAR	Clears source routing table and forces dynamic rebuilding of table by sending default frame type to each computer on the network.
REMOVE=number	Removes node address from the computer’s source routing table. Use this parameter when a bridge has gone down. Replace number with a 12-digit (6byte) hexadecimal number. If you specify fewer than 9 digits, ROUTE.COM adds a 4000h prefix to the nubmer. For example, REMOVE=2 is interpreted as REMOVE=400000000002.
TRA=number	A number (between 00 and 255) specifying a THIS RING ALTERNATE count for broadcasts. The source router alternates between source routed and non-source routed frames. The default is 00.
TRO=number	A number (between 00 and 255) specifying a THIS RING ONLY count for broadcasts. The default is 00.
XTX=number	Specifies the number of times (between 00 and 255) ROUTE.COM transmits on a timed-out route. The default is 02 times.
U	Unloads ROUTE.COM.
?	Displays command line help usage information.


RTF_TOPIC_825122342


Reaching Technical Support

When you purchase products from Novell*, you have a choice of services that put you in touch with all the technical resources you’ll need.

You have the following resources for technical support:

NetWire*

Network Support Encyclopedia Professional Volume* (NSEPro*)

Your local Novell Partner

Novell Technical Services*

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Removing Client 32

Purpose

To reverse all changes made by running Client 32* Setup on a computer.

To remove Client 32

1.	Delete the CLIENT32 directory.

2.	Open AUTOEXEC.BAT in a text editor.

3.	Delete the line that calls the STARTNET.BAT.

4.	Save the change and exit the editor.

5.	Remove any Client 32 Windows** components installed on the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Removing Client 32 Windows Components

Purpose

To reverse the changes Client 32* Setup makes to Windows** computers.

Note: This procedure is generalized for Windows 3.1 and Windows for Workgroups 3.11. Some tasks may not be applicable to removing Client 32 support for Windows from your computer.

To uninstall Client 32 support for Windows

1.	In Program Manager, switch to the NetWare* Tools window.

2.	Select each icon in the group and press Delete.

3.	With the focus on the empty NetWare Tools window, press Delete.

4.	From the File menu in Program Manager, choose Run.

5.	Type "SYSEDIT" on the command line.

6.	Click the SYSTEM.INI window.

7.	Do the following:

7a	Delete "VNETWARE.386" from the Network = line in the [386 Enh] section.

7b	Delete the "device = VLANINT.386" line from the the [386 Enh] section.

7c	Delete "netware.drv" from the "secondnet.drv = " or the "network.drv =" line in the [boot] section.

7d	Delete "Novell NetWare (v4.0)" from the "secondnet.drv =" or the "network.drv =" line in the [boot.description] section.

8.	Click the WIN.INI Window.

9.	Delete the "load = NWPOPUP.EXE" line from the [Windows] section.

10. Close SYSEDIT and save your changes to SYSTEM.INI and WIN.INI.

11.	Delete the Client 32 files from the Windows root and Windows SYSTEM directories.

12. If you installed support for TCP/IP, rename WINSOCK.OLD and WLIBSOCK.OLD in the Windows root and Windows SYSTEM directories to WINSOCK.DLL and WLIBSOCK.DLL, respectively.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Running Setup from NAM

Network Application Manager (NAM) is an add-on utility to NetWare Administrator (NWAdmin) that enables network network supervisors to create NDS* objects for applications. For information on using NAM to install Client 32* software, see APPSNAP.HLP, NAL.HLP, and README.NAL in the NAM\NLS\ENGLISH directory of the ADMIN2 diskette or the \ADMIN directory.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Running Setup from a Login Script

Running Automatic Client Upgrade

Overview

Determining When to Use ACU

Setting up Automatic Client Upgrade

Controlling the DOS-Based Setup

Using the ACU Programs

NWDETECT.EXE

NWSTAMP.EXE

NWLOG.EXE

REBOOT.COM

Sample Login Scripts

NDS Example

Bindery Example


Running Setup from the Network

After you create a network install directory, network users can run the DOS-based or Windows**-based Setup program from the network.

Prerequisite

Create a network install directory

To run a user-initiated Setup from the network

1.	Log in to the network.

2.	Map a drive to the network install directory.

3.	Run Client 32* Setup from Windows or from DOS.

Note: A network supervisor can influence the amount of user input for the DOS-based Setup by editing the INSTALL.CFG file in the network install directory.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


SROUTE.NLM Options

Syntax

LOAD SROUTE [board=number ] [name=board_name ] [def | gbr | mbr] [time=number ] [rsp=ar | nr] [clear | remove=number ] [xtx=number ] [tra=number ] [tro=number ] [unload (board=number )] [?]

Example

LOAD SROUTE BOARD=1 GBR

Option	Purpose
BOARD=number	Specifies the number for the network board you want to modify parameters on or load source routing for. The board number is determined by the order in which the LAN drivers are loaded, starting with board number 1. The defalut is 1.
NAME=board_name	Specifies the board name.
DEF	Sends all Unknown Unicast frames as All Routes Broadcast frames.
GBR	Sends General Broadcast frames to All Routes Broadcast frames.
MBR	Sends Multicast frames to All Routes Broadcast frames.
TIME=number	Specifies how often the source routing table is updated, in seconds. Enter an integer between 3 and 255. The default is 10.
RSP=AR | NR	Specifies how the computer responds to a broadcast request. NR responds directly to a broadcast frame. AR responds with an All Routes Broadcast frame. AR is the default.
CLEAR	Clears the source routing table and forces dynamic rebuilding of table. Use CLEAR when an IBM bridge has gone down and an alternate route is available.
REMOVE=number	Removes a specific node address from the computer's source routing table.
XTX=number	Specifies the number of times (between 00 and 255) SROUTE.NLM transmits on a timed-out route. The default is 02 times.
TRA=number	A number (between 00 and 255) specifying THIS RING ALTERNATE count for broadcasts. The source router alternates between source routed and non-source routed frames. The default is 00.
TRO=	A number (between 00 and 255) specifying a THIS RING ONLY count for broadcasts. The default is 00.
UNLOAD [BOARD=number ]	Removes the source routing support for the specified network board.
?	Displays command line help.


Sample Bindery Login Script for ACU

IF member of "update" THEN

MAP I:=SERVER1\SYS:\PUBLIC\CLIENT\DOSWIN

#I:NWDETECT /T NETX

IF ERROR_LEVEL = "1" THEN WRITE "Upgrading NetWare Client Software."

#I:INSTALL

IF ERROR LEVEL = "0" THEN

#I:NWSTAMP Novell_Inc_client32 4.1.0

#I:NWLOG /F I:\LOG\UPDATE.LOG /M "Upgrade Successful for user %LOGIN_NAME %NETWORK_ADDRESS:%P_STATION"

WRITE "Upgrade completed. Your computer will reboot to run the new software."

PAUSE

#I:REBOOT

ELSE

#I:NWSTAMP Novell_Inc_client32 4.0.0  #I:NWLOG  /F I:..\LOG\FAILED.LOG /M "%LOGIN_NAME %NETWORK_ADDRESS:%P_STATION. "Upgrade failed. Check NWCINST.LOG in the NETX directory for details."

WRITE "The upgrade program did not complete. Contact a network supervisor."

END

PAUSE

END

MAP DEL I:

END


Sample NDS Login Script for ACU

IF MEMBER OF "ClientUpdate" THEN

MAP I:=SERVER1\SYS:PUBLIC\CLIENT\DOSWIN

WRITE "Searching for client version information."

#I:NWDETECT Novell_Inc_Client32 4.0.0 4.2.0

WRITE "Detection completed"

IF ERROR_LEVEL = "0" then write "Updating NetWare Client."

#I:INSTALL

IF ERROR_LEVEL = "0" THEN

#I:NWSTAMP Novell_Inc_Client32 4.1.0

#I:NWLOG /f I:\LOG\UPDATE.LOG

WRITE "Update completed. Your machine will now reboot."

PAUSE

#I:REBOOT

ELSE

#I:NWSTAMP Novell_Inc_Client32 4.0.0

#I:NWLOG /F I:\LOG\FAILED.LOG /M "See NWCINST.LOG"

WRITE "Update failed. Contact a network supervisor."

END

PAUSE

END

MAP DEL I:

END


See Also
AUTOEXEC.BAT

Changes Setup Makes to All Clients

TCP/IP and NetWare/IP

Overview of TCP/IP and NetWare*/IP*

Configuring TCP/IP

Configuring NetWare/IP

Changes to TCP/IP Clients

SNMP and Host MIB

Overview of SNMP

Configuring SNMP

Overview of Host Resource MIB

Configuring Host Resources MIB

Changes to SNMP Clients

TSA for SMS

Overview of TSA for SMS*

Configuring TSA for SMS

Changes to TSA Cients


See Also 16_bit Protocols
Related Topics

Overview

Loading 32-bit ODI* Drivers

16-bit ODI Drivers

Adjusting Driver Settings


See Also 16_bit_ODI
Related Topics

Overview

Loading 32-bit ODI* Drivers

Using 16-bit Protocols with Client 32*

Core Modules

ODI LAN Driver Modules

Adjusting Driver Settings


See Also ACU When
Related Topics

Overview

Setting up Automatic Client Upgrade

Running Setup from a Login Script


See Also CLIENT32
Related Topics

IPX.NLM

LSLC32.NLM

NIOS.EXE

Core Modules


See Also CMSM.NLM
Related Topics

ETHERTSM.NLM

TOKENTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Driver Modules


See Also Changes All
Related Topics

Overview

Windows Clients

TCP/IP Clients

SNMP Clients

TSA Clients

Changes Setup Makes to Clients


See Also Changes O
Related Topics

All Clients

Windows Clients

TCP/IP Clients

SNMP Clients

TSA Clients

Changes Setup Makes to Clients


See Also Changes Win
Related Topics

Overview

All Clients

TCP/IP Clients

SNMP Clients

TSA Clients

Changes Setup Makes to Clients


See Also Config Driver
Related Topics

Choosing an ODI* Driver

Installing Unlisted LAN Drivers

Modifying Driver Settings


See Also DOS Options
Related Topics

Configuring Windows Components

TCP/IP NET.CFG Settings

NetWare*/IP* NET.CFG Settings

SNMP NET.CFG Settings

TSA NET.CFG Settings


See Also DOS Win
Related Topics

Install Options for DOS


See Also Driver C
Related Topics

Choosing an ODI* LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Changes Setup Makes to All Clients

NET.CFG Settings


See Also ETHERTSM
Related Topics

TOKENTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Driver Modules


See Also FDDITSM
Related Topics

ETHERTSM.NLM

TOKENTSM.NLM

Overview of ODI

ODI LAN Driver Modules


See Also Floppy O
Related Topics

Overview

Installing from downloaded disk images

Setting up Client 32*


See Also HOSTMIB section
Related Topics

Host MIB Section (NET.CFG)

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*

Configuring Protocol Support


See Also Host MIB O
Related Topics

Configuring Host Resources MIB

Overview of SNMP

Changes to SNMP Clients


See Also I/O Port
Related Topics

Choosing an ODI* LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings


See Also IPX
Related Topics

CLIENT32.NLM

LSLC32.NLM

NIOS.EXE

Core Modules


See Also IRQ
Related Topics

Choosing an ODI* LAN Driver

Installing Unlisted LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings


See Also Install DOS
Related Topics

Install Options for DOS

Controlling the DOS-based Install

Using INSTALL.EXE

Setting up Client 32*


See Also Install Dir from Disk
Related Topics

Running Setup from a Login Script

Running Setup from NAM

Running Setup from the Network

Setting Up Client 32*


See Also Install Dirs
Related Topics

Choosing an ODI* Driver

Adjusting Driver Settings

Changes to the AUTOEXEC.BAT

Configuring Additional Options


See Also Install Main
Related Topics

Overview

System requirements

Changes Setup Makes to Clients

Uninstalling Client 32*


See Also Install O
Related Topics

System requirements

Setting up Client 32*

Editing INSTALL.CFG

Changes Setup Makes to Clients

Uninstalling Client 32


See Also Install Win
Related Topics

Specifying Installation Directories

Choosing an ODI* Driver

Adjusting Driver Settings

Changes to the AUTOEXEC.BAT

Completing Setup

Configuring Additional Options

Setting up Client 32*


See Also Install_CD
Related Topics

Overview of Running Setup from a Local Drive

Installing from Downloaded Disk Images

Installing from Floppy Disks

Setting up Client 32*


See Also Installing O
Related Topics

Installing Client 32* from Windows**

Installing Client 32 from DOS


See Also LSL
Related Topics

LSLC32.NLM

ODI LAN Driver Modules


See Also LSLC32.NLM
Related Topics

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

NIOS.EXE

Core Modules

ODI LAN Driver Modules


See Also Loading 32_bit
Related Topics

Overview

16-bit ODI* Drivers

Using 16-bit Protocols with Client 32*

Core Modules

Adjusting Driver Settings


See Also Local Images
Related Topics

Overview

Installing from a local CD-ROM

Installing from floppy disks

Overview of Running Setup from the Network

Setting up Client 32*


See Also Local O
Related Topics

Installing from CD-ROM

Installing from floppy disks

Installing from downloaded disk images

Setting up Client 32*


See Also Login
Related Topics

Overview of Using Client 32

Using Network Resources


See Also Login Script
Related Topics

Overview of Running Setup from the Network

Creating a Network Install Directory

Running Setup from the Network

Setting Up Client 32*


See Also MIB Devices
Related Topics

Overview of SNMP and Host Resources MIB

Configuring Host Resources MIB

Changes to SNMP Clients

NET.CFG Settings

Configuring Additional Options


See Also MIB Search
Resources

Overview of SNMP and Host Resources MIB

Configuring SNMP

Listing Devices for Host MIB

NET.CFG Settings

Configuring Additional Options


See Also N16ODI
Related Topics

Using 16-bit Protocol Stacks with Client 32

PC32MLID.LAN

PDOSMLID.NLM

LSL.COM

Example of 16-bit ODI LAN Driver

Overview of ODI

ODI LAN Driver Modules


See Also NAM
Related Topics

Overview

Running Setup from the Network

Running Setup from a Login Script

Setting up Client 32


See Also NESL
Related Topics

LSL.COM

Optional Protocols

Example of 16-bit ODI LAN Driver

ODI LAN Driver Modules


See Also NIOS
Related Topics

CLIENT32.NLM

IPX.NLM

LSLC32.NLM

Core Modules


See Also NWDETECT
Related Topics

NWSTAMP.EXE

NWLOG.EXE

REBOOT.COM

Running Setup from a Login Script


See Also NWIP
Related Topics

NET.CFG Settings


See Also NWIP CFG
Related Topics

NWIP Section (NET.CFG)

Controlling the DOS-Based Setup

Configuring Protocol Support

Setting Default Parameters for Client 32*

NWIP Section


See Also NWIP Section
Related Topics

NWIP Section (NET.CFG)

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*

Configuring Protocol Support


See Also NWLOG
Related Topics

NWDETECT.EXE

NWSTAMP.EXE

REBOOT.COM

Running Setup from a Login Script


See Also NWSTAMP
Related Topics

NWDETECT.EXE

NWLOG.EXE

REBOOT.COM

Running Setup from a Login Script


See Also Named Pipes
Related Topics

Overview of Setting Up Named Pipes

NET.CFG Settings

Setting Up Client 32


See Also Named Pipes Ov
Related Topics

Setting Up a Computer to Run Named Pipes

NET.CFG Settings

Setting Up Client 32


See Also Net Install ACU
Related Topics

Overview

Setting up a Network Installation Directory

NWDETECT.EXE

NWSTAMP.EXE

NWLOG.EXE

REBOOT.COM

Running Setup from a Login Script


See Also Net Install H
Related Topics

Overview of Network Install

Installing Client 32* from Windows**

Installing Client 32 from DOS

Setting up a Network Installation Directory

Running Setup from a Login Script

Setting up Client 32


See Also Net Install O
Related Topics

Overview

Running Setup from a Login Script

Running Setup from the Network


See Also Net Install Ov
Related Topics

Setting up a Network Installation Directory

Running Setup from a Login Script

Running Setup from the Network


See Also NetBIOS
Related Topics

Overview of Setting Up NetBIOS

Setting Up Client 32

Setting Up Additional Software


See Also NetBIOS Ov
Related Topics

Setting Up NetBIOS

Setting Up Client 32

Setting Up Additional Software


See Also Network Board
Related Topics

Choosing an ODI* LAN Driver

Installing Unlisted LAN drivers

Configuring the LAN Driver

Modifying LAN Driver Settings


See Also Network Resources
Related Topics

Overview of Using Client 32

Logging In to a NetWare Network


See Also Optimize Drivers
Related Topics

Increasing Speed

Minimizing  Memory Usage

Ensuring Data Integrity

Editing the NET.CFG file

STARTNET.BAT


See Also Optimize Memory
Related Topics

Increasing Speed

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

STARTNET.BAT


See Also Optimize Ov
Related Topics

Increasing Speed

Minimizing  Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

STARTNET.BAT


See Also Optimize Speed
Related Topics

Minimizing  Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file

STARTNET.BAT


See Also Optimize Startnet
Related Topics

Increasing Speed

Minimizing  Memory Usage

Ensuring Data Integrity

Loading LAN Drivers

Editing the NET.CFG file


See Also Optimizing Integrity
Related Topics

Increasing Speed

Minimizing Memory Usage

Loading LAN Drivers

Editing the NET.CFG file

STARTNET.BAT


See Also Overview ACU
Related Topics

Setting Up Automatic Client Upgrade

When to use ACU

NDS* Example

Bindery Example

Running Setup from a Login Script


See Also Overview ODI
Related Topics

CMSM.NLM

ETHERTSM.NLM

TOKENTSM.NLM

FDDITSM.NLM

ODI LAN Driver Modules


See Also PC32MLID
Related Topics

Loading 16-bit ODI Drivers

N16ODI.COM

Example of 16-bit ODI LAN Driver

ODI LAN Driver Modules


See Also PDOSMLID
Related Topics

Using 16-bit Protocol Stacks with Client 32

LSL.COM

N16ODI.COM

Overview of ODI

ODI LAN Driver Modules


See Also Password TSA
Related Topics

NET.CFG Settings

[TSA] Section (INSTALL.CFG)


See Also Product Ov
Related Topics

What's New in Client 32*?


See Also REBOOT
Related Topics

NWDETECT.EXE

NWSTAMP.EXE

NWLOG.EXE

Running Setup from a Login Script


See Also ROUTE
Related Topics

Overview of Setting Up Source Routing

Setting up Source Routing

ROUTE.COM Options

ODI LAN Driver Modules


See Also Remove Ov
Related Topics

Overview of Turning Off Client 32*

Setting Up Client 32

Changes Setup Makes to Clients

Uninstalling Client 32


See Also Removing Win
Related Topics

Overview

Turning Off Client 32*

Uninstalling Client 32


See Also Requester Section SA
Related Topics

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*


See Also SMS C
Related Topics

Overview of TSA for SMS

Changes to TSA Cients

NET.CFG Settings

Configuring Additional Options


See Also SMS Changes
Related Topics

Overview of TSA for SMS*

Configuring TSA for SMS

NET.CFG Settings

Configuring Additional Options

Changes Setup Makes to Clients


See Also SMS O
Related Topics

Configuring TSA for SMS*

Changes to TSA Cients

NET.CFG Settings

Configuring Additional Options


See Also SNMP C
Related Topics

Overview of SNMP and Host Resources MIB

Configuring Host Resources MIB

Listing Devices for Host MIB

Changes to SNMP Clients

NET.CFG Settings

Configuring Additional Options


See Also SNMP C MIB
Related Topics

Overview Host Resources MIB

Listing Devices for Host MIB

Changes to SNMP Clients

Overview of HOSTMIB.NLM

NET.CFG Settings

Configuring Additional Options


See Also SNMP CFG
Related Topics

EnableMonitorCommunity

NET.CFG Settings

Controlling the DOS-Based Setup

[SNMP] Section (INSTALL.CFG)


See Also SNMP Changes
Related Topics

Overview of SNMP and Host Resources MIB

Configuring SNMP

Configuring Host Resources MIB

NET.CFG Settings

Configuring Additional Options

Changes Setup Makes Clients


See Also SNMP O
Related Topics

Configuring SNMP

Configuring Host Resources MIB

Changes to SNMP Clients

NET.CFG Settings

Configuring Additional Options


See Also SNMP Section
Related Topics

Desktop SNMP Section (NET.CFG)

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*

Configuring Protocol Support


See Also SROUTE
Related Topics

Overview of Setting Up Source Routing

Setting up Source Routing

SROUTE.NLM Options

ODI LAN Driver Modules


See Also Sample Bind
Related Topics

Sample NDS* Login Script for ACU

Running Setup from a Login Script


See Also SelectedDrives
Related Topics

NET.CFG Settings

[TSA] Section (INSTALL.CFG)


See Also Setup Options
Related Topics

Controlling the DOS-Based Setup

Selecting Setup Options


See Also Source Routing
Related Topics

Overview of Setting Up Source Routing

Setting Up Client 32

Setting Up Additional Software


See Also Source Routing Ov
Related Topics

Setting Up Source Routing

Setting Up Client 32

Setting Up Additional Software


See Also StackSize
Related Topics

NET.CFG Settings

[TSA] Section (INSTALL.CFG)


See Also Startnet
Related Topics

Changes Setup Makes to All Clients

Changes Setup Makes to Clients

Increasing Speed

Minimizing  Memory Usage

Loading LAN Drivers


See Also Sys Req
Related Topics

Overview

Setting up Client 32*

Changes Setup Makes to Clients

Uninstalling Client 32


See Also TCPIP
Related Topics

Configuring TCP/IP

Changes to TCP/IP Clients

TCP/IP NET.CFG Settings

NetWare*/IP* NET.CFG Settings

Configuring Additional Options


See Also TCPIP C
Related Topics

Overview of TCP/IP and NetWare*/IP*

Changes to TCP/IP Clients

TCP/IP NET.CFG Settings

Configuring NetWare/IP

Configuring Additional Options


See Also TCPIP CFG
Related Topics

Protocol TCPIP Section (NET.CFG)

Setting Default Parameters for Client 32*

Configuring Protocol Support

[TCP/IP] Section


See Also TCPIP Changes
Related Topics

Overview of TCP/IP and NetWare*/IP*

Configuring TCP/IP

TCP/IP NET.CFG Settings

NetWare/IP NET.CFG Settings

Configuring Additional Options

Changes Setup Makes to Clients


See Also TCPIP Section
Related Topics

Protocol TCPIP Section (NET.CFG )

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*

Configuring Protocol Support


See Also TCPIP.NLM
Related Topics

Overview of TCP/IP and NetWare/IP

Core Modules

Optional Protocols


See Also TOKENTSM
Related Topics

ETHERTSM.NLM

FDDITSM.NLM

Overview of ODI

ODI LAN Driver Modules


See Also TSA
Related Topics

NetWare* DOS TSA Section (NET.CFG)

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*

Configuring Protocol Support


See Also TSASMS
Related Topics

Overview of NetWare TSA for SMS

Optional Protocols


See Also TSAServerName
Related Topics

NET.CFG Settings

[TSA] Section (INSTALL.CFG)


See Also TSAWorkstation Name
Related Topics

NET.CFG Settings

[TSA] Section (INSTALL.CFG)


See Also Target Dirs
Related Topics

Controlling the DOS-Based Setup

Controlling Installation Files and Target Directories


See Also Uninstall
Related Topics

System requirements

Setting up Client 32*

Changes Setup Makes to Clients

Uninstalling Client 32


See Also Uninstall O
Related Topics

Turning off Client 32*

Removing Client 32

Uninstalling Windows** Components

Uninstalling Protocols

Uninstalling Client 32


See Also Uninstall Off
Related Topics

Overview

Removing Client 32*

Uninstalling Windows** Components

Uninstalling Protocols

Uninstalling Client 32


See Also Uninstall Remove
Related Topics

Overview

Removing Client 32* Windows** Components

Turning off Client 32

Uninstalling Client 32


See Also Uninstall Soft
Related Topics

Overview

Turning off Client 32*

Removing Client 32

Uninstalling Windows** Components

Uninstalling Client 32


See Also Uninstall Win
Related Topics

Overview

Turning off Client 32*

Removing Client 32

Uninstalling Protocols

Uninstalling Client 32


See Also Unlisted Drivers
Related Topics

Choosing an ODI* Driver

Configuring the LAN Driver

Modifying Driver Settings


See Also Using Client 32 O
Related Topics

Logging In to a NetWare Network

Using Network Resources


See Also Whats New
Related Topics

Product Overview


See Also changes
Related Topics

System requirements

Setting up Client 32*

Changes Setup Makes to Clients

Uninstalling Client 32


See Also driverTranslationTable Section
Related Topics

Controlling the DOS-Based Setup

Setting Default Parameters for Client 32*


See Also inst cfg
Related Topics

Installing Client 32* from DOS

Setting Up Client 32

Running Setup from a Login Script


See Also inst cfg defaults
Related Topics

Overview

Editing INSTALL.CFG

Selecting Setup Options

Configuring Protocol Support

Controlling Installation Files and Target Directories

Controlling the DOS-based Install


See Also inst cfg edit
Related Topics

Overview

Using a Setup File Other than INSTALL.CFG

Creating a Network Install Directory

Sections

Controlling Installation Files and Target Directories

Setting Default Parameters for Client 32*

Selecting Setup Options

Controlling the DOS-based Install


See Also inst cfg other file
Related Topics

Editing INSTALL.CFG

Selecting Setup Options

Setting Default Parameters for Client 32*

Configuring Protocol Support

Controlling Installation Files and Target Directories

Controlling the DOS-based Install


See Also inst cfg ov
Related Topics

Editing INSTALL.CFG

Selecting Setup Options

Setting Default Parameters for Client 32*

Configuring Protocol Support

Controlling Installation Files and Target Directories

Controlling the DOS-based Install


See Also inst cfg protocol
Related Topics

Overview

Editing INSTALL.CFG

Selecting Setup Options

Setting Default Parameters for Client 32*

Controlling Installation Files and Target Directories

Controlling the DOS-based Install


See Also inst cfg setup section
Related Topics

Overview

Editing INSTALL.CFG

Using a Setup File Other than INSTALL.CFG

Setting Default Parameters for Client 32*

Configuring Protocol Support

Controlling Installation Files and Target Directories

Controlling the DOS-based Install


See Also inst cfg target dirs
Related Topics

Overview

Editing INSTALL.CFG

Selecting Setup Options

Setting Default Parameters for Client 32*

Configuring Protocol Support

Controlling the DOS-based Install


See also odi
Related Topics

Installing Unlisted ODI* LAN Drivers

Configuring the LAN Driver

Modifying Driver Settings

Changes Setup Makes to All Clients

NET.CFG Settings


SelectedDrives

Specifies the local drives (excluding floppy drives) TSA manages for backup services.

Syntax: SelectedDrives = drive_letter

Default: C, D, E

Example:

[TSA]

SelectedDrives = C, D


Selecting Setup Options

Overview

The [Setup] section of INSTALL.CFG maintains option information for the DOS-based setup. For example, you can configure Setup to run without displaying installation choices to the user.

You should check this section to make sure the following options are set correctly for the installation you want to perform.

Making Changes

Editing INSTALL.CFG

Options

InstallType

TargetPath

InstallWindows

WindowsUserPath

UpdateDOSSystemFiles

OverwriteStartnetBat

DoInstallIfLowSpace

CopyAllUnicodeFiles

OverwriteNewerFiles

OverwriteReadOnlyFiles

OverWriteReadOnlySYSFiles

Use32Bit-Drivers


Selecting a Network Board

Specify the type of board installed in the computer.

1.	Click the name that matches the type of network board your computer uses.

2.	Click OK.


ServerName

Specifies the name of the SMS* server that backs up the client's local drives.

Syntax: SeverName = server_name

Default: none

Example:

[TSA]

ServerName = Server_2

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Default Parameters for Client 32

Overview

The DOS-based Setup program reads various sections of INSTALL.CFG to determine default values to write to a computer's NET.CFG. You can specify default values for the NetWare* DOS Requester* section and protocol sections in NET.CFG by editing the corresponding sections in INSTALL.CFG. When Client 32* is installed on a computer, Setup updates the computer's NET.CFG with the parameters and values you specified.

You can also specify the name of an updated driver in the [driverTranslationTable] section.

Making Changes

Editing INSTALL.CFG

Sections

[REQUESTER] Section

[TCP/ IP] Section

[NWIP] Section

[SNMP] Section

[HOSTMIB] Section

[TSA] Section

[driverTranslationTable] Section

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Additional Software

Setting Up Peer-to-Peer Support for Windows for Workgroups

Overview

Setting Up Peer-to-Peer Support for Windows for Workgroups

Setting Up NetBIOS

Overview of Setting Up NetBIOS

Setting Up NetBIOS

Setting Up Named Pipes

Overview

Setting Up Named Pipes

Setting Up Source Routing

Overview

Setting Up Source Routing


Setting Up Automatic Client Upgrade

Prerequisites

Create a network install directory

Review the information on the ACU programs (NWDETECT, NWLOG, NWSTAMP, REBOOT)

Review the sample login scripts

To set up Automatic Client Upgrade

1.	Using a NetWare* administration tool such as NetWare Administrator, create a user group for the users you want to upgrade to Client 32*.

2.	Create a LOG directory at the root of the network install directory.

3.	Grant all users installing Client 32 Create and Write rights to the LOG directory.

4.	Copy the .MSG files from the \DOS_ACU\NLS\ENGLISH directory to the \DOS_ACU directory or the directory that contains the ACU programs.

If you have a CD-ROM or a network installation, the \DOS_ACU directory is located in the \ADMIN directory. If you created installation diskettes, copy the files from the \DOS_ACU\NLS\ENGLISH on the ADMIN2 diskette to the same directory as the ACU programs.

5.	Review the INSTALL.CFG file to make sure the parameters are correct for your network.

6.	Open the system, container, or profile login script in NWADMIN, NETADMIN, or SYSCON.

7.	Insert commands to run NWDETECT.EXE, NWSTAMP.EXE, and NWLOG.EXE, using IF...THEN...ELSE statements to handle return codes.

See the sample login scripts for ideas on how to set up the login scipt.

8.	Insert a command to run INSTALL.EXE from the network install directory.

9.	If you want to reboot the computer after installing Client 32, insert a command into the login script to run REBOOT.COM.

10.	Save the login script and exit the NetWare* administration utility.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Client 32

Running Setup from a Local Drive

Overview

Installing from CD-ROM

Installing from Downloaded Files

Installing from a Floppy Drive

Running Setup from the Network

Overview

Creating a Network Install Directory

Running User-Initiated Setup from the Network

Running Setup from a Login Script

Running Setup from Network Application Manager

Running the Setup Programs

Overview

Installing Client 32 from Windows

Installing Client 32 from DOS

Controlling the DOS-based Setup


Setting Up Named Pipes

Prerequisites

Install Client 32* on the computer

Set up a NetWare* OS/2** client computer to run Named Pipes services (for more information, see NetWare Client for OS/2 User Guide )

To set up a DOS or Windows computer to run Named Pipes

1.	Modify the STARTNET.BAT file in a text editor by adding a line to run DOSNP.EXE from the Client 32 working directory.

Run DOSNP.EXE after the line that loads CLIENT32.NLM. For example:

IPX.NLM

CLIENT32.NLM

DOSNP.EXE

2.	(Optional) Modify the NET.CFG file in a text editor by making the necessary configurations in the Named Pipes section.

3.	Restart the computer to load the Named Pipes software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up NetBIOS

Prerequisites

Install NetBIOS on a NetWare* server

Install NetWare* Client 32* for DOS and Windows** 3.x  on the computer

To install NetBIOS on a computer

1.	Modify the STARTNET.BAT file in a text editor, by adding a line to load NETBIOS.EXE.

Load NETBIOS.EXE after the line that loads IPX. For example,

IPX.NLM

NETBIOS.EXE

CLIENT32.NLM

2.	(Optional) Modify the NET.CFG file in a text editor by making the necessary configurations for your NetBIOS application in the NetBIOS section.

3.	Restart the computer to load NetBIOS.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Peer-to-Peer Support for Windows for Workgroups

Prerequisites

Install Windows** for Workgroups 3.11 on the computer

Install Client 32* on the computer

Note: You must select 16-bit ODI* LAN drivers during Setup.

Procedure

1.	Double-click the Network Setup icon in the Windows** Network program group,

2.	Click Drivers to configure the ODI LAN driver for Windows for Workgroups.

3.	Set up the protocols you want to use.

4.	Click Close to exit the Network Drivers dialog box.

5.	Click OK in the Network Setup dialog box.

6.	Click No when prompted to overwrite files on the computer.

7.	Click Continue to return to Windows without restarting the computer.

8.	Modify the computer's startup files to load ODIHLP.EXE after LSLC32.NLM.

9.	To activate Windows for Workgroups peer-to-peer networking, restart the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up Source Routing

Prerequisites

Load source routing (ROUTE.NLM) on a NetWare* server

Install Client 32* on the computer

The source-routing driver a computer uses depends on the type of ODI* LAN driver the computer is running. Load SROUTE.NLM for 32-bit ODI LAN drivers. Load ROUTE.COM for 16-bit ODI LAN drivers.

Set up source routing

1.	Modify the STARTNET.BAT file in a text editor by adding a line to load the appropriate source routing driver from the Client 32 working directory.

Load SROUTE.NLM after loading the ODI LAN driver but before loading IPX.NLM.

If the computer loads 32-bit ODI LAN drivers, add a line to load SROUTE.NLM and any options for the driver. For example:

LOAD CNE2000.LAN

LOAD SROUTE.NLM

LOAD IPX.NLM

LOAD CLIENT32.NLM

If the computer loads 16-bit ODI LAN drivers, add a line to load ROUTE.COM and any options for the driver. For example:

NE2000.COM

LOAD LSLC32.NLM

LOAD PC32MLID.LAN

ROUTE.COM

LOAD IPX.NLM

LOAD CLIENT32.NLM

3.	Save your changes and exit the text editor.

4.	To load source routing, restart the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up a Network Install Directory from CD-ROM

If you have a Client 32* CD-ROM, you can copy the contents of the CD-ROM to a network directory and run Client 32 Setup from the network. You must set up a network install directory to use Automatic Client Upgrade.

If you have a CD-ROM drive attached to a NetWare* server, you can mount the CD-ROM as a volume of the server. You can use a mounted CD-ROM to run user-initiated installs over the network.

To run Client 32 Setup from a network directory

1.	Create a directory on the network.

2.	Copy the contents of the Client 32 CD-ROM to the network directory you created.

Important: Make sure you preserve the directory structure of the CD-ROM when you copy files to the network directory. In DOS, you can do this by using the /E option with the XCOPY command.

For example, to copy the contents of the Client 32 CD-ROM to a directory named "C32SETUP" on drive G:, change to CD-ROM drive and enter the following at a DOS prompt:

XCOPY *.* G:\C32SETUP /E

Windows** automatically preserves the directory structure when copying directories.

Note: You do not need to copy the ADMIN and DISKETTE directories to the network directory.

3.	(Optional) Edit the INSTALL.CFG file.

4.	Grant the users that need to install Client 32 Read and File Scan rights to the network install directory.

For example, to grant the group "Upgrade" access to the C32SETUP directory, change to the C32SETUP directory and enter the following at a DOS prompt:

RIGHTS C32SETUP RF /NAME=Upgrade

5.	Use a network install method to run Client 32 Setup from the network.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Setting Up an Install Directory from Diskettes

Installing Client 32* from a single directory is faster than installing from diskettes and Setup does not prompt users to insert diskettes.

To create a network install directory from diskettes

1.	Create a directory on the network.

2.	Copy the contents of the 8 diskettes you downloaded to the network directory you created. The diskettes are:

DISK1DOS

DISK1WIN

DISK<2-5>

ADMIN<1,2>

Note: If you downloaded the Network Installation files, you do not need to copy the image files to the network. Just make sure the files you downloaded are in a network directory.

3.	Grant Read and File Scan rights to the users or groups of users you want to upgrade.

For example, to grant the group "Upgrade" access to the C32SETUP directory, change to the C32SETUP directory and enter the following at a DOS prompt:

RIGHTS C32SETUP RF /NAME=Upgrade

4.	Use a network install method to run Client 32 Setup from the network.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Source Disk Keywords

DISK1DOS

The first installation source disk for the DOS install program (INSTALL.EXE).

DISK#

The source disk for the file.


Specifying Installation Directories

Target Directory

The directory where Setup copies Client 32* files. Type the complete path name. You can use an existing directory or you can type a new directory name. The default target directory is C:\NOVELL\CLIENT32.

Windows Directory

The directory where the computer runs Windows. Setup uses this path to find and edit the WIN.INI and SYSTEM.INI files.

If the computer runs Windows from the network, you must copy the modified Windows** setup files (WIN.INI and SYSTEM.INI) to the Windows directory after installation. The Windows setup files are copied automatically to the network drive if you use the DOS installation program (INSTALL.EXE) to install Client32.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


StackSize

Specifies the stack size for TSA.

Syntax: StackSize = number_bytes

Default: 2048

Range: 512 to 4096 bytes

Example:

[TSA]

Stack Size = 1024


TCP/IP and NetWare/IP
Overview of TCP/IP and NetWare/IP

Transmission control protocol/internet protocol (TCP/IP) is a protocol suite that enables diverse computer platforms to share information. One use of TCP/IP is to connect computers over global networks, such as the internet. Another use of TCP/IP is to connect main frames, minicomputers, and microcomputers in a corporate network.

NetWare*/IP* sends and receives IPX* packets in an IP format. NetWare/IP enables networked applications that use only IPX to run over TCP/IP networks. It also provides a way for separate IPX networks to communicate across IP connections.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


TargetPath

This line of INSTALL.CFG specifies the directory Client 32* uses as its working directory.

Syntax: TargetPath = AUTO | path

Default: AUTO

Example:

[Setup]

TargetPath = C:\CLIENT32

Note

AUTO allows Setup to determine the target directories.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Trademarks

Copyright © 1993-1994, 1996, Novell, Inc.  All rights reserved.  Patent Pending.

Novell Trademarks

Client 32 is a trademark of Novell, Inc.

DR DOS is a registered trademark of Novell, Inc. in the United States and other countries.

Internetwork Packet Exchange and IPX are trademarks of Novell, Inc.

IPX/SPX is a trademark of Novell, Inc.

LAN Workplace is a registered trademark of Novell, Inc. in the United States and other countries.

Link Support Layer and LSL are trademarks of Novell, Inc.

ManageWise is a trademark of Novell, Inc.

Multiple Link Interface Drive and MLID are trademarks of Novell, Inc.

NE2000 is a trademark of Novell, Inc.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare 3 is a trademark of Novell, Inc.

NetWare 4 is a trademark of Novell, Inc.

NetWare Client is a trademark of Novell, Inc.

NetWare Core Protocol and NCP are trademarks of Novell, Inc.

NetWare Directory Services and NDS are trademarks of Novell, Inc.

NetWare DOS Requester is a trademark of Novell, Inc.

NetWare/IP is a trademark of Novell, Inc.

NetWare Loadable Module and NLM are trademarks of Novell, Inc.

NetWare Name Service is a registered trademark of Novell, Inc. in the United States and other countries.

NetWire is a registered service mark of Novell, Inc. in the United States and other countries.

Network Support Encyclopedia Professional Volume and NSEPro are trademarks of Novell, Inc.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Novell Application Notes is trademark of Novell, Inc.

Novell Authorized Reseller is a service mark of Novell, Inc.

Novell DOS is trademark of Novell, Inc.

Novell Gold Partner is a service mark of Novell, Inc.

Novell Labs is a trademark of Novell, Inc.

Novell Platinum Partner is a service mark of Novell, Inc.

Novell Technical Services is a service mark of Novell, Inc.

Open Data-Link Interface and ODI are trademarks of Novell, Inc.

Packet Burst is a trademark of Novell, Inc.

PartnerNet is a service mark of Novell, Inc.

Personal NetWare is a trademark of Novell, Inc.

Sequenced Packet Exchange and SPX are trademarks of Novell, Inc.

Storage Management Services and SMS are trademarks of Novell, Inc.

The Novell Network Symbol is a trademark of Novell, Inc.

Virtual Loadable Module and VLM are trademarks of Novell, Inc.

Third-Party Trademarks

3Com is a registered trademark of 3Com Corporation.

Apple is a registered trademark of Apple Computer, Inc.

AppleTalk is a registered trademark of Apple Computer, Inc.

CompuServe is a registered trademark of CompuServe, Inc.

G/Net is a registered trademark of Gateway Communications, Inc.

IBM is a registered trademark of registered trademarks of International Business Machines Corporation

LocalTalk is a trademark of Apple Computer, Inc.

Macintosh is a registered trademark of Apple Computer, Inc.

Microsoft is a registered trademark of Microsoft Corporation.

MS-DOS is a registered trademark of Microsoft Corporation.

Network Driver Interface Specification and NDIS are trademarks of PC-Plus Communications LP.

ProNET is a registered trademark of Proteon, Inc.

Proteon is a registered trademark of Proteon, Inc.

Windows is a registered trademark of Microsoft Corporation.

XNS is a trademark of Xerox Corporation.


TrapCommunity

Specifies the name of the SNMP community that has rights to capture alerts sent from the computer.

Syntax: TrapCommunity = name

Default: public

Example:

[SNMP]

TrapCommunity = public


Turning Off Protocol Support

You can remove support for protocols by commenting out the references to the protocols in the STARTNET.BAT. If you want to remove the protocol settings as well, you can remove them from the computer's NET.CFG file.

To turn off protocol support

1.	Open STARTNET.BAT in a text editor.

By default, STARTNET.BAT is in the C:\NOVELL\CLIENT32 directory.

2.	Comment out the line that loads the protocol you do not want to load on the computer.

For example, if you want to remove support for TCP/IP, place a REM statement before the line that loads TCP/IP:

REM LOAD C:\NOVELL\CLIENT32\TCPIP.NLM

3.	Save your changes and exit the editor.

4.	Reboot the computer.

To remove protocol settings

1.	Turn off protocol support

2.	Open NET.CFG in a text editor.

By default, NET.CFG is in the C:\NOVELL\CLIENT32 directory.

3.	Comment out or delete the section that maintains the settings for the protocol you want to remove.

4.	Save your changes and exit the editor.

5.	Reboot the computer.


Turning Off Client 32

Purpose

To temporarily remove Client 32* functionality from a computer.

To turn off Client 32

1.	Open AUTOEXEC.BAT in a text editor.

2.	Comment out the line that calls STARTNET.BAT. For example:

REM @CALL STARTNET

3.	Save the change and exit the editor.

4.	Reboot the computer.

To revert to a previously installed VLM or NETX client

1.	Open AUTOEXEC.BAT in a text editor.

2.	Change the path to STARTNET.BAT to the file you used in the previous installation. For example:

@CALL C:\NWCLIENT\STARTNET.BAT

3.	Save your changes and exit the editor.

4.	Reboot the computer.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Uninstalling Client 32

Turning Off Client 32

Overview

Turning Off Client 32

Turning Off Protocol Support

Removing Client 32

Overview

Removing Client 32

Removing Client 32 Windows Components


UpdateDOSSystemFiles

This line of INSTALL.CFG specifies whether Client 32* Setup makes changes to AUTOEXEC.BAT and CONFIG.SYS.

Syntax: UpdateDOSSystemFiles = TRUE | FALSE

Default: TRUE

Example:

[Setup]

UpdateDOSSystemFiles = TRUE

Notes

True changes AUTOEXEC.BAT and CONFIG.SYS and backs up the older files with a .OLD extension.

FALSE creates AUTOEXEC.NEW and CONFIG.NEW that you can use to make changes to the computer's system files.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Use32BitDrivers

This line of INSTALL.CFG specifies whether Client 32* Setup installs a 32-bit ODI* LAN driver on the computer, if the driver is available.

Syntax: Use32BitDrivers = TRUE | FALSE

Default: TRUE

Example:

[Setup]

Use32BitDrivers = TRUE | FALSE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using 16-bit Protocol Stacks with Client 32

16-bit protocol stacks require a shim called PDOSMLID.NLM to communicate with the 32-bit ODI* modules. Load the LSL.COM at least after NIOS.EXE is loaded. Load the shim and the 16-bit protocols after loading LSL.COM in STARTNET.BAT. For example:

LSL.COM

N16ODI.COM

NESL.COM

PDOS[eth | tok | fddi].COM

Note: PDOS*.COM loads PDOSMLID.NLM

Then load your 16-bit ODI compliant protocol stacks. If you are using 16-bit NDIS** compliant stacks, you must load ODINSUP.COM and then the 16-bit NDIS stack.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using Network Resources

Computers running Client 32* can connect to a Novell* NetWare* network and use resources such as printing and file sharing. Some setup is required to specify the network printers and drives you want to use. You can set up your networking environment using the following tools.

Tool	OS	To Get Help
NetWare User Tools	Windows	Double-click NetWare User Tools in the NetWare Tools program group. Press F1 for help.
NETUSER	DOS	Enter "NETUSER." Help for each menu appears at the bottom of the screen.
CAPTURE	DOS	Enter "CAPTURE /?".
MAP	DOS	Enter "MAP /?".
* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using Network Support Encyclopedia

The Network Support Encyclopedia Professional Volume* (NSEPro*) is a knowledge base of Novell technical information on CD-ROM. Updated and delivered 12 times a year, this extensive collection provides you with a convenient, hands-on information source and is accessible through Windows**, DOS, and Macintosh**.

The NSEPro includes:

Downloadable files, patches and drivers

Thousands of Technical Information Documents (TIDs)

Product documentation

Novell* Application Notes*

GroupWare Professional’s Guide

Novell Labs* certification bulletins

To order your NSEPro annual subscription directly from Novell, call 1-800-377-4136 in the United States and Canada.

The NSEPro is also available from any Novell Authorized Reseller* representative. For more information, call 1-800-828-3362.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using a NetWare 4.11 Server to Install Client 32

If you installed client files on a NetWare* 4.11 server, you can map a drive to the SYS:PUBLIC\CLIENT\DOSWIN directory and run INSTALL.EXE or SETUP.EXE.

NetWare Client* 32* for DOS and Windows** 3.x  is also available on the NetWare 4.11 CD in the PRODUCTS\DOSWIN32\IBM_1 directory. You can copy the contents of the ENGLISH directory to a network directory or mount the CD-ROM as a volume of a NetWare server to run Client 32 Setup from the network.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


Using a Setup File Other Than INSTALL.CFG

You can specify a configuration file for the DOS-based installation other than INSTALL.CFG. 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.

To use a setup file other than INSTALL.CFG

Type /C=path\filename on the INSTALL.EXE command line.

For example, to specify C32SALES.CFG, type the following:

INSTALL /C=C:\NOVELL\CLIENT32\C32SALES.CFG


What's New
What's New?

Client 32 and VLM

Client 32* software has an advanced architecture that departs from VLM* software. The new architecture enables Windows** 3.1x  and DOS clients to run the 32-bit client software in protected mode. Client 32 also requires less than 5 KB of conventional memory, while providing a larger cache.

The following architectural advances make Client 32 easier to use, faster, and more reliable than previous NetWare* clients.

GUI Login

It’s never been easier to log in to a NetWare network. Now Windows 3.x clients can log in to a network and run login scripts from a Windows interface as well as from a DOS prompt.

Automatic Reconnect/Retry

Client 32 can detect changes in the client's network environment and restore connections or reconnect to the network when the network service comes back online. This makes Client 32 the most reliable NetWare client available. Even if the computer loses its connection to the network, the computer continues to run without having to reboot.

Network Application Launcher

Client 32 includes Network Application Launcher, a program that enables network supervisors to use NetWare Administrator (NWAdmin) to define application objects available to desktops.

Lower Memory Requirements

Client 32 caches frequently used data, such as file content and network information, resulting in less traffic on the network and faster response times on the client.

Client 32 requires less than 5 KB of conventional memory and 500 KB of extended memory. Depending on how much memory a computer has installed, Client 32 can use up to 50% of free memory as cache memory. You can set the client to use up to 75% of free memory for caching.

Utilities for Upgrading Client Software

Client 32 comes with software that helps you to upgrade from other NetWare clients. You can run Setup from a login script using Automatic Client Upgrade or you can use Network Application Manager to upgrade NDS* clients.

Support for Multiple LAN Boards

You can install several LAN boards in a computer to attach to multiple networks. Multiple board support also adds stability to the computer's network connection, because if a network service or LAN board on the client becomes unavailable, the computer can continue to communicate with the network using a second network board.

NetWare Loadable Modules

Client 32 replaces Virtual Loadable Module (VLM) software with NetWare Loadable Module* (NLM*) software. The client NLM format is similar to the server format and enables DOS and Windows 3.1x  clients to run the requester in 32-bit protected mode.

The NLM format enables workstations to use the same 32-bit ODI* LAN drivers that NetWare servers use, ensuring compatibility with existing LAN drivers.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


When to Use ACU

When is it appropriate to use ACU?

Depending on the diversity of client settings on computers in each login group, ACU may or may not be a practical solution for upgrading clients.

For example, if the users in an Organizational Unit use computers with dissimilar protocol stacks, TSR programs, and memory configurations, ACU might not be a viable option for upgrading the computers.

For groups of computers using similar hardware components and NET.CFG settings, ACU does not place a restriction on the number of clients that it can upgrade.

You can use existing login groups with ACU or you can create new login groups. Consider the following rules for when setting up login groups for ACU:

The computers should have similar memory configurations and TSRs.

The computers should use the same path naming conventions for NetWare* and Windows** software on the local drive, for example, C:\WINDOWS and C:\NWCLIENT.

The computers should be running the same version of NetWare client software.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


WinInstall DNS Address
Domain Name Server Address

The IP address of the domain name server. A domain name server is required for internet access.


WinInstall DNS Domain Name
DNS Domain Name

The name of the domain name server. The domain name server provides access to the internetwork.


WinInstall Default Router Address
Default Router Address

The IP address of the router the computer uses to connect to another network, such as a Wide Area Network (WAN) or the internet.


WinInstall IP Address
Client IP Address

The IP address of the computer. The IP address is a set of 4 numbers from 1 to 255 separated by periods. For example, 111.222.233.24.

Setup places the IP Address in the IP_ADDRESS line in the NET.CFG file.


WinInstall Subnetwork Mask
Subnetwork Mask

The network address of the subnetwork the computer is on. The subnetwork netmask address should be the same for most of the computers on a common segment.


Windows Files
Files Setup Copies to the Windows** SYSTEM Directory

CALWIN16.DLL	NWDRVLGO.BMP
CLNWIN16.DLL	NWGDI.DLL
CLXWIN16.DLL	NWIPXSPX.DLL
CTL3D32.DLL	NWLOCALE.DLL
CTL3DV2.DLL	NWNET.DLL
LGNW3116.DLL	NWPOPUP.EXE
LOCWIN16.DLL	NWPSRV.DLL
LOGINW31.DLL	NWUSER.EXE
NCPWIN16.DLL	PRTWIN16.DLL
NETWARE.DRV	VLANINT.386
NETWIN16.DLL	VNETWARE.386
NWCALLS.DLL
Files Setup Copies to the Windows Language Directory

LOGIN.DAT	LOGINW31.HLP
LOGIN.MSG	NETWARE.HLP


WindowsUserPath

The drive and directory of WIN.COM.

Syntax: Windows-UserPath = path

Default: none

Example: WindowsUserPath = C:\WINDOWS

Note

The path cannot be a on a network drive.


WorkstationName

Identifies the computer to the SMS* backup server.

Syntax: WorkstationName = 1-10_character_string

Default: none

Example:

[TSA]

WorkstationName = back_up

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[AUTOEXEC] Section

The [AUTOEXEC] section of INSTALL.CFG contains the information that Setup adds to the AUTOEXEC.BAT file to call the STARTNET.BAT file. If you do not want the DOS-based Setup to add this information, comment out or remove the information in this section.

Syntax: placement  :command

Default: BOTTOM:@CALL %sSTARTNET


[Files] Section

The [Files] section of INSTALL.CFG contains a list of all files Client 32* Setup copies to the computer's hard drive and the target directory for each file. Information for each file is specified on the same line using four key words separated by semicolons. The four types of keywords indicate the souce disk, the target directory, installation type, and the source directory, respectively.

Syntax: source_disk:destination:os_protocol:source_dir_and_filename

Example:

[Files]

DISK2:CLIENT:DW:CLIENT32\NIOS.EXE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[HOSTMIB] Section

The [HostMIB] section of INSTALL.CFG defines default valules for Host Resources MIB support. You must install SNMP to use Host Resources MIB support.

Setup Options

OverrideLocalSettings

InstallHOSTMIB

Default Settings

Modem

Printer

SWDirectorySearch

SWDirectorySearchDepth

Tapedrive


[NWIP] Section

The [NWIP] section of INSTALL.CFG sets parameters for the computer's Netware*/IP* environment.

Setup Options

InstallNWIP

OverrideLocalSettings

Default Setting

NWIP_Domain_Name

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[REQUESTER] Section

The [REQUESTER] section of INSTALL.CFG contains basic network client configuration information. The parameters in this section use the same syntax as the NetWare* DOS Requester* section in NET.CFG. If you want to use ACU to install Client 32* without user intervention, you must include a setting for at least the following parameters:

First Network Drive

Name Context

Preferred Tree

Preferred Server

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[SNMP] Section

The [SNMP] section of INSTALL.CFG sets default parameters for the computer's SNMP environment. Setup updates these parameters in the client's NET.CFG file under the Desktop SNMP section.

Install options

InstallSNMP

OverrideLocalSettings

Default Settings

ControlCommunity

EnableControlCommunity

EnableMonitorCommunity

EnableTrapCommunity

MonitorCommunity

TrapCommunity

snmpEnableAuthenTraps

sysContact

sysLocation

sysName


[TCP/IP] Section

The [TCP/IP] section of INSTALL.CFG defines default values for the TCP/IP environment. You can have the protocol stack attempt to find IP address values by leaving the Client IP, Router, and Subnetwork Mask addresses blank or by typing "0.0.0.0" for the address.

Setup Options

InstallTCP

OverrideLocalSettings

Default Settings

DNS_domain

ip_address

ip_netmask

ip_router

NameServerAddress


[TSA] Section

The [TSA] section of INSTALL.CFG specifies default values for the NetWare* DOS TSA parameters in NET.CFG.

Setup Options

InstallTSA

OverrideLocalSettings

Default Settings

DiskBuffers

Password

SelectedDrives

ServerName

StackSize

WorkstationName

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[WINDELETE] Section

The [WINDELETE] section of INSTALL.CFG  lists the files that Client 32* Setup 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.

Syntax: filename

Example:

[WINDELETE]

NWPOPUP.EXE

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[driverTranslationTable] Section

The [driverTranslationTable] section of INSTALL.CFG equates the Long Driver Name of a 16-bit ODI* LAN driver with the 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 Setup 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 and 32-bit driver names.

Syntax: existing_driver_name  = new_driver_description

Example:

[driverTranslationTable]

Novell NE2 Ethernet = Novell Ethernet NE/2

Note: If you are using a third-party driver and the filename has changed from the 16-bit to the 32-bit version, the driver translation table will not work and you cannot use ACU to install Client 32*. Run a user-initiated install.

To equate 16-bit and 32-bit drivers

1.	Open INSTALL.CFG in a text editor.

2.	Under [driverTranslationTable] type the Long Driver Name for the 16-bit driver followed by an equal (=) sign and the 32-bit driver’s description.

3.	Save INSTALL.CFG in the install directory and close the text editor.

* Novell trademark.  ** Third-party trademark.  For more information, see Trademarks.


[titles] Section

The [titles] section of INSTALL.CFG assigns the names Setup uses to prompt for Setup disks.

Syntax: DISK# :'disk name '

Example:

[titles]

DISK1DOS:'NetWare Client 32 for DOS Disk 1'


[wingroup] Section

The [wingroup] section of INSTALL.CFG assigns the names of the Program Manager program group and icons that Setup creates on Windows computers.

Syntax: GROUP = object  :group label

Example:

[wingroup]

group=NW.GRP:NetWare Tools

Syntax: ICON = filename  :destination_dir_keyword  :icon label

Example:

[wingroup]

icon=nwuser.exe:winsys:NetWare User Tools


ip_address Option

Syntax: ip_address = IP ADDRESS

Default: 000.000.000.000

Example:

[TCP/IP]

ip_address = 1.2.3.4


ip_netmask Option

Syntax: ip_netmask = <IP_ADDRESS>

Default: 255.255.255.0

Example: ip_netmask = 11.22.33.44


ip_router

Syntax: ip_router = IP_ADDRESS

Default: 000.000.000.000

Example: ip_router = 1.2.3.4


see also sample scripts
Related Topics

Sample Bindery Login Script for ACU

Running Setup from a Login Script


snmpEnableAuthenTraps

Sends an SNMP trap message when the computer receives an unauthorized request for SNMP information.

Syntax: snmpEnableAuthenTrap = on | off

Default: off

Example:

[SNMP]

snmpEnableAuthenTrap = on


sysContact

Lists the name of a person responsible for supporting the computer. For example, you could list the e-mail address of a network supervisor.

Syntax: sysContact = 1 - 255 character string

Default: suzanne@company.com

Example:

[SNMP]

sysContact = jhowe@place.com


sysLocation

Gives a description of the location of the computer.

Syntax: sysLocation = 1 - 255 character string

Default: Building 2

Example:

[SNMP]

sysLocation = Building C, Room 122


sysName

Specifies the workstation name that identifies the computer.

Syntax: sysName = name

Default: none

Example:

[SNMP]

sysName = computer_1