Digital PDFs

EK-DEIWA-IN-C01

July 1993

163 pages

Original

6.0MB

view download

OCR Version

5.3MB

view download

Document:	WaveLAN PC-AT Installation and Operation
Order Number:	EK-DEIWA-IN
Revision:	C01
Pages:	163
Original Filename:

OCR Text

WaveLAN

PC-AT Installation and Operation

July 1993

This manual, in conjunction with the WaveLAN PC-AT Installation and
Configuration card, describes how to install and operate the WaveLAN card
ina PC-AT or PC/ISA compatible. This manual is intended for the hardware
installer and the network manager.

Supersession/Update Information:

alilaliitlall

Part Number:

EK-DEIWA-IN. CO1

This is a revised manual.

EK-DEIWA-IN. C01

The information in this document is subject to change without notice and should not be construed as
a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no re-

sponsibility for any errors that may appear in this document.

The following are trademarks of Digital Equipment Corporation: DECnet, PATHWORKS, and the
DIGITAL iogo.
The following are third-party trademarks:

3Com is a registered trademark of 3Com Corporation.

IBM, OS/2, and Personal Computer AT are registered trademarks of International Business Machinas Corporation.

Microsoft and MS-DOS are registered trademarks of Microsoft Corporation.
NCR is a registered trademark of NCR Corporation.
NetWare and Novell are registered trademarks of Novell, Inc.
PC/TCP is a trademark of FTP Software, Inc.
Velcro is a registered trademark of Velcro USA, Inc.
WavelL
AN is a registered trademark of NCR Corporation.

This manual was produced by Telecommunications and Networks Publications.

Federal Communications Commission (FCC)
Radio Frequency Interference Statement

The following statement applies only to the WaveLAN 915MHz Network Interface
Card:

This device complies with Part 15 of FCC Rules. Operation of this device is subject
to the following two conditions:

This device may not cause harmful interference.

This device must accept any interference that might cause undesired
operation.

Information to User
This device must be installed and used in strict accordance with the manufacturer’s
instructions. However, there is no guarantee that interference to radio communica-

tions will not occur in a particular commercial installation. If this device does cause
interference, which can be determined by turning the host equipment off and on, the
user is encouraged to consult the instruction manual of the host equipment or the localdevice supplier. In case the device does cause harmful interference with an autho-

rized radio service, the user/operator shall promptly stop operating the device until
harmful interference has been eliminated
Digital Equipment Corporation is not re sponsible for any radio or television interfer-

ence caused by unauthorized modification of this device or the substitution or attachment of connecting cables and equipment oiher than specified by Digital Equipment

Corporation. The correction of interference caused by such unauthorized modification, substitution or attachment will be the responsibility of the user.

Statement of Compliance per Government of Canada
Department of Communication TRC-76
“Spread Spectrum systems in the band 902-928 MHz cannot claim protection from
other users or cause interference to authorized users or services operating in the same
or adjacent bands, that is, they operate on a “no-interference no-protection” basis.
Authorized services are listed in the Canadian Table of Frequency Allocations or as
determined by the Department of Communications from time to time.”

Contents
Federal Communications Commission Radio Frequency
Interference Statement
Safety
Preface

Overview of WaveLAN
1.1

Introducing WaveLAN .. ... . ... ... i,

1-1

1.2

Typical Network Configurations ........................

1-1

1.3

WaveLAN Components . ...,

1-4

1.3.1

The WaveLLAN Network Interface Card ................

1-4

1.3.2

The Omnidirectional Antenna Module Kit ..............

1-5

1.33

WaveLAN Software Diskette

1-6

1.34

WaveLAN PC-AT Installation and Operation Guide

......

1-6

1.3.5

Wave LAN PC-AT Installation and Configuration Card . ...

1-6

1.3.6

Optional WaveLAN Components .....................

1-6

........................

1.4

Card Specifications

..........
.. .ottt

1-8

1.5

RaANge ... e
e

1-9

Preparing for Installation
2.1

What YouNeed

....... ... ...

...

2.2

Installation Steps

. ......

2-1

2.3

The Installation Worksheet . . ........
... ... .. ... ...,

2-2

i i

2-1

Installing the Network Interface Card
3.1

Unpacking the Network Interface Card ...................

3.2

Installing the Security Feature .. ........................

Installing the Remote Boot Feature ......................

Verifying the Hardware Configuration Switches ............

341

Verifying the WavelLAN 915 Configuration Switches .. ...

3.4.2

Verifying the WaveLLAN 2400 Configuration Switches . ...

3.5

Setting the VOBase Address .................

3.6

Setting the Remote Boot Base Address ...................

3.7

Using LEDS ... ..oiiiiiiiiiiiiii
i
it iiiiinen

3.8

Installing the Interface Cardin Your PC ..................

3.9

The OmniDirectional Antenna ....................oovn..

39.1

Connecting the WaveLAN915Antenna ................

39.2

Connecting the WaveLAN 2400 Antenna ...............

310

AntennaPlacement.............
..
ittt

Using the Antenna SupportBracket......................

Software Installation and Card Configuration
4.1

Before YouBegin ..........
... it

4.2

Configuration Parameters ............cooviiiiiinenenn

Automatically Creating a Card Configuration Disk ..........

Manually Configure Using the SETCONF and INSTCONF
UtHteS ..ot
e
e

Setting the Configuration Parameters
it

....................

45.1

Description .. ....... o

45.2

Network Identifier ............
.. ...

453

MACAddressType ......coviiiiiiiiiiin

454

Datalink Security ....... ... . ol

4.6

Saving the Configuration Parameters .. ...................

4.7

Installing a Configuration

4.8

Parameier Options for Batch Operation . ..................

Switching Workstations Between Networks

..........
... .. ... ..

---------------

Radio-Frequency Network Operations
5.1

5.1.1

5.1.2

5.1.3
5.2

53
5.3.1
532
5.4

5.5
5.5.1
5.5.2
553

5-1

Signal Interference ........ ...
Signal Attenuation ........... ..o

5-1

e
Signal-to-NOISE ... vvveviiiiiii
Optimizing Network Performance .................oonn
Problem Determination .............coviiiiiiiianaeannn

5-2

Component Failure ...............cociiiiiiinn
Environmentand Operation . .......... ...t

5-6

Diagnostic Utilities . . .. ...
Troubleshooting List ........... ...y

5-7

Unable to Communicate with the Server . . ..............
Poor Station Performance Relative to the Network Average
Overall Network Performance IsPoor .................

5-2

3-5
5-6
5-7
5-8

5-8
5-8

The Point-to-Point Diagnostics Utility
6.1
6.2

6.3
6.3.1

6.3.2
6.3.3

6.3.4

Radio-Frequency Network Operations ...................

Running Point-to-Point Diagnostics .....................

Installing the Point-to-Point Diagnostics Utility ............
Running the Point-to-Point Diagnostics Utility .............

...
The Measurement Data Display ...................
Antenna Positioning .. ........ . o o i
..
Logging the MeasurementData . ..................,

Parameter Options for Batch Operation . ...............

6-1
6-1
6-2

6-5
6-7
6-7

The Node Diagnostics Utility
7.1

Node Diagnostics for the NetWare IPX and DOS ODI Driver .

. ..............coiiiiiiniaennn

7-2

civiiii i

7-4

Saving the DiagnosticData ..........................
Parameter Options for Batch Operation ................

7-6

Node Diagnostics for the NetWare OS/2 Requester .........

7-8

7.1.1

Counter Information

7.1.2

Driver StatistiCs ... ...

7.1.3
7.14

7.2

7.1

7-2

Counter Information

-------------------------------

7-7
7-9

vii

7.2.2
7.3

Parameter Options for Batch Operation

................

7-12

Node Diagnostics for the NDIS Driver ...................

7-13

7.3.1

Counter Information

..............
.. ... ... 0....

7-14

7.3.2

Diagnostic Indicators . ............
... ... .. . oL

7-16

7.3.3

Saving the DiagnosticData ..........................

7-17

7.34

Parameter Options for Batch Operation

................

7-18

...........
... ...
i

7-19

8.1

Configuration Setup Utility Messages ................
...,

8-2

8.2

Configuration Install Utility and Network Driver Messages ...

8-5

8.3

Node Diagnostics Utility Messages ......................

8-11

8.4

Point-to-Point Diagnostics Utility Messages ...............

8-16

7.4

Interpretingthe Data

Messages

NetWare Driver Installation
Al

NetWare Version 2.1x Installation .......................

A-2

Workstation Shell Driver Generation .. ...................

A-3

NetWare Operating System Generation ...................

Generating and Installing an External Bridge ..............

A-5

NetWare Version 2.2 Installation ........................

A-5

Workstation Shell Driver Generation

..................

A-5

AS.2

Router Driver Generation ..................c.ccvu...

A-6

AS53

File ServerlInstallation . .........
... ... ... .. civoi...

A-6

NetWare Version 3.1x Server Installation .................

A-7

A6.1

Autoloading the NetWare Version 3 File Server Driver ....

A-7

A62

Loading the WaveLLAN NetWare Version 3 Driver Manually

A-8

viii

NetWare Requester for OS/2 . ....... ..

...

.. ... ...,

A-9

Installing the DOSODI Driver .........................

A-11

NetWare Lite Installation ...............
... .. ... ......

A-13

A10

Checking Your NetWare Installation .....................

A-13

NDIS Driver Installation
B.1

Introduction ... ...

B-1

B.2

NDIS Driver Installation General Information

.............

B-2

B.2.1

The CONFIGSYSFile ...........
.. ... .. . ...t

B-2

B.2.2

The PROTOCOL.INIFile ...........
... ... ... ......

B-3

B.23

The AUTOEXEC.BAT File ..........................

B-4

B.2.4

Driver Initialization . ...........
... ... ..
..

B-4

PATHWORKSFORDOS(DECnet) ...........c.covu....

B-4

B.3

B.3.1

The CONFIGSYSFile .....

... ... .

...

B-5

B.3.2

The PROTOCOL.INIFIle .. ..........
... .. .. ...,

B-5

B33

The AUTOEXEC.BAT File ............
... . ... ......

B-6

.........
... i

B-6

B.4.]

The CONFIGSYSFile ... ... ... .. ...

B-7

B.4.2

The PROTOCOLINIFile .................
... .. .....

B-8

B43

The AUTOEXECBATFile ..........................

B-10

TCP/IP and LAN Watch Installation .....................

B-10

B.5.1

Install the Driver Software . ..........................

B-10

B.5.2

The CONFIGSYSFile

...... ... ... ... .. ... ...,

B-11

B.53

The PROTOCOL.INIFile ..........
... ... . ...
..

B-11

B54

The AUTOEXEC.BATFile .. .......
... .. ... ...,

B-11

B.4

B.5

PATHWORKS FORDOS(TCP/IIP)

........ ... ... ... ... . ... ... ....

B-12

B.6.1

Install the Driver Software . ..........................

B-12

B.6.2

The CONFIGSYSFile .........
... ... ... oo,

B-12

B.6.3

The PROTOCOL.INIFile ...............
... ... ... ...

B-12

B.6.4

The AUTOEXEC.BATFile ............... e

B-13

B.6

StarLAN Installation

...

. e

B-13

B.7.1

Installing OS/2 1.3 EE (Including Requester) ............

B-13

B.7.2

The CONFIG.SYSFile ..........
. ... ... ... .....

B-14

B.7.3

The PROTOCOL.INIFile . ..........................

B-14

B.7

IBM OS2 LAN Server

...

. ...

...................

B-15

PC LAN Support Program Installation .................

B-15

B.8.1.1

The CONFIGSYSFile . .........
... ... ..........

B-16

B.8.1.2

The PROTOCOL.INIFile ........
... ... ... .......

B-16

B.8.1.3

The AUTOEXECBATFile . .......................

B-17

B.8
B.8.1

IBM DOS LAN Requester Version 1.2

B.8.2

B-17

B.8.2.1

The CONFIGSYSFile ...... ...

.. . ...........

B-17

B.8.2.2

The PROTOCOLINIFile ... ....................

B-18

B.8.2.3

The DOSLAN.INI or AUTOEXEC.BAT Files .........

B-18

B.8.2.4

Notes for Users of MS-DOS Version5.0: ............

B-19

3Com 3+OpenInstallation . .......
... ... ... ... . ...

B-20

B.10

LAN Manager Installation . ............................

B-20

B.10.1

LAN Manager Version 2.0 Installation . ................

B-20

B.10.2

LLAN Manager Version 2.1 Installation . ................

B-21

Microsoft Windows for Workgroups
Cl1

DOS Requester Installation ..........................

Microsoft Windows for Workgroups Driver Installation . ... ..

C-1

Installation Worksheet
D.1

Installation Worksheet

... ..

..o ol

D-1

1-1

Wavel.LAN Networks Connected by Means of Wired Backbone

1-3

1-2

Basic WaveLAN Component Set ...........
... ... ... ...

1-5

3-1

Handling the Network Interface Card

3-2

Installing the Secunity Feature ... ...

3-3

Installing the BootROM

3-4

WavelLAN 915 Hardware Configuration Switches

..........

3-6

3-5

WaveLLAN 2400 Hardware Configuration Switches

.........

3-7

3-6

WaveLAN SIS LEDs Display .................
.. ... ...

3-7

Inserting the Network Interface Card ... .. ... ... .. ... ...

3-11

3-8

Connectingthe Antenna . .. ....... ..

... .. ... ..........

3-14

3-9

Typical AntennaPosition . ...........
.. ... ... ...

3-15

3-10

Using the Antenna Mounting Brackct ....................

3-16

Index

Figures

...

... ... ... ..

...
... . ...
.. ... .

...

.. .. ...

3-3

... ... ... ...

3-5

Opening Screen of SETCONFEXE

.....................

4-4

SETCONF Parameter Entry Screen ......................

4-5

Configuration Install Utility - Initial Screen .. .............

4-9

Configuration Install Utility - IRQ Screen ................

4-10

Configuration Install Utility — Update Screen ..............

4-11

Station Placementinan Open Office .....................

5-3

Using an Antenna Extension . ..........
... ... ... ....

5-4

Bridging in a Dispersed Network . ..............
... ... ...

5-5

Point-to-Point Diagnostics Initial Screen ..................

6-2

No Other Station Is Active Yet

..........
... . ... ......

6-3

Link Quality AssessmentDisplay .......................

6-4

Link MeasurementDataDisplay ........................

6-5

Example Saved Measurements

6-7

.........................

‘sl

|
> >
i
t
W
B
=
e

Node Diagnostic Counters — NetWare IPX Driver

..........

7-3

Driver Statistics - NetWare IPX Driver ..................

7-5

Saved Counter Set - NetWare IPX

. ... ... .............

7-7

Diagnostic Counters - NetWare OS/2 Requester .. ..........

7-9

Driver Statistics — NetWare OS/2 Requester . ..............

7-11

Saved Counter Set - NetWare OS/2 . .....................

7-12

NDIS Node Diagnostic Counters ..................ccoo...

7-15

Saved NDIS Counter Set . .........
.. .. ...t

7-18

SNR Example . ... ...

7-21

. .

WaveLAN Card Specifications

......................
...

1-8

1 0 Base Address Switch Settings ...........
... .. ... . ...

3-8

Remote Boot Base Address Switch Settings ... ............

3-8

Function of LEDs for the WaveLAN 9IS

... .........

3-9

WaveL AN Driver Configuration Options .................

A-1

...

WaveLAN Driver Files for NetWare

Page

xii

blank

paqge

Safety AA

Any warning or caution that appears in this manual is defined as follows:

Warning

Contains information to prevent personal injury.

Caution

Contains information to prevent damage to equipment.

Vorsicht

Enthidlt Informationen, die beachtet werden miissen, um
den Benutzer vor Schaden zu bewahren.

Achtung

Enthilt Informationen. die beachtet werden missen, um
die Geréte vor Schaden zu bewahren.

Danger

Signale les informations destinées a prévenir les accidents corporels.

Attention

Signale les informations destinées a prévenir la détérioration

Aviso

matériel.

Contiene informacién para evitar danos personales.
.7

Precaucion

Contiene informacién para evitar dafios al equipo.

xiii

The cautions that must be observed for the hardware described in this manual are listed

below in English, German, French, and Spanish. The pages on which these safety messages appear are also listed.

WARNING A

Do not attempt to install the interface card without disconnecting
the power cord and other cables from your perscnal computer. If you
fail 10 take this precaution, you could receive a severe electrical
shock or cause damage to your personal computer. [Page 3-10]

VORSICHT

Bevor Sie die Schnitstellenkarte installieren, miissen Sie das
Netzkabel und alle anderen am Computer angeschlossenen Kabel

unbedingt

herausziehen.

Bei

MiBachtung dieser

Sicherheits-

maBnahme besteht Elektrisierungsgefahr und die Méglichkeit, Th-

ren Personalcomputer schwer zu beschéadigen.

DANGER

N'essayez pas d'installer la carte sans déurancher le cordon d’ali-

mentation ni les autres cables de votre ordinateur. Si vous ne prenez pas cette précauuon, vous risquez d’étre électrocuté ou d’endommager votre ordinateur.

AVISO

No intente instalar la tarjeta de la interfaz sin desconectar el
cable de alimentacion y los demds cables de su ordenador person-

al. Si no toma esta precaucion, podria recibir una descarga eléctrica grave o causar dafios a su ordenador personal.

XIV

CAUTION A

Static electricity can severely damage the interface card. To
prevent damage when unpacking and handling the interface card,
make sure you touch a grounded metal surface, such as the chass1s of your personal computer, to discharge the excess static elec-

tncity from your body. [Page 3-1, 3-10]

ACHTUNG

Die elektronischen Teile der Schnittstellenkarte konnten durch
statische Elektrizitdt schwer beschddigt werden. Berithren Sie
vor dem Auspacken und Einbauen der Karte ein geerdetes Me-

tallteil, 2 .u Coispiel das Gehduse thres Computers, um eventuell .n lhrem K jrper angesammelte statische Eleknziti: zu
Cauaden.

ATTENTION

L’électricité statique peut endommager la carte d’interface.
Pour éviter tout risque lors du déballage et de la manipulation

de la carte, touchez une surface métallique mise 2 la terre, par
exemple le boitier de votre ordinateur, afin de vous décharger
de I'électricité statique.

PRECAUCION

La electncidad estitica puede daiar seriamente la tarjeta de la

interfaz. Para ev tar dafios al desempaquetar y manejar dicha
tarjeta, asegurese de tocar una superficie metélica conectada a
tierra, como puede ser el chasis de su ordenador personal, a fin

de descargar cl exceso de electricidad estética que su cuerpo
haya podido adquirir.

CAUTION A

Before installing the WavelLAN Network Interface Card (NIC),
be sure to turn off the power to the personal computer. Refer to

the safety advisory in the WaveLAN PC-AT Installation and Opcration guide. [Wavel
AN PC-AT Installation und Configuration

card, Page 4]

ACHTUNG

Schalten Sie den Computer aus, bevor Sie die Netzwerkkarte
WavelLAN 1nstallieren.

Beachten Sie die Sicherheitsvorschrif-

ten in der Installauons- und Betricbsanleitung fiir die Netzwerkkarte WaveLAN PC-AT.

ATTENTION

Avant d’installer la carte d’interface réscau WaveLAN, melttez
I'ordinateur hors tension. Reportez-vous aux conscils de sécuri-

¢ qui figurent dans le guide d’installation ct de fonctionnement
de la carte d’interface réscau WaveLAN.

PRECAUCION

Antes de instalar la Tarjeta de Interfaz de Red (NIC) de WaveLAN, asegirese de cortar la ahimentacion del ordenador per-

sonal. Véase el aviso de seguridad del manual de instalacion y
funcionamiento de WaveLAN PC-AT.

Xvi

Preface

About This Manual
This manual explains how to install and use the WaveLAN® Network Interface Card
in an Industry Standard Architecture (ISA) Personal Computer AT® (PC-AT ) or
PC/ISA compatible, running in a Network Driver Interface Standard (NDIS) compatible network environment, such as PATHWORKSTM or Microsoft® LAN Manager or a Novell® NetWare® network environment.

The WaveLAN Network Interface Card (NIC) is available in the following two variants:

The WaveLAN North America NIC operates in the 915 MHz ISM
band. Throughout this manual, this NIC is referred to as the WaveLAN 915.

The WaveLAN International NIC operates in the 2400 MHz (2.4
GHz) band. Throughout this manual, this NIC is referred to as the
WaveLAN 2400.

This manual describes the installation and operation of both the WaveLAN 915 and
the WaveL
AN 2400 products.

Wh~ Should Use This Manual
This manual is intended for the hardware .nstaller and the network manager. This

manual assumes you have a working knowledge of basic PC operations and are familiar with network driver installation procedures.

Xvii

Conventions
The following conventions are used in this manual:

Example

Description

Enter

The Enter key is shown with an intial capital letter.

INSTCONFEXE

MS-DOSTM filenames and directories are shown in uppercase type.

instconf -a3e(

MS-DOS command line entries are shown in lowercase
bold type.

10H

Hexadecimal numbers are represented by the letter “H”
which immediately follows the number.

Overview of This Manual
Chapter 1

Introduccs you to WavcLAN networking concepts and describes the system components.

Chapter 2

Lists the installation steps and what you should consider
before you begin.

Chapter 3

Describes how to sct up and install the WaveLAN Network
Interface Card in a PC, and how to connect and position the
antenna.

Chapter 4

Describes how to use the configuration utilities to install
user-selectabie configuration options.

Chapter 5

Describes the characteristics of radio-frequency operation
and how to optimize network performance. Introduces the
diagnostic utilitics.

Chapter 6

Describes how to use the Point-to-Point Diagnostics utility
to optimize antenna placement and verify proper operation
of the WavelLAN card and antenna.

Chapter 7

Describes how to use the Node Diagnostics utility to monitor network performance and pinpoint problem areas.

Chapter 8

Describes error and warning messages displayed by the
Configuration utilitics, the network drivers, and the Diagnostics utilities.

Xviii

Appendix A

Provides information to install WaveLAN network drivers
in a Novell NetWare environment.

Appendix B

Describes the steps required to install the WaveL
AN Network Driver Interface Specification (NDIS) driver in
NDIS-compatible network environments, such as
PATHWORKS or LAN Manager.

Appendix C

Describes how to install the Microsoft Windows for
Workgroups driver.

Appendix D

Allows you to keep a hardcopy record of the installation.

Further Information
The README.TXT file on the WaveLLAN software diskette contains information
not available when this manual was printed.
The DISKETTE.TXT file lists all directories and files on the diskette, with a short
description of each entry.

Xix

1
Overview of WavelLAN

1.1

Introducing WaveL
AN
WaveLAN® provides cable-free departmental local area networkin ; ‘or personal

computers. This gives you the flexibility to relocate people and equ:pment, or to add
more stations to your network, without the planning effort and cost of recabling.
Because WaveL AN uses spread-spectrum communications technology, it provides a
level of data security.

1.2

Typical Network Configurations
Your WaveLAN Network Interface Card (NIC) and driver software have been developed for use with common industry-standard networking systems, including sys-

tems supporting the Network Driver Interface Standard (NDIS),
PATHWORKSTM and LAN Manager as well as Novell® NetWare®.

such as

1-1

Typical configurations include:
¢

Standalone WaveLAN network, including one or more servers with clients.

Physically separated WaveLAN networks (for example: on different floors of
the same building) connected by means of a wired backbone (Figure 1-1).

Wired network with a bridge allowing connection into the network from one
or more WaveLLAN stations.

A wireless bridge connecting two wired LANs (overcoming physical ob-

stacles to a wired connection).
Wave LAN NICs can be configured with different network identifiers to allow multiple networks to share the same work area. This type of configuration allows a workstation to be easily switched from one network to another.

Wavel
AN PC-AT installation and Operation

Figure 1-1:

WaveLAN Networks Connected by Means of Wired Backbone

Dept. A

, ;Br'i'dge.'Routévr; ”
OrS‘erver

- Workstation: _

Wired

Backbone

Workstation
Bridge, Router,
or Server

.
peptB

LKG-6977-921

Overview of WavelLAN

1-3

1.3

Wavel.
AN Components
The WaveLLAN adapter kit contains the basic set of components required to install
WavelLAN in a PC. This kit includes:
WaveLAN NIC

Omnidirectional Antenna Module kit
WaveLAN software diskette (3.5-inch or 5.25-inch)

WaveLAN PC-AT Installation and Operation guide
WaveLAN PC-AT Installation and Configuration card

Figure 1--2 shows the basic WaveLAN component set.

Optional WaveLAN components include:
—

Encryption Security feature kit.

Directional Antenna kit for interfacility communications. This option is
available only for the WaveLAN 915.
30-foot (9-meter) Antenna Extension Cable kit (available only for the
WaveLAN 915).

Remote Boot feature (available only for the WaveLLAN 2400).
Wireless Newwork Connect products.

1.3.1

The WavelL
AN Network Interface Card
The WaveLAN NIC isaprinted circuit board which acts as an interface between your
PC and the rest of the network. The NIC is installed in an I1SA slot inside the PC. It

contains a radio-frequency modem in addition tc the circuitry needed to process the
signals exchanged between your PC and other stations on the network. The NIC also
contains a socket for the optional security chips.
The WaveLAN 2400 also contains a socket for the optional Remote Boot ROM.

Wavel
AN PC-AT Installation and Operation

Figure 1-2:

Basic WavelL.AN Component Set

[J wavelAN
software

WaveLAN documentat:onL

- installation and Operation guide
_ insta!latson and Conflguranon card

Qél
LKG81941.3.2

The Omnidirectional Antenna Module Kit

The Omnidirectional Antenna Module kit includes a coaxial cable and tool for attachment to the NIC. The module is accompanied by amounting bracket that you can
use to attach it to the wall or stand it upright on a flat horizontal surface, such as aPC
base, desktop, wall, or filing cabinet.

Overview of WavelAN

1.3.3

WaveLAN Software Diskette
The WaveLAN software diskette conststs of:
Utilities to configure your NIC after it is installed in the PC
Network driver files enabling you to use your NIC in a NetWare or
NDIS-compalible environmenti

Diagnostic utilities allowing you 10 position workstations and antennas for
best performance, and to monitor and diagnose your network

1.3.4

WaveLAN PC-AT Installation and Operation Guide
This document provides the necessary information to install and operate WaveLAN.

1.3.5

Wavel.AN PC-AT Installation and Configuration Card
This card provides a quick overview to install and configure WaveLAN.

1.3.6

Optional WaveLAN Comgonents
The optional components for the WaveLAN 915 include the following:
‘Tne encryption security feature —- used to provide extra network sccurity by

encrypting all data transmitted on the network. If this option is sclected, it
must be installed in all stations in the WaveLLAN network.
The Directional Antenna kit — allows wircless interfacility communications
up to 5 miles (8 km) range.
The Antenna Extension Cable — used to move the antenna away from areas

of excessive interference, or to increase its height to provide a better transmission path in difficult environments. (30 feet).
Wireless Network Connect — used to connect a WaveLLAN to a wired Ethernct Local Arca Network (LAN).
Remote Wireless Network Connect — used to connect two Ethemet LANs in

different buildi=~s, up to 5 miles apart, using a wireless, radio frequency connection,

1-6

WaveLAN PC-AT Installation and Operation

The optional components for the WaveLAN 2400 include the following:

The encryption security feature — used to provide extra network security by
encrypting all data transmitted on the network. If this option is selected, it
must be installed in all stations in the WaveLAN network.

Remote Boot ROM for NetWare — enables a NetWare client to boot from the
server.

Wireless Network Connect — used to connect a WaveLAN network to a
wired Ethernet Local Area Network (LAN).

Overview of WavelL
AN

1-7

1.4

Card Specifications
Table 1-1 describes the specifications for the WaveLLAN card.

Table 1-1:

WaveLAN Card Specifications
WaveLAN 815

wavelAN 2400

Frequency:

902 - 928 MHz band

2.4 GHz band

Modulation technique:

(RF) Direct Sequence Spread Spectrum ~ (Information)
Differential Quadrature Phase Shift Keying (DQPSK)

Output power:

500 mW

100 mW

Data rate:

2 Mbps

Medium access protocol:

CSMA/CA (Carrier Sense Multiple Access/Collision
Avoidance)

Bit error rate:

Better than 10 - @ -72 dBm receiver threshold

Power consumption

+ 5V

1500 mA (maximum)

1600 mA (maximum)

- 12V:

32 mA (maximum)

40 mA (maximum)

+12V:

330 mA (maximum)

175 mA (maximum)

Hardware strapping:

/0 Base Address

I/0 Base Address, Remote
Boot Base Address

Regulations:

FCC - Type approved per
Part 15.126

User or site license may be
required. Check country
specific requirements.

LED indicators:

Card Power
Receive Data Activity

N/A

Transmit Data Activity

WavelLAN PC-AT Installation and Operation

1.5

Range
The range of the WaveLAN NIC, with the attached Omnidirectional Antenna, varies
according to a number of environmental factors, such as building construction,

building layout, furniture, and antenna positioning. Typical performance in different
environments is given below:
Range

WaveLAN 91§

WaveLAN 2400

Open office:

800 foot (244 meter)

400 foot (120 meter)

Semi-open office:

200 foot (60 meter)

100 foot (30 meter)

Closed office:

105 foot (32 meter)

50 foot (15 meter)

The environment definitions listed are defined as follows:
Open office

Antennas can see each other (for example, there are no
physical obstructions between them).

Semi-open office

Work space is divided by shoulder-height, hollow wall elements; antennas are at desktop level.

Closed office

Fully enclosed work space with nonmetallic, nonconcrete
walls from floor to ceiling.

Overview of WavelL
AN

1-9

2
Preparing for Installation

2.1

What You Need
To install a WaveLAN® network station, you must have the following:
A PC-AT compatible with a free 1SA card slot
MS-DOSTM Version 3.2 or higher or OS/2® Version 1.2x or higher

One of the following network operating environments:
-

Any network operating system supporting the NDIS standard, such as
PATHWORRKSTM or LAN Manager

Novell® NetWare® Version 2.1x or higher, Version 3.1x, Version 4.0 or
NetWare Lite

The basic WaveLLAN component set. which consists ofa Network Interface
Card (NIC). an O.anidirectional Antenna Module kit, and software diskette(s)
The appropriate tool for removing the cover of your PC

2.2

Installation Steps
I

Install the WaveLAN NIC.

if desired, install the optional encryption chip (and the optional Boot ROM
for the WaveL
AN 2400 only) on the WaveLAN NIC. Verify the IO base

address. Then, install the card in a PC and connect the antenna. These steps
are described in Chapter 3,

2-1

Set the Network Configuration Parameters.
Run the Configuration Setup utility to set the Network Configuration parameters and create a Card Configuration diskette. Do this only once per network.

This step is described in Chapter 4.
Configure the WaveLAN NIC.
Using the Card Configuration diskette, run the Configuration Install utility to in-

stall the Network Configuration parameters on each WaveLAN card. This step is
described in Chapter 4.
Test the Communica.ions Path (optional).
When you have installed at least two WaveLAN NICs, and before installing

any network drivers, uvse the Point-to-Point Diagnostics utility to check your
WavelLAN installation. This step is described in Chapter 6.

Install the Network Drivers.

Install or generate a network driver. The procedure is different for each network operating system. Refer to the appropriate appendix for information
about installing drivers.

Refer to...

For Information About...

Anpendix A

installing NetWare drivers

Appendix B

installing NDIS compatible drivers, including examples for
the PATHWORKS, LAN Manager, PC/TCPTM, StarLAN,
and LAN Server environments

Appendix C

2.3

Microsoft Windows for Workgroups

The Installation Worksheet
The Installation Worksheet. locatea in Appendix D. is designed to help you carry the
information you need through the various installation steps. It also serves as a hardcopy record of your installation, which will help you maintain your WaveLAN network or adapt it to meet changing requirements.

WavelAN PC-AT Instaiiation and Operation

3
Installing the Network !nterface Card

Unpacking the Network Interface Card
Use the following guidelines when handling the

Wave LAN® Network Interface

Card (NIC) (Figure 3-1):
1.

Carefully open the antistatic shipping bag.

CAUTION A
Static electricity can severely damage the interface
card. Topreventdamage whenunpacking and han-

dling the interface card. you should make sure you
touch a grounded metal surface, such as the chassis
of your PC, to discharge the excess static electric-

(2]

ity from your body.
Hold the NIC by its edges when ycu remove it from its shipping bag. Do not
touch any of the components or the edge connectors along the bottom of the

NIC.
103

3.1

Place the NIC on the antistatic bag on a flat surface.

3-1

Figure 3-1:

Handling the Network Interface Card

Edge Connectors
LKG-6979-921

3.2

Installing the Security Feature
To use the optional encryption feature in your WaveLLAN network, you nced to
install the encryption chip in each NIC.
1.

Following the precautions described earlicr about static electricity, carefully
remove the security chip from its antistatic packaging.

3-2

Wavel
AN PC-AT Installation and Operation

[

Examine and familiarize yourself with where the chip and the socket will be
instatied (Figure 3-2). Note the arrow embossed on the base of the socket and
the dot in the middie of the bevelled edge marking the position of Pin 1.
Alse. note the keyed corner of the chip and its corresponding socket.

3. Make sure the chip is correctly aligned, with the arrow in the socket base
pointing to the dot marking the Pin 1 position and the keyed comers in line.
4.

Carefully push the chip into its socket.

Figure 3-2:

Installing the S

position
marker

Keyed

LKG-6980-92!

NOTE

Figure 3-2 shows the security chip installation on
the WaveLAN 915. Use the same instructions to
install the security chip in the WaveLAN 2400.

Installing the Network Interface Card

3-3

Installing the Remote Boot Feature
To install the Remote Boot ROM on the WaveLLAN 2400, follow these steps:
1.

Following the instructions described in Section 3.1 about static electricity,

carefully remove the Boot ROM from its antistatic packaging.
Examine and familiarize yourself with the chip and the socket where it will

be installed (see Figure 3-3). Make sure that none of the connection pins are
bent.
(s

3.3

Make sure the chip is correctly aligned. The notch at one end of the chip
should line up with the notch in the socket. (This correctly orients Pin 1 in the

socket with Pin 1 on the Boot ROM.)

Wavel
AN PC-AT Installation and Operation

Instailing the Boot ROM

Alignment

Pooooocoodol,

notches

Figure 3-3:

LKG-8195-93

Holding the chip lengthways between the finger and thumb, engage the pins

on one side with the corresponding row of holes in the socket, and gently manipulate the chip until the pins on both sides are engaged. Carefully push the
chip into its socket.

Installing the Network Interface Card

3-5

3.4

Verifying the Hardware Configuration Switches
The WavelLAN NICs have a switch block containing four switches.

3.4.1

Verifying the WaveLAN 915 Configuration Switches
Figure 3-4 shows the WaveLAN 915 switch block. The first two switches (switches
1 and 2) arc used to set the card’s I/O base address. Switches 3 and 4 are not used on
the WaveL AN 915.
Figure 3-4:

WaveLAN 915 Hardware Configuration Switches

)

Unused switches: SW3, SW4

/0O base address: SW1, Sw2

LKG-8244931

3-6

Wavel
AN PC-AT Installation and Operation

3.4.2

Veritying the WaveLAN 2400 Contiguration Switches
Figure 3-5 shows the WaveLAN 2400 switch block. The first two switches
(switches 1 and 2) arc used to set the card’s 1/O base address. Switches 3 and 4 are
used to select the Remote Boot address or to disable the Remote Boot ROM.
Figure 3-5:

WaveLAN 2400 Hardware Configuration Switches

Boot ROM base address
switches SW3, SW4

/Q base address:
SWi, SW2

LKG-8196-92i

3.5

Setting the IO Base Address
The 1/O base address switches are factory presct to address 0300H. Change this setting only if another device already installed in your computer is using this address.

Use a small flat-blade screwdriver to set the switches. Record the settings on the
Installation Worksheet in Appendix D. Table 3-1 shows the available I/O base addresses.

installing the Network Inierface Card

3-7

Table 3-1:

/O Base Address Switch Settings

/O Address

Switch 1

Switch 2

0300H

OFF

OFF (Default)

0390H

OFF

03COH*

OFF

03EOM

NOTE

*1/O Address 03COH is used by many EGA and VGA
video adapter cards. If your video adapter is using this

170 Address, do not use it for the WaveLAN NIC.

3.6

Setting the Remote Boot Base Address
If you are using the Remote Boot feature for the WaveLAN 2400, use the information in this section to set the Remote Boot base address.
The remote boot address switches are factory preset to disable remote boot. Change

this setting only if you have installed the Remote Boot ROM and plan to use it immediately. Table 3-2 shows the available remote boot addresses.
Table 3-2:

Remote Boot Base Address Switch Settings

Base Address

Switch 3

Switch 4

Disabled

OFF

OFF (Default)

C8000H

OFF

DOO0OH

OFF

D8000H

To set the switches, use a small flat-blade screwdriver. Record the settings on the appropriate installation worksheet in Appendix D.
NOTE
If you have installed the Remote Boot ROM, but are not
going to use this feature immediately, or if you later dis-

continue using it, make sure (o set or reset the switches
to disable remote boot.

3-8

WavelLAN PC-AT Installation and Operation

3.7

Using LEDs
The WaveL AN 915 has three Light Emitting Diodes (LEDs) that provide a visual
indication of the status of the card (Figure 3-6). Table 3--3 describes the functions of
the LEDs.

Table 3-3:

Function of LLEDs for the WavelLAN 915

LED display

Status

Description

First LED

Continuous light

Card has power

Second LED

Flashing light

Receive data activity

Third LED

Flashing light

Transmit data activity

Figure 3-6:

WaveLAN 915 LEDs Display

Card Power

/ Receive Data

/— Transmit Data

LKG-7195-921

NOTE
The WaveL
AN 2400 does not have any Light Emitting
Diodes (1.LEDs) indicators.

installing the Network Intertace Card

3-9

3.8 Installing the Interface Card in Your PC
The following directions apply to most PCs. See your PC owner’s manual for more
information on how to install an adapter board.

CAUTION A
Stauc elecincity can severely damage the interface
card. To prevent damage when unpacking and handling
the interface card, you should make sure you touch a
grounded metal surface, such as the chassis of your PC,
1o discharge the excess static electricity from your body.

Tumn off the power switch and disconnect cables.

Turn off the power to your PC and any attached devices. Disconnect the power cord and other cables.

WARNING A
Do not attempt to install the interface card without dis-

connecting the power cord and other cables from your
PC. If you fail to take this precaution, you could receive
a severe electrical shock or cause damage to your PC.

Remove the cover of your PC.

Refer to your PC owner's manual for specific instructions about removing the
cover.

Choose an ISA expansion slot and remove the 1/0O cover plate.
Prepare the expansion slot to hold your NIC by removing the slot’s /O cover
plate. The 1/O cover plate is attached by a single screw on the top.

3-10

Remove the blank I/O cover plate for the expansion slot you have chosen.

Wavel
AN PC-AT Installation and Operation

Insen the NIC.
Align the edges of the card with the expansion slot and gently press on the
top of the card until the edge connector is seated in the slot (Figure 3-7).

Figure 3-7:

Inserting the Network Interface Card

Inscrt and tighten the retaining screw in the 1/0 cover plate of the WaveLAN

NIC.

Installing the Network Interface Card

3-11

Install the antenna.

Refer to Section 3.9 for detailed information about connecting the antenna to

a WaveLAN NIC.

3.9 The OmniDirectional Antenna
The Omnidirectional Antenna is a compact, high-performance antenna designed for

easy installation and flexible usage in an indoor work group environment, such as an
office or department store. The antenna module is fitted with a coaxial cable which
allows it to be placed on the desktop or mounted on a wall or other surface adjacentto
the PC.
The antenna kit includes:
¢

Antenna module with cable

Support bracket for vertical or horizontal placement

Support bracket mounting accessories:

Screws and wall anchors

Adhesive backed Velcro® fastening strips

(able attachment tool (available only for the WaveLAN 915)

An optional 30-foot (9-meter) Antenna Cable Extension kit is also available for the
WavelLAN 915.

3.9.1

Connecting the WaveLAN 915 Antenna
To connect the antenna to the WaveLAN 915, screw the male F-type connector to the
female connector protruding from the WaveLAN card end bracket. Connect the an-

tenna using the following steps (Figure 3-8):
1.

Screw the antenna cable connector onto the card’s antenna connection until
hand tight.

3-12

Wavel
AN PC-AT Installation and Operation

On some PCs you may have difficulty doing this with fingers alone In that
case, use the antenna attachment tool provided. Slip the attachment tool (the
large end first) over the cable connector and push the connector through until
it seats snugly in the tool. The connector should protrude about .1 inch (2

mm) from the small end of the tool. You can now use the attachment tool to
screw the cable connector home. (The tool remains on the cable after fitting.)
[

Reinstall the cover and attach the cables.

Reattach the PC's cover. Move your PC to its intended location, and attach
the power cord and other cables.

3.9.2

Connecting the WaveLAN 2400 Antenna
Use these steps to connect the WaveLLAN 2400 antenna (Figure 3-8):
1.

To connect the antenna to the WaveLAN 2400, simply push the cable end

connector onto the connector situated in the middle of the card’s end bracket

until it clicks into place.

Reattach the PC's cover. Move your PC to its intended location, and attach

the power cord and other cables.

Installing the Network Interface Card

3-13

Figure 3-8:

Cornecting the Antenna

WaveLAN 915

A
N,

WavelLAN 2400
-G\

LKG-8197-92!

3.10 Antenna Placement
‘The antenna performs best in an open environment with as few obstructions as pos-

sible (Figure 3-9). Signal strength can be significantly affected by closeness to metal surfaces and, 1o a lesser extent, by concrete walls, thick masonry walls, and solid,
high-density matcrials. To ensure the best performance:

Ensure the antenna is sccurely connected to the WaveLAN NIC in your PC.

Position the antenna at right angles to the mounting surface.

Place the antenna as high as possible.

Avoid lcaving the antenna where it may be concealed by working materials

such as books or papers.
e

3-14

Avoid placing the antenna flat against a metal, concrete, or masonry surface.

WaveLAN PC-AT Installation and Operation

Figure 3-9:

Typical Antenna Position

LKG-8309-921

Installing the Network Interface Card

3.11 Using the Antenna Support Bracket
The antenna module is constructed to snap onto its support bracket in one of two
positions (Figure 3--10):

At its midpoint, allowing the module to sit flat against the support bracket.

This method is suitable for windows and light hollow partitions. It is not recommended for metal, concrete, masonry, or solid wood surfaces.

Atits edge, taking a position at right angles to the support bracket. This is the
normal and preferred method, allowing the antenna module to hang from a
vertical suiface or stand on a horizontal one.

Figure 3-10: Using the Antenna Mounting Bracket

LKG-6985-921

3-16

Wavel
AN PC-AT Installation and Operation

You can affix the support bracket to a vertical su.face in one of two ways:
e

With the wall anchors and screws provided. This method is recommended for

concrete and masonry walls, papered or with a rough surface.
e

With the Velcro fastening strips. Use this method for smooth hollow surfaces,

such as half-height office dividing walls and filing cabinets or windows. On
cleth-covered walls, attach only the Velcro to the antenna.

Instatling the Network Interface Card

3-17

Software Installation and Card Configuration

4.1

Before You Begin
Use the MS-DOSTM DISKCOPY command to create a working copy of your
Wave LAN® diskette. Use your working copy in all card configuration and

driver installation procedures. Store the original diskettes in a safe piace.

4.2

Configuration Parameters
You need to define and install the configuration parameters before your WaveLAN
Network Interface Card (NIC) can operate in your environment. These parameters
include:

Network ID - Used to differentiate one WaveLAN network from another if
more than one network is located in the same area. All stations on a network
must have the same Network ID.

Medium Access Control (MAC) Address Type - Identifies the type of addressing used to differentiate one station from another in the same network.
This can be UNIVERSAL (which is the default), in which case the unique
value factory-installed on the NIC will be used, or Local, in which case you

can assign a value to the MAC address.

MAC Address — Used only if Local address type is selected. You can assign
an address value when the configuration is being installed. The value you
assign must be unique within the network.

4-1

[Interrupt Request Line Number (IRQ) - You can select one of eight IRQ val-

ues 3,4, 5,7, 10 (default), 11, 12, 15. You must select an IRQ not in use by
another device in your PC.
Optional features include:
e

Datalink Security - If you intend to use data encryption and have installed the

security chip on the WaveLAN NIC, this parameter allows you to enable and
disable encryption.

Encrypticn Key — If encryption is enabled, you can specify a key value or
have one generated automatically. The encryption key must be the same for
ail stations in the network.

Remote Boot ~ If you are using the WaveLAN 2400, you can use the Remote

Boot feature. (Refer to your Remote Boot User’s Guide for more information.)
There are two ways you can configure the WaveLAN NIC’s network parameter values:

Automatically create a card configuration disk by running the INSTALL program on the distribution media (Section 4.3).

Manually set the configuration using the SETCONF.EXE and INSTCONEFEXE utilities (Sections 4.4 - 4.7).

4.3

Automatically Creating a Card Configuration Disk
Use the following procedure to create a card configuration disk:
1.

Use the DOS FORMAT/'S command to create a bootable MS-DOS diskette.

Place the WaveLAN distribution diskette in drive A and type A:INSTALL.

This procedure prompts you for the following:
Prompt

Response Options

Network ID

nn-nn

MAC Address Type

Universal*/Local

Datalink Security

Disable*/Enable (Encryption option)

‘Detault

4-2

Wavel AN PC-AT Installation and Operation

The Installation procedure prompts you to put your bootable MS-DOS diskette in the drive. Once the diskette is in the drive, the procedure writes out
the file INSTCONF.EXE to your diskette.
Now you can use this newly created configuration diskette to load the network parameter values on each WaveLAN NIC in the network.

Place this new configuration diskette in drive A and type A:INSTALL (or
reboot with this diskette).

4.4 Manually Configure Using the SETCONF and INSTCONF Utilities
Configuring the WaveLAN NIC is a two-step procedure:

Use the Configuration Setup utility SETCONF.EXE to set the parameter values common to all stations in the network (for example, all parameters except
MAC Address and IRQ). The values you set are written to the executable

Configuration Install file INSTCONF.EXE (or to another name you assign).
NOTE
You need only perform step 1 once. The parameter val-

ues you select apply to all WaveLAN NICs in the net-

work.

Run the executable Configuration Install file INSTCONF.EXE) at each PC
to install the parameter values on the NIC. In this step, you must select an
IRQ (default=10). You can also assign a local MAC Address if you selected
the Local option during Configuration setup.
NOTE

If you installed the Remote Boot feature on the
WaveLAN 2400, see your Boot ROM User’s guide for

details on how to install a configuration.

4.5

Setting the Configuration Parameters
To set the configuration parameters, you need a PC running MS-DOS and equ ipped
with a floppy disk drive. The WaveL
AN NIC does not have to be installed.

Software Installation and Card Configuration

4-3

Place your working copy of the WaveL
AN softwarz diskette in the floppy disk drive.

Change to directory \CONFIG.DOS on the floppy drive. Type setconf and press
Enter. The initial screen appears (Figure 4-1).
NOTE
If your PC 1s equipped with a monochrome monitor, or
if the screen display 1s difficult to read, display quality

may be improved if you use the Monochrome Com-

mand Line Option set. Type setconf —m at the DOS
prompt.

Figure 4-1:

(

Opening Screen of SETCONF.EXE

WaveLAN CONFIGURATION SETUP [PC-AT] V n.n
Load Configuration Install File
Save Configuration Install File

Quit without Saving

Use Cursor Keys to selec! option and press [Enter]

Load - Loads the Configuration Install utility file you wish to display

or modity
Save - Saves the changes you have made, and exits from the program
Quit - Exits from the program without saving

{F1] - General Help

LKG-6991-921

Use the cursor keys, or type L. to load the Configuration Install file. You are then
asked for the name of the file to load. If you are installing a board for the first time,
enter: instconf (or the name that you assigned to the Install Configuration file).
NOTE
INSTCONFE.EXE is the name of the unmodified config-

uration installation file supplied on the WaveLAN software diskette.

Wavel
AN PC-AT Installation and Operation

After the Configuration Install file is loaded, you see the Parameter Entry screer
(Figure 4-2).

Figure 4-2:

SETCONF Parameter Entry Screen

WavelAN CONFIGURATION SETUP [PC-AT} V nn

input Filename:

INSTCONF.EXE

Description:

Original File as delivered.

Network 10:

Nene

MAC Address Type:

Universal

Datalink Security:

Disabled

Press [Enter) to accept field entry
Enter up to 50 characters of text.

Use of this field is optional. Enter any descriptive information you wish
to record tor your own reference, e.g. your name, date of installation,
department name etc. This information is displayed when you run the Install
utibity.

{ESC] cancels text input and restores the previous description.

[F1]} - General Help

[F10] - Retum to previous menu

LKG-6992-921

NOTE
Figure 4-2 shows the parameter entry screen for the
factory default Configuration Install file. If you have
previously instalied

a configuration using INST-

CONF.EXE, the last parameter values used will be displayed.

4.5.1

Description

Enter the information you think might be useful to help you manage your WaveLAN

configuration. The information you enter is displayed when you install the configuration, and also, if you run the setup utility again, using the same input file. If you
maintain multiple networks or frequently reconfigure stations, this information becomes valuable reference data. This entry is optional.

Software Instaliation and Card Configuration

4-5

4.5.2

Network identifier

A unique network identifier (Network ID) logically connects the stations in a
WaveLAN network (as cabling physically connects stations in a wired network).

The Network ID is used to distinguish this network’s traffic from other radio-frequency signals in the vicinity, such as traffic for another nearby WavelLAN network.
All nodes in a network must have the same Network ID.

You must enter a Network ID the first time you run the Configuration Setup utility.
You can enter a hexadecimal number up to 4 digits, or press F2 to generate a random
value.

4.5.3

MAC Address Type

Every WaveLAN NIC contains a unique factory-installed address conforming to the
universal MAC address convention. If you prafer to use a locally determined ad-

dressing system, select the Local option.
4.5.4

Datalink Security
Use this parameter to turn encryption on or off. A selection here is meaningful only if

the optional security feature is installed on the WaveLAN NIC.

If you sefect ENABLED, the program displays the current value of the encryption
key. If this value is NONE (which is the case when you use the program for the first

time
), you must enter a valid 16-hexadecimal key value. The easiest way to accomplish this is to use F2 to generate one.

NOTE
Guidelines for valid key values are given in the documentation that comes with your secunity feature kit. If

youintend to manually enter the encryptionkey. please
read these guidelines carefully before you do so.

4-6

Wavel
AN PC-AT Installation and Operation

4.6 Saving the Configuration Parameters
When you are satisfied with the entries you have made on the Data Entry screen,
press F10 1o reium to the closing screen and select the Save option.
You can save your changes to the file that you loaded at the beginning of the Sctup
program, in which case, cxisting parameter values are overwritten, or you may

¢hoose 1o have the new values written to a different fite. If you direct the valuesto a

different file, the program prompts you for the new filename.
NOTE
If you are going to insiall this configuration on multiple
WaveLLAN NICs, you should copy the Configuration
Insiall file to a bootable disketie. You can then usc this
diskette to install the contiguration parameters on each
WavelLAN NIC in the network.

To create adiskette that you can use to install the configuration parameters on each
WavelLAN NIC, follow these sieps:

Prepare an MS--DOS bootable diskette (use the DOS FORMAT command

with the /S option).

Copy the Configuration Install file you have just created to the bootable diskette.

NOTE
You can maintain muluple Configuration Install files.
This faciltates flexible resource-switching between

networks orregular reconfiguration for security or other
reasons. A network-switching example 1s described in

Sccuon 4.9,

4.7

Installing a Configuration
You used the Configuration Sctup utilily to set parameter values in the executable
Configuration Install file. Now you must run this filc to install the configuration valucs on the WavelLAN NIC.

Software Installation and Card Configuration

4-7

To complete this part of the configuration process, you must already have installed
the WaveLAN NIC in a PC. You also need to know:
e

/0O Base Address (set by switches on the NIC when it was installed - default
value is 300)

Interrupt Request Line number (required to run the NIC's startup diagnostics
before configuration - default value is 10)
NOTE
The following pages describe the full-screen operation
of the installation utility. You can bypass some screen

operations by using command line options, described in
Section 4.8.
NOTE
The Configuration Install uulity performs startup diag-

nosti¢ routines which preempt normal operation of the
WaveLLAN NIC. Do not attempt to install a configuration whule the network driver is runmng.

Place the diskette containing the Configuration Install file in the floppy disk drive.

Make sure the DOS prompt matches the drive you have selected. Type instconf (or
the name you used to save the parameter setup) and press Enter. The initial screen
appears (Figure 4-3).

WavelAN PC-AT Installation and Operation

Figure 4-3:

Configuration Install Utility - Initial Screen

WavelLAN CONFIGURATION INSTALL [PC-AT] Van

Enter Card Address:

300

Enter the 3-digit hexadecimal address of the card to be configured, or press
|ENTER] to accept the default value (300H).
The card address you enter should correspond to the one set using the
configuration switches, when the card was physically instalted in this
network station The Install utility uses the card address to locate the
card to be contigured

[F1] -~ General Help

{F10; — Exit {abandon installation!) J
LKG-6993-92i

Use this screen to indicate the 1/0 base address of the WaveLAN NIC. The address
should match the one sct on the card (Section 3.4). To accept the default value, press
Enter.

Software Installation and Card Configuration

The program now begins the card’s startup diagnostics. If this is successful, the
Interrupt Request Lire screen is displayed (Figure 4-4).
Figure 4-4:

Contiguration Install Utility - IRQ Screen

WavelLAN CONFIGURATION INSTALL [PC-AT} Vnn
Enter Interrupt Request Line:

WavelAN card is configured to 16 bits.
Enter the decimal Interrupt Request Line number, or press [ENTER] to
accept the currently configured number.
interrupt Request Line numbers allowed are 3, 4,5, 7, 10, 11, 12, and 15,
The number you enter should be one that is not used by another card or
device mstalled in this station. After successtul entry, the card is
contigured tor the new number

{F1} — General Help

[F10] — Exit (abandon installation!) /
LKG-6994-921

You can usc this screen 10 change the Interrupt Request Line number. If the configu-

ration is being installed for the first time, the value shown is the factory default (10).
To accept the default value, press Enter. The startup diagnostics will now continue.

successful

completion,

the

Configuration

Update

screen

displayed

(Figure 4-6).
The Update screen displays:

The current configuration parameter values. In Figure 4-5, the screen displays the original values.

The new values that the Configuration Install utility will install.

Regardless of whether security is enabled or not, the value of the encryption key is
never displayed.

Wavel
AN PC-AT Installation and Operation

Figure 4-6:

Configuration Install Utility — Update Screen

WavelAN CONFIGURATION INSTALL {PC-AT] V n.n

Description:

—- New Values —
FE-30

Network 1D:

— Card Values ——
None

MAC Address Type:

Local

Universal

MAC Address:

42-00- - - ~

08-00-0E-20-00-01

Datalink Security:

Enabled

Disabled

MAC Address Entry

Update Card Configuration
Exit

Use cursor keys to select option and press ([ENTER].
The new contiguration requires a locally administered MAC Address value.
You must enter the last 8 digits of the MAC Address before updating
the card!

{F1] ~ General Help

J
LKG-6995-92!

When the new MAC Address Type is Local, a Local MAC address must be present

before the update can take place. In the above example, the MAC address field is
partially blank, indicating that aLocal MAC address has not yet beenentered. In this
case, sclect MAC Address Entry from the menu before selecting Update.
When the new MAC Address Type is Universal, you will not have to enter a ncw

MAC address. When both old and new MAC Address Types are Local, anew Local
MAC address is not required. The MAC address entry consists of 8-hexadecimal

digits, and must be a unique value (within this network).
Sclect Update to install the new configuration parameters. Select Exit to leave the
program after Update, or 10 exit the program at any time.

This completes the Hardware Configuration.

Software Installation and Card Contiguration

4-11

4.8

Parameter Options for Batch Operation
Command line options are designed to allow the Install utility to run in batch mode.
For example, a station with asingle WaveLAN NIC installed could participate in two
separate networks at different times of the day by running batch files containing different Configuration Install utility files, each installing a different Network ID.
Command line options allow you to:
e

Select batch mode of operation (not full-screen)

Indicate the NIC’s /O Base Address

Set the Interrupt Request Line number

Set the Local MAC Address (when Local MAC addressing is used)

Select monochrome display mode

The following parameters are shown in uppercase for clarity. Youcan also use lowercase characters.

-B

Selects batch mode. In batch mode the full-screen displays
are suppressed. Therefore, you must also specify all other
configuration parameters which normally would be entered.

The NIC’s /O base address and IRQ are required when in
batch mode.
-Annn

Identifies the NIC’s IO base address (nnn is the hexadecimal value) to allow access to the NIC. Required in batch
mode. When not in batch mode, this parameter suppresses

display of the Install utility
s initial screen.
-Inn

Sets the Interrupt Request Line number (nn is the decimal
value). Required in batch m~de. When not in batch mode, it

suppresses the Install utility's IRQ entry screen.
~Lnnnnnnnn

Sets the Local MAC Address (nnnnnnnn is the hexadeci-

mal value). In batch mode, if MAC addressing is being

changed from Universal to Local, this parameter is required.

4-12

WavelL
AN PC-AT Installation and Operation

-M

Sets the video mode to monochrome. Used for some mor.ochrome monitors and certain video adapters. Its application
in batch mode is to ensure that error messages are properly
displayed.
NOTE
When an error occurs in batch mode, the program reverts to full-screen mode to repornt the error. You cannot

correct parameter errors at this point. You must repair

the batch file and rerun, or restart the program without
parameters. Also, when an error occurs, the program

terminates with the DOS ERRORLEVEL exit code set
to 1. This allows you the possibility of executing alternative baich file commands. You can find more information on using DOS exit codes inthe MS-DOS User’s
Reference Manual.

Command line parameters are placed on the DOS command line directly after the
filename of the Configuration Install utility file. Parameters are separated from the
filename and from each other by at least one space. Parameters may occur in any order.

Example:

instneta -a300 -b

This command automatically installs the configuration represented by INSTNETA.EXE in a NIC with I/O base address 300H and where the IRQ will not change.
No screens are displayed.

Example:

instnetb -a3e0 -i10

This command begins configuration installation on a NIC with I/O base address
3EOH and set the IRQ to 10. The first and second screens are not displayed.

4.9

Switching Workstations Between Networks
To switch a workstation from one network to another, you must rerun the Configura-

tion Install utility to change the workstation’s Network ID. This should be done only
when the workstation’s LAN driver is not active (for example, during a warm or cold
reboot).

Software Installation and Card Configuration

4-13

One way to easily switch a workstation between networks on a regular basis is to
execute the Configuration Install utility as a command on a bootable DOS diskette.
The following example shows how a workstation can sometimes be assigned to network NET1 and at other times to network NET?2.

cxample
1.

Create a bootable DOS diskette.

Run the Configuration Setup utility twice to create two Configuration Install
utility files: INSTNET! and INSTNET?2, differing only in their Network IDs.
For example:

INSTNET1.EXE:

INSTNET2 EXE:

Network ID

= 0AOI

MAC Address Type

= Universal

Datalink Security

= Disabled

Network ID
MAC Address Type

= 0A02
= Universal

Datalink Security

= Disabled

Create two .BAT files, one for each network. For example:
NETI1.BAT:

instnet! -b —-a300

NET2.BAT:

instnet2 ~b -a300

To switch networks, do the following:

To switch to NET1:

Reboot using the bootable diskette
Run netl
Example: c:\netl
Reboot from your standard disk

To switch to NET2:

Reboot using the bootable diskette
Run net2
Example: c:\net2
Reboot from your standard disk

4-14

Wavel
AN PC-AT Installation and Operation

5
Radio-Frequency Network Operations

5.1

Radio-Frequency Network Operations
In general, operating a radio-frequency Local Area Network (LAN) is the same as
most other types of LANs. However, due to the nature of the transmission medium,
radio-frequency networks are more sensitive 10:
@

Signal interference (noise)

Signal attenuation

5.1.1

Signal Interference

Signal interference (or noise) is radio-frequency signals. detected by areceiving antenna, that are not transmitted by any station in the receiving station’s network. The
source of the interfering signal may be:

An adjacent WaveLAN network with a different Network 1D

Another (not WaveLAN) radio-frequency network

Non-network sources, such as:
-

Security gates (like those often placed near the entrances of shops and
department stores)
Elevator motors

Photocopiers
Microwave ovens

For most non-network noise sources the effect is localized and can be eliminated by
antenna or station relocation.

5.1.2

Signal Attenuation

Signal attenuation is a loss of signal strength, which occurs naturally over distance,
but which also can be caused by radio-frequency barriers in the signal path. Examples of barriers are:

Metal surfaces surrounding an antenna

Enclosed locations with concrete walls, floor, and ceiling

Nearly every object (partitions, furniture, people) in the path of the signal causes
some degree of attenuation. In most cases, this docs not have a significant effect on
network perfermance. Careful placement of the antenna minimizes the effect onnetwork performance.

5.1.3

Signal-to-Noise

A station's communications capability is significantly reduced when the noise level

perceived by that station regularly exceeds the strength of signals received.

5.2

Optimizing Network Performance
You can optimize network performance through careful placement of servers and
workstations, taking into account the radio-frequency characteristics of the work environment. These depend on a large number of factors, including:

5-2

(Construction materials

Office plan (closed or open)

Presence of windows

WaveiL
AN PC-AT installation and Operation

It is not possible to predictexactly how the environment will affect network performance, if at all. The following are some general guidelines for network station arrangement,

A file server is often the busiest station on a network. In an open or semi-open work
area, it is recommended that you arrange the network in such a way that file servers
occupy a central position (Figure 5-1).
Figure 5-1:

Station Placement in an Open Office

LKG-6986-92i

Radio-Frequency Network Operations

5-3

If your network server is kept in an area with other potentially noisy equipment (for

example, a photocopier), you should consider using an antenna extension cable
(available only for the WaveLAN 915) to enable the antenna to be placed outside the
noisy area (Figure 5-2). This reduces the effect of background noise from the serv-

er's local environment.
Figure 5-2:

Using an Antenna Extension

- Print Room

LKG-6987-921

When a network is dispersed across two or more work groups, separated by a large

open space or situated on different floors, it may be necessary to use a bridge toover-

come signal attenuation (Figure 5-3).
Due to a combination of distance and signal-blocking floors and walls, the path be-

tween the server and stations A and B suffers attenuation, making communication
difficuit. An ethernet adapter with the appropriate software must be installed in the
bridges enabling them to act as a bridges. Stations A and B then communicate with
the server by means of stations X and Y.

Wavel
AN PC-AT Installation and Operation

Figure 5-3:

Bridging in a Dispersed Network

StaonA

StationY
{Bridge)

File Server.

StaonB

R
-

StationC
LKG-6987-92!

You can usc the Point-to-Point Diagnostics utility to determine if a bridge is really
nccessary.

5.3

Problem Determination
Problems in a WaveLLAN network can be related to:
¢

Component failure (of card or antenna)

Environment and operation

Radio-Frequency Network Operations

5-5

Component Failure

5.3.1

Component failure is normally detected by a startup diagnostics routine built into
AN NIC. These programs are:
three programs which use the WaveL
e

WaveLAN network driver

Configuration Install utility

Point-to-Point Diagnostics utility

The startup diagnostics routine which, as its name implies, is run at program startup,
checks out all the major hardware components on the WaveLLAN NIC before allowing its calling program (the network driver, for instance) to continue. The following
components are tested:
e

PC bus interface

The card’s memory

Parameter storage area

[ AN controller

RF (radio-frequency) modem

Security feature (only if the card is configured for Datalink Security)

A component failure causes an error message to be displayed.
NOTE
The startup diagnostic routine does not test the antenna.

To detect antenna failure, you need to run the Point-toPoint Diagnostic utility.

Environment and Operation

5.3.2

Environment and operation-related problems can be caused by one or more of the
following:

5-6

Poor station or antenna placement (Section 3.10)

A difficult network environment

Wavel AN PC-AT Instaliation and Operation

Path defects (antenna, cable, connection)

Competition from adjacent networks

Network loading

You can use the diagnostic utilities to diagnose and resolve environmental and ~perational problems.

5.4

Diagnostic Utilities
There are two diagnostic utility programs:
e

Point-to-Point

The Point-to-Point Diagnostics utility allows you to verify the communications path between two stations. You can use it to measure local noise and to
find the best antenna position. Refer to Chapter 6 for more information about
the Point-to-Point Diagnostic utility.
e

Node

The Node Diagnostics utility allows you to display and process a worksta-

tion's diagnostic counters, which are maintained by the network driver. It
provides a means to check the WaveLAN network and to determine the cause
of poor network performance in general or to pinpoint stations where performance is poor in relation to the network average. Refer to Chapter 7 for
more information about the Node Diagnostic utility.

5.5

Troubleshooting List
This list identifies some common symptoms and solutions for environmental or
operational problems.

Radio-Frequency Network Operations

5.5.1

Unable to Communicate with the Server
Check that:

The antenna is securely connected

The workstation and server have the same Network ID

Security is disabled at both stations, or security is enabled and both sta-

tions are using the same key

Run Point-to-Point Diagnostics between this station and another nearby sta-

tion to verify the station can communicate.
Run Point-to-Point Diagnostics between this station and the server or bridge

to test the communications path. You must take the server or bridge off line
to do this.

5.5.2

Poor Station Performance Relative to the Network Average
Run Node Diagnostics. The diagnostic counter values can indicate possible

causes (for example, local noise is high).
Run Point-to-Point Diagnostics between this station and the server to verify

the path (for example, attenuation between server and this station is too high).
5.5.3

Overall Network Performance Is Poor
1.

Run Node Diagnostics on every station. The diagnostic counter values can

indicate possible causes (for example, overall noise is high, network load is

high, or interference from another wireless LAN).
If counter values show that some stations have significantly higher percentages of lost packets than others, run Point-to-Point Diagnostics between those
stations and the server.

5-8

WaveLAN PC-AT Installation and Operation

6
The Point-to-Point Diagnostics Utility

6.1

Running Point-to-Point Diagnostics
The Point-to-Point Diagnostics utility allows you to . erify that:

Cards and antennas function correctly to allow exchange of messages.

Antenna positioning is optimal.

Stations are within operating range of each other.

You can also use the utilitv to get information about local noise and environmental

suitability. Measurement data can be saved to a disk file. The Point-to-Point Diagnostics utility is run out-of-service, that is, the participating stations are not logged in
to the normal Wave LAN® network. They are instead, set up as a dedicated commu-

nications link, using a special dedicated Network 1D, for the duration of the test.

6.2

Installing the Point-to-Point Diagnostics Utility
You cannotrun the Point-to-Point Diagnostics utility while the network driver isrun-

ning. To run the utility, you mustreboot the station without starting the network driver. You also must run the utility between two stations at the same time.
Digital recommends that you install the Point-to-Point Diagnostics utility on a bootable diskette. Follow these steps to install the Point-te-Point Diagnostics utility:
1.

Prepare an MS-DOSTM bootable diskette.

6-1

Copy the file PTPDIAG.EXE from directory \PTPDIAG.DOS on the
WavelLAN software diskette to the bootable diskette.

6.3

Running the Point-to-Point Diagnostics Utility
Because the Point-to-Point Diagnostics utility tests the communications path between two stations, you must run the utility on two stations at the same time. For each
station, you must know the /O Base Address of the WaveLAN NIC, which was set
when the NIC was installed.

To run the utility, place the MS-DOS bootable diskette in drive A of the workstation
or server and reboot. Type ptpdiag and press Enter. You should see the utility's startup screen (Figure 6~1). Youcan use this screen to identify the /O base address of the
WaveLAN NIC. To accept the default value (0300H), press Enter.
Figure 6-1:

Point-to-Point Diagnostics Initial Screen

(

WavelLAN POINT-TO-POINT [PC-AT] V n.n

300

Enter Card Address:

Enter the 3-digit hexadecimal address of the Network Interface Card to be

diagnosed or press [ENTER] to accept the detault value (300H).

The card address you enter should correspond to the one set using the
conhguration switches, when the card was physically instailed in this
network station. The Diagnostic utility uses the card address to locate the

card to be diagnosed.

[F1] - General Help

[F10} - Exit

‘/
LKG-6996-92

At the next (menu) screen, you can choose to run Card Diagnostics, Wireless Communication Link Test, or exit from the program.

WavelLAN PC-AT Installation and Operation

The Card Diagnostics option allows you to rerun the card’s stariup diagnostics to
verify the card’s hardware components. This test was already run at uiility startup
and is the same test as is run at network driver startup and also when you installed the
station configuration.
The Wireless Communication Link Test tests the communications path between two
stations. A special “Diagnostic Link ID” is used to prevent interference from other
stations not involved in the test. After a link has been established, the program ex-

ecuting at each participating station begins to measure signal reception conditions.
Based on these measurements, the utility displays an assessment of the link quality.
You can continue to a second screen to display the measurement details.
When you start the test from the first station, a screen is displayed similar to that

shown in Figure 6-2. You must start the test at a second station before communication can take place between the stations. When one station detects transmission from
another station executing the test, measurement begins.
Figure 6-2:

(

No Other Station Is Active Yet

WavelAN POINT-TO-POINT [PC-AT] V n.n

Wireless Communication Link 1 Test

awaiting messages from remote station......

Startup Link Test on other station or check antenna connection.

[F1]~ Help

[ESC} - Menu

LKG-6397-921

After a few seconds, the link quality assessment is displayed {Figure 6-3). Link
quality ratings are good. acceptable, or poor.

The Point-to-Point Diagnostics Utility

6-3

Figure 6-3:

Link Quality Assessment Display

WavelAN POINT-TO-POINT [PC-AT] Vnn

Wireless Communication Link 1 Test

Link Quality. Acceptable

\\ [F1] - Help

[PgDn] - Show Data

[F10] - Save Data

[ESC) - Menli/
LKG-6998-92!

You can investigate the link quality in more detail by pressing the PgDn key to dis-

play the Measurement Data screen (Figure 6-4). If you start the Link Test on more
than onc station, the message “awaiting messages ...”" is displayed. The problem
could be:
e

Antenna not properly connected.

Action: Check the antenna connection.
e

Signal too weak. The antenna is completely shiclded by a radio-frequency
barrier or the stations arc too far apart.
Action: Rclocate the antenna and/or the station. You do not need to restart the

test, measurement begins automatically when signals from the other station
are detected.
e

[ocal noise level too high for signal mcasurement. The antenna is (oo close
1o a local noisc source.
Action: Relocate the antenna and/or the station or eliminate the local noise
source.

Wavel
AN PC-AT Installation and Operation

WaveLAN NIC or antenna defective.

Action: Replace the antenna and/or the NIC.
e

Security feature mismatch. If the optional encryption security feature has
been implemented., it is possible that one of the stations does not have encryption enabled or that the encryption key values are different.
Action: Check your installation records. Ensure both stations have security
enavled and are using the same security key, or both stations are configured
to ha e security disabled.

Diagncstic Link ID mismatch. If you are using Command Line parameters to
set the Link 1D, this must be the same for both stations.
Action: Check the setting if used.

6.3.1

The Measurement Data Display

The utility displays measurement data for both the local and remote stations. Each
station is identitied by its MAC address (Figure 6-4).
Figure 6-4:

Link Measurement Data Display

WaveLAN POINT-TO-POINT [PC-AT] V n.n

)

Wireless Communication Link 1 Test

Max.]
16

Local Receive Conditions

12—

— Max.
e Max 8588 pin
Min.

Max.—
16

Remote Receive Conditions

o Max——~ Max.
;
i
E
Mi

125

g4 -1

4 -

Min.

Signal

Quality

SNR

Signal

Level

Quality

Address:08-00-0E-1F-2A-01
Remote Tx Packet : 00003456
Local Rx Packet
: 00003401
Successful Rx
.
98.4%

\ {Fi]-Help

Address;08-00-0E-1F-00-11
Remote Tx Packet : 00003456
Local Rx Packet
: 00003448
Successful Rx
;.
99.5%

Link Quality: Acceptable

[F2}-Freeze

SNR

[F3]- Reset

[F10]-Save

[ESC]~ Menu
LKG-6309-921

The Point-to-Point Diagnostics Utility

6-5

For each station, six measurements are displayed:
e

Signal quality

Signal-to-noise ratio (SNR)

Signal level

Packets transmitted from the remote station

Packets received at this station

Percentage successful packets received

The link quality assessment is based on the signal quality and SNR measurements.
Signal Quality

Signal quality is an indication of the clarity of signals received. This can be affected by the number and position of
radio-frequency reflecting surfaces (such as exposed steel

structural components of some buildings) in the environment of the signal path.
SNR

Signal-to-noise ratio is based on the strength of the received

signal relative to the local noise. The received signal level
is displayed alongside the SNR measurement.
6.3.2

Antenna Positioning

The signal quality and SNR displays give you an opportunity to interactively determine the best antenna placement, by watching the display as you try out various positions.

Some environments cause pockets of reduced signal quality to occur in an unpredictable way. A small relocation of the antenna is often enough to give a significant improvement.

If SNR is poor and signal level is high, the antenna is too close to a local noise source.

Action; Relocate the antenna and/or the station or eliminate the local ncise source.
If SNR is poor and signal level is low, the problem is most likely signal attenuation
caused by antenna shielding or stations too far apart.
Action: Remove shielding or relocate the antenna and/or the station.

6-6

Wavel
AN PC-AT installation and Operation

6.3.3

Logging the Measurement Data
By pressing F10, you can save the measurement data to a log file. You can choose

between spreadsheet compatible Comma-Separated Value (CSV) or ASCII format.
An example of measurement data saved in ASCII format is shown in Figure 6-5.
Figure 6-5:

Example Saved Measurements

( = *LINK TEST REPORT """
Description
Link Quality

: Description
: Good

Stari Link test : 19 September 1992, 13:50
End Link test : 19 September 1992, 13:51

Local station

Address:

% Successful Rx
Signal quality (3-18)
SNR (0-18)
Signal level (0-18)

Remote station

08000E20006D

08000E200226

Mean Min. Max.
1000 16
15 16
i8
18 18

Mean Min. Max.
99 -~
15
185 17
17
17 18

Date

Time

Date

Time

Signal quality,

Max. at

19/09/92

19/09/92
19/09/92
19/09/92

19/09/92

13:51

Marx. at
Min. at
Max. at

13:51

19/09/92

SNR

18/09/82

13:51

Min. at

19/09/92

13:50

19/09/92

Signal level

Min. at

13:51
13:51
13:50

19/09/92
19/09/082
19/09/92

\ ...'.END LOGO&.':

13:51

13:51
13:51
13:51
13:51
)
LKG-7000-62|

You can append data to an existing file or save to a new file, and you can choose
to save the data only once or at regular intervals during the test.

6.3.4

Parameter Options for Batch Operation
You can use parameter options on the MS-DOS command line to specify:
e

An /O base address.

A Diagnostic Link ID.

Monochrome display mode.

The Point-to-Point Diagnostics Utility

6~7

The following parameters are shown in uppercase for clarity. You can also use lowercase characters.

-Axxx

Identifies the card's I/O base address (xxx is the hexadecimal value) to allow access to the card. This parameter suppresses display of the diagnostic utility’s initial screen.

~Nxx

Sets the Diagnostic Link ID (xx is the decimal value in the
range 01 - 10). You can use this parameter to run two
Point-to-Point tests on different pairs of stations simulta-

neously. When not used, the default value (01) is used. Station pairs must have the same Link ID set.
Sets the video mode to monochrome. Used for some monochrome monitors and nonstandard video adapters. Use this
parameter if you have difficulty viewing the display.
Example:

ptpdiag

-a300

-nl0

This command runs Point-to-Point diagnostics on a WaveLAN NIC at address
300H. The Diagnostic Link 1D is set to 10. To successfully run the test, you should
start the utility on another station, with the Diagnostic Link ID also set to 10.

WaveL
AN PC-AT Installation and Operation

I
The Node Diagnostics Utility

Atevery workstation in a WaveLAN® network, the network driver maintains an extended set of diagnostic counters. Counter values are set to zero when the driver
boots and accumulate until the next reboot.
The Node Diagnostics utility allows you to display the values ofa workstation’s

diagnostic counters. You can also save the counter values to a disk file. The Node
Diagnostics utility runs while the workstation LAN driver is active.

The Node Diagnostics utility provides a means to check the WaveLAN network and
to determine the cause of poor network performance or station performance. By col-

lecting counter values periodically, you can build a profile of network capability.
This can help you assess the performance impact of network changes or external
events.

Separate Node Diagnostics utilities are provided for the following drivers:
e

NetWarew [PX and DOS ODI drivers (Refer to Section 7.1)

NetWare OS2 Requester driver (Refer to Section 7.2)

Network Driver Interface Standard (NDIS) driver (Refer to Section 7.3)

7.1

Node Diagnostics for the NetWare IPX and DOS ODI Driver
To install the NetWare IPX/ODI Node Diagnostics utility, copy all the files on the
WavelLAN software diskette into the directory \NODEDIAG\NETWARE. This directory is located on the workstation's hard disk or on a network server accessible
from the workstation.

NOTE
The Node Diagnostics utility runs only on a worksta-

tion. You cannot run the Node Diagnostics utility on a
NetWare server.

You can run the IPX/ODI Node Diagnostics utility interactively or in batch mode. In
interactive mode, the counters are displayed on the workstation's screen. When exit-

ing the program, you can save the data in a file. In batch mode, the counters are writ-

ten directly to a file. For information on how to run the Node Diagnostics Utility in
batch mode, refer to Section 7.1.4.
To run the Node Diagnostics in interactive mode, change to the directory where the
Node Diagnostics utility files are stored, type ndipxdos, and press Enter at the

MS--DOS prompt.

If a single WaveLAN IPX or DOS ODI driver is active in the workstation, the program will display the diagnostic counters for that driver. If more than one WaveLAN

DOS ODI driver is active in the workstation, a card selection screen is displayed to

allow you to specify which WaveLLAN card statistics should be displayed.
7.1.1

Counter Information
Figure 7-1 illustrates the diagnostic counter display for the IPX driver. The DOS

ODI counter display is similar. The screen display shows two sets of counters. On the
left side of the screen, you can see the standard set of NetWare driver-maintained

counters. The four counters used in network problem determination are:
Total Tx Packets

The total number of packets successfully transmitted by this
workstation since network driver startup.

Total Rx Packets

The total number of packets successfully received by this

workstation since network driver startup.

7-2

WavelL
AN PC-AT Installation and Operation

Packet Rx too small

Number of times a packet received from the network was
smaller than the smallest size packet that can be transmitted. Activity on this counter can indicate Signal Interference.

Checksum Error

Number of Cyclic Redundancy Check errors and alignment
errors that occurred while receiving packets. Activity on
this counter can indicate Signal Interference or collisions
occurring frequently.

Figure 7-1:

Node Diagnostic Counters -~ NetWare IPX Driver

Node Diagnostics Utility DOS V n.n

Monday Sept 18 1992 3.04 p.m. _\

Standard NeiWare Counters

Wavel
AN Counters

Tota! Tx Packets
Total Rx Packets

140789
140889

Defers
Board Misc. Errors

No ECB Available

419

Packet Tx Too Big
Packet Tx Too Small
Packet Rx Overflow
Packet Rx Too Big
Packet Rx Too Small
Packet Tx Misc. Error

0
0
136
0
0
6

P
iSC.
sz,';e{f‘
Misc.
Error

Hardware Rx Mismatch

Checksum Error

[F1] - Help

29680
0

Rx Frames

141901

Own NWIiDs
Other NWIDs
Low SNR
Good SNR
Excelient SNR

Shell Driver

542813
30031
173
299
41493

PC-AT Vn.n

Node Address: 08-00-0E-20-00-13

Sample

[F2] - Percentages

: 50

[F10) - Exit

LKG-7001-921

The right side of the screen shows a set of counters specially maintained for WaveLLAN cards. A description of these counters follows:
Defers

Total number of times a packet to be transmitted was

delayed by the WavelLAN card io prevent a collision with a

packet from another staticn. Activity on this counter is related to the volume of traffic in the air.

The Node Diagnostics Utility

7-3

Board Misc Error

Number of times the board was unable to transmit a packet
due to an unspecified board failure. This may indicate a
transient problem (one that may not impact performance to

a significant degree). If the value of this counter is regularly
nonzero, you should consider replacing the card.
Rx Frames

Number of packets that have been successfully received at
this workstation since network driver startup. (This counter
is not displayed in DOS ODI Node Diagnostics.)

Own NWIDs

Number of packets from the local WaveLAN that have becn
detected by the board. This counter shows the total of all
packets detected, including those addressed to other stations
on this network.

Other NWIDs

Number of packets from other WaveLANS or corrupted

packets that have been detected by the board. (Noise can
cause this counter to increment.)
SNR

Number of signal-to-noise ratio (SNR) samples that were

taken, per category, on incoming packets with own NWID.
Signal-to-Noise sampling takes place at the station at regular intervals (about 18 times per second) while the network
driver is running. All network traffic detected by this station is sampled. The result increments one of three counters
corresponding to Low, Good, and Excellent.
7.1.2

Driver Statistics

The utility uses these counters, with the four NetWare counters already described, to
provide a set of driver statistics that you can use to diagnose network problems.
The driver statistics are summarized below:

% Successful Packets The percentage of packets transmitted to this station
that were acknowledged as received.
% Received Bad

Packets

The percentage of all frames received that were in error (for
example, checksum errors and packets too small).

7-4

AN PC-AT Installation and Operation
Wavel

9% Medium Busy

The percentage of all attempts to transmit that were
deferred to prevent collisions.

% QOther NWID

The percentage of all frames detected at this station
that did not originate in this network.

9 SNR Categories

The percentage of all signal-to-noise samples taken
that incremented a particular SNR category. The

SNR categories are Low, Good, and Excellent.

To see the driver statistics, press F2. Figure 7-2 shows the driver statistics screen.
Figure 7-2:

Driver Statistics — NetWare IPX Driver

Node Diagnostics Utitity DOS V n.n

Monday Sept 18 1892 3.04 p.m.

Driver Statistics

Successful Packets

100.0 %

Recsived Bad Packets

0.0%

Medium Busy

17.4%

Other NWID

5.2%

Low SNR

0.4%

Good SNR

0.7%

Excellent SNR

[F1] - Help

98.9 %

[ESC] - Previous Screen

LKG-7002-82i

The Node Diagnostics Utility

7-5

7.1.3

Saving the Diagnostic Data

Upon exiting from the Diagnostics Counter display, you can choose to Save the
counter values to a disk file, or Quit the program without saving. If you select Save,
you are asked to enter the name of a disk file to save to. You can append the data to an

existing file or specify a new filename.
The diagnostic counters are saved in an ASCII Comma-Separated Value (CSV) file
that can be read and processed by many spreadsheet programs. The program also
saves the workstation’s node address and the system date/time stamp. The data is
saved in the following format:
“Driver Name”,"Driver name text”

“Driver Version”,"major version.minor version”
“Card Address”,“card-address-value”
“Node Address”,"node-address-value
CrLf

“Date” MMDDYYYYCrLf,
“Hour
" HHCrLf

“Minutes” MMCrLf
“tally-name” tallyvalueCrLf
“tally-timesname”,tallyvalueCrLf
etc.

CrLf
NOTE
CrLfisequivalent to Carriage return Linefeea (hexadecimal ODOA).

7-6

Wavel
AN PC-AT Installation and Operation

Figure 7-3 shows how the counters displayed in Figures 7-1 and 7-2 are saved on
disk:
Figure 7-3:

Saved Counter Set — NetWare IPX

“Driver Name” "Shell Driver PC-AT"
“Dnver Version®,"n.n"

*Card Address”,°0300"
“Node Address”,“08000E200001”
“Date”, 05191992
“Hour",
16

04
“Minutes”

“Totat Tx Packets" 140789
“Total Rx Packets”, 140889
“No ECB Available® 420

“Packet Tx Too Big",0
“Packet Tx Too Small",0

“Packet Rx Overflow", 136
“Packet Rx Too Big",0
“Packet Rx Too Small”,0
“Packet Tx Misc. Emror"
6
“Packet Rx Misc Error",0
“Retry Tx"*-"
“Checksum Error”,3
“Hardware R« Mismatch”,0
“Defers” 29680

“Board Misc. Error”,0
“Ax Frames” 141005
“Own NWIDs" 548091
“Other NWiDs" 30035
“Low SNR",173
*Good SNR*,300

“Excellent SNR" 41901
“% Successful Packets”, 100.0

“% Received Bad Packets",0.0

“% Medwm BusyTM,
17 .4
“% Qther NWID".6
2
"% Low SNR" 0.4
", Good SNR" 0.7

"o, Excellent SNR".98
9

/
LKG-7003-92!

NOTE
For DOS ODI, the “Rx Frames” value captured is “-”.

7.1.4

Parameter Options for Batch Operation
By using parameter options on the MS-DOS command line, you can run the Node
Dragnostics utility in batch mode. The screen display is suppressed and the counters
are saved directly 10 a specified disk file.

The Node Diagnostics Utility

7-7

The batch mode of operation enables you to combine data collection and subsequent
processing in one MS-DOS .BAT file that you can run at regular intervals (for example, daily, before workstation shutdown).
Parameter options are shown in uppercase for clarity. You can also use lowercase
characters.

-B

Selects batch mode. Full-screen display is suppressed. This
is a required parameter - if missing, all other parameters
are ignored.

Fpath

Required parameter, path is the full pathname, including
filename and extension, of the file to save the counter val-

ues in. If an extension is not specified, .CSV is used.
-A

Optional parameter. Indicates that data is to be appended to
the file. If the file is new, this parameter is ignored.

Cnnnn

If multiple WaveLAN cards are installed, selects the card
with VO Base Address nnnn.
NOTE
I0 Base Addresses are displayed when you start the

utility in interactive mode.

Example:

ndipxdos

-b -fc:\diag\counters -a

This command will run the Node Diagnostics utility in batch mode and append the
counter values to file COUNTERS.CSV in directory \DIAG on drive c:. For further
information. refer to Section 7.4.

7.2

Node Diagnostics for the NetWare 0S/2 Requester
To install the Node Diagnostics utility for the NetWare OS/2 Requester, copy all the
files on the WaveL
AN software diskette into the directory NODEDIAG\NETWARE. This directory is located on an OS/2 workstation’s hard disk or on a network
server accessible from the workstation.

7-8

Wavel
AN PC-AT installation and Operation

You can run the Node Diagnostics utility interactively or in batch mode. In interac-

tive mode, the counters are displayed on the workstation’s screen. Upon exiting from
the program, you can choose to save the displayed data to a disk file. In batch mode,
the counters are written directly to adisk file without being displayed on the screen.
For information on how to run the Node Diagnostics utility in batch mode, refer to
Section 7.2.2.

7.2.4

Counter information

To run the Node Diagnostics in interactive mode, change to the directory where the

Node Diagnostics utility files are stored, type ndipxos2, and press Enter at the OS/2
Full-Screen prompt. Figure 7-4 displays the diagnostic counters.

Figure 7-4:

Diagnostic Counters — NetWare 0S/2 Requester

Node Diagnostics Utility 08/2 V n.n

)

Monday August 26 1992 3.04 p.m.

Standard NetWare Counters

Wavel
AN Counters

Total Tx Requests
Tota! Rx Packets
No ECB Available
Packet Tx Too Big
Packet Tx Too Small
Packet Rx Overflow
Packet Rx Too Big
Packet Rx Too Smali

Deters
Board Misc. Errors
Own NWIDs
Other NWIDs
Low SNR
Good SNR
Excellent SNR

1125620
1125436
23
0
15

Packet Tx Misc. Error
Packet Rx Misc. Error

0
0

Retry Tx

Checksum Error
Hardware Rx Mismatch

[F1] - Help

163
0

Node Address

57833
0
1116432
8482
137
100423
15832

08000E200001

Sample 27

[F2] -~ Percentages

(F10] - Exit

LKG-7004-91!

The Node Diagnostics Utility

7-9

The screendisplay shows two sets of counters. On the left side of the screen, you can
see the standard set of NetWare driver-maintained counters. The four counters used
in network problem determination include:
Total Tx Requests

Total number of packets this workstation requested to transmit since network driver startup.

Total Rx Packets

Total number of packets successfully received by this
workstation since network driver startup.

Packet Rx too small

Number of times a packet received from the network was

smaller than the smallest size packet that can be trans-

mitted. Activity on this counter can indicate Signal Interference.

Checksum Error

Number of Cyclic Redundancy Check errors and alignment
errors that occurred while receiving packets. Activity on

this counter can indicate Signal Interference or collisions
occurring frequently.

The right side of the screen shows a set of counters specially maintained for WaveLAN cards. The following is a description of the counters that are used:
Defers

Total number of times a packet to be transmitted was

delayed by the WaveLLAN card to prevent a collision with a
packet from another station. Activity on this counter is related to the volume of traffic in the air.
Board Misc Error

Number of times the board was unable to transmit a packet
due to an unspecified board failure. This may indicate a
transient problem (for example, one that may not impact
performance to a significant degree). If the value of this
counter is regularly nonzero, you should consider replacing
the card.

Own NWIDs

Number of packets from the local WaveLAN that have been

detected by the board. This counter shows the total of all

packets detected, including those addressed to other stations
on this network.

7-10

WavelL
AN PC-AT Installation and Operation

Other

NWIDs

Number of packets from other WaveLANS or corrupted
packets that have been detected by the board. (Noise can
cause this counter to increment.)

SNR

Number of signal-to-noise ratio (SNR) samples that were
taken, per category, on incoming packets with own NWID.

Signal-to-Noise sampling takes place at the station at regular intervals (about 18 times per second) while the network
driver is running. All network traffic detected by this station is sampled. The resuit increments one of three counters

corresponding to Low, Good, and Excellent.
The utility uses these counters, along with the four NetWare counters already described, to provide a set of driver statistics that you can use to diagnose network
problems. To see the driver statistics, press F2 (Figure 7-5). The driver statistics are
summarized in Section 7.1.2.
Figure 7-5:

Driver Statistics - NetWare 0S/2 Requester

(Node Diagnostics Utility 0S/2 V n.n

Monday August26 1992 3.04 p.m.\

Driver Statistics
Successful Packets
Received Bad Packets

98.8 %
No Packets Received

Medium Busy

155%

Other NWID

258 %

Low SNR

3.0%

Good SNR

36.8%

Excellent SNR

60.2 %

[F1]) ~ Help

[ESC] - Previous Screen

‘/

LKG-7006-021

The Node Diagnostics Utility

7-11

7.2.2

Parameter Options for Batch Operation
By using parameter options on the OS/2 Full-Screen command line, you can run the
Node Diagnostics utility in batch mode. The screen display is suppressed and the

counters are saved directly to a specified disk file.
The batch mode of operation enables you to combine data collection and subsequent
processing in one OS/2 .CMD file that you can run at regular intervals (for example,
daily, before workstation shutdown). For information on saving the Diagnostic Data,
refer to Section 7.1.3.

Figure 7-6 shows how the counters are saved on disk.

Figure 7-6:

(

Saved Counter Set — NetWare 0S/2

“Node Address”,"08000E200001"
“Date”,082681992
“Hour”,15

“Minutes”,04

“Total Tx Requests”, 1125620

“Total Rx Packets”, 1125621
*No ECB Available”,23
“Packet Tx Too Big”,0
“Packet Tx Too Smali”,0
“Packet Rx OverflowTM,3
“Packet Rx Too Big",0

“Packet Rx Too SmailTM, 15
“Packet Tx Misc. Error,0
“Packet Rx Misc. Ermor",0
“Retry Tx".0

Checksum Error”, 163
“Hardware Bx Mismatch",0

“Deters”,57833
“Board Misc. Error”,0
“Own NWIDs", 1116432
*Other NWIDs",8482
“Low SNR",172
“Good SNR",50382
“*Excellent SNR",100423

¥ Successful Packets”,98.8
“% Received Bad Packets”,0.0
“¥% Medium Busy”,15.5

“% Other NWID",25.8
“¥% Low SNR",3.0
“oh Good SNR",36.8

“% Excellent SNR",60.2

j
LKG-7006-921

7-12

WavelLAN PC-AT Installation and Operation

The following parameter options are shown in uppercase for clarity. You can also use
lowercase characters.

-B

Selects batch mode. Full-screen display is suppressed. The
following parameter, the filename to save to, is required.

Fpath

Required parameter, parh is the full pathname, including
filename and extension, of the disk file to save the counter
values to. If an extension is not specified .CSV is used.

-A

Optional parameter, used with the —F parameter. Indicates
that data is to be appended to the file. If the file is new, this

parameter is ignored.

Cnnn

Optional parameter for both batch and interactive operation.
When more than one WaveLLAN card is installed in a work-

station, this parameter is used to select the card for which
driver diagnostic counters are to be displayed. nnn is the
card's VO Base Address. If this parameter is omitted,

counters are displayed for the last driver loaded.

Example:

ndipxos2 -b

-fc:\diag\hounters -a

This command will run the Node Diagnostics utility in batch mode and append the
counter values to file COUNTERS.CSV in directory \DIAG on drive c:.
Example:

ndipxos2

—3e0

This command will run the Node Diagnostics utility interactively and display the

diagnostic counters for the driver using the WaveLAN card at 'O Base Address
O03EOH. For further information, refer to Section 7.4.

7.3

Node Diagnostics for the NDIS Driver
You can install the NDIS Node Diagnostics utility on an MS-DOS workstation,

OS’2 workstation, or OS/2 server. For information on parameter options for batch
operation, refer to Section 7.3.4.

MS-DOS:

Copy

the

file

NDNDIDOS.EXE

from

Directory

File

Description

\(root)

AWVLAND1.0BJ
BWVLANO1.0BJ

NetWare Version 2.x Operating System driver
modules
(for servers, bridges, and routers) for:

CWVLANO01.0BJ

LANA,LANB, LANC, or LAN D

DWVLANO1.0BJ
\(root)

SWVLANO1.CBJ

NetWare Version 2.x Shell driver module (for
workstations)

\(root)

WVLANO1.LAN

NetWare Version 2 O.S. Driver Description File
for Version 2.15 Rev. C, and later versions

\(root)

WVLANO1.215

Copy of WVLANO1.LAN

\(root)

WVLANO1.21X

NetWare Version 2 0.S. Driver Description File
for Versions earlier than Version 2.15

\WNETWARE
. NW3

WVLANO3.LAN

NetWare Version 3 driver for Version 3.1x
(for servers)

\NETWARE.OS2

WVLANO4.SYS

Driver for use with NetWare Requester for 05/2

\NETWARE.DOS

WVLAND5.COM
DRIVER.LST

Netware DOS ODI Driver

Substitute drivers list file for NetWare Lite

If you are installing WaveLLAN in a NetWare 2.1x environment, refer to Section A.1.
If you are installing in a NetWare 2.2 environment, refer to Section A.5.
To install a NetWare Version 3 server, refer to Section A.6.
To install a WaveLAN driver with the NetWare Requester for OS/2, refer to Section
Al

To install the WaveLAN DOS ODI driver, refer to Section A.8.

NetWvare Version 2.1x Installation
The WaveL
AN software diskette has volume label: LAN_DRV_448. You can use

the hard disk or standard floppy disk methods of driver generation. If you are going
to use the hard disk method:

A-2

WavelLAN PC-AT Installation and Operation

Create a subdirectory of directory \NETWARE, called LAN_DRV_.448.

Copy all the files from the root directory of the WaveLAN diskette to the
newly created hard disk subdirectory.
NOTE
If you are running a NetWare version earlier than 2.15
Rev C, you should use the file WVLANO1.21X as the
driver description file. Use the DOS command:

copy wvlan01.21x wvlan0Ol.lan

to replace the driver description file in your working
copy of the installation diskette or LAN_DRV_.448
subdirectory of your hard disk (depending on dnver
generation method used).

A.2 Workstation Shell Driver Generation
To generate a workstation shell driver:

Use the Custom Shell Generation Level of SHGEN.

If using the standard floppy disk method, choose Load and Select Item from
the LAN Driver Options menu to load the driver file directly from the
Wavel.AN software diskette.

Use the Configure Driver/Resources vption to select the correct /O Base Address from the list of available configurations (refer to Table A-1).

NetWare Driver Installation

A-3

To install the workstation shell driver, you can either:
I

Create a workstation boot diskette, as described in the Novell documentation

or, if the workstation has a hard disk:
2.

Copy the Network Shell files created in the Shell Generation step directly to
the root directory on the workstation’s hard disk. You should copy the files
IPX.COM and the NetWare shell file (NET3.COM, NET4.COM,

NETS5.COM), which corresponds to the DOS version used on the workstation.

A.3 NetWare Operating System Generation
The following guidelines will help you to complete the operating system generation
procedure for a WaveL
AN card installed in a file server:
1.

Use the Default Configuration option of NETGEN.
If you are using the standard floppy disk generation method, you should select Load and Select Item from the LAN Driver Options menu to load the
WaveLLAN drivers from your installation software diskette.

Select the LAN driver object file appropriate to the network (A, B, C, D).
NETGEN will select a configuration from those listed in Table A-1.
NOTE
The I/0O Base Address switch settings on the WaveLAN
card must correspond to those selected here. If thereis a

conflict, you may have to redo some of the WaveLAN
installation steps.

A-4

WavelLAN PC-AT Instaliation and Operation

A.4 Generating and Installing an External Bridge
If you are installing the WaveLLAN card in an external bridge, the following guidelines will help you to complete the bridge generation procedure:
l.

Use the Default Configuration option of BRGEN.

If you are running BRGEN from floppy disks, you should select Load and
Select ltem from the LAN Driver Options menu to load the WaveLAN driv-

ers from your installation software diskette.
BRGEN will select a configuration from those listed in Table A-1.
NOTE

The I/ Base Address switch settings on the WaveLAN

card must correspond to the address sclected here. If
there 1s a conflict, you may have to redo some of the
WavelLAN installation steps.

A.5 NetWare Version 2.2 installation
A.5.1

Workstation Shell Driver Generation

To generate a DOS workstation shell driver:
1.

Run WSGEN.

When asked to select a LAN driver, press INSERT. Insert the WaveLAN software diskette in a floppy disk drive and press ENTER. Follow the screen

prompts to select the WaveLAN driver.

When prompted, select the correct I’O Base Address from the list of available

configurations (refer to Table A-1). The configuration you select should
match the selection you made when you installed the WaveLAN card.

Complete the shell generation and workstation installation procedure as described in the Novell documentation.

NetWare Driver installation

A-5

Router Driver Generation

A.5.2

To generate a router driver:
1.

Run ROUTEGEN.

When asked to select a LAN driver, press INSERT. Insert the WaveLLAN soft
ware dishette in a floppy disk drive and press ENTER. Follow the screen

prompts to select the WaveLAN driver. Select the LAN driver object file ap-

propriate to the network (A, B, C, D).
When prompted, select the correct /O Base Address from the list of available
configurations (refer to Table A-1). The configuration you select should
match the selections you made when you installed the WaveLAN card.
NOTE
An asterisk (*) indicates that the configuration option
conflicts with other hardware configurations selected.
If there 1s a conflict, you may have to redo some of the
WaveLAN installation steps.

Complete the router generation and installation procedure as described in the
Novell documentation.
A.5.3

File Server Installation
1.

Run the INSTALL utility. Select Advanced Installation and follow the screen

prompts until you see the Operating System Generation screen.
For the network in which the WaveLAN card will run (A, B, C, or D), highlight the network board Driver field, and press [INSERT]. Insert the WaveLAN software diskette in a floppy disk drive and press [ENTER]. Follow the

screen prompts to select the WaveL
AN driver from the list of available drivers.

When prompted, select the correct /O Base Address from the list of available
configurations (refer to Table A-1). The configuration you select should
match the selections you made when you installed and configured the WaveLAN card.

A-B

Wavel
AN PC-AT Installation and Operation

NOTE

An asterisk (*) indicates that the configuration option
conflicts with other hardware configurations selected.
If there is a conflict, you may have to redo some of the
AN installation steps.
WaveL

Complete the file server generation and installation procedure as described in
the Novell documentation.

NetWare Version 3.1x Server Installation

A.6

The WaveLAN driver for NetWare Version 3 is configured at run time. You can load
and configure the driver when the server is running, or you can have the driver automatically loaded at server startup.

Install the server in the normal way, using the NetWare INSTALL utility.
A.6.1

Autoloading the NetWare Version 3 File Server Driver
If you want the driver loaded automatically each time the server comes up, you

should edit the AUTOEXEC.NCF file, using the NetWare INSTALL utility:
1.

Copy file WVLANO3.LAN from directory \WETWARE.NW3 on your working copy of the WaveLAN software diskette to a directory on the file server.

Load the INSTALL utility.

Select EDIT AUTOEXEC.NCF from the SYSTEM OPTIONS menu.

NetWare Driver Installation

A-7

Add the following 2 lines to AUTOEXEC.NCF:
load <PATH> wvlan03 port=<portnr>

bind ipx to wvlan03 [port=<portnr>] net=<netnr>
where:
<path>

The server directory to which the WaveL
AN driver was

copied.
<portnr>

The /O Base Address of the WaveL
AN card to link the

driver to. In the bind command line only specify the port
parameter (including “[]") if more than one WaveL
AN card

has been installed.
<netnr>

Identifies a unique (Novell) network number for the net-

work this card will be associated with.
Example of an AUTOEXEC.NCF file:
file server name NET3
ipx internal net 311C
load c:\wvlan03 port=390

bind wvlan03 net=1001
5.

If more than one WaveL
AN card is installed, repeat step 4 for the remaining

cards.
6.

Exit from the INSTALL utility and restart the server to load the WaveLAN

driver(s).
A.6.2

Loading the WaveLAN NetWare Version 3 Driver Manuaily

If you have not included the WaveLAN driver in AUTOEXEC.NCF, you can load
the driver manually while the server is running:
Place the working copy of the WaveLAN diskette in drive A.
2.

At the prompt, type the following command line:

load a:\wvlan03
The system will prompt you to enter a port number.

A-8

Wavel
AN PC-AT Installation and Operation

Bind the driver to an installed card. Type the following command line:

bind ipx to wvlan03
The system will prompt you to enter a network number. If more than one
WaveL
AN card is installed or the driver has been loaded twice, the system
will prompt you for the port number of the card to bind the driver to.

When the WaveLAN driver is successfully loaded, it displays the message:
Digital Equipment Corporation WaveLAN AT Vn.nn (yymmdd)

Vn.nn

the driver's version number

yymmdd

the driver’s creation date in year, month, day format

A.7

NetWare Requester for 0S/2
To install the Wave LAN driver for use with NetWare Requester for OS/2, proceed as
follows:
1.

Install the NetWare Requester for OS/2.

Install the NetWare Requester on an OS/2 workstation in the standard manner. Note the directory to which the standard driver files are copied. This is
usually C:\NETWARE\DRIVER. During the installation process, you must

select a LAN driver. Select the driver NE2000. On exiting the INSTALL util-

)

ity, do not select the REBOOT option.
Copy the WaveLAN driver to the driver directory.
Insert the working copy of the WaveLLAN diskette in drive A:. Copy the Wa-

veLAN driver WVLANO4.SYS to the directory to which the standard driver
files were copied in step 1. For example:

copy a:\netware.os2\wvlan(4.sys c:\netware\driver

NetWare Driver Installation

A-9

Edit the CONFIG.SYS file.

Use the OS/2 editor to edit the LAN driver definitions in CONFIG.SYS.
Change the DEVICE definition line for the driver NE2000.SYS to indicate
the WaveLLAN driver. For example, if you have copied the WaveLAN driver
to the same directory as the standard drivers, then change the LAN driver

section of CONFIG.SYS.
device=c:\netware\driver\ne2000.sys
to

device=c:\netware\driver\wvlan(04.sys
4.

Optionally, create a NET.CFG file.

The default /O Base Address (Port address) is 0300H. If you have installed
the WaveLLAN card to use a different 'O Base Address, or if you have installed more than one WaveLAN card in the workstation, you will need to
create or update a NET.CFG file. The NET.CFG file must contain LINK
Driver statements and should be placed in the workstation's root directory.
The WavelLAN card is installed at address 03EOH. The NET.CFG file should con-

tain the following lines:
Link Driver WVLANO4
Port 3e0
Two WaveLLAN cards are installed, at addresses 0300H and 0390H. The NET.CFG
file should contain the following lines:
Link Driver WVLANO4 (first card)

Link Driver WVLANO4 (second card)
Port 360
5.

Reboot the OS/2 workstation.
When the WaveL
AN driver is successfully loaded., it displays the message:

Digital Equipment Corporation WaveLAN AT Vn.nn (yymmdd)
where:

A-10

Vn.nn

the driver’s version number

yymmdd

the driver’s creation date in year, month, day format

WavelL
AN PC-AT Installation and Operation

Installing the DOS ODI Driver

A.8

To install the WaveLAN driver for use in a NetWare DOS ODI workstation, proceed
as follows:

Copy the WaveLAN driver to the root directory.

Insert the working copy of the WaveLLAN diskette in drive A:. Copy the
WavelLAN driver WVLANO05.COM to the workstation's root directory.

Example command:

copy a:\netware.dos\wvlan05.com c¢:\
2.

Copy the NetWare DCS ODI support files to the root directory. Insert the

NetWare WSGEN diskette in drive A:. Copy a NetWare shell file to the
workstation's root directory. Suitable files are:
NET3.COM

for MS-DOS Version 3.x

NET4.COM

for MS-DOS Version 4.x

NET5.COM

for MS-DOS Version 5.0

NETX.COM

for all the above MS-DOS versions

From the \DOSODI subdirectory of the WSGEN diskette, copy the following
files:

LSL.COM

(Link Support Layer)

IPXODIL.COM

(IPX Protocol Stack file)
NOTE

For some NetWare versions, these files are provided on
aseparate DOS ODI WORKSTATION SERVICES diskette.

NetWare Dniver installation

A-11

Edit the AUTOEXEC.BAT file.
Edit the workstation's AUTOEXEC.BAT file to include the following lines in
the order shown here:
LSL
WVLANOS

IPXODI

NETS

(example)

Optionally, create a NET.CFG file.

The default O Base Address (Port address) is 0300H. If you have installed
the WaveL
AN card to use a different O Base Address, or if you have installed more than one WavelLAN card in the workstation, you will need to
create or update a NET.CFG file. The NET.CFG file must contain LINK
Driver statements and should be placed in the workstation’s root directory.
The WaveL
AN card is installed at address 03EOH and uses the Ethernet_II (DIX)
frame format. The NET.CFG file should contain the following lines:

Link Driver WVLANO5
Port 3e(

Frame Ethemet_II

Two WaveL
AN cards are installed, at addresses 6300H and 0390H. The NET.CFG
file should contain the following lines:

Link Driver WVLANOS (first card)
Link Driver WVLANOS (second card)
Port 390

In addition, the AUTOEXEC.BAT file must contain two occurrences of the driver
filename:
LSL
WVLANO5
WVLANOS

IPXODI

A-12

WaveLAN PC-AT Installation and Operation

NetWare Lite Instaliation

A.9

To install NetWare Lite with the WaveLAN DOS ODI driver, do the following:
1.

Use the DOS DISKCOPY command to make a backup copy of your NetWare

Lite installation diskette.

Copy the WaveLAN files:
DRIVER.LST
WVLANOS.COM

from directory \NETWARE.DOS on the WaveLAN software diskette to the
backup NetWare Lite Installation diskette. (Note: DRIVER.LST replaces an
existing file of the same name on the NetWare Lite disk.)
Install NetWare Lite using the backup installation diskette.

A.10 Checking Your NetWare Instaliation
Run the NetWare COMCHECK utility to verify thot your newly installed WaveLAN

network stations can communicate with each other.

Use the WaveL
AN Diagnostic utilities, described in this manual, to optimize antenna positioning. and to troubleshoot environmental or operational problems.

NetWare Driver Installation

A-13

B
NDIS Driver Installation

B.1

Introduction
The Network Driver Interface Specification (NDIS) was issued by 3Com® and
Microsoft Corporation as a standard for the development of network drivers and
communication protocols. Many network operating environments provide NDIS
support.

This chapter describes the steps typically required to install the WaveLAN NDIS
driver in NDIS-compatible network environments, and provides examples for the
following environments:

PATHWORKSTM for DOS (DECnetTM) (Digital Equipment Corporation)

PATHWORKS for DOS (TCP/IP) (Digital Equipment Corporation)

PC/TCPTM, LAN Watch (FTP Software, Inc.)

St LAN(NCR®)

(S/2 LAN Server (1BM Corporation)

3+Open (3Com)

| AN Manager (Microsoft and NCR)

B.2 NDIS Driver Installation General Infornation
In the LAN Manager environment, the NDIS driver installation is done by using the
L.AN Manager Setup program. The installation default values are modified manually.

In non-LAN Manager environments, the installation of the NDIS driver depends on
the way the software thatuses the NDIS driver is installed. In general, you must complete the following four steps:
1.

Install the driver software.

Edit the CONFIG.SYS file.

Edit the PROTOCOL.INI file.

Edit AUTOEXEC.BAT.

As aresult, the following lines will be added or changed in the various system files.
B.2.1

The CONFIG.SYS File

The CONFIG.SYS file should contain at least the following lines:
DEVICE=<ppath><protocol_manager> (/l.<ppath>)
DEVICE=<dpath><wavelan_driver>
DEVICE=<ppath><protocol_stack_file>
where:

<ppath> is the drive and directory containing the protocol files.
<dpath> is the drive and directory containing the WaveL
AN driver.
<protocol_manager> is the protoco! manager filename.

<protocol_stack_file> is the protocol stack filename.

<wavelan driver> is the name of the WaveLLAN driver file (OWVLANO02.0S2 for
0S8/2 or DWVLANO2.DOS for DOS).

B-2

AN PC-AT Installation and Operation
WavelL

B.2.2 The PROTOCOL.INI File

During the WaveLAN driver installation, three parameters are added to the file
PROTOCOL.INIL

DriverName

= WVLAN$

I0Base
ACR

= 0x300
=6

In PC-AT systems, change the value of IOBase to the /O Base Address used when
configuring the card.

The PROTOCOL.INI file should contain at least the following lines:
[PROTOCOL MANAGER]

DriverName = PROTMAN$
{<protocol_stack>]

DriverName = <protocol_stack_name>
/Bindings = “WAVELAN"
[WAVELAN}

; Protocol.ini entry for the WaveLAN Communications Adapter.
DriverName
= WVLANS$
10Base
ACR

= 0x300
=06
NOTE

Lines starting with a semicolon are comment lines. These lines are ignored
by the Protocol Manager.

The term WAVELAN may be replaced by another name, as long as the name
between the quotes is exactly the same as the name between square brackets
in the line immediately following.

NDIS Driver Installation

B-3

B.2.3 The AUTOEXEC.BAT File
The AUTOEXEC.BAT file (DOS systems only) should contain at least the following statement:
<bpath>NETBIND
where:

<bpath> is the drive and directory where NETBIND
. EXE resides, for example,

CALANMAN.DOS\DRIVERS\PROTMAN for LAN Manager.
B.2.4

Driver Initialization

After a successful installation, the driver displays the following message at startup:
Digital Equipment Corporation WaveLAN AT NDIS driver Vn.nn

B.3 PATHWORKS FOR DOS (DECnet)
Before irstalling PATHWORKS for DOS (DECnet), you need the following informatior :

Node name of the PC (Format: xxxxxx)

Node address of the PC (Format: nn.nnn)

Node name of the File Server (Format: Xxxxxx)

Node address of the File Server (Format: nn.nnn)

Select other NDIS driver when prompted by the PATHWORKS installation
procedure

Driver Location:

(A: \MSLANMAN.DOS\DRIVERS\WAVELAN\DWVLANO02.DOS)
e

PROTOCOL.INI STUB File (A: \MSLANMAN.DOS\DRIVERS\WAVELANV)

B-4

WavelLAN card 10 Base Address

WavelLAN PC-AT Installation and Operation

Refer to the PATHWORKS for DOS Client Installation and Configuration Guide
with Diskettes for information on installing PATHWORKS for DCS (DECnet). The

PATHWORKS installation will modify the following files:
e

CONFIG.SYS

PROTOCOL.INI

AUTOEXEC.BAT
NOTE
If your WaveLAN IO address is other than the

defaul. of 300H you will need to edit the
PROTOCOL.INI file when prompted by the
PATHWORKS installation procedure.

B.3.1

The CONFIG.SYS File
The CONFIG.SYS file should contain at least the following lines:
device=\decnet\himem.sys
shell="command.com /P /e:526

DEVICE=\DECNET\PROTMAN.SYS /I.C.\DECNET
DEVICE=\DECNET\DWVLANO02.DOS
lastd ive=z
B.3.2

The PROTOCOL.INI Flie

The PROTOCOL.INI file should contain at least the following lines:
[protocol manager]

DRIVERNAME = PROTMAN$
[IPX4MAC]

DRIVER = IPX$MAC
BINDINGS

=DWVLANO02.DOS

NDIS Driver Installation

B-5

DATALINK]

DRIVERNAME = DLLSMAC
LG_BUFFERS

=16

SM_BUFFERS

OUTSTANDING =32
HEURISTICS

BINDINGS

=DWVLANO2.DOS

Specify IRQ level used by workstations network adapter
NILIRQ

[DWVLANO2.DOS]

: Protocol.ini entry for the WaveLAN Communications Adapter.

B.3.3

DriverName

= WVLANS$

I0Base

= 0x3e0

ACR

The AUTOEXEC.BAT File
The AUTOEXEC.BAT file should contain the following statement to start the network:

call \DECNET\STARTNET

B.4 PATHWORKS FOR DOS (TCP/IP)
Before installing PATHWORKS for DOS (TCP/IP), you need the following in-

formation:

B-6

Node name of the PC (TESTI is used in this example.)

Node 1P address of the PC (192.20.1.2 is used in this example.)

Node name of the File Server (FILES] is used in this example.)

Node IP address of the File Server (192.20.1.1 is used in this example.)

Domain name of the IP network (XYZ.ABC.COM is used in this example.)

Subnet mask of the network (255.255.255.0 is used in this example.)

Name server address (192.20.1.3 is used in this example )

WavelLAN PC-AT installation and Operation

Default gateway address (192.20.1.4 is used in this example.)

Select other NDIS driver when prompted by the PATHWORKS installation
procedure.

Driver Location:

(A \MSLANMAN.DOS\DRIVERS\WAVELAN\DWVLANO02.DOS)

PROTOCOL.INI STUB File (A: \MSLANMAN.DOS\DRIVERS\WAVELAN\)
WaveL
AN card 10 Base Address

Refer to the PATHWORKS for DOS Client Installation and Configuration Guide
with Diskettes for information on installing PATHWORKS for DOS (TCP/IP). The
PATHWORKS installation will modify the following files:
e

CONFIG.SYS

PROTOCOL.INI

AUTOEXEC BAT

NOTE

If your WaveLAN 10 address is other than the default of
300, you will need to edit the PROTOCOL.INI file
when prompied by the PATHWORKS installation procedure.

B.4.1

The CONFIG.SYS File

The CONFIG.SYS file should contain at least the following lines:
shell=\command.com /P /e:526
DEVICE=\tcpipnemm.dos

DEVICE=\tcpip\PROTMAN.SYS /I:C:\TCPIP

DEVICE=\cpip\DWVLANO02.DOS
DEVICE=\tcpip\tcpdrv.dos /1:C: \tcpip
lastdrive=z
device=\(cpipshimem.sys

NDIS Driver Installation

B-7

B.4.2 The PROTOCOL.INI File

The PROTOCOL.INI file should contain at least the following lines:
PROTOCOL INI file created by TCPIPOMO.V41 V1.1.026
via TCPIPWIK.V41 V2.0.012
A

oo o

ok o AR

o ok ke ke o o s sk ok oK s a3k ok ke ok ok e ok ol oK o ak Ak o ok ok ok ok ok e 3K s ok oK Ak ak ok ok K ol Ak ok ke Ak ok o ok g ok K

ok
1]

Protocol Manager Initialization File Template

o o ok o

ok ook oK

ok o ok ok ok 3k S 3 ok sk ok ok oK 3k 3 st ok 3ok

o ke 3 o b sk ok ok ok ok ak sk sk ok ok ok sk ok Sk ok ok 3k ok ok ok ok 3k ok

[PROTOCOL MANAGER]

DRIVERNAME = PROTMAN}$
< ok ok e ok ok ok ok ok ok ke k sk sk ok ok ok ok ok ok ok o ok ok ok ok ok ok ok
A

PROTOCOLS

« % ok e sk ok dk ok ok ok s Ak ook Ak ok

ok Kok R 3 ok sk Nk 3k ok Sk ok

: DLC Protocol
[DLC])
DRIVERNAME = MDLC$%
BINDINGS =

. TCP Protecol Drivers
[TCPLITE]
DRIVERNAME = TCPLITE$
BINDINGS = DWVLANO02.DOS
SNAP = NO

IPADDRESS =1922012
IPSUBNET.MASK = 2552552550

IPGATEWAYO = 1922014
DEFAULTS = LIGHT-USER

B-8

Wavel
AN PC-AT Installation and Operation

TCP.WINDOW = 2

UDP.BCAST.ZERO = NO
{TCPGLOBAL]

HOSTNAME = "test1”

NETFILES = "c:\icpip”
[DNR]

DRIVERNAME = DNR$
BINDINGS = TCPLITE
NAMESERVERO = 19220 1.3

DOMAIN = "xyz.abc.com”
[NMDRV]

DRIVERNAME = NMDRV$
BINDINGS = TCPLITE

SYSTEMDESC = "PATHWORKS for DOS (TCP/IP) V2.0"
[SOCKETS]

DRIVERNAME = SOCKETS$
BINDINGS = TCPLITE

MAXSENDSIZE = 102
POOLSIZE = 10000
NUMSOCKETS = 32
NUMTHREADS = 32
{(IPX4MAC]

DRIVER =1PX$MAC
BINDINGS = DWVLANO02.DOS
[TELNET]

DRIVERNAME = TELNET}
BINDINGS = TCPLITE
NSESSIONS =4

MAX_OUT_SENDS =3
MAX_SEND_SIZE = 128
DRIVER_EOL = 1
APP_EOL = 1

NDIS Driver instaliation

B-9

REDIREC_COM = |

ECH_CHAR = """
BRK_ACTION =3
MUI_PROMPT = "MUI> "
[TINYRFC]

DRIVERNAME = TINYRFC$
BINDINGS = TCPLITE
NUMNAMES = 6

NUMSESSIONS = 8

. BCASTADDR =
INTERNETNAMES = 4
~ o

ok ok

ok 3k R Sl e Sk 3k ok o sk Sk ok ok ok ok ok ok ok oK e Sk sk sk R ok

ADAPTERS

<%k

*
*

s sk ok Aok ok ok ok ok ok ke ok ok A oK ok ok ok ok ok e ok ok e ok ke ok 3 ok o o ok ok

(DWVLANO2.DOS]
» Protocol.ini entry for the WaveLAN Communications Adapter.

B.4.3

DriverName

= WVLANS$

IOBase

= 0x300

ACR

The AUTOEXEC.BAT File
The AUTOEXEC.BAT file should contain the following statement to start the network:

cali\TCPIPM\STARTNET

B.5 TCP/IP and LAN Watch Installation
B.5.1

Instali the Driver Software

Install the TCP/IP generic Ethernet software.

B-10

Wavel
AN PC-AT Installation and Operation

Copy the NDIS driver from the\MSLANMAN.DOS\DRIVERS\WAVELAN direcAN disk to the \LANMAN directory.
tory on the WaveL
B.5.2 The CONFIG.SYS File

The CONFIG.SYS file should contain at least the following lines:
DEVICE=C:\LANMAN\PROTMAN.SYS
DEVICE=C: LANMANDWVLANO02.DOS
DEVICE=CA\LANWATCH\DIS_PKT.GUP
DEVICE=CNLANWATCH\NFCUST.SYS
DEVICE=C:\LANWATCHANPCUST.SYS
B.5.3

The PROTOCOL.INI File

The PROTOCOL.INI file should contain at least the following lines:
[PROTOCOL MANAGER]

DRIVERNAME = PROTMAN$
{PKTDRV]

DRIVERNAME = PKTDRV$
BINDINGS ="DWVLANO2_NIF"
INTVEC = 0X65

CHAINVEC = 0X66
[DWVLANO2_NIF]

. Protocol.ini entry for the WaveLAN Communications Adapter.
DriverName

B.5.4

10Base

= WVLAN$
= 0x300

ACR

The AUTOEXEC.BAT File

The AUTOEXEC.BAT file should contain at least the following lines:
SET PATH=C:\LANWATCH;CA\LANMAN
NETBIND

NDIS Driver installation

B-11

B.6 StarLAN Instaliation
B.6.1

Install the Driver Software
Install StarLAN.

Copy the NDIS driver from the \MSLANMAN.DOS\DRIVERS\WAVELAN directory on the WaveL
AN disk to the \STARLAN directory.
B.6.2 The CONFIG.SYS File

The CONFIG.SYS file should contain at least the following lines:
DEVICE=C\STARLAN\PROTMAN.DOS/i:CA\STARLAN
REM DEVICE=C\STARLAN\SLAN.DOS
DEVICE=C\STARLAN\DWVLANO02.DOS
DEVICE=CASTARLANWETBEUIL.DOS
REM DEVICE=C\STARLAN\SLIM.DOS
B.6.3

The PROTOCOL.INI File

The PROTOCOL.INI file should contain at least the following lines:
: PROTOCOL.INI file for NETBEUI and the
: NCR AT StarlLAN adapter
[protocol manager]

drivername = PROTMAN$
|netbeui_xif)

drivername = NETBEUI$
bindings = wavelan

(... Non WaveL
AN specific lines . . .)
[wavelan]

:Protocol.ini entry for the WaveLAN Communications Adapter.

B8-12

DriverName

= WVLANS

10Base

= 0x300

ACR

Wavel
AN PC-AT Installation and Operation

B.6.4 The AUTOEXEC.BAT File

The AUTOEXEC.BAT file should contain at least the following line:
C:STARLANWNETBIND

B.7 IBM OS/2 LAN Server
To install the Wave LAN driver in LAN Server, you should first install adriver for an

IBM-supported ETHERAND network adapter, and then replace that driver software
and PROTOCOL.INI file by the respective WaveLAN files. The network card used
for this purpose is the Western Digital card because its characteristics, from an installation viewpoint, are closest to the WaveLAN card.
NOTE

If youare installing WaveLAN inanexisting configuration where the selected adapter is not the Western Digital card (but, for instance, a Token Ring card), then you
must remove LAN Requester from your systemanddoa

complete reinstallation. This is necessary to ensure that

CONFIG.SYS and PROTOCOL.INI are correctly set
up.

B.7.1

Installing 0S/2 1.3 EE (Including Requester)
In the Basic Configuration Services Main menu, choose the LAN Services, and select the Western Digital adapter, Universal Address.

In the Communication Manager, Advanced Configuration function, LAN Features

selection, Western Digital selection, and IEEE 802.2 selection, make sure that the
802.3 protocol and Universal Address are installed.

Copy the NDIS Driver from the WaveLAN disk to CACMLIB. The driver is
OWVLANO02.0S82 in directory:. \MSLANMAN OS2\DRIVERS\WAVELAN.

NDIS Driver Installation

B-13

B.7.2

The CONFIG.SYS File

In the following example, note the REM statement which shows the Western Digital
drive used during the initial installation. Also, note the CFG=C:\CMLIB\ETHERNET.CFG parameter in some of the statements. ETHERNET.CFG is the user-defined name of the configuration file generated during the Communication
Manager/LAN Features installation process.

CONFIG.SYS should contain at least the following lines:
DEVICE=C\CMLIB\LANDD.SYS
DEVICE=C\CMLIB\PROTMAN.OS2/I.C\CMLIB
REM DEVICE=C\CMLIBWMACWD.0S2
DEVICE=C\CMLIB\OWVLANO02.0S82
DEVICE=C\CMLIB\ETHERDD.SYS . .
.. CFG=C\CMLIB\ETHERNET.CFG
RUN=CA\CMLIB\ACSEPSYS.EXE

RUN=CA\CMLIB\NETBIND.EXE
DEVICE=C:\CMLIBWETBDD.SYS ..
..CFG=C:\CMLIB\ETHERNET.CFG
DEVICE=CNIBMLANWETPROG\RDRHELP.SYS

IFS=CNBMLANWETPROG\NETWKSTA.SYS ..
/I.CNBMLAN

B.7.3

The PROTOCOL.INI File

In the following example, the lines before END OF FILE have been copied from the
the original PROTOCOL.IN! file generated by the LAN Requester installation.
Nonapplicable lines have been removed.
The lines after END OF FILE have been copied from the PROTOCOL.INI file in

directory \MSLANMAN.DOS\DRIVERS\WAVEL
AN on the WaveLAN software
diskette.

Use an editor to change the BINDINGS statement and to add the *“[WAVELAN]”
line.

B-14

Wavel
AN PC-AT Installation and Operation

Edit PROTOCOL.INI to contain the following lines:
;
Protocol Manager Definition
[PROTOCOL_MANAGER]
DriverName = PROTMANS$
;

IBM ETHERAND Protocol Definition

[ETHERAND]

DriverName =OS2EE$
Bindings = WAVELAN
J¥#%% END OF FILE *#***
[WAVELAN]

;

.Protocol.ini entry for the WaveLAN Communications Adapter.

B.8

DriverName

=WVLANS

IOBase

= 0x300

ACR

=06

IBM DOS LAN Requester Version 1.2
The installation of the DOS Requester consists of two parts:
e

[nstailation of the PC LAN Support program, which creates the basic LAN
software environment to access the WaveLAN adapter. This is a prerequisite
for installing the actual DOS Requester. Follow the instructions as described
in the LAN Support Program User’s Guide to generate the environment for

the Western Digital adapter.
e

B.8.1

Installation of the DOS Requester.

PC LAN Support Program Installation
To install the PC LAN Support program, do the following:
1.

Install the driver software.

Edit the CONFIG.SYS file.

Edit the PROTOCOL.INI file.

Edit

AUTOEXEC BAT.

NDIS Driver installation

B-15

B.8.1.1

The CONFIG.SYS File

Replace the DEVICE=\MACWD.DOS line by DEVICE=\DWVLANO02.DOS. In the
following example, note the REM statement which shows the Western Digital driver

that was used during the initial installation. Note that the parameters behind the device
drivers in the other lines may not be mentioned in the User’s Guide but must be there to
make the system run.
Detailed infcrmation on the parameters can be found in the DXMINFO.DOC file on
the PC LAN support diskette.

The CONFIG.SYS file should contain ai least the following lines:

DEVICE=\LANMAN\PROTMAN
EXE
DEVICE=\DWVLANO2.DOS
REM

DEVICE=\MACWD.DOS

DEVICE=\DXMAOMOD.SYE 001
DEVICE=\DXMEOMOD.SYS
DEVICE=\DXMTOMOD.SYS E O=N
B.8.1.2

The PROTOCOL.IN! File

In the following example, the lines before END OF FILE have been copied from the
the original PROTOCOL.INI file generated by the LAN Requester installation.
Nonapplicable lines have been removed.

The lines after END OF FILE have been copied from the PROTOCOL.IMNI file in
directory MSLANMAN.DOS\DRIVERS\WAVELAN on the WaveL
AN scftware

diskette.
Use an editor to change the BINDINGS = statement and to add the [ WAVELAN]
line.

B-16

Wavel
AM PC-AT Installation and Operation

The PROTOCOL.INI file should contain at least the following lines:

— Protocol Manager Definition ———
s ——
{PROTOCOL_MANAGER]}

DriverName = PROTMAN$

V-

-— 1BM ETHERAND Protocol Definition

{ETHERAND]

DriverName =DXMEOQO$%
Bindings = STATEMENT
BINDINGS=WAVELAN
J¥**% END OF FILE ****
{WAVELAN] ;

:Protocol.ini entry for the WaveLAN Communications Adapter.

B.8.1.3

DriverName

= WVLANS

10Base

= 0x300

ACR

The AUTOEXEC.BAT File

If needed, edit AUTOEXEC.BAT to contain the following lines:
SET COMSPEC=C:\DOS\COMMAND.COM

PROMPT $psg
NETBIND

B.8.2

DOS Requester Installation
Follow the instructions as described in the Operating System/2 Local Area Network

Server Version 1.3 DOS Requester User’s Guide. Make backup copies of the CONFIG.SYS, AUTOEXEC.BAT, and any existing PROTOCOL.INI file.

B.8.2.1

The CONFIG.SYS File

In this example, note that DOSL
AN is the default name used by the DOS Requester.
SYSTEM and LANMAN were user-selected during installation. Also, note the pa-

rameters behind DXMTOMOD.SYS. which are placed by the DOS Requester installation process. The O=N parameter has to be entered manually when the DOS
Requester installation process asks

if you agree

with the changes

to the

DXMTOMOD.SYS driver line.

NDIS Driver Installation

B-17

The CONFIG.SYS file should contain at least the following lines:

SHELL=C\COMMAN D.COM/E:2000/P
BUFFERS=20
FILES=20

DEVICE=C\DOSLAN\LANMAN\PROTMAN
EXE . .
NMAN
. ECA\DOSLAN\LA
DEVICE=C\DOSLAN\SYSTEM\DWVLANI02.DOS

REM
DEVICE=C:\DOSLAN\SYSTEM\MACWD.DOS
DEVICE=CA\DOSLAN\SYSTEM\DXMAOMOD.SYS001
DEVICE=C\DOSLAN\SYSTEM\DXMEOMOD.SYS
DEVIC E=C\DOSLAN\SYSTEM\DXMTOMOD.SYS. .
..8=12 C=14 ST=12 O=N
LASTDRIVE=Z
FCBS=16,8

B8.8.2.2

The PROTOCOL.INI File

The PROTOCOL.INI file is the same as the one for the PC LAN Support Program
(Section B.8.1.2).

B.8.2.3

The DOSLAN.INI or AUTOEXEC.BAT Files

The DOSLANL.INI file contains default parameters used by the NET START command.

You should change the value of the /WRK: parameter to set the Oplock flag off (=0):
Oid value:

/WRK:1111211012

New value:

/WRK:1111211002

Alternatively, you can override the default parameter value by editing the NET
START command in AUTOEXEC.BAT.
Edit AUTOEXEC.BAT to contain the following lines:
NET START RCV MCRQSTR WAVEDOM . .
.

B-18

/WRK: 1111211002

Wavel
AN PC-AT Installation and Operation

B.8.2.4

Notes for Users of MS-DOS Version 5.0:

MS--DOS 5.0 uses the SETVER command to return a DOS version number other
than 5.0to a program. This mechanism is enabled when DOS 5.0 is installed by put- ting the line DEVICE=<dospath>SETVER.EXE in the CONFIG.SYS file. This
line should be removed or “REM”ed to avoid problems when running the DOS LAN
Requester software.

The driver software can be loaded into Upper Memory as shown in the following
example of the CONFIG.SYS file.
The CONFIG.SYS file should contain at least the following lines:

REM

DEVICE=C\DOSSO\SETVER.EXE

DEVICE=C\DOSSOHIMEM.SYS
DEVICE=C:\DOSSO\EMM2386.EXE NOEMS
DOS=HIGH,UMB
FILES=20
STACKS=0,0

SHELL=C\COMMAND.COM /E:2000/P
BUFFERS=20

DEVICEHIGH=C\DOSLAN\LANMAN\PROTMAN.EXE . .

.. [LcADOSLAN\LANMAN

DEVICEHIGH=C\DOSLANSYSTEM\DWVLANO02.DOS
REM

DEVICE=C:\DOSLAN\SYSTEM\MACWD.DOS

DEVICEHIGH=C\DOSLAN\SYSTEM\DXMAOMOD.SYS
.. 001

DEVICEHIGH=C\DOSLAN\SYSTEM\DXMEOMOD
.SYS
DEVICEHIGH=C\DOSLAN\SYSTEM\DXMTOMOD
SYS
.. 5=12C=14S8T=12 O=N
LASTDRIVE=Z
FCBS=16.8

NDIS Driver Installation

B-19

3Com 3+Open installation

B.9

To install the WaveLAN driver in a 3Com 3+Open network, you should firstinstall a
driver for 3Com-supported ETHERNET network adapter, and then replace that
driver software and PROTOCOL.INI file by the respective WaveL
AN files. The network card used for this purpose is the Western Digital card because its characteristics, from an installation viewpoint, are closest to the WaveL
AN card.
The driver to use for DOS is DWVLANO02.DOS, which can be found on the

WaveLLAN disk in the directory: MSLANMAN.DOS\DRIVERS\WAVELAN.
The driver to use for 0S/2 is OWVLANO02.0S2, which can be found on the WaveLAN disk in the directory: \MSLANMAN.OS2\DRIVERS\WAVELAN.
Edit the system files in accordance with the general guidelines described in Section
B.2 in this appendix. A sample PROTOCOL.INI file can be found in both of the
above directories.

B.10

LAN Manager Installation

Use the LAN Manager SETUP utility to install the WaveLAN NDIS driverina LAN
Manager environment. The general installation procedure is described in the Microsoft LAN Manager Installation Guide. This appendix provides additional information specific to WaveLAN driver installation.

NOTE
The installation procedures for LAN Manager Versions

2.0and 2.1 are different. If you are installing LAN Manager Version 2.1, refer to Section B.10.2.

B.10.1 LAN Manager Version 2.0 Installation

B-20

Start the LAN Manager SETUP program, and select the Actions menu.

Insert your working copy of the WaveLAN diskette in a disk drive.

WavelL
AN PC-AT Installation and Operation

Choose Import from the Actions menu, and specify the WaveL
AN diskette’s
drive letter when asked. The Import Network Drivers dialog box is displayed.

Select the WaveLAN driver (use the Space key) and exit. The driver is copied
to directory \LANMAN\DRIVERS\WAVELAN (or \LANMAN.DOS\DRIVERS\WWAVEL AN on an MS-DOS workstation).

Choose View/Mudify from the Actions menu, and use the Network Drivers
dialog box to install the driver.

Choose Save from the Actions menu, to save the new driver installation.
NOTE

The WaveLAN driver uses standard protocols (for example: Netbeui).

B8.10.2 LAN Manager Version 2.1 Installation

Microsoft LAN Manager Version 2.1 is supplied with an earlier version of the WaveLAN driver.

Using the LAN Manager SETUP program, install LAN Manager and select
other driver.

Insert your working copy of the WaveLAN diskette in the disk drive when
prompted. The SETUP program finds the following drivers:

\e]

MSLANMAN.DOS\DRIVERS\WAVELAN\DWVLANO02.DOS
MSLANMAN.OSZ2\DRIVERS\WAVELAN\DWVLANO02.0S2
Continue with the installation as documented in your LAN Manager Installation manual.

NDIS Driver Installation

B-21

C
Microsoft Windows for Workgroups

C.1 Microsoft Windows for Workgroups Driver Installation
We have included an OEMSETUPINF file on our distribution diskette. Follow the
instructions given in the “Installing and Configuring Network-Adapter Drivers” in
the “Configuring Hardware” chapter of the Microsoft Windows for Workgroups
User's Guide.

D
Installation Worksheet

D.1 Installation Worksheet
The Installation Worksheet on the following page is designed to help you carry the
information you need through the various installation steps. It also serves as a hardcopy record of your installation, which will help you maintain your WaveLAN network or adapt it to meet changing requirements.

AN 915 PC-AT Installation and Configuration
WaveL
Installer

Station

Date

Hardware instaliation:

I/0 Base Address Switch settings (Switches 1 and 2):

[J
N

swi:off SW2: off Address: 0300H
on Address: 0390H
off

]

off Address: 03COH

on Address: 03E0H

Switches 3 and 4 are not used.

Security Feaiure installed:

D Yes D No

Configuration Instatlation:
Description:

Network 1D:

MAC Address Type: [] Universal

] Local

Local Address

Datalink Security:

[7] Enabled

|_! Disabled

Key

Configuration Install utility filename:

[ nstconeexe
interrupt Request Line (IRQ):

D-2

10 11

12 153 4 57

Wavel AN PC-AT installation and Operation

WaveL
AN 2400 PC-AT Installation and Configuration
Iinstaller

Station

Date
Hardware Installation:

I/0 Base Address Switch settings (Switches 1 and 2):

O
O

swioff sw2: off
off
on

Address: 0300H
Address: 0390H

off

Address: 03COH

Address: 03EOH

Remote Boot Address Switch Settings (switches 3 and 4):

swa:.off swa:

off

Address: Disabled

off

Address: C8000H

oft

Address: DOOOOH

Address: D8000H

Security Feature installed:

D Yes D No

Configuration Installation:
Description:

Network ID:

MAC Address Type: [ ] yniversal

D Local

Local Address

Datalink Security:

[] pisabled

[] Enabled
Key

Configuration Install utility filename:

[J INSTCONF.EXE
interrupt Request Line (IRQ):

Installation Worksheet

]

101112153457

Index

MAC Address Type, 4-1

Numbers
3Com 3+Open, installing, B-20

Network ID, 4-1

saving parameters, 4-7
setting parameters, 4-3
CONFIG.SYS file, B-2, B-5, B-7,

B-11, B-12, B-14, B-16, B-17

Anntena, placement of, 6-0

Antenna extension usage, illustration of,

Configuration Install utility
illustration of initial screen, 4-9

illustration of IRQ screen, 4-10

5-4

AUTOEXEC.BAT file, B-4, B-6. B-10,
B-11,B-13, B-17

illustration of Update screen, 4-11
messages, 8-5

Configuration Setup utility, messages,
8-2

Configuration utilities

Bridging in a dispersed network,
illustration of, 5-5

for configuring the NIC, 2-2
messages, 8—1

Conventions, of this manual, xviii
Counters
tor NDIS driver, 7--14

for NetWare OS/2 Requester, 7-9

Card configuration, 4-1

Node Diagnostic utility, 7-2

illustration of, 7-3

creating disk, 4-2
parameters, 4-1

datalink security, 4-2
Interrupt Request Line Number

(IRQ). 4-2
MAC Address, 4-1

D
Datalink Security parameter,
setting, 4-6

index~1

Diagnostic utilities, 5-7

Installing hardware

Node utility, 5-7

configuration, 4-7

Point-to-Point utility, 5-7

network inteiface card, 3-10

DISKETTE.TXT file. xix

Remote Boot ROM, 3-4

DOS ODI Driver, installing, A-11

iliustration of, 3-5
security feature, 3-2
illustration of 3-3

Installing netwo . operating systemr

Hardware configuration switches, 3-6

3Com 3+Open, B-20

checking N~{Ware installation, A-13

DOS ODi Driver, A-11
IBM DJS Requester Version 1.2,
B-15

IVO base address, switch settings, 3-8

IBM OS/2 LAN Server, B-13

IBM DOS LAN Requester Version 1.2

Lan Manager, B-20

AUTOEXEC.BAT file, B-17

Microsoft Windows for Workgroups

CONFIG.SYS file, B-16

driver, C-1

installing. B-15

NetWare driver, A-1

PC LAN support, B-15

NetWare external bridge, A-S

PROTOCOL.INI file, B-16

NetWare Lite, A-13

IBM DOS LAN Requester Version 1.3,

NetWare Requester for OS/2, A-9

CONFIG.SYS file, B-17

NetWare Version 2.1x, A-2

IBM OS2 LAN Server

NetWare Version 2.2, A-S

CONFIG.SYS file, B-14

NetWare Version 3.1x server, A-7

installing, B-13

PATHWORKS for DOS (DECnet),

PROTOCOL.INI file, B-14

B-4

Inserting the network interface card, il-

PATHWORKS for DOS (TCP/1P),

lustration of, 3-11

B-6

Install utility, A-6, A-7

Point-to-Point utility, 6-1

Instaliation

StarLAN, B-12

of the network drivers, 2-2
of the NIC, 2-1, 3-1
preparing for, 2-1
worksheet, 2-2

TCP/1P and LAN Watch, B-10

INSTCONF utility, 4-3
Interrupt Request Line Number (IRQ)

parameter, 4-2

Installation worksheet, 2- 2, D-1
WaveLAN 2400, D--3
WaveLAN 915, D-2

Wave LAN International NIC, D-3

LAN Manager, installing, B~20

WaveLAN North America NIC, D-2

LAN Manager Version 2.0, B-20

Index-2

LAN Manager Version 2.1, B-21

NetWare Version 2.1x, installing, A-2
NetWare Version 2.2
file server installation, A-6
installing, A-5

M
MAC Address parameter, 4-1

MAC Address Type parameter, 4-1
setting, 4-6

Messages, 8-1

Configuration Install utility, 8-5
Configuration Setup utility, 8-2
Node Diagiostic utility, 8-11

Point-to-Point Diagnostic utility, 8-16
Microsoft Windows for Workgroups
Driver, installing, C-1

router driver generation, A-6
shell driver generation, A-5
NetWare Version 3.1x

autoloading the file server driver, A-7

instaliing WaveLLAN driver, A-7
loading the WaveLAN driver
manually, A-8

Network configurations

connected by a wired backbone, 1-3
typical, 1-1
Network ID parameter, 4-1

setting, 4-6
Network interface card

handling, 3-2

NDIS driver

installing, B-1

Node Diagnostic utility, 7-13
NDIS driver installation

AU TOEXEC.BAT file, B4
CONFIG.SYS file, B-2
driver initialization, B—4

general infcrmation, £E-2
PROTOCOL.INI file, B-3
NetWare COMCHECK utility, A-13
NetWare external bridge
installing, A-5
generating, A-5

unpacking, 3-1
Network problems, determining, 5-5

NIC. See network interface card
Node Diagnostic utility, 7-1
for NDIS driver, 7-13

counter information, 7-14
diagnostic indicators, 7-16
illustration of counter information,
7-15

parameter options, 7-18

saving diagnostic data, 7-17
for Netware IPX/ODI, 7-2

counter information, 7-2

NetWare Lite, installing, A-13

driver statistics, 7-4

NetWare operating system generation,

parameter options, 7-7

A-4

NetWare OS/2 Requester. Node Diagnostic utility, 7-8
NetWare Requester for OS/2, installing
WaveLAN driver, A-9

saving data, 7-6
for NetWare OS/2 Requester, 7-8

counter information, 7-9
driver statistics, 7-11
illustration of counters, 7-9

Index-3

parameter options, 7-12

illustration of initial screen, 6-2

interpreting data, 7-19

installing, 6-1

messages, 8-11

link measurement data display, 6-5

illustration of, 6-5
messages, 8-16

(o)

monochrome display mode parameter

Omnidirectional antenna, 3-12
connecting, illustration of, 3-14
kit contents, 3—12
placement of, 3-14
illustration of, 3-15
support bracket, 3—16

Optimizing network performance, 5-2

option, 6-7
parameter options, 6-7

running, 6-2
Problem determination, 5--5

component failure, 5-5, 5-6
environment and operation, 5-5, 5-6
PROTOCOL.INI file, B-3, B-5, B-8,

B-11, B-12, B-14, B-16

Overview, of this manual, xviii

Radio-frequency networks, 5-1
Parameter options

for batch operation, 4-12
exampies of, 4-13
PATHWORKS for DOS (DECnet)

signal attenuation, 5-2
signal interference, 5-1

signal-to-noise, 5-2
Range of card, 1-9

AUTOEXEC.BAT file, B-6

closed office, 1-9

CONFIG.SYS file, B-5

open office, 1-9

installing, B—4

PROTOCOL.INI file, B-5
PATHWORKS for DOS (TCP/IP)

semi-open office, 1-9
README.TXT file, xix

Remote boot

AUTOEXEC.BAT file, B-10

base address, 3-7

CONFIG.SYS file, B-7

base address switch settings, 3-8

instailing, B-6

disabling, 3-7

PROTOCOL.INI file, B-8

setting base address, 3-8

Point-to-Point diagnostics, running, 6-1

Point-to-Point utility, 6-1
diagnostic link ID parameter option,
6-7

I'O base parameter option, 6-7

Index-4

Remote Boot ROM

disabling, 3-8
installing, 34

Remote Wireless Network Connect, use
for, 1-6

S
Security feature, installing, 3-2

SETCONF

utility, 4-3

illustration of opening screen, 4-4

illustration of Parameter Entry Screen,
4-5

Setting network configuration
parameters, 2-2

Setting switches, 3-8

Shell driver generation, A-3
StarLAN
AUTOEXEC.BAT file, B-13

CONFIG.SYS file, B-12
installation, B-12

installing driver software, B-12

PROTOCOL.INI file, B-12
Static electricity, warnings about, 3-10

Station placement, illustration of, 5-3

Switching, between networks, 4-13
examples of, 4-14

WaveLLAN

card specifications, 1-8
components, 1-4

configuration utilities, 1-6

diagnostic utilities, 1-6
introduction of, 1-1
network driver files, 1-6
WaveLAN 2400

configuration switches, 3-7
illustration of, 3-7
installation worksheet, D-3

range of card, 1-9

specifications, 1-8
WaveLAN 915

configuration switches, 3-6
illustration of, 3-6
installation worksheet, D-2
LED:s, 3-9

function of, 3-9
range of card, 1-9

specifications, 1-8
WaveLAN components, 1-4

antenna extension cable, 1-6
T

associated documentation, 1-6
illustration of, 1-5

TCP/IP and LAN Watch

network interface card, 14

AUTOEXEC.BAT file, B-11

omnidirectional antenna, 1-5

CONFIG.SYS file, B-11

optional, 1-6

installing, B~10

optional directional antenna, 1-6

PROTOCOL.INI file, B-11

optional Remote Boot ROM, 1-7

Testing the communications path, 2-2
Troubleshooting, 5-7
communication problems with the
server, 5-8

optional security feature, 1-6, 1-7
software diskette, 1-6
WaveL
AN driver

configuration options, A-1

poor network performance, 5-8

files for NDIS, B-1

poor station performance, 5-8

files for NetWare, A-2

index-5

WavelLAN International.

See also WaveLAN 2400
WaveLLAN International NIC, configura-

tion switches, 3-7

illustration of, 3-7
WaveLLAN North America NIC