WaveLAN/PCMCIA User's guide - web server

�� 

��

The product described in this book is a licensed product of Lucent 

Technologies Inc. --formerly the communications systems and technology 

units of AT&T. 

WaveLAN, WavePOINT and WaveMANAGER and WaveMONITOR are 

registered trademarks, or trademarks of Lucent Technologies. 

IBM and AT are registered trademarks of International Business Machines 

Corporation. 

Microsoft, Windows 95, Windows NT, MS-Word, and MS-DOS are 

registered trademarks or trademarks of Microsoft Corporation. 

Novell and Netware are registered trademarks of Novell, Inc. 

Velcro is a registered trademark of Velcro, Inc. 

Adobe and Adobe Acrobat is a registered trademark of Adobe Systems Inc. 

All other brand and product names are trademarks or registered trademarks 

of their respective holders. 

April, 1998 

It is the policy of Lucent Technologies to improve products as new 

technology, components, software, and firmware become available. Lucent 

Technologies, therefore, reserves the right to change specifications without 

prior notice. 

All features, functions, and operations described herein may not be marketed 

by Lucent Technologies in all parts of the world. In some instances, drawings 

are of equipment prototypes. Therefore, before using this document, consult 

your Lucent Technologies representative or Lucent Technologies office for 

information that is applicable and current. 

Copyright ©1998 Lucent Technologies 

All Rights Reserved

Chapter 1 Introduction 

Chapter 2 Hardware Installation 

Table of Contents 

About WaveLAN/PCMCIA . . . . . . . . . . . . . . . . 1-1 

Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 

Network Configurations . . . . . . . . . . . . . . . . . . . 1-5 

Connecting to Ad-Hoc Workgroups . . . . . 1-5 

Connecting to an Infrastructure . . . . . . . . 1-5 

Roaming Operation . . . . . . . . . . . . . . . . . . . 1-6 

WaveLAN/PCMCIA Features . . . . . . . . . . . . . . 1-8 

Power Management . . . . . . . . . . . . . . . . . . . 1-8 

Installing your WaveLAN Kit. . . . . . . . . . . . . . . 2-1 

Inserting the PC Card. . . . . . . . . . . . . . . . . . 2-1 

Mounting the Antenna Module . . . . . . . . . 2-2 

Proceeding with the Installation. . . . . . . . . 2-2 

Card Removal and Re-insertion . . . . . . . . . . . . . 2-3 

Windows 95 and Windows NT Systems. . 2-3 

MS-DOS Systems . . . . . . . . . . . . . . . . . . . . . 2-5 

Apple Powerbook Systems . . . . . . . . . . . . . 2-6 

Chapter 3 Installation for Windows 95 & Windows NT 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 

What You Need to Know . . . . . . . . . . . . . . 3-1 

Plug & Play Support. . . . . . . . . . . . . . . . . . . 3-1 

User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 

Preparing Driver Installation . . . . . . . . . . . . . . . 3-4 

i


ii 

Getting Started . . . . . . . . . . . . . . . . . . . . . . . . 3-4 

Preparation for Windows NT Systems. . . . 3-5 

Installing the Miniport Driver . . . . . . . . . . . . . . 3-11 

Network Installation . . . . . . . . . . . . . . . . . . 3-14 

Setting the WaveLAN Parameters . . . . . . 3-15 

Finishing your WaveLAN Installation. . . 3-21 

Working with WaveLAN & Windows . . . . . . . 3-24 

View other WaveLAN stations . . . . . . . . . 3-24 

Checking the Network Protocol Settings. 3-26 

Display WaveLAN Parameters . . . . . . . . . 3-28 

Installing WaveMANAGER/CLIENT . . . . . . . 3-30 

About this Utility. . . . . . . . . . . . . . . . . . . . . 3-30 

Installing this Utility . . . . . . . . . . . . . . . . . . 3-30 

Chapter 4 Diagnostics for Windows 95 & Windows NT 

WaveMANAGER/CLIENT . . . . . . . . . . . . . . . . . 4-1 

Monitoring Options. . . . . . . . . . . . . . . . . . . . 4-1 

Running WaveMANAGER/CLIENT. . . . . . . . . 4-3 

Using Link Test . . . . . . . . . . . . . . . . . . . . . . . 4-5 

Using Site Monitor . . . . . . . . . . . . . . . . . . . . 4-9 

Logging Measurement Data . . . . . . . . . . . 4-14 

Other Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 

Frequency Select Option. . . . . . . . . . . . . . . 4-17 

Access Control Table Manager . . . . . . . . . 4-18 

Chapter 5 Installation for MS-DOS 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 

Installation for Card & Socket Services . . . . . . . 5-2


Collecting the Information . . . . . . . . . . . . . 5-3 

Installing the Network Operating System 5-3 

Running the INSTALL Program . . . . . . . . 5-4 

Verifying the Installation. . . . . . . . . . . . . . . 5-7 

Frequency Selection (2.4 GHz) . . . . . . . . . . 5-7 

Swapping Cards . . . . . . . . . . . . . . . . . . . . . . 5-8 

Enabler-based Installation . . . . . . . . . . . . . . . . . . 5-9 

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9 


Copying the WaveLAN Software. . . . . . . . 5-9 

Set up the Enabler. . . . . . . . . . . . . . . . . . . . 5-10 

Driver Configuration . . . . . . . . . . . . . . . . . 5-11 

Finishing Installation . . . . . . . . . . . . . . . . . 5-15 

Verify the Installation. . . . . . . . . . . . . . . . . 5-15 

Creating a Utilities Diskette . . . . . . . . . . . 5-16 

Frequency Selection (2.4 GHz) . . . . . . . . . 5-17 

Chapter 6 Diagnostics for MS-DOS 

Point-to-Point Diagnostics. . . . . . . . . . . . . . . . . . 6-1 

About the Point-to-Point Diagnostics . . . . 6-1 

Running Point-to-Point Diagnostics . . . . . . . . . 6-2 

Selecting the Local WaveLAN Card . . . . . 6-3 

Selecting a Link Test Partner. . . . . . . . . . . . 6-3 

Changing Local Identifiers . . . . . . . . . . . . . 6-4 

Search for Other Stations . . . . . . . . . . . . . . . 6-4 

Changing the Test Partner. . . . . . . . . . . . . . 6-5 

The Measurement Data Display . . . . . . . . . 6-6 

Positioning your WaveLAN Computer . . 6-7 

Logging Measurement Data . . . . . . . . . . . . 6-7 

Command Line Parameters. . . . . . . . . . . . . 6-8 

iii


Chapter 7 Frequency Select Utility 

iv 

About the Frequency Select Utility . . . . . . . . . . . 7-1 

Do I Need to Use This Utility?. . . . . . . . . . . 7-1 

Running the Frequency Select Utility. . . . . . . . . 7-3 

Select a New Frequency . . . . . . . . . . . . . . . . 7-4 

Command line parameter . . . . . . . . . . . . . . 7-4 

Chapter 8 Installation for Apple Powerbook Systems 

Appendix A WaveLAN/PCMCIA 

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 

What You Need to Know . . . . . . . . . . . . . . . 8-1 

Removing and Re-inserting your Card . . . 8-2 

Installing in Ethertalk TCP/IP Environments. . 8-3 

Installing the AppleTalk Software . . . . . . . 8-3 

Configuring your WaveLAN Card. . . . . . . 8-5 

Classic and Open Transport Environments. . . . 8-8 

Which one to Choose?. . . . . . . . . . . . . . . . . . 8-8 

Installing the Classic Networking Software8-9 

Installing the Open Transport Software. . 8-10 

Configuring your WaveLAN Card. . . . . . 8-11 

Enabling AppleTalk for Classic. . . . . . . . . 8-12 

Enabling Apple Talk for Open Transport 8-13 

Enabling TCP/IP for Classic . . . . . . . . . . . 8-14 

Enabling TCP/IP for Open Transport . . . 8-15 

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1


Environment Definitions: . . . . . . . . . . . . . .A-2 

Appendix B Driver Installation Examples 

NetWare Examples . . . . . . . . . . . . . . . . . . . . . . . . B-1 

Installing a Driver for Personal NetWare . B-1 

Installing a DOS/ODI Workstation DriverB-1 

NDIS Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 

LAN Manager Installation. . . . . . . . . . . . . . B-3 

Windows v.3.11 Installation . . . . . . . . . . . . B-4 

Appendix C WaveLAN Power Management 

Appendix D Troubleshooting 

About WaveLAN Power Management . . . . . . . C-1 

Considering Power Management. . . . . . . . C-1 

The NetWare Watchdog Mechanism. . . . . C-2 

Connecting to a Single Server . . . . . . . . . . . C-3 

Connecting to Multiple Servers . . . . . . . . . C-4 

Power Management Examples . . . . . . . . . . . . . . C-6 

Restrictions on Using Power ManagementC-8 

Windows 95 & Windows NT . . . . . . . . . . . . . . .D-1 

Verify Card Operation . . . . . . . . . . . . . . . . .D-1 

Windows does not detect my Card . . . . . .D-2 

Windows NT does not detect my card . . .D-3 

WaveMANAGER/ CLIENT does not start . . 

D-3 

Wrong Driver Version . . . . . . . . . . . . . . . . .D-3 

Upgrading from earlier Driver Versions. .D-4 

v


vi 

Error Messages (MS-DOS) . . . . . . . . . . . . . . . . . D-6 

Radio-frequency Network Characteristics. . . D-13 

Signal Interference. . . . . . . . . . . . . . . . . . . D-13 

Signal Attenuation. . . . . . . . . . . . . . . . . . . D-14 

Problem Determination . . . . . . . . . . . . . . . . . . D-14 

Using the Diagnostics Utility. . . . . . . . . . D-15 

Troubleshooting List . . . . . . . . . . . . . . . . . D-15

WaveLAN Technical Support 

You can find the most recent software and user documentation 

for all WaveLAN products on our World Wide Web Site. 

WaveLAN Software and Documentation 

FTP Server FTP://FTP.WAVELAN.COM/PUB 

World Wide Web HTTP://WWW.WAVELAN.COM 

If you encounter problems when installing or using this 

product, or would like information about our other WaveLAN 

products, please contact your Authorized WaveLAN Reseller, 

or local Lucent Technologies Sales Office. 

In emergency, or when no local support is available, you can 

reach us at the addresses or telephone numbers listed below. 

WaveLAN Regional Support 

USA usasupport@wavelan.com 

Carribean/Latin America/ Canada calasupport@wavelan.com 

Europe/ Middle-East/ Africa emeasupport@wavelan.com 

Asia/Pacific 

WaveLAN Global Support 

apasupport@wavelan.com 

U.S.A. Voice: +1 800 WAVELAN 

Fax: +1 937 445 5552 

If applicable, please complete the WaveLAN Driver Problem 

Report form and Fax or E-Mail it to us. This form is available 

on WaveLAN software diskette 1 as WVLANPRF.TXT 

vii

Radio Frequency Interference Statement 

Canada: 

This device complies with RSS-210 of Industry and Science Canada. 

USA - Federal Communications Commission (FCC): 

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 may 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 communications 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 local device supplier. In case the device does cause 

harmful interference with an authorized radio service, the 

user/operator shall promptly stop operating the device until harmful 

interference has been eliminated. 

Lucent Technologies is not responsible for any radio or television 

interference caused by unauthorized modification of this device or 

the substitution or attachment of connecting cables and equipment 

other than specified by Lucent Technologies. 

The correction of interference caused by such unauthorized 

modification, substitution or attachment will be the responsibility of 

the user. 

viii

Who Should Read this 

Manual 

Overview of the Manual 

About This Manual 

WaveLAN/PCMCIA User’s Guide 

Preface 


The WaveLAN/PCMCIA card provides wireless 

communications capability to users of notebook and notepad 

computers in a personal computer based Local Area Network 

(LAN). This manual is a user’s guide to installing and using the 

card. 

This manual should be read by anyone intending to install or 

use the WaveLAN/PCMCIA card. The manual assumes that 

you have a working knowledge of basic PC operations and are 

familiar with driver installation procedures for the Network 

Operating System to be used. 

Note: When you intend to use the WaveLAN/PCMCIA Card as the 

WaveLAN interface for your WavePOINT-II access point, 

please refer to the ‘Getting Started Guide that was shipped 

with your WavePOINT-II device. 

Chapter 1, Introduction 

Describes the functions and features of WaveLAN/PCMCIA 

and the contents of the PCMCIA kit. 

Chapter 2, Hardware Installation 

Describes how to connect the WaveLAN/PCMCIA hardware 

to your computer. 

Chapter 3, Installation for Windows 95 & Windows NT 

Describes how to install the WaveLAN software in a computer 

that runs the Windows 95 or Windows NT operating system. 

ix

Preface 


Chapter 4, Diagnostics for Windows 95 & Windows NT 

Describes how to use the WaveMANAGER/CLIENT to: 

● Run wireless diagnostics in your WaveLAN network 

● Check or change the frequency of your WaveLAN Card. 

Chapter 5, Installation for MS-DOS 

Describes how to install the WaveLAN software in a MS-DOS 

based computer using: 

● Card and Socket Services, or 

● The Enabler program 

Chapter 6, Diagnostics for MS-DOS 

Describes how to use the Point-to-Point Diagnostics utility to 

run wireless diagnostics in your WaveLAN in your network. 

Chapter 7, Frequency Select Utility 

Describes how you can verify the operating frequency of 

WaveLAN 915 MHz or 2.4 GHz cards, and how to select an 

alternative frequency for 2.4 GHz cards. 

Chapter 8, Installation for Apple Powerbook Systems 

Describes how to install the WaveLAN software in an Apple 

Powerbook computer that supports the: 

● Apple Ethertalk Networking software 

● Apple Classic Networking software 

● Apple Open Transport Networking software 

Appendices A, WaveLAN/PCMCIA 

B, Driver Installation Examples 

C, WaveLAN Power Management 

D, Troubleshooting 

x WaveLAN/PCMCIA User’s Guide

Conventions for this 

Document 

Preface 


Throughout this WaveLAN document we use the following 

icons to picture various computing and/or networking devices. 

These icons are used consistently throughout all WaveLAN 

End-User Information Products. 

Icon Description 

Wireless (mobile) Client Station 

equipped with WaveLAN/PCMCIA 

Wired Client Station 

typically equipped with standard Ethernet card. 

Wireless Client Station 

equipped with WaveLAN/ISA 

WavePOINT-II access point 

optionally equipped with WaveLAN/PCMCIA or 

WaveLAN/EAM 

Server Station 

Wired Ethernet Cable/Backbone 

Wireless WaveLAN Coverage Area (Cell) 

Note: 

You may also encounter one of the following conventions: 

Provides general information 

Hint: Provides information that may be of interest to specific users 

Caution: Provides information to prevent damage to equipment, or to 

prevent configuration errors of the devices. 

Warning: Provides information to prevent personal Injury 

WaveLAN/PCMCIA User’s Guide xi

Further Information 

All software diskettes that are shipped with your WaveLAN 

products, include a file called ‘readme.txt’. These files contain 

information about the software and/or drivers on the diskette. 

You are advised to print and read these files prior to installing 

your WaveLAN products, as they may contain information that 

was not available when this document was printed. 

Alternatively you can also access the readme.txt files on the 

internet at the Documents Library of our WaveLAN website. 

http://www.wavelan.com 

On the WaveLAN website you will also find WaveLAN news 

and information about software updates. 

The WaveLAN software for Windows or Apple Powerbook 

systems also includes online help information. Click the help 

button on your screen or press the F1 

function key to access 

the online help files. 

For WaveLAN Technical Support, please consult the 

information printed on page vii of this document.

Chapter 1 

Introduction 


Introduction 

About WaveLAN/PCMCIA 1-1 

Kit Contents 1-2 

Network Configurations 1-5 

Connecting to Ad-Hoc Workgroups 1-5 

Connecting to an Infrastructure 1-5 

Roaming Operation 1-6 

WaveLAN/PCMCIA Features 1-8 

Power Management 1-8

Introduction1 

About WaveLAN/PCMCIA 

About WaveLAN/PCMCIA 1 

The WaveLAN/PCMCIA card is a wireless network interface 

card for notebooks, notepads and other computing devices 

equipped with a PCMCIA (Personal Computer Memory Card 

International Association) Type II card socket. 

WaveLAN is a set of wireless networking products that enable 

you to setup your computer for: 

● “Connecting to Ad-Hoc Workgroups” 

● “Connecting to an Infrastructure” 

WaveLAN adapters function like any standard wired Ethernet 

card, but: WaveLAN has cut the wires! 

Where an ethernet card requires a cable connection to a hub 

and/or patch panel, the cable physically ties you to the location 

where you installed the wired connection. 

WaveLAN allows you to connect to a Local Area Network 

(LAN) anywhere within the network environment. 

Unlike Ethernet, WaveLAN will enable you to roam 

throughout the network environment while remaining 

connected to the LAN. 

Like Ethernet cards, you will need to install the 

WaveLAN/PCMCIA card, using network client drivers, and 

network protocols. WaveLAN is transparent to your network 

operating system, and uses the same frametypes as Ethernet 

networks: Your computer and network operating system will 

not notice the difference between an Ethernet or WaveLAN 

Card, however the flexibility of WaveLAN will make sure you 

will! 

WaveLAN/PCMCIA User’s Guide 1-1

Introduction 

Kit Contents 

Figure 1-1 

1WaveLAN/PCMCIA Kit 

Kit Contents 1 

The WaveLAN/PCMCIA adapter kit (Figure 1-1 on page 1-2) 

includes the following items: 

1 WaveLAN/PCMCIA PC card. 

2 Antenna Module (with mounting bracket). 

3 WaveLAN software. 

4 User’s Guide (this book). 

The kit comes in two versions - with or without the built-in 

encryption feature. 

1-2 WaveLAN/PCMCIA User’s Guide

WaveLAN/PCMCIA Card 1 

Antenna Module 1 

WaveLAN Software 1 

The 

The 

Your 

Introduction 

Kit Contents 

WaveLAN/PCMCIA card (PC card) is a credit card size 

network adapter which fits in a PCMCIA Type II card socket 

in a personal computer. 

compact antenna module connects to the PC card with a 

450 mm (18 in.) cable, allowing the module to rest on the 

desktop or other work surface. The antenna module may also 

be mounted on the computer body using the bracket provided 

for that purpose. 

LED indicators on the antenna module provide status 

information (Power On/Off, Transmit, Receive). 

WaveLAN/PCMCIA adapter card is shipped with three 

software diskettes: 

1 Driver and diagnostic software for Microsoft Windows 95 

or Windows NT operating systems: 

● Miniport Driver and ‘INF’ file for card installation 

● WaveMANAGER/CLIENT program to monitor 

wireless performance. 

2 Driver and diagnostic software for Microsoft MS-DOS 

operating systems: 

● An install program for computers that support Card 

and Socket Services (CS&SS), or 

● The Enabler program, for computers that do not have 

Card and Socket Services installed. 

● Network drivers for NetWare (ODI)- or NDIScompatible 

networking environment. 

● The Point-to-Point Diagnostics and WaveMONITOR 

tools to diagnose the wireless link with other 

WaveLAN stations or WavePOINT access points. 

● Frequency Select Utility, that enables you to modify 

the factory-set operating frequency (limited to specific 

2.4 GHz units only). 

3 Driver software for Apple/Macintosh Powerbook 

computers. 


Introduction 

Kit Contents 

WaveLAN User’s Guide 1 

An 

● Apple Classic environments 

● Apple Open Transport environments 

overview of the User’s Guide is described in the Preface on 

page -ix of this document. 

You can download this document in electronic format (Adobe 

Acrobat PDF) form the WaveLAN website: 

http://www.wavelan.com 


Connecting to Ad-Hoc 

Workgroups 1 

Figure 1-2 

1Ad-Hoc Wireless Workgroup 

Connecting to an 

Infrastructure 1 

Introduction 

Network Configurations 

Network Configurations 1 

Your WaveLAN/PCMCIA station can participate in group 

workplace computing along with other portable or desktop 

computers equipped with WaveLAN adapter cards. The 

wireless workgroup (or ‘cell’) is identified by a Network 

Identification Designator (NWID). To connect to the wireless 

workgroup, all stations must be configured with the same 

NWID. In ad-hoc workgroups, this NWID is usually an NWID 

code agreed upon by the participants of the workgroup. 

Where cable physically connects wired stations in an Ethernet 

network, the NWID logically connects the wireless stations in 

a WaveLAN cell as pictured in Figure 1-2. 

When you would like to connect your WaveLAN/PCMCIA 

station into an existing wired LAN infrastructure, your 

wireless cell can be extended with a WavePOINT access point; 

a transparent bridge between the WaveLAN and Ethernet 

stations. Figure 1-3 on page 1-6 illustrates the WaveLAN 

Infrastructure concept. 

All members of the WaveLAN cell must be configured with 

the same WaveLAN Network ID (NWID). In this case, the 

NWID value is determined by the NWID value that is 

programmed into the WavePOINT unit. 


Introduction 


Figure 1-3 

1WaveLAN Infrastructure 

Roaming Operation 1 

Mobile stations have access to the wired LAN when within 

range of the WavePOINT, and using the correct NWID value. 

In multi-cell environments, where multiple WavePOINTs have 

been placed at selected locations within the facility, a mobile 

station would need to use different NWID values, each time it 

enters another wireless cell. 

For proper wireless operation, each cell must be identified by a 

unique NWID, that the LAN Administrator can program into 

the WavePOINT unit (as described in the documentation that is 

shipped with the WavePOINT unit). 

To allow a mobile station to remain seamlessly connected to 

the network, you can setup the WaveLAN devices for roaming 

operation. 

For roaming operation (as pictured in Figure 1-4 on page 1-7, 

you can group all WaveLAN devices that belong to the same 

LAN into a logical group, called the ‘The Domain’. 

The Domain is identified by a unique Domain ID. 


Figure 1-4 

1WaveLAN Roaming Domain 

Introduction 


To connect your station to a WaveLAN Domain, your 

WaveLAN/PCMCIA station must use the same Domain ID as 

the Domain ID value that your LAN Administrator 

programmed into the WavePOINT access points. 

To allow your WaveLAN/PCMCIA station to roam at will 

throughout the Domain while remaining connected to the 

network: 

1 Enable the roaming feature, and 

2 Configure your WaveLAN/PCMCIA station to use the 

same Domain ID as the WavePOINT access points 

Once properly configured, your wireless station will be able to 

automatically retrieve the NWID value that is required to 

communicate within a specific cell. Active communication 

remains possible as long as the station remains within range of 

the WavePOINT access points of your Domain. 

Note: To support roaming WaveLAN stations, make sure the 

WavePOINTs have the roaming feature enabled as well, and 

that both stations and WavePOINTs use an identical Domain 

ID value. 


Introduction 

WaveLAN/PCMCIA Features 

Power Management 1 

WaveLAN/PCMCIA Features 1 

Using spread-spectrum radio communications technology, 

WaveLAN/PCMCIA brings the benefits of wireless 

connectivity to the mobile computer user. 

WaveLAN/PCMCIA conforms to the PCMCIA PC Card 

standard and supports industry-standard network operating 

systems. 

In addition, WaveLAN/PCMCIA provides: 

● Station mobility (up to pedestrian speed). 

● Roaming (when used with WavePOINT or compatible 

access points). 

● “Hot Card Swap” and “Phantom Binding” (when installed 

in Windows 95/NT environments and on MS-DOS 

systems that have PCMCIA Card and Socket Services 

installed). 

WaveLAN/PCMCIA is fully interoperable with other members 

of the WaveLAN family of wireless LAN products. 

WaveLAN provides a power management feature which 

allows the card to be put into a low power consuming state 

when no active communication is taking place. The card will 

become active at regular intervals to respond to network 

Watchdog messages, thereby maintaining the network 

connection. Using this feature can result in better battery 

performance for mobile users. The feature is configurable to 

take account of the specific Watchdog parameter settings used 

by the network operating system. Power Management is 

currently available for the WaveLAN ODI driver only. 


Power Management & 

Network Time-outs 1 

Introduction 

WaveLAN/PCMCIA Features 

Note: You may need to disable other power management schemes 

active in your computer for WaveLAN power management to 

operate correctly. 

Some network operating systems log users off automatically 

after a period of inactivity. This can happen as a result of the 

card being removed, the station being out of range of a 

WavePOINT or WaveLAN cell, or through using a (non- 

WaveLAN) power management scheme. If this is likely to 

cause problems you should consult your Network Supervisor 

about modifying the network’s timer values, and/or disable the 

power management function. 


Chapter 2 

Hardware Installation 



Installing your WaveLAN Kit 2-1 

Inserting the PC Card 2-1 

Mounting the Antenna Module 2-2 

Proceeding with the Installation 2-2 

Card Removal and Re-insertion 2-3 

Windows 95 and Windows NT Systems 2-3 

Removing the Card from Windows 95 2-4 

Reinserting the Card in Windows 95 2-5 

Removing the Card from Windows NT 2-5 

Reinserting the Card in Windows NT 2-5 

MS-DOS Systems 2-5 

CS&SS-Based Installations 2-5 

Enabler-Based Installations 2-6 

Apple Powerbook Systems 2-6

Inserting the PC Card 2 

Figure 2-1 

2Inserting the card (side slot) 

Hardware Installation2 

Installing your WaveLAN Kit 

Installing your WaveLAN Kit 2 

The WaveLAN/PCMCIA Card will fit into any PC Card Type 

II slot. To insert the WaveLAN/PCMCIA Card: 

1 Connect the antenna module to the WaveLAN PC Card. 

2 Slide the card into a PCMCIA slot in the computer (see 

Figure 2-1). 



Installing your WaveLAN Kit 

Mounting the Antenna 

Module 2 

Proceeding with the 

Installation 2 

If desired, you can use the antenna mounting bracket to fix the 

WaveLAN/PCMCIA antenna module to your computer as 

shown in Figure 2-1. 

1 Slide the antenna module onto the mounting bracket. 

2 Determine where you would like to place the antenna 

module 

Caution: Mind that the position of the antenna module allows the cable 

to bend naturally around corners and that no excessive force is 

applied to the cable connector, for example when opening or 

closing the display panel of your laptop computer. 

3 When you have determined where you want to affix the 

bracket, remove the protective strip from the adhesive pad 

4 With the Antenna Module attached, press the bracket 

firmly in position. 

You can now remove and remount the antenna module 

whenever you wish. 

Once you have the WaveLAN/PCMCIA hardware installed, 

you can proceed with the WaveLAN driver installation. Turn 

to the chapter that applies to the operating system installed on 

your computer: 

● Chapter 3, “Installation for Windows 95 & Windows NT” 

● Chapter 5, “Installation for MS-DOS” This chapter also 

applies to computers that run the Windows 3.11 user 

interface. 

● Chapter 8, “Installation for Apple Powerbook Systems”. 


Windows 95 and 

Windows NT Systems 2 

Removing the Card from 

Windows 95 2 


Card Removal and Re-insertion 

Card Removal and Re-insertion 2 

Depending on the type of operating system installed on your 

computer, you can remove and re-insert your 

WaveLAN/PCMCIA Card whenever you like. 

This feature, also referred to as ‘Hot Swapping’ for PC Cards 

is supported by the following installation types: 

● Windows 95 Systems 

● “CS&SS-Based Installations” for “MS-DOS Systems” 

(see page 2-5) 

Note: When re-inserting the card, the WaveLAN/PCMCIA Card will 

become operational again. However your network operating 

system may not be able to restore the network connection. For 

certain network operating systems, you may need to restart 

your computer to rerun the network login procedures, before 

you can reconnect to the network. 

Although Windows 95 and Windows NT (version 4.0) are 

similar in appearance, there is a major difference between the 

two operating systems, affecting the support for removal and 

re-insertion of PC Cards (‘Hot Swapping’) and ‘plug & play’ 

support. 

You can remove the WaveLAN card at any time from a 

computer that runs on the Windows 95 or Windows NT 

Operating System. You are advised however to follow the 

procedure as described for each of the operating systems. 

You are advised to disable the PC Card prior to removing the 

card. This will allow the operating system to disable the 

WaveLAN drivers. To disable your PC card: 




Figure 2-2 

2PC Card Properties Window 

Reinserting the Card in 

Windows 95 2 

1 Click the Start button on the Windows Taskbar. 

2 Point to ‘Settings’ and click the ‘Control Panel’ item 

3 On the Control Panel double-click the PC Card icon to 

open the ‘PC Card (PCMCIA) Properties’ window. 

4 Select the PC Card slot that contains the 

WaveLAN/PCMCIA Card, and click the Stop button. 

5 Wait for the Operating System to acknowledge the drivers 

have been disabled and remove the WaveLAN/PCMCIA 

Card from the PC Card slot. 

Hint: When the ‘Show control on taskbar’ item on the ‘PC Card 

(PCMCIA) Properties’ window is selected as pictured in 

Figure 2-2, you can skip steps 1 to 3 by double-clicking the PC 

Card icon on the right-bottom side of your screen on the 

Windows task bar. 

Windows 95 systems support ‘plug & play’, i.e. you can easily 

re-insert the card. Windows 95 will detect the ‘new hardware 

and enable the drivers again. 


Removing the Card from 

Windows NT 2 

Reinserting the Card in 

Windows NT 2 

MS-DOS Systems 2 

2 CS&SS-Based Installations When 



To remove your WaveLAN/PCMCIA Card from a Windows 

NT system you are advised to power off your computer and 

remove the card. Optionally restart your computer if you 

would like to proceed working with your computer without the 

WaveLAN/PCMCIA card. 

Windows NT systems (version 3.51 and v.4.0) do not support 

‘plug & play’. When you would like to re-insert the 

WaveLAN/PCMCIA card into a computer that runs the 

Windows NT operating system, you are advised to: 

1 Power off the computer 

2 (Re-)Insert the WaveLAN/PCMCIA Card, and 

3 Power-up the computer again. 

The Windows NT system will now detect the 

WaveLAN/PCMCIA card again and install the required 

WaveLAN drivers. 

In MS-DOS environments, you can install the 

WaveLAN/PCMCIA cards using either Card Services and 

Socket Services (CS&SS), or the Enabler program (described 

in Chapter 5, “Installation for MS-DOS”.) 

you install the WaveLAN/PCMCIA card into a MS- 

DOS based system that supports Card and Socket Services, the 

WaveLAN drivers will support “Hot Swapping” and “Phantom 

Binding”. 

Phantom Binding is the feature where the Card Services and 

Socket Services will load the WaveLAN software without the 

card being present. 

Hot Swapping refers to the feature where you can insert or 

remove the card at any time when the computer is running. 

Communications will cease when the card is removed and will 

recommence when the card is replaced in the computer. 

Same network restrictions apply as described in the note on 

page 2-3. 




2 Enabler-Based Installations In 

Apple Powerbook 

Systems 2 

MS-DOS based computers that do not support Card 

Services and Socket Services (CS&SS) you would typically 

install WaveLAN/PCMCIA with the Enabler program. 

In Enabler based installations, you will still be able to remove 

the WaveLAN card and re-insert it later. However, if you 

would insert another PC Card into your computer in the 

meantime, this might adversely affect the ability of the 

WaveLAN/PCMCIA card to resume operation. 

Inserting another card while the WaveLAN card is removed is 

not recommended for Enabler-based installations. 

Once your WaveLAN/PCMCIA card has been configured (as 

described in Chapter 8, “Installation for Apple Powerbook 

Systems”), you can insert your WaveLAN/PCMCIA card 

either before or after you boot your Powerbook System. 



Installation for Windows 95 & Windows NT 

Chapter 3 

Installation for Windows 95 & 

Windows NT 

Introduction 3-1 

What You Need to Know 3-1 

Plug & Play Support 3-1 

User Profiles 3-2 

Preparing Driver Installation 3-4 

Getting Started 3-4 

Preparation for Windows NT Systems 3-5 

Installing the Miniport Driver 3-11 

Network Installation 3-14 

Setting the WaveLAN Parameters 3-15 

Finishing your WaveLAN Installation 3-21 

Working with WaveLAN & Windows 3-24 

View other WaveLAN stations 3-24 

Checking the Network Protocol Settings 3-26 

Display WaveLAN Parameters 3-28 

Installing WaveMANAGER/CLIENT 3-30 

About this Utility 3-30 

Installing this Utility 3-30

What You Need to Know3 

Plug & Play Support 3 

Installation for Windows 95 & Windows NT3 

Introduction 

Introduction 3 

Installing a WaveLAN/PCMCIA card requires the same level 

of expertise that you would need to install any other type of 

standard Ethernet network adapter card. It is assumed that you 

have a working knowledge of standard Window 95 and 

Windows NT operations and an average knowledge of 

installing network adapter cards. 

Although similar in appearance Windows 95 and Windows NT 

are operating systems that show different behavior when 

installing new hardware for your computer. Major differences 

are: 

● Plug & Play Support 

● User Profiles 

Windows 95 systems support ‘Plug & Play’ for PC Cards. 

Once a card is inserted into the computer, the Windows 95 

system will automatically detect the card, and enable the 

WaveLAN Miniport Driver. When Windows 95 can not find 

the required driver, for example when this is the very first time 

that you insert the WaveLAN/PCMCIA card into your 

computer, the Windows 95 operating system will prompt you 

to install the driver. 

Once the WaveLAN Miniport Driver is installed, you can 

remove and re-insert the card whenever you like. This is also 

referred to as ‘Hot Swapping’. 

Windows NT operating systems (version 3.51 and v. 4.0) do 

not support ‘plug and play’. This means that you will need to 

‘introduce’ the hardware to your computer, in order to install 

the WaveLAN/PCMCIA card. 



Introduction 

User Profiles 3 

Second drawback is that your Windows NT system will not 

support ‘Hot Swapping’ of PC Cards. 

When you would like to remove or re-insert PC Cards from a 

computer that runs the Windows NT operating system, you 

will always need to: 

1 Power off your computer 

2 Remove or re-insert the WaveLAN/PCMCIA card 

3 Restart your computer again. 

Note: ‘Plug and Play’ support for Windows NT Operating systems 

will be available for Windows NT version 5.0, which is 

expected to be released by Microsoft Corporation later in 

1998. 

Both Windows 95 and Windows NT operating systems work 

with user profiles that enable users to specify user-specific 

settings in computer environments where multiple persons 

share the same computer terminal. 

For Windows 95 systems the user profiles only concern the 

visual appearance of the Windows 95 desktop and user-defined 

preferences. The Windows 95 user profiles do not have any 

impact on WaveLAN Installation. 

On Windows NT systems however, user profiles (accounts) are 

associated with dedicated levels of authority (privileges), for 

example: 

● Users, who are allowed to change the visual appearance of 

the Windows NT desktop and user-defined preferences. 

● Power Users, who can create User accounts or User 

Groups 

● Administrators, who can manage and control the overall 

configuration of the workstation. 



Introduction 

Note: To install (or uninstall) the WaveLAN/PCMCIA Card in a 

Windows NT environment, you will need to login as the 

‘Administrator’ or ensure that your login profile provides the 

same level of privileges. 

The privilege settings for each user (account) are set in the 

Microsoft Windows NT ‘User Manager’ program. Please 

consult the documentation that was shipped with your 

Microsoft Windows NT Operating System or station for more 

information. 



Preparing Driver Installation 

Getting Started 3 

Preparing Driver Installation 3 

When installing a WaveLAN/PCMCIA Card you will typically 

install: 

● The WaveLAN Miniport Driver 

● Network (client) Operating Software and protocols 

● (optionally) The WaveMANAGER/CLIENT diagnostics 

program (described on page 3-30). 

Network Client software is included with the Windows 95 and 

Windows NT installation software. Before you start the 

installation you are advised to keep the Windows CD-ROM or 

software diskettes at hand. 

Note: If you are upgrading from an earlier version of the WaveLAN 

Miniport driver, please read “Upgrading from earlier Driver 

Versions” on page D-4 first. 

As the Windows operating systems differ slightly (see “What 

You Need to Know” on page 3-1) some of the screens pictured 

in this chapter may look different from the actual display on 

your screen. The parameter settings for your WaveLAN card 

however will be similar for both Windows 95 and Windows 

NT systems. 

To install the WaveLAN/PCMCIA Card, proceed as follows: 

1 Insert the WaveLAN/PCMCIA card into your computer. 

2 Make sure the cable from the antenna module is properly 

connected to the WaveLAN/PCMCIA Card. 

3 Power up your computer. 

When your computer system runs the Windows 95 Operating 

System, the ‘Plug & Play’ functionality will detect your 

WaveLAN/PCMCIA Card and pop-pup with a message 


Preparation for Windows 

NT Systems 3 

Enabling the PC Card 

Controller 3 



identifying it is installing the WaveLAN drivers. Skip to 

“Installing the Miniport Driver” on page 3-11 to proceed with 

the installation. 

When installing WaveLAN/PCMCIA on a Windows NT 

operating system (version 3.51 or v.4.0) you will need to 

perform the Preparation for Windows NT Systems as 

described below, prior to Installing the Miniport Driver. 

When your computer runs the Windows NT Operating system, 

you will need to perform a few additional steps to introduce 

the card to your computer. These steps include: 

● Enabling the PC Card Controller of your computer 

● Running Windows NT Diagnostics, to verify the 

availability of the default I/O Port Address and IRQ value 

for the WaveLAN/PCMCIA card. 

● Enabling Network Support for your (client) station. 

When this is the first time you install a PC Card into your 

computer, you may probably need to enable the PC Card 

Controller. This is to ‘instruct’ the Windows NT System to 

actively look for cards in the PC Card sockets at start-up. 

1 Click the ‘Start’ button on the Windows Taskbar. 

2 Point to Settings and click the ‘Control Panel’ item. 

3 In the Control Panel window, double-click the PC Card’ 

icon to open the PC Card Properties window (see Figure 

3-1 on page 3-6). 

4 In the PC Card Properties window, double-click one of the 

PC Card Sockets. 

5 Click the OK button to confirm and close the PC Card 

Properties window. 




Figure 3-1 

3Enabling the PC Card 

Controller 

Running Windows NT 

Diagnostics 3 

When installing the WaveLAN/PCMCIA Card to your 

Windows NT operating system, you will be prompted to 

confirm or modify the WaveLAN factory-set values for I/O 

Port and Interrupt Request vector (IRQ): 

● I/O Port 0320 

● IRQ 11 

Unlike the Windows 95 operating system, Windows NT is not 

able to check automatically whether the proposed values are 

already used by another device. 

To avoid the possibility of a hardware conflict with another 

device, you are advised to use the Windows NT Diagnostic 

program, to determine whether the default I/O port and IRQ 

for your WaveLAN card are available, and if not to select an 

alternative value. 

To run the Windows NT Diagnostics: 


Figure 3-2 

3Verifying IRQ vector 

Availability 



1 Click the ‘Start’ button on the Windows NT Taskbar. 

2 Point to Programs and select the item ‘Administrative 

Tools’. 

3 From the list of ‘Administrative Tools’ click the item 

‘Windows NT Diagnostics’. 

4 From the Windows NT Diagnostics screen, click the tab 

‘Resources’ to display the window pictured in Figure 3-2 

below. 

. 

The ‘Resources’ tab (see Figure 3-2) enables you to verify 

a number of configuration settings for the hardware 

devices installed into your computer. 

5 Click the button ‘IRQ’ to display the Interrupt Request 

Vectors (IRQ) currently in use by other devices in your 

computer. 

The default IRQ for WaveLAN/PCMCIA is 11. 

Is the value 11 already listed? 




3-8 WaveLAN/PCMCIA User’s Guide 

● If No, you can use the WaveLAN default. Write down 

IRQ 11 and proceed with the next step. 

● If Yes, this means that another device is already using 

the IRQ, i.e. you will need to select another value for 

your WaveLAN/PCMCIA card. 

See whether one of the following values is available 

(i.e. not listed in the Windows NT Diagnostics 

window): IRQ 03, 04, 05, 07, 12, 15 

Select one non-listed value and write it down before 

you proceed with the next step. 

6 Click the button I/O Port to display the ‘I/O Base 

Addresses’ currently in use by other devices in your 

computer (see Figure 3-3 on page 3-9). 

The default I/O Port for WaveLAN/PCMCIA is 0320- 

0327. Is this value already listed? 

● If No, you can use the WaveLAN default. Write down 

I/O Base 0320 and proceed with the next step. 

● If Yes, this means that another device is already using 

this port address, i.e. you will need to select another 

value for your WaveLAN/PCMCIA card.

Figure 3-3 

3Verifying I/O Port Availability 



When the default WaveLAN I/O Port has already been 

assigned to another device: 

1 Select one of the alternative values from the table 

below 

WaveLAN/PCMCIA Supported I/O Base Addresses 

0320 (Default) 0350 0380 03B0 03E0 

0328 0358 0388 03B8 03E8 

0330 0360 0390 03C0 03F0 

0338 0368 0398 03C8 

0340 0370 03A0 03D0 

0348 0378 03A8 03D8 

2 Verify if this alternative value is available (i.e. not 

listed in the Windows NT Diagnostics window). 




Enabling Network Support 3 

To 

3 Write down the alternative I/O Port value and proceed 

with the next step. 

Having finished these steps, you should now have a note that 

identifies the I/O Port Address and IRQ value that you can use 

to install the WaveLAN Miniport Driver. 

introduce your WaveLAN network adapter card to the 

Windows NT Operating System, you will need to enable 

Network support for your WaveLAN station. 

1 From the Windows NT Taskbar click the ‘Start’ button. 


3 In the Control Panel window, double-click the ‘Network’ 

icon to open the ‘Network Settings’ window. 

If no network has been installed yet, you will be prompted 

to install it now. 

4 Click “Yes” to install Windows NT Networking 

Windows NT Networking Setup will start to determine the 

type of network adapter card that you would like to use to 

connect to the network. 

5 When prompted to start the automatic “Network Adapter 

Card Detection”, select “Do Not Detect”. 

The automatic card detection does not work with 

WaveLAN cards. 

Windows NT will display a new window to confirm it did 

not detect a network card. 

6 Click ‘Continue’ to select the card manually and proceed 

with “Installing the Miniport Driver” on page 3-11. 


Figure 3-4 

3Select your Network Adapter 


Installing the Miniport Driver 

Installing the Miniport Driver 3 

When Windows 95 automatically detected your hardware, it 

will prompt you to select a driver from a list or to install the 

driver from a ‘Disk provided by Hardware Manufacturer’. 

Some Windows operating systems may prompt you to select 

the type of network adapter first, to select the appropriate 

driver (see Figure 3-4). 

This is usually the case when: 

● Your computer came with a factory-installed version of 

Windows 95 (usually referred to as Windows 95 OSR2). 

● Your computer runs Windows NT (v.4.0), and you used the 

‘Select Card Manually’ option as described under 

“Enabling Network Support” on page 3-10. 

Hint: To make sure you install the latest available driver, always 

select the ‘Disk provided by Hardware Manufacturer’ or the 

‘Have Disk’ option, to install the driver from the diskette that 




Figure 3-5 

3Select WaveLAN Adapter 

Type 

came with your WaveLAN card, or from the set of files you 

downloaded from our WaveLAN website. 

1 In the ‘Select Network Adapter’ window (see Figure 3-4) 

click the ‘Have Disk’ button. 

2 Insert the WaveLAN software disk for Windows 95 & NT 

environments into floppy drive A: of your computer and 

click the ‘OK’ button to proceed. 

Alternatively use the ‘Browse’ option to open the folder 

where you saved the driver files that you downloaded form 

the WaveLAN website. Click ‘OK’ to proceed. 

Windows NT systems may prompt you to select the type of 

WaveLAN card (see Figure 3-5). Select the type and brand 

name that matches your hardware and click OK to confirm. 

Windows will start copying files from the Windows 

installation disks or CD-ROM and the WaveLAN installation 

diskette. 

If the system prompts you to identify the location of files (see 

Figure 3-6), enter the correct drive and directory. 


Figure 3-6 

3Identify the location of files 



● For Windows System files (typically *.dll) this is 

usually the Windows CD-ROM. e.g. D:\win95. 

● When your computer came with the Windows 

Operating System factory-installed, point to the 

directory that contains the Windows Setup files 

(*.cab): e.g. c:\windows\options\cabs 

● When the system prompts you to identify the 

WaveLAN Driver files (typically file names starting 

with the characters ‘wv’), specify the drive and 

directory that contains your WaveLAN software (e.g. 

the floppy disk drive or directory where you saved 

downloaded files). 

Hint: When you had a network adapter installed on your computer 

before, most Windows System files associated with 

networking (*.dll) are already available on your hard disk 

drive. If you do not have the Windows CD-ROM available, 

you may try replacing the proposed path in the ‘Copy files 

from’ dialog box with: 

C:\windows\system or 

C:\windows\ 

If the Operating System continues the installation 

procedure without the repeated error message, the 

requested files were already on the hard-disk drive. 

3 Click the “OK” button to proceed. 




Network Installation 3 

Figure 3-7 

3Windows Network Properties 

When this is the very first time that Networking support is 

installed onto your computer, the Windows operating system 

will prompt you to enter a computer and workgroup name. 

These names will be used to identify your computer on the 

Microsoft Network Neighborhood. 

Click the “OK” button to display the window as pictured in 

Figure 3-7. 

1 Select the “Workgroup” Field. 

2 Specify a unique name for your computer. 

3 Enter the name of your workgroup. 

4 (Optional) Provide a description of the computer. 

Note: All computers that should be able to share files or printers 

must use the same workgroup name. For more information 

about setting your network, consult your Windows 

documentation or the Windows on-line help information. 


Setting the WaveLAN 

Parameters 3 

Figure 3-8 

3WaveLAN Parameters 

(Win95) 

Figure 3-9 

3Confirm I/O Port and IRQ 

(Windows NT only) 



When you confirm the Windows workgroup parameters by 

clicking the OK button, Windows will open the parameter 

window for your WaveLAN/PCMCIA Adapter. 

When you run the Windows 95 operating system, the window 

will look as pictured in Figure 3-8. 

When you are running the Windows NT operating system, you 

will be prompted to confirm or modify the settings of the I/O 

Port address of your WaveLAN Adapter, and its IRQ value 

(see Figure 3-9). 




Which Parameters do You 

Need? 3 

Enter the values that you wrote down when running the 

Windows NT Diagnostics as described on page 3-6. When you 

click the ‘Continue’ button, Windows NT will display the 

parameter window for your WaveLAN/PCMCIA Adapter as 

pictured in Figure 3-10 on page 3-20. 

This window enables you to specify the WaveLAN specific 

parameters, required to connect your computer to the network. 

When you are connecting your station to an ad-hoc network 

(see page 1-5), you will need to set the following parameters: 

● Network Identification Designator (NWID) 

● Station Name 

● (Optional) Encryption Enable and Encryption Key 

When connecting your station to a WaveLAN network 

infrastructure, you will need to set the following parameters: 

● Roaming Enable 

● Domain ID 

● (Optional) Beacon Key 

● Station Name 

● (Optional) Enable Encryption and enter the Encryption 

Key 

When you purchased a WaveLAN adapter with factoryinstalled 

security feature, you can optionally enable 

Encryption and set the Encryption key. 

Note: When connecting to an existing network, you may need to 

consult your network administrator for the parameter settings 

that apply to your network environment. 

To set the WaveLAN parameters: 

1 Select the parameter item in the Property list. 

2 Use the mouse to click the Value field. 

3 Enter the parameter value that applies to your network 

environment. 


NWID 3 

Roaming 3 

The 

When 



4 Use the mouse again to go back to select the next 

parameter item. 

5 When finished click the “O.K.” button. 

Network Identification Designator (NWID) is a unique 

code, that logically connects stations in a single WaveLAN 

network group (like cabling physically connects wired stations 

in a cabled network). 

Valid values are any four digit hexadecimal values in the range 

0100 H through FFFF H. 

All stations in a wireless workgroup must use the same NWID. 

When you would like to connect your station to an ad-hoc 

network (see “Connecting to Ad-Hoc Workgroups” on page 

1-5) you must enter the NWID value that is used by the other 

workgroup participants. This is usually a value agreed upon by 

the workgroup participants. 

When connecting to a WaveLAN Roaming Infrastructure (i.e. 

a WaveLAN network that includes WavePOINT access 

points), you may ignore the setting of the NWID field, as your 

station will retrieve the NWID automatically (see “Connecting 

to an Infrastructure” on page 1-5). 

you would like to connect your station to a WaveLAN 

Roaming Infrastructure use this option to ‘Enable Roaming.’ 

A Roaming Infrastructure is a WaveLAN network 

environment that includes WavePOINT access points (see 

“Connecting to an Infrastructure” on page 1-5). 

Roaming allows your station to connect automatically to any 

WaveLAN workgroup in the network environment, despite the 

fact that each wireless workgroup is using a different NWID. 

The station will listen for Beacon messages transmitted by 

WavePOINT access points to automatically retrieve the NWID 

code of a WaveLAN workgroup. 




Domain ID 3 

Beacon Key 3 

The 

(Optional) 

If Roaming Enable is set to “ON”, you must also specify the: 

● Domain ID and 

● (optionally) the Beacon Key. 

If your wireless network environment does not include 

WavePOINT access points, set “Roaming Enable” to “OFF”. 

and set the NWID code to a value that matches the one used by 

the other wireless stations in the vicinity of your WaveLAN 

station. 

Domain ID is a unique code, that connects multiple 

WaveLAN workgroups into one wireless network environment 

(the Domain). 

Valid Domain ID values are any four digit hexadecimal value 

in the range 0001 H through FFFF H. 

In WaveLAN Roaming Infrastructure networks, all WaveLAN 

stations and WavePOINT access points must use the same 

Domain ID value. 

When connecting your station to an Ad-hoc network you may 

ignore this parameter. 

When you enable the Roaming Option, your mobile 

station will try to retrieve the NWID information from Beacon 

messages transmitted by the WavePOINT access point in the 

wireless domain. 

Your LAN Administrator however, may have configured your 

WavePOINT access points to use a Beacon Key that will 

encode the NWID information. 

When trying to connect your WaveLAN station to a WaveLAN 

Infrastructure, consult your LAN Administrator for the correct 

Beacon Key value. 

Valid Beacon Key values are any four digit hexadecimal value 

in the range 0001 H through FFFF H. 


Encryption Enable 3 

Encryption Key 3 

(Optional) 



Ad-hoc networks do not use Beacon messages, so when 

connecting to an ad-hoc network, you may ignore the Beacon 

Key parameter. 

This option can only be used when you are using a 

WaveLAN card has been equipped with a factory-installed 

security feature. If you want to encrypt wireless data 

transmissions, set encryption to “ON” and set the Encryption 

key. 

Note: When you decide to enable encryption for this station, please 

mind that communication will only be possible with 

WaveLAN stations and WavePOINT devices that: 

● Have a factory-installed security feature as well. 

● Have enabled their encryption feature. 

● Use exactly the same encryption key. 

Consult your LAN Administrator for information that applies 

to your network environment. 

Only 

needed if Encryption Enable is “ON”. 

A valid Encryption Key value is any 16 digit hexadecimal 

value, where the16 digits must be entered as 8 digit pairs. 

Each digit can be any hexadecimal value in the range of 0-9 

and A-F. The second digit of each pair however, must be an 

even hexadecimal value (i.e. 0,2,4,6,8,A,C or E). 




Figure 3-10 

3WaveLAN Parameters 

(Windows NT) 

Station Name 3 

Station Address 3 

The 

When 

WaveLAN Station Name will be used to identify your 

WaveLAN station in the WaveLAN diagnostic tools like the 

WaveMANAGER/CLIENT described in Chapter 4. 

You are advised to enter the same name as the one you entered 

for the ‘Computer Name’ in the Windows Network 

Neighborhood (see page 3-14). 

installing the WaveLAN card into a system that runs the 

Windows NT system, you can also enter an alternative to the 

factory-set MAC Address value, using the Station Address 

field. You are advised to leave this field blank, unless you are 

familiar with local MAC Addressing schemes, and you do 

intend to use a user-defined Local MAC Address. 

On Windows 95 systems, this Station Address field is not 

displayed upon initial configuration. However when you 

intend to use Local Mac Addressing for this station: 

1 Finish the WaveLAN Installation first. 

2 Reboot your computer 

3 Display the WaveLAN properties again (as described on 

page 3-28). 

Now the Windows 95 system will display the Station 

Address field. 

4 Enter the Local MAC Address in the Station Address field. 

5 Click the ‘OK’ button to confirm the modification and 

reboot your computer. 


Finishing your 

WaveLAN Installation 3 

Figure 3-11 

3Finished Setting up the 

Hardware 

After the Reboot... 3 

When 



When you have finished “Setting the WaveLAN Parameters”, 

click “OK” to proceed with the installation process. Windows 

will finish ‘building the driver configuration database’ and 

copy some files from your CD-ROM or diskette to your 

harddisk. 

When the Windows operating system prompts you to identify 

the location of the Windows files, specify the drive and 

directories of the Windows Installation CD-ROM or diskettes 

(see also page 3-13). 

When Windows has finished the copying of files, it will 

prompt you to restart your computer. 

1 Remove the WaveLAN software diskette from drive a:\ 

2 Click the “OK” button to restart your computer. 

you have rebooted your computer, your Windows 

operating system should detect the WaveLAN/PCMCIA card 

(usually you can hear this by the sound effect of the PC Card 

Socket Controller). 

Windows will load the driver and will open with a dialog box 

that enables you to enter a user name and a user password. The 

password you enter here will be the one used to log into the 

Windows Network Neighborhood. 

Windows may display multiple password dialog boxes 

according to the number of network clients you installed, 




Figure 3-12 

3Windows Network Properties 

where each dialog box prompts you for the password of a 

specific network operating system, for example: 

● Microsoft Network logon 

● Novell Netware logon 

Hint: When you do not like to enter up to 3 passwords or more every 

time you start-up your computer, you can configure Windows 

Networking to use Windows Logon as your ‘primary logon’. 

You may consider using the same user name and password for 

the Windows logon as for your the logon procedure to the 

network operating systems. 

Doing so, the username and corresponding password for the 

other network systems will be stored in a personal password 

list (username.pwl). 




Upon future reboots, the Windows Operating system will only 

prompt you to enter the Windows username and password to 

unlock the personal password list. 

From there, the Windows operating system will automatically 

logon to the other operating systems, using the logon names 

and passwords in the personal password list. 

This personal password list (username.pwl) can only be used 

by the person that knows the correct username and 

corresponding password for the Windows logon. It is not 

possible to open or read a password list file using standard text 

file viewers, such as ASCII editors or notepad. 



Working with WaveLAN & Windows 

View other WaveLAN 

stations 3 

Working with WaveLAN & 

Windows 3 

To view other computers in your wireless network, start the 

Windows Explorer program (‘the File Manager’). Scroll down 

the list of files and folders to look for the item “Network 

Neighborhood”. 

Double-click the “Network Neighborhood” item to display all 

stations in your Microsoft Networking Group. 

To display other workgroups in the network environment, 

double-click the “Entire Network” icon. 

If there is a second Network Operating System running in your 

network environment (for example a Novell Netware 

network), the “Entire Network” window, will also display 

available servers running under the second Network Operating 

System. 

If you click on these servers, you may be asked to enter your 

user name and password that apply to the other Network 

Operating System 

If you cannot find other (WaveLAN) networked computers 

verify whether the other WaveLAN computers are: 

● Powered up and logged on to the network. 

● Configured to operate with an identical: 

● Networking Protocol. 

● NWID or Domain ID 

● WaveLAN Operating Frequency. 

To verify the radio connection with other stations, you can also 

run the WaveMANAGER/CLIENT as described in Chapter 4. 


About Workgroups and 

Domains 3 



So far you have learned about WaveLAN Workgroups and 

Domains. 

● A WaveLAN Workgroup being the wireless coverage area 

of a number of WaveLAN stations. This could be an adhoc 

wireless workgroup of wireless stations as pictured in 

Figure 1-2 on page 1-5), or the wireless cell that is 

serviced by a single WavePOINT access point (Figure 1-3 

on page 1-6). Each Workgroup is identified by a unique 

NWID. 

● The WaveLAN Domain is group of multiple WaveLAN 

workgroups, that have been united into one wireless 

networking environment. This group of WaveLAN 

workgroups is identified by a shared Domain ID. 

When you are using Windows Networking, you will encounter 

the definitions ‘Workgroup and Domain’ in a different context, 

where 

● Windows Workgroups identify a group of networked 

computers that are logically united into a specific group of 

stations. The Windows workgroup may include both wired 

and wireless stations, and is identified by a Workgroup 

name. 

● In larger networking topologies that include Microsoft 

Windows NT servers, the LAN Administrators may have 

setup multiple ‘families’ of workgroups, where each 

family is identified by a Domain Name. 

WaveLAN Workgroups may, but do not necessarily need to 

correspond with the Windows Workgroups. WaveLAN stations 

can roam between different physical locations and, if radio 

connectivity requires switching, may connect dynamically to 

any other another WavePOINT access point. 

Doing so, the WaveLAN station may connect to another 

WaveLAN Workgroup, but will always remain in the same 

logical Windows Workgroup. 




Checking the Network 

Protocol Settings 3 

Ad-hoc networks 3 

For 

Upon initial installation, your Windows Operating system will 

typically install a basic set of networking protocols. 

You may need to check whether the installation process truly 

added the protocols and configured the protocol settings as 

required for your network environment. 

networking in ad-hoc workgroups, you will typically use 

Microsoft Networking for Windows Workgroups (Network 

Neighborhood). 

To use Microsoft Networking for Windows Workgroups, all 

stations must: 

● Use the NetBEUI protocol 

● Enable File and Print sharing 

The NetBEUI protocol can operate simultaneously with any 

other networking protocol. 

To add a protocol, or change the settings for ‘file and print’ 

sharing: 

1 Click the Start button from the Windows Taskbar. 

2 Point to ‘Settings’ and click the Control Panel item. 

3 In the Control Panel, double-click the ‘Network 

Neighborhood’ icon. 

4 Verify if the list of network components includes the 

following item: 

● Client for Microsoft Networks 

When this item is listed, skip to the next step. 

When the item is not listed, click the ‘Add’ button, and 

select Add Client to install this networking component. 

5 Next verify if the NetBEUI protocol is installed. 


● For Windows 95, scroll down the list of network 

components to look for the item ‘NetBEUI -> 

WaveLAN/PCMCIA Adapter’ 

● For Windows NT, click the tab ‘Protocols and look for 

the item ‘NetBEUI Protocol’

Infrastructure Networks 3 

When 



If the NetBEUI protocol is not listed, click the ‘Add’ 

button, and follow the instructions of the Windows 

Operating system as they appear on your screen. 

connecting your station to an network infrastructure, 

you will usually need additional networking protocols 

according to the Network Operating system. 

● IPX/SPX compatible protocols when your networking 

environment is using the Novell Netware network 

operating system. 

● TCP/IP when you would like to connect your computer to 

a network that uses IP addressing, and/or you would like to 

connect to the internet. 

These networking protocols can operate simultaneously with 

any other networking protocol. 

To verify whether your station has been configured for the 

correct type of networking and networking protocols: 



3 In the Control Panel, double-click the ‘Network 

Neighborhood’ icon. 

4 Verify if the list of network components includes the 

following items: 

● Client for Microsoft Networks 

● (optional) Client for Netware Networks If the protocol 

is already available, click the ‘Cancel’ button to exit 

this configuration screen. 

● If the items are already available, skip to the next step. 

● If the items you require are missing, click the ‘Add’ 

button and select ‘Add Client’ to add the client 

software of the networking software that you would 

like to install. 




Display WaveLAN 

Parameters 3 

Verifying the WaveLAN 

Operating Frequency 3 

5 When the proper Client software is installed, but you do 

not see the required protocols, click the ‘Add’ button, and 

follow the instructions of the Windows Operating system 

as they appear on your screen. 

Consult your LAN Administrator for more help or information 

about configuring the IPX/SPX and/or TCP/IP properties. 

When you would like to view or modify WaveLAN 

parameters, for example because you would like to connect to 

another (type of) network, proceed as follows: 



3 On the Windows Desktop, use the right mouse button to 

click the ‘Network Neighborhood’ icon. 

4 From the pop-up menu, select ‘Properties. 

5 In the Network Properties Window, select the 

WaveLAN/PCMCIA Adapter and click the ‘Properties’ 

button. 

On Windows NT systems you will be prompted to confirm 

the I/O port address and IRQ value. If your WaveLAN 

adapter is working OK, just click ‘Continue’. 

6 (Optional) Change the parameters you would like to 

modify, and click 

● Ok to confirm your changes, or 

● Cancel to ignore your modifications. 

Hint: When displaying WaveLAN parameters without intent to 

change the settings, you are advised always to use the ‘Cancel’ 

button to close the parameter windows. 

.To verify or modify the operating frequency of your 

WaveLAN radio, you can use the “Frequency Select Option” 




of the “WaveMANAGER/CLIENT” utility that is described in 

Chapter 4. 

See also “Installing WaveMANAGER/CLIENT” on page 3-30 

If you changed parameters in the “Network” window, 

Windows may prompt you to re-boot your computer. 



Installing WaveMANAGER/CLIENT 

About this Utility 3 

Installing this Utility 3 

Installing 

WaveMANAGER/CLIENT 3 

The WaveMANAGER/CLIENT is a diagnostics tool to verify 

the wireless communications quality between your WaveLAN 

station and other WaveLAN stations or WavePOINT access 

points. 

The WaveMANAGER/CLIENT was designed to run on the 

Windows 95 and Windows NT (version 4.0) operating 

systems. 

● When your computer runs the Windows NT operating 

system version 3.51 you may AT YOUR OWN RISK, try 

to install and run the program. Although the major 

functions of the program will be accessible, it is not 

guaranteed that the program will function stable. 

● When your computer runs Windows for workgroups 

(windows 3.x) you can not use the WaveMANAGER 

/CLIENT program. Restart your computer in MS-DOS 

mode and use the Diagnostics for MS-DOS for MS-DOS 

systems as described in Chapter 6. 

The installation of the WaveMANAGER/CLIENT utility is 

controlled via a so-called Installshield wizard. To install 

WaveMANAGER/CLIENT: 

1 Insert the WaveLAN diskette for Windows 95 and 

Windows NT environments 

2 Click the ‘Start’ button on the on the Windows Taskbar. 

3 Click ‘Run’ and type the path to the install program. 

● At the prompt type ‘A:\setup.exe’ 



Installing WaveMANAGER/CLIENT 

● Alternatively click the Browse button, and navigate to 

the disk drive and directory that contains the 

WaveLAN software. and double-click the ‘setup.exe’ 

program. 

4 Click OK to confirm and start the WaveMANAGER/ 

CLIENT installation. 

5 Follow the instructions as they appear on your screen. 

The Installation program will copy the 

WaveMANAGER/CLIENT program with the associated online 

help files to your harddisk drive, and create an icon on the 

‘Programs’ menu. 

When the installation program has finished, skip to Chapter 4, 

“Diagnostics for Windows 95 & Windows NT” 



Diagnostics for Windows 95 & Windows NT 

Chapter 4 

Diagnostics for Windows 95 & 

Windows NT 

WaveMANAGER/CLIENT 4-1 

Monitoring Options 4-1 

Running WaveMANAGER/CLIENT 4-3 

Using Link Test 4-5 

Using Site Monitor 4-9 

Logging Measurement Data 4-14 

Other Options 4-17 

Frequency Select Option 4-17 

Access Control Table Manager 4-18

Monitoring Options 4 

Diagnostics for Windows 95 & Windows NT4 

WaveMANAGER/CLIENT 


Once your network has been configured and installed, you can 

use WaveMANAGER/CLIENT to: 

● Monitor the performance of your network; 

● Verify optimal placement of your WavePOINT-II access 

points and wireless stations. 

WaveMANAGER/CLIENT is a ‘mobile’ wireless utility that 

can only run on a WaveLAN equipped station, typically a 

portable device such as a notebook computer. 

WaveMANAGER/CLIENT includes: 

● Monitoring Options 

● Logging Measurement Data 

● Frequency Select Option 

● Access Control Table Manager 

WaveMANAGER/CLIENT offers two monitoring methods: 

● Link Test, and 

● Site Monitor 

For on-line help, press the F1 

Function Key on your keyboard 

or click the ‘Help’ button on the WaveMANAGER window. 

Both the Link Test option and Site Monitor allow you to store 

Measurement data, as described under “Logging Measurement 

Data” on page 4-14. 



WaveMANAGER/CLIENT 

Link Test 4 

Site Monitor 4 

You 

The 

can use the Link Test option to investigate a specific link 

between two wireless stations. 

In Link Test mode, the Link Test partners exchange data 

packets to determine the link quality. 

You can use the measurement results to analyze the radio 

frequency path between the two partners in more detail. 

monitors a specific link between two stations and can therefore 

be used to analyze the Link Test quality of the communications 

path with the Link Test Partner. 

Site Monitor option enables you to display the 

communications quality of multiple WavePOINT-II units 

simultaneously. You can use the Site Monitor to: 

● Determine the overall wireless coverage of your 

WaveLAN network. 

● Determine or optimize the placement of your WavePOINT 

access points, in order to provide seamless connectivity to 

mobile stations. 

In Site Monitor mode, the WaveMANAGER/CLIENT station 

will listen for beacons transmitted by all WavePOINT access 

points to determine the communications quality for each 

WavePOINT. 

Roaming throughout the wireless network environment with 

your WaveMANAGER/CLIENT station, you will be able to 

identify areas that may not have adequate coverage, or that 

suffer from in-band interference by other (wireless) equipment 

such as security gates, microwave ovens or photo copiers. 

This will help you to verify and optimize the placement of 

your WavePOINT-II units. 

Every location where wireless stations will be used must be 

covered by at least one WavePOINT that provides a 

communications quality that is acceptable or better. 


Figure 4-1 

4WaveMANAGER/CLIENT 

Main Window 

Main Window 4 

This 


Running WaveMANAGER/CLIENT 

Running 


To start WaveMANAGER/CLIENT: 

1 Click the Start button in the Windows Task bar 

2 Point to ‘Programs’ and select the item ‘WaveLAN’ 

3 In the list of WaveLAN program files select 

‘WaveMANAGER CLIENT’ to open the window pictured 

in Figure 4-1. 

opening window of WaveMANAGER/CLIENT first will 

give an indication of the connection from your 

WaveMANAGER/CLIENT station to the network surrounding 

the nearest WavePOINT-II unit. 

The Communications Quality indicator displays the quality of 

the link between the management station and the WavePOINT- 

II unit identified in the ‘Network Connection’ field. 




The Communications Quality is displayed as one of the 

following colors and descriptions: 

Color Description 

● Green Communication Quality is good, no intervention 

is required 

● Yellow Communication Quality is acceptable, no 

intervention ia required. 

● Red Communication Quality is poor, intervention is 

required (see Appendix D, “Troubleshooting”) 

● Blank No connection 

If the Communications Quality indicator is fully red and 

displays ‘No connection, no access point found’, your 

WaveMANAGER Station has been configured for operation in 

a wireless infrastructure as described in Chapter 1, 

“Introduction”. 

When the ‘Network Connection’ field does not list a 

WavePOINT name, your WaveMANAGER/CLIENT Station 

may be: 

● Out of range of the WavePOINT units or, 

● Use a Domain ID value that does not match the value of 

the network (see “Selecting other Domain IDs” on page 

4-12) 

For information on possible solutions, please refer to 

Appendix D, “Troubleshooting”. 

When the communications quality indicator is blank and 

displays “Not available”, your WaveMANAGER Station is 

configured for operation in an ad-hoc wireless workgroup; i.e. 

roaming is disabled (see “Selecting another Link Test Partner” 

on page 4-8 for more detailed information). 


Using Link Test 4 



You can use the Link Test to monitor one specific link 

between: 

● two stations in a point-to-point link 

● two WaveLAN computers in an ad-hoc wireless 

workgroup (see Figure 1-2 on page 1-5) 

● A WaveLAN computer and a WavePOINT-II unit in a 

WaveLAN Infrastructure environment (see Figure 1-3 on 

page 1-6). 

The communications quality of the link is expressed in terms 

of a general quality indication, the SNR value of the link and 

the number of packets received and lost. Each of the values 

shown is the result of several measurements carried out during 

a certain interval. 

The Link Test can be performed from stations with either a 

WaveLAN/PCMCIA card or an ISA card. This station could 

be a WaveMANAGER Station or an ordinary workstation. 

In Link Test mode, your WaveMANAGER Station will stick to 

the Link Test partner, i.e., roaming between WavePOINTs will 

be disabled for the run-time session of the Link Test. 

To start the Link Test, click the ‘Link Test’ button in the 

opening window of WaveMANAGER/CLIENT. This will 

display the window as show in Figure 4-2: 




Figure 4-2 

4WaveMANAGER Link Test 

The Link Quality indicator shown in the top section of the 

window gives a first impression of the communications quality 

of the current link, which is the link between the local and the 

remote stations shown below the link quality indicator. 

The link quality is displayed as one of the following colors and 

descriptions: 

Color Description 

● Green Good, communication quality is good, no 

intervention required 

● Yellow Acceptable, the communications quality is 

acceptable, no intervention required 

● Red Poor, the communications quality is poor, 

intervention is required (refer to Appendix D, 

“Troubleshooting”) 

● Blank No connection, select a Link Test partner 

The ‘Advice’ button will provide more information about the 

Link Quality qualification and, if applicable, provide 

suggestions to improve the Link Quality. 


Analyzing Link Quality 4 

Resetting the diagnostic 

counters 4 

When 



you want to investigate the Link Quality in more detail, 

the fields in the middle of the window show the 

communications quality in terms of the SNR value of the link. 

The bottom field shows the percentage of packets received 

compared to the number of packets sent. 

To investigate Link Quality results in more detail, you can use 

one of the following options: 

● Freeze the display by clicking the ‘Freeze’ button 

● Display details by clicking the ‘Details’ button 

For example, when the Signal to Noise (SNR) indicator 

displays a value that is less than expected, the Details view will 

show whether this is due to a low signal level (stations are too 

far apart) or a high noise level (a source of interference that is 

located in the communications path between the two Link Test 

partners). 

You can use the Local/Remote indicators to identify whether 

the cause of reduced performance is in the area of the Link Test 

partner (Remote) or in the vicinity of the WaveMANAGER 

Station (Local). 

Signal Quality is a measure of the “clarity” of the signal. This 

indicator needs special attention only when performing Link 

Tests to diagnose the impact of signal reflections caused by 

high ceilings or reflecting surfaces such as steel structural 

components. 

You may wish to reset the diagnostic counters in order to 

restart the Link Test measurements. 

An example of a situation in which this may be useful is when 

you have traced and remedied a case of poor performance; e.g. 

you switched off a photocopier, which was causing 

interference. Clicking the ‘Reset’ button will analyze the Link 

Quality once again, ignoring negative results that were 

possibly influenced by the source of interference. 




Selecting another Link Test 

Partner 4 

Figure 4-3 

4Selecting another Link Test 

Partner or NWID 

To investigate the link with another station or access point, 

click the ‘Other’ button. This will display the window shown 

in Figure 4-3: 

● To select another Link Test partner, select a station from 

the remote station list in the right half of the window. 

● To scan for other stations within the same wireless cell, 

click the ‘Scan for Stations’ button. This will display all 

stations within range of your WaveMANAGER Station 

that use the same NWID, as shown in the NWID field in 

the left half of the window. 

Click OK to start the Link Test with the selected station. 

To set up a Link Test with a station in another wireless cell: 

1 Enter the correct NWID value in the NWID field. 

2 Click the ‘Apply’ button. 

3 Click the ‘Scan for Stations’ button to display a list of 

stations within range of your WaveMANAGER Stations 

that use the new NWID value. 

4 Select a remote station. 


Using Site Monitor 4 



5 Click the ‘OK’ button to start the Link Test with the 

selected station. 

When you are connected to a WaveLAN Infrastructure, but 

you do not know the NWID values of other workgroups in the 

Domain, you can also click the ‘Scan for NWIDs in this 

Domain’ button. This will allow you to retrieve a list of 

NWIDs from other workgroups within in your infrastructure, 

that are within range of your station. 

6 Click the ‘Scan for NWIDs in current domain’ button. 

7 Select a NWID from the displayed list. 

8 Click the ‘Apply’ button. 

You can use the Site Monitor to display the quality of 

communications with multiple WavePOINT units 

simultaneously. It shows which WavePOINT units are 

available, and of the available WavePOINT units, it shows the 

communications quality. 

The Site Monitor option is available only to 

WaveMANAGER/CLIENT Stations equipped with a 

WaveLAN PCMCIA card. To use the Site Monitor, the 

WaveMANAGER/CLIENT Station must have the roaming 

options enabled. 

To start the Site Monitor, click the ‘Site Monitor’ button in the 

main window of WaveMANAGER/CLIENT. This will display 

the following window: 




Figure 4-4 

4Site Monitor Window 

Each row displays the communications quality with the 

WavePOINT units identified in the first column. When this 

column does not display all WavePOINTs, some of the units 

may be out of range of your WaveMANAGER Station. 

You can use the pull-down menus of the other columns to 

display a variety of diagnostic tallies in the format and 

arrangement that you prefer. The recommended set of tallies 

for most monitoring tests is as follows: 

● SNR (Signal to Noise Ratio) 

● Signal level 

● Local Noise level 

● Remote Noise level 

The Signal to Noise (SNR) ratio is calculated as the sum of 

Signal Level minus Noise Level, where Noise Level represents 

the highest value of either Local or Remote Noise at the time 

of measurement. 

You will need the Signal Quality indicator only in exceptional 

circumstances, for example when you are performing a site 

survey in environments with high ceilings or where reflecting 

surfaces, such as steel structural components might cause 

excessive signal reflections. 




The colors used to express the various parameters are the same 

as those used on WaveMANAGER/CLIENT’s opening 

window. 

When walking through your wireless LAN environment, each 

location should be covered by at least one WavePOINT that 

provides an SNR that is acceptable (yellow) or better (green). 

If the Signal to Noise Ratio is of poor quality, use the 

information in the other columns to obtain additional 

information. If this does not sufficiently clarify the reasons for 

the poor quality, please refer to the chapter Troubleshooting. 

If the first column does not display all WavePOINT units you 

may have expected, you may be out of range or your 

WaveLAN card has been configured with a Domain ID that is 

different from that of the subnet you are trying to diagnose. 

To change the list of WavePOINT units for which information 

is displayed, or to log the measurement data, perform one of 

the following actions, activated by the buttons along the 

bottom of the window: 

● To detect other wireless domains, click the ‘Detect’ button 

● To select another Domain ID or other WavePOINT units, 

click the ‘Domain/Other’ button 

● To reset the diagnostic counters, click the ‘Display/Reset’ 

button 

● To sort the list of WavePOINT units, click the ‘Display/AP 

Sort’ button 

● To set parameters for the logging function, click the 

‘Logging/Setup’ button 

● To start or stop the logging function, click the 

‘Logging/Once, Start or Stop’ button 




4 Selecting other Domain IDs If 

Figure 4-5 

4Domain Selection Dialog Box 

the Site Monitor did not list the WavePOINT units you 

expected, you may need to select another Domain ID. 

This may happen in situations where your 

WaveMANAGER/CLIENT station has been configured with a 

Domain ID which is different from the Domain ID used by the 

network under investigation. 

The ‘Select another Domain ID’ option enables you to: 

● temporarily change the Domain ID used by your 

WaveMANAGER/CLIENT station, or 

● scan for the presence of other wireless domains in the 

vicinity. 

To do so, click the ‘Other’ button in the domain section at the 

bottom of the window. This will display the following dialog 

box: 

To change the Domain ID of your WaveMANAGER/CLIENT 

station, enter a new Domain ID in the ‘Domain ID’ field. In 

addition to the Domain ID, you may need to enter a correct 

beacon key value in order to decode the network IDs of the 

WavePOINT units shown. Click OK to confirm the new 

Domain ID. 


Resetting the diagnostic 

counters 4 

Sorting the list of 

WavePOINT units 4 



The new Domain ID value will be valid only for the run-time 

session of the WaveMANAGER/CLIENT program. When you 

exit the program, your wireless station will revert to its usual 

Domain ID value, as identified for the WaveLAN adapter in 

the “Network Neighborhood” properties of your station. 

To scan for the presence of other wireless domains, click the 

‘Detect’ button. If there are other wireless domains in the 

vicinity of your WaveLAN network, the ‘Detect’ option will 

show all other Domains with the number of access points that 

belong to it. 

You cannot retrieve the Domain ID or NWIDs of the 

neighboring WaveLAN networks. 

You may wish to reset the diagnostic counters in order to 

return all values of the parameters to their initial values and to 

restart all measurements. To do so, click the ‘Reset’ button in 

the ‘Display’ field of the Site Monitor window. A reset will 

also clear the WavePOINTs that are no longer within range. 

The list of WavePOINT units is sorted in descending order of 

the SNR values as they were registered when you opened the 

Site Monitor screen. 

When you have moved along through the area covered by the 

network, you may wish to sort the list of WavePOINT units in 

order to show the WavePOINT units with the best 

communications quality at the top of the list. 

To sort the list of access points again in its new order of SNR 

values, click the ‘AP Sort’ button. 

When you use the logging option (see “Logging Measurement 

Data” on page 4-14), please note that sorting the list of access 

points may affect the listings in your logfiles as well. 




Logging Measurement 

Data 4 

Manual Logging 4 

The 

The WaveMANAGER/CLIENT logging option enables you to 

save measurement data for later evaluation or comparison with 

previous measurements. You can view saved logfiles with any 

ASCII editor, or import the data into standard spreadsheet or 

database applications. The logfiles are saved in Comma 

Separated Value (CSV) file format. 

Both Site Monitor and Link Test enable you to log 

measurement results, for later evaluation. The measurement 

data can be logged automatically at regular intervals or 

manually. 

WaveMANAGER/CLIENT saves the data to Comma 

Separated Value (CSV) logfiles that can be imported into 

standard spreadsheet or database applications for further 

analysis. 

Comparison of measurement data with previous measurements 

may help you investigate the performance of your wireless 

LAN over a period of time, for example to analyze the 

consequences of relocated network equipment. To perform the 

comparison, use the functionality of your spreadsheet or 

database applications into which you import the data from the 

logfiles. 

manual logging function allows you to log the 

measurement data at specific locations and moments, e.g., 

when you are running Site Monitor to perform a site survey or 

when you are investigating a particular source of interference. 

When you choose the manual mode, you may wish to enable 

the ‘Add extra info’ option to allow you to add comments to 

your logging information, e.g. a description of the location or 

event. If you enable this option, a dialog box will appear each 

time you press the Log ‘Once’ button. 

The Manual Logging option is typically used on 

WaveMANAGER/CLIENT stations that roam throughout the 

network environment running Site Monitor. 


Automatic Logging 4 

Setting the Logging 

Options 4 

Figure 4-6 

4Logging Setup Dialog Box 

Starting or Stopping the 

Logging Function 4 

The 



automatic logging function allows you to log the network 

performance over a longer period of time. This may be useful 

if you wish to monitor recurring events or variation in values. 

When you choose the automatic mode, you need to set the 

measurement interval to the required number of seconds. 

Automatic logging is typically used when the 

WaveMANAGER/CLIENT station is running a Link Test at a 

particular location. 

To set the logging options, click the ‘Setup’ button in the 

‘Logging’ field. This will display the following window. 

In both modes, the measurement data is saved in the file 

entered in the ‘Path and file name’ field. Each time new data is 

saved, this information is added to the existing file. If you wish 

to save the data in a new file, use this field to enter a new file 

name. 

Depending on your choice of logging option, the button to the 

right of the ‘Setup’ button on the WaveMANAGER/CLIENT 

diagnostics windows will be labeled ‘Once’ (manual option) or 

‘Start’ (automatic option). 

If you chose the manual option, click the ‘Once’ button each 

time you wish to log data. 




For the automatic option, click the ‘Start’ button. Click this 

button again to stop the logging function. 

To change the logging option, proceed as described in “Setting 

the Logging Options” on page 4-15. 


Frequency Select Option 4 


Other Options 

Other Options 4 

The WaveMANAGER/CLIENT is primary a diagnostics tool. 

It includes however also two other options that enable you to 

control your WaveLAN network: 

● Frequency Select Option 

● Access Control Table Manager 

The Frequency Select option enables you to verify or modify 

the operating frequency of your WaveLAN Card. The number 

of selectable channels is subject to local regulations. 

The WaveMANAGER/CLIENT Frequency Select option 

enables you to: 

● Check the operating frequency of any WaveLAN card. 

● Change the operating frequency of a WaveLAN 2.4 GHz 

card. 

Note: When you are running an MS-DOS based system, you can 

check or change the frequency of your WaveLAN Card using 

the Frequency Select Utility described in Chapter 7. 

The factory installed operating frequency of a 2.4 GHz card is 

2.422 GHz. Use Frequency Select to select a different 

frequency when: 

● Your existing WaveLAN network (e.g. with WavePOINTs 

and WaveLAN cards) operates at another radio frequency. 

● Your wireless network suffers from interference by other 

wireless devices. 

Earlier versions of WaveLAN/ISA and Micro Channel cards 

and WavePOINT access points can operate at one fixed 

frequency only. To comply with local regulations these 



Other Options 

Access Control Table 

Manager 4 

products have been set to operate at one of the following 

frequencies: 

● 2.425 GHz (WaveLAN Channel Type_A) 

● 2.460 GHz (WaveLAN Channel Type_B) 

● 2.4305 GHz (WaveLAN Channel Type_D) 

You can determine the frequency used by already-installed 

WaveLAN cards by running this utility. 

The frequency of a WavePOINT can be determined from the 

last 4 digits of the model number, printed on a label on the 

back of the unit. Use the following list to convert the model 

number to the associated frequency channel: 

● 3105-0111 (WaveLAN Channel Type_A) 

● 3105-0112 (WaveLAN Channel Type_B) 

● 3105-0114 (WaveLAN Channel Type_D) 

If you are not certain about the frequency used by your 

WaveLAN products, contact your local supplier. 

The Access Control Manager is an advanced option for 

network administrators that would like to implement the 

Access Control security feature for WavePOINT access points. 

This feature enables the network administrator to restrict 

access to WavePOINT access points to a limited number of 

authorized WaveLAN stations. These authorized stations are 

identified by the unique MAC Address of their WaveLAN 

Card. 

When Access Control for the WavePOINT is enabled, the 

WavePOINT will only forward messages from/to stations that 

are listed in a so-called Access Control Table. 


Create the Access Control 

Table 4 

Edit an existing table 4 

To 


Other Options 

You can use the Access Control Manager to: 

● Create, or edit the Access Control Table 

● Add this station’s MAC Address to the table 

● Remove stations from the Access Control Table. 

To create an Access Control Table: 

1 Start the WaveMANAGER/CLIENT program 

2 Click the button ‘Access Control’ from the 

WaveMANAGER/CLIENT Main window. 

3 In the top field of the window, enter the path and file name 

that you would like to assign to the Access Control Table 

file (*.tbl). 

4 Click the Save button to save the Access Control Table 

file. 

When you do not specify a path or name, the Access 

Control Table Manager will save the file with the default 

name in the WaveMANAGER/CLIENT program 

directory: 

c:\program files\wavelan\wavemanager\client\wpaccess.tbl 

You can now edit the Access Control Table file, or add this 

station’s MAC address to the Access Control Table file. 

5 When finished, click the button ‘Save’ again to save your 

modifications to the Access Control Table file. 

edit the Access Control Table file, you will first need to 

open an existing file, or create a file as described above. 

To open a file: 


2 In the Main window, click the button ‘Access Control’, to 

start the Access Control Table Manager. 

3 Click the button ‘Open’ to open the default file, or enter 

the path and file name that identifies the Access Control 

Table file of your choice. 

4 You can now: 

● Add stations to the Table 



Other Options 

Add stations to the Table 4 

You 

● Remove stations from the Table. 

● Modify a station’s Description 

5 When finished, click the button ‘Save’ to save your 


can add stations to the Access Control Table manually or 

automatically. 

To add stations manually, you will need to know the Universal 

MAC Address of the WaveLAN cards that have been inserted 

into your wireless stations: 

1 Enter the Universal MAC Address of the station’s 

WaveLAN Card 

2 (Optional) Enter a description of the station associated 

with the MAC Address (e.g. Harry’s Notebook) 

3 Click the ‘Add’ button to add the address to the ‘Access 

Control Table Contents’ field. 

4 Repeat steps 1 to 3 for any other WaveLAN station that 

you would like to include to the Access Control Table file. 



When you do not know the MAC Addresses of all the 

WaveLAN cards in your network, you can use the retrieve the 

Universal MAC Address of your WaveLAN stations 

automatically. 

1 Create an Access Control Table file and save it to a floppy 

disk. 

2 Take this disk to each of your WaveLAN stations 

3 At each station, start the WaveMANAGER/CLIENT 

program and click the button ‘Access Control’ to start the 

Access control Table Manager. 

4 Insert the diskette into the floppy disk drive of the 

WaveLAN station. 

5 Open your Access Control Table file from the diskette 

6 Click the button ‘Read MAC from card’ to read this 

station’s Universal MAC Address. 


Remove stations from the 

Table 4 

Loading the Access Control 

Table into your WavePOINT 4 


Other Options 

7 (Optional) Enter a description of the station associated 

with the MAC Address (e.g. John’s Desktop) 

8 Click the ‘Add’ button to add the address to the ‘Access 

Control Table Contents’ field. 

9 Save the Access Control Table file back to the diskette 

10 Exit the WaveMANAGER/CLIENT program 

11 Take out the floppy disk and move on to the next 

WaveLAN station. 

12 Repeat steps 3 to 11 for any other WaveLAN station that 

you would like to include to the Access Control Table file. 

Note: For WaveLAN stations that do not support the Miniport Driver 

(typically MS-DOS and Windows 3.x platforms) you can use 

the MS-DOS utility wpaccess.exe that is described in the 

installation and operation guide for WavePOINT. This 

document can be downloaded from the WaveLAN website. 

To remove stations from the Access Control Table file: 


2 In the Main window, click the button ‘Access Control’, to 

start the Access Control Table Manager. 

3 Enter the path and file name that identifies the Access 

Control Table file of your choice, and click the button 

‘Open’ to open the file. 

4 From the ‘Access Control Table Contents’ filed select the 

MAC Address that you would like to deny access to the 

WavePOINT access point. 

5 Click the button ‘Delete’ to remove the station from the 

list of authorized stations. 

6 Repeat steps 4 and 5 for each other station that you would 

like to remove. 



The Access Control Table Manager is only a processing tool to 

collect and maintain the list of MAC Addresses for WaveLAN 



Other Options 

stations that are authorized to send/receive traffic via the 

WavePOINT access points. 

To activate Access Control for your WavePOINT devices, or to 

update the Access Control data, you will need to upload the 

Access Control Table file into the WavePOINT access points, 

using the: 

● WaveMANAGER/AP program to upload the file to 

WavePOINT-II access points. 

● WavePOINT Configurator to upload the file to previous 

generation WavePOINT access points. 

WaveMANAGER/AP requires the Windows 95 or Windows 

NT (v4.0) Operating system. 

The WavePOINT Configurator requires the MS-DOS 

operating system. 

You are advised to load the same Access Control Table file 

into all WavePOINTs in your network. 

Please refer to the user documentation that was shipped with 

your WavePOINT devices for more detailed information 

Note: You can not use the WaveMANAGER/CLIENT to activate or 

update the Access Control data into your WavePOINT access 

points. 


Chapter 5 

Installation for MS-DOS 




Installation for Card & Socket Services 5-2 

Collecting the Information 5-2 


Running the INSTALL Program 5-3 

Verifying the Installation 5-6 

Frequency Selection (2.4 GHz) 5-7 

Swapping Cards 5-7 

Enabler-based Installation 5-8 

Overview 5-8 


Copying the WaveLAN Software 5-8 

Set up the Enabler 5-9 

Driver Configuration 5-11 

Finishing Installation 5-13 

Verify the Installation 5-13 

Creating a Utilities Diskette 5-14 

Frequency Selection (2.4 GHz) 5-15

Card and Socket Services 5 

Enabler Based Installation 5 

Card 

If 

Installation for MS-DOS5 

Introduction 


Under MS-DOS there are two options to install your 

WaveLAN/PCMCIA software: 

● Card and Socket Services based installation 

● Enabler Based Installation 

Services & Socket Services (CS&SS) is commercial 

software that is usually included when you buy a new 

computer. CS&SS software is not included with the 

WaveLAN/PCMCIA Kit. 

The WaveLAN drivers and utilities have been developed to 

take advantage of PCMCIA Card and Socket Services. If your 

computer does not already have Card and Socket Services 

installed, you are advised to contact your computer’s supplier 

to determine if Card and Socket Services software is available 

for your computer, and install it if possible. 

Turn to page 5-2 for installation instructions. 

you cannot obtain suitable Card and Socket Services 

software you can install the WaveLAN/PCMCIA card using a 

program called the Enabler. 

Using the Enabler program, you will need to install the 

WaveLAN software manually, and edit the system files to set 

WaveLAN configuration parameters. 

Another situation where you might consider installing the 

Enabler is when there are constraints on conventional memory 

usage and there are no other PCMCIA cards in the system. 

For installation instructions using the Enabler program, turn to 

page 5-9. 



Installation for Card & Socket Services 

Installation for Card & Socket 

Services 5 

If Card Services and Socket Services (CS&SS) are installed on 

your computer you can quickly and easily install WaveLAN 

using the INSTALL program on the WaveLAN diskette. 

The INSTALL program will ensure that: 

● the correct versions of the WaveLAN driver, support files 

and utilities are installed and 

● all system files are updated with the correct initialization 

parameters. 

WaveLAN installation in a computer with Card and Socket 

Services is a 4-step procedure: 

1 Contact your network Administrator to collect the 

information required to connect your computer to the 

network. 

2 Install the network (client) software as supplied with your 

network operating system software. 

3 Run the WaveLAN INSTALL program from the 

WaveLAN diskette for MS-DOS 

4 Reboot the computer to verify that the drivers load 

successfully. 

5 (2.4 GHz cards only) Optionally verify and/or change the 

operating frequency of your 2.4 GHz card. 


Collecting the 

Information 5 

Installing the Network 

Operating System 5 



Before you begin the WaveLAN installation, you should 

collect the following information from your network 

administrator. The INSTALL program will ask you to supply 

this information. 

● The type of network driver required for your network 

(ODI or NDIS). 

● Whether or not the network requires your transmissions to 

be encrypted (cards with the Security Feature). 

● Whether or not the network allows you to roam with your 

WaveLAN. 

— If roaming is allowed, you will need your network's 

four digit Domain ID. Also, you should determine 

whether or not a beacon key is required and, if so, its 

four digit value. 

— If roaming is not allowed, you will need your 

network's four digit Network ID. 

The following items only apply to ODI-based networks (e.g. 

Novell NetWare): 

● The network's frame type. 

● Whether or not the network is configured to allow 

WaveLAN Power Management and, if so, the proper 

settings. Appendix C contains more information about 

Power Management. 

Use the documentation that comes with the network operating 

system to do the installation. If asked to insert a diskette 

containing an “updated”, “OEM”, or “other vendor” - 

supplied driver, insert the WaveLAN diskette in drive A:. 

Appendix B contains examples of installing a WaveLAN 

workstation driver in various network operating environments. 




Running the INSTALL 

Program 5 

5 Starting the Install Program To 

Controlling the Install 

Program 5 

The INSTALL program will check your system for PCMCIA 

Card and Socket Services software. (If no PCMCIA software 

is found, you will not be able to continue with the installation). 

The program will also: 

● Customize the installation to suit your system. 

● Modify your system files. 

The program will create a WAVELAN directory on your hard 

drive, copy the software components into that directory and 

various WAVELAN subdirectories, and modify network 

configuration details. 

start the program, slide the WaveLAN diskette into your 

floppy disk drive. From your DOS prompt, change to your 

floppy drive by typing: a: and pressing the ENTER key. 

(If your floppy drive responds to a different letter, substitute 

that letter for “a”) 

Now begin the installation program by typing install and 

pressing the ENTER key. 

Here are a few basic points to keep in mind as you progress 

through the INSTALL program: 

● Use the cursor (arrow) keys Up/Down to move up and 

down in presented lists 

● Use the cursor (arrow) keys Right/Left and the 

Backspace/Delete keys to change the value in parameter 

text fields. 

● Press the ENTER key to accepted highligthed values or to 

move to the next step of the Install program. 

● Press the F1 

function key at any time during the program 

to get a help dialog that provides information about the 

screen you are currently viewing. When you are finished 

with a help screen, press any key to return to the program. 


Working with the Install 

Program 5 

Controlling System File 

Updates 5 



● Press the F10 function key to return to the screen you were 

previously viewing. This is especially helpful if you 

accidentally press the ENTER function key before you are 

finished with a screen. 

● Press ESC 

twice in a row to exit the installation program. 

Note: If the INSTALL program asks you to insert your WaveLAN 

card even though you already have, eject the card and try reinserting 

it. If the card is properly inserted, then it should be 

recognized and the program should continue. 

The INSTALL program is designed to be as automated as 

possible. When required, the program will prompt you to enter 

or acknowledge user-configurable parameters. 

In most cases, the program will present you a text field, 

containing highlighted default values, or a series of options in 

the form of a list. The field or form will include a description 

about the type of information requested: 

For example, one of the first decisions you must make is the 

type of Network Operating System (NOS) you are going to 

use. 

The INSTALL program will automatically update your system 

files. It will, however, give you the option to rename and save 

your original files. 

● If you ignore this request, the INSTALL program will 

simply overwrite the old files. 

● If you choose to save your old files, you can always copy 

them over the new files created by the installation if you 

are having a problem getting your WaveLAN configured. 

Hint: You are advised to use the ‘Rename original files’ option. 

Doing so will enable you to restore the original configuration 

of your computer, allowing the computer to work the way it 

did before you tried to install the WaveLAN drivers. 




Finishing the Installation 5 

If 

Before the software files are copied onto your system, you will 

be given the opportunity to view, accept or modify the 

configuration settings you selected during the program. 

● If you accept the settings, the files will be copied without 

letting you review the choices you made. 

● If you choose to view the configuration settings, the 

program will display: 

— The names of the directories into which the WaveLAN 

and network software drivers will be copied. 

— Your WaveLAN card's configuration details, including 

IRQ, I/O Port and network frame type. 

If you catch any errors made during the installation, you can 

correct them using the modify option. 

you accept the settings, the system files will be copied to 

your computer. 

1 Insert your WaveLAN/PCMCIA Card into your computer 

2 Verify the Antenna Module is properly connected 

3 Reboot your computer in order to have the computer load 

the new settings. 

When the system has rebooted properly, you will be able to use 

your WaveLAN card. 

Caution! Novell NetWare install utilities will create a network 

configuration file NET.CFG. The WaveLAN INSTALL 

program also stores a set of WaveLAN parameter settings in 

this NET.CFG files. 

Some Novell NetWare install utilities always recreate the 

NET.CFG file overwriting existing parameters. When, for any 

reason, you would need to re-install the NetWare operating 

system software, always make sure to re-run the WaveLAN 

INSTALL program afterwards. 


Verifying the Installation 5 

Frequency Selection (2.4 

GHz) 5 



When the WaveLAN driver loads, a message similar to one of 

the following will be displayed: 

DOS/ODI driver: 

WLAN DOS ODI vX.xx (YYMMDD) 

PCMCIA XXXX MHz Roaming enabled Domain ID = xxxx Default 

NWID = xxxx 

Power Management disabled Security Feature Disabled 

NDIS-2 driver: 

WaveLAN DOS NDIS 2 Driver vXX.xx 

PCMCIA XXXX MHz Roaming enabled Domain ID = xxxx Default 

NWID = xxxx 


These messages indicate that your driver loaded successfully, 

with the configuration parameters displayed. 

To verify wireless performance, run the Point-to-Point 

Diagnostics Utility (described in Chapter 6). 

The factory-set operating frequency of 2.4 GHz cards is 

subject to local regulations. For most units that support 

frequency selection, the factory-set operating frequency is 

2.422 GHz. 

All WaveLAN devices within a WaveLAN network should 

operate at the same operating frequency, to allow flawless 

communication. 

If you have installed a 2.4 GHz card and intend to use it in 

networks with older WaveLAN 2.4 GHz ISA cards, Micro 

Channel cards or WavePOINTs you may need to verify and/or 

change the operating frequency of your WaveLAN/PCMCIA 

card, in order to connect it to the network that includes the 

previously installed WaveLAN products. 

Appendix D describes how to use the WFREQSEL utility to 

change the operating frequency. 




Swapping Cards 5 

The INSTALL program upgrades an internal area of the 

WaveLAN card called the Card Information Structure (CIS). 

If you replace the card by one configured with an earlier 

software release, or replace it with a new card, you should 

run the INSTALL program on the replacement card to 

ensure compatibility with the WaveLAN software installed on 

the computer. 


Overview 5 

Installing the Network 

Operating System 5 

Copying the WaveLAN 

Software 5 


Enabler-based Installation 

Enabler-based Installation 5 

Using the Enabler program, you will need to install the 

WaveLAN software manually, and edit the system files to set 

WaveLAN configuration parameters. 

The recommended installation procedure is as follows: 

1 Install the network operating system software on your 

computer. 

2 Copy the WaveLAN software to the computer’s hard disk. 

3 Edit the following system files: 

● CONFIG.SYS file 

● Network Configuration File 

(to include WaveLAN-specific parameters). 

4 Reboot the computer to verify that the Enabler executes 

successfully and the network driver is loaded. 

5 (Optionally) Create a WaveLAN Utilities Diskette. 

6 (2.4 GHz cards only) Optionally verify and/or change the 

operating frequency of your 2.4 GHz card. 

Use the documentation that comes with the network operating 

system to do the installation. If asked to insert a diskette 

containing an “updated”, “OEM”, or “other vendor” - 

supplied driver, insert the WaveLAN diskette in drive A:. 

Appendix B contains examples of installing a WaveLAN 

workstation driver in various network operating environments. 

The WaveLAN/PCMCIA disk includes a small batch file 

(cpy2hdsk.bat) that will help you to copy the 

WaveLAN/PCMCIA software to the harddisk of your 




Set up the Enabler 5 

computer. To copy the WaveLAN software, proceed as 

follows: 

1 Choose a name for the hard disk directory where the 

software will be kept, e.g. c:\wavelan 

2 Place the WaveLAN software diskette in drive A: 

3 Make drive A: the current drive 

4 Run the batch file CPY2HDSK.BAT with the chosen 

harddisk directory name as parameter. 

Example DOS commands: 

a:\ 

a: cpy2hdsk c:\wavelan 

The Enabler program must be run before any program 

(network driver or utility) can access the WaveLAN card. To 

ensure the Enabler is always run at start-up time, it should be 

executed as a “DEVICE” statement in the CONFIG.SYS file. 

Use a DOS line editor to add a DEVICE line in CONFIG.SYS. 

The DEVICE line must contain parameters for: 

● Memory space address (of a 4096-byte space). 

● I/O Base address. 

● Interrupt Request Line number (IRQ). 

Format: 

where: 

= device = []enabler.sys /m=xxxx /b=xxx /i=nn 

“[...]” Enclose optional parameters (do not type brackets). 

Disk drive and directory containing ENABLER.SYS 


Driver Configuration 5 



/m=xxxx Memory space address (4-digit hexadecimal) 

Valid range: ‘C000 - EF00’ in increments of ‘100’ (‘C000’,, ‘C100’,, 

‘C200’,, etc.) 

/b=xxx, I/O Base address (3-digit hexadecimal) 

Valid range: ‘300 - 370’ in increments of ‘8’ (‘300’,, ‘308’,, ‘310’,, 318’,, 

etc.) 

/i=nn IRQ (1- or 2-digit decimal) 

Valid values: ‘3’,, ‘4’,, ‘5’,, ‘7’,, ‘9’,, ‘10’,, ‘11’,, ‘12’,, ‘14’,, ‘15’ 

The DEVICE statement must contain parameter values for 

each card, and the values must be different for each card. 

Example statement: 

device = c:\wavelan\enabler\enabler.sys /m=d100 /b=300 /i=11 

The Enabler uses memory addresses ‘0d1000’H - ‘0d1fff’H, 

I/O base address ‘0300’H and IRQ 11. 

Note 1: Remove any other PCMCIA-related DEVICE statements from 

CONFIG.SYS. If Socket Services or Card Services are 

present, remove these also. The documentation that came with 

your computer or other PCMCIA device should help you to 

identify these statements. 

Note 2: If you are using a memory manager such as EMM386.EXE, 

the memory space required by the Enabler should be 

“excluded”. For the example above, add a line like the 

following: 

= device=c:\dos\emm386.exe noems x=d100-d1ff 

Note 3: If Microsoft Windows is installed, add a statement to 

SYSTEM.INI to protect the Enabler’s memory space. The 

statement should be added to the “386Enh” section of 

SYSTEM.INI. Example: 

= [386Enh] ... EMMExclude=D100-D1FF ... 

The following network drivers are supplied with 

WaveLAN/PCMCIA for installation on MS-DOS Systems: 




DOS/ODI Driver 

Configuration 5 

● A DOS/ODI driver to use in Novell NetWare 

environments (NetWare, Personal NetWare). The 

DOS/ODI driver uses a configuration file called NET.CFG 

● A DOS/NDIS-2 driver for NDIS-compatible environments 

such as LAN Manager and Windows for Workgroups. The 

NDIS driver uses a configuration file called 

PROTOCOL.INI 

You can place some WaveLAN-specific parameters in the 

network configuration file. 

The WaveLAN configuration parameters for the DOS/ODI 

driver are set in the file NET.CFG. A sample NET.CFG file is 

provided in the root directory of the WaveLAN software 

diskette. 

Note: When editing, be sure to place the WaveLAN parameters, 

indented, directly after the link driver statement. 

The following table on the next page lists WaveLAN-specific 

parameters with their value ranges and usage: 

Parameter Range Usage 

Socket x ‘x’ in the range [A - H,ah,x] 

NWID xxx ‘xxxx’ hexadecimal 

value in the range 0100H 

through FFFFH 

Domain ID xxxx ‘xxxx’ hexadecimal 


through FFFFH 


Identifies the PCMCIA card 

socket. (“X,x” - use first found). 

Identifies the WaveLAN Network 

ID. Required if no roaming. If used, 

must be same for all WaveLAN 

cards in the network. The default 

value is ‘0100’. Using this value 

may result in unintentional overlap 

with adjacent WaveLAN cells. 

This parameter controls roaming. 

If set to ‘0000’, Roaming is 

disabled, i.e. station does not 

connect automatically. If set to any 

other value, Roaming is enabled. 

All stations in the Domain must 

have the same Domain ID.

DOS/NDIS-2 Driver 

Configuration 5 

Beacon Key xxxx ‘xxxx’ hexadecimal 


through FFFFH 

Station Address 

xx.....xx 

Station Name x...........x Any alpha-numeric string 

(max. 31 characters - no 

spaces allowed) 

Encryption Key xx.....xx 0xnn, 8 groups of 2 

hexadecimal digits (‘nn’) 

separated by commas or 

‘0’ 

Power Up x...x Decimal value in the 

range 0- 65535 

Power Down x...x Decimal value in the 

range 0- 65535 



Used to encode the NWID 

transmitted by a Roaming access 

point. Must be same for all stations 

in the Domain. ‘0000’ = no 

encoding. 

12 hexadecimal digits Overrides the card’s factory 

installed Universal MAC 

address.The 2nd digit of the first 

digit-pair must be 2,6,A, or E 

Can be used by the Point-to-Point 

diagnostics utility. 

A 16 hexadecimal digit value 

enables encryption. The value ‘0’ 

disables encryption. 

If Power Management used, time 

in seconds that the card is in 

normal power-consuming mode. 

See Appendix C for discussion 

Time in seconds that the card is in 

low power-consuming 

‘Sleep”mode. If not used (or set to 

‘0’) Power Management will be 

disabled. 

Required Parameters: 

If the card is installed in a roaming workstation,a Domain ID is required. All other 

parameters are optional. 

If the card is not going to be used in a roaming environment a NWID is required. 

The WaveLAN configuration parameters for the DOS/NDIS-2 

driver are set in the file PROTOCOL.INI. A sample 

PROTOCOL.INI file is provided in directory 

\MSLANMAN.DOS\DRIVERS\WAVELAN of the WaveLAN 

software diskette. 

The table below lists WaveLAN-specific parameters with their 

value ranges and usage: 




Parameter Range Usage 

PCMCIA_Socket 

= x 

‘x’ in the range [A - H,ah,x 

NWID = 0xnnnn ‘nnnn’ hexadecimal value 

in the range 0100 through 

FFFF 

Domain_ID = 

0xnnnn 

Beacon_Key = 

0xnnnn 

Station_Address 

0xnn 

Station_Name = 

x..................x 

Encryption_Key 

0xnn 

‘nnnn’ hexadecimal value 


FFFF 

‘nnnn’ hexadecimal value 


FFFF 

0xnn, 6 groups of 2 


separated by commas 

Any alpha-numeric string 

(max. 31 characters - no 

spaces allowed) 

0xnn, 8 groups of 2 


separated by commas or 

‘0’ 


Identifies the PCMCIA card 

socket. (“X,x” - use first found). 

Optional parameter, defaults to 

“‘X”. 

Identifies the WaveLAN Network 

ID. Required if no roaming. If used, 

must be same for all WaveLAN 

cards in the network. The default 

value is ‘0100’. Using this value 

may result in unintentional overlap 

with adjacent WaveLAN cells. 

This parameter turns on roaming. 

If not used, or if set to ‘0x0000’, 

station cannot roam. All stations in 

the Domain must have the same 

Domain ID. 

Used to encode the NWID 

transmitted by a Roaming access 

point. Must be same for all stations 

in the Domain. ‘0x0000’ = no 

encoding. 

Overrides the card’s factory 

installed Universal MAC 

address.The 2nd digit of the first 

digit-pair must be 2,6,A, or E 

Can be used by the Point-to-Point 

diagnostics utility. 

A 16 hexadecimal digit value 

enables encryption. The value ‘0’ 

disables encryption. 

Required Parameters: 

If the card is installed in a roaming workstation,a Domain ID is required. All other 

parameters are optional. 

If the card is not going to be used in a roaming environment a NWID is required.

Finishing Installation 5 

Verify the Installation 5 



To finish the installation Insert your WaveLAN/PCMCIA 

Card into your computer and verify the Antenna 

Module is properly connected 

Reboot your computer in order to have the computer load the 

new settings. 

After installing the PC card you should reboot your computer 

to verify that the Enabler executes correctly. Correct execution 

of the Enabler is confirmed with the message (example): 

WaveLAN/PCMCIA (DOS) Enabler vx.x 

Enabler Installed: 

1. Memory: D100, IO Base: 300, IRQ: 11 

The message that indicates that the driver was loaded 

succesfully differs slightly dependent on the type of driver: 

For ODI drivers this message is similar to: 

WLAN DOS ODI vX.xx (YYMMDD) PCMCIA XXXX MHz Roaming 

enabled Domain ID = xxxx Default NWID=xxxx 

Power Management disabled Security Feature disabled 

For NDIS drivers this message is similar to: 

WaveLAN DOS NDIS 2 Driver vXX.xx PCMCIA XXXX MHz Roaming 

enabled Domain ID = xxxx Default NWID=xxxx 


To verify wireless performance, run the Point-to-Point 

Diagnostics Utility (described in Chapter 6, “Diagnostics for 

MS-DOS”). 

Note: For Enabler-Based installations, you will need a Utilities 

Diskette to run the Point-to-Point Diagnostics program. 

See Creating a Utilities Diskette for more information. 




Creating a Utilities 

Diskette 5 

The Utilities diskette is a bootable diskette which enables you 

to run the Point-to-Point Diagnostics utility or Frequency 

Select Utility (described in Chapter 6, “Diagnostics for MS- 

DOS” and Chapter 7, “Frequency Select Utility”). 

The reason why you need to create this diskette, is that these 

WaveLAN Utilities do not run when the WaveLAN driver is 

enabled via the Enabler program. 

Restarting your computer from the Utilities Diskette, will 

provide an alternative boot sequence, enabling you to run the 

WaveLAN Utilities on Enabler-based WaveLAN systems as 

well. 

The WaveLAN/PCMCIA software includes a small batch file 

(utl2boot.bat) that will help you to create the Utilities Diskette: 

1 Change to the hard disk directory where the WaveLAN 

software was installed. 

2 Insert a DOS-formatted diskette in drive A: 

3 Run the batch file UTL2BOOT.BAT. 

Example DOS commands: 

c:\ 

c: cd \wavelan utl2boot 

In order to allow the WaveLAN utilities to find configuration 

information relating to the WaveLAN card,you will also need 

to create a WAVELAN.INI file. 

4 Use an ASCII text editor, such as the MS-DOS EDIT 

program to create a file called WAVELAN.INI: 


cd\ 

cd wavelan 

edit wavelan.ini 

The WaveLAN.INI file should contain two lines that 

idenitfy the full path filename of the configuration file, and 

the type of driver installed (ODI or NDIS-2). 

Example (ODI): 

FileName=c:\nwclient\net.cfg 

FileType=netc

Frequency Selection (2.4 

GHz) 5 

Example (NDIS): 



FileName=c:\windows\protocol.ini 

FileType=prot 

5 Finally, copy the file WaveLAN.INI you created under the 

step called “Finishing Installation” on page 5-15 to your 

utilities diskette. 

c:\ 

c: cd\wavelan 

copy wavelan.ini a: 

The factory-set operating frequency of 2.4 GHz cards is now 

2.422 GHz. If you have installed a 2.4 GHz card and intend to 

use it in networks with older WaveLAN 2.4 GHz ISA cards, 

Micro Channel cards or WavePOINTs you need to change the 

PC card’s operating frequency to the one currently used by the 

older products. 

Chapter 7, “Frequency Select Utility” describes how to use the 

WFREQSEL utility to change the operating frequency. 

Note: For Enabler-Based installations, you will need a Utilities 

Diskette to run the Frequency Select program. 

See “Creating a Utilities Diskette” on page 16. for more 

information. 


Chapter 6 

Diagnostics for MS-DOS 



Point-to-Point Diagnostics 6-1 

About the Point-to-Point Diagnostics 6-1 

Running Point-to-Point Diagnostics 6-2 

Selecting the Local WaveLAN Card 6-3 

Selecting a Link Test Partner 6-3 

Changing Local Identifiers 6-4 

Search for Other Stations 6-4 

Changing the Test Partner 6-5 

The Measurement Data Display 6-6 

Positioning your WaveLAN Computer 6-7 

Logging Measurement Data 6-7 

Command Line Parameters 6-8

About the Point-to-Point 

Diagnostics 6 

Diagnostics for MS-DOS6 

Point-to-Point Diagnostics 

Point-to-Point Diagnostics 6 

The Point-to-Point Diagnostic Utility is a MS-DOS based 

utility that allows you to verify the communications path 

between two WaveLAN stations, or between a WaveLAN 

station and WavePOINT access point. 

You can use this utility to: 

● Check that cards and antennas function correctly to allow 

exchange of messages 

● Optimize antenna positioning 

● Verify whether stations are within operating range of each 

other 

● Diagnose the occurrence of local RF noise and 

environmental suitability. 

The Point-to-Point Diagnostics Utility has a log-file option, to 

save measurement data to a disk file. 

Note: The Point-to-Point Diagnostic is a MS-DOS based utility. 

If you would like to run this utility on a Windows 95/NT 

computer, the computer must have MS-DOS installed. Restart 

the computer in MS-DOS mode, as you can not run the utility 

from an MS-DOS box under Windows. 



Running Point-to-Point Diagnostics 

Running Point-to-Point 

Diagnostics 6 

If you have installed the WaveLAN client driver for Card and 

Socket Services, you can run the program from the WaveLAN 

Utilities subdirectory of the hard disk while the WaveLAN 

network driver is running (the driver becomes temporarily 

inactive). Type: 

cd \wavelan\util 

ptpdiag [Enter] 

To run the utility when the Enabler is installed, place the 

Utilities diskette in drive A: of the workstation or server and 

reboot. Type: 

ptpdiag [Enter] 

Note: The Point-to-Point diagnostic utility includes a "remote 

diagnostics" feature that allows a link test with a remote station 

without operator intervention at the remote station. Some older 

versions of the WaveLAN network drivers installed on desktop 

computers do not support remote diagnostics. For these 

WaveLAN stations you must start up Point-to-Point 

diagnostics in each station for which the communications path 

is to be tested. Check the documentation supplied withthe 

older software versions. 


Selecting the Local 

WaveLAN Card 6 

Figure 6-1 

6Main Selection Screen 

Selecting a Link Test 

Partner 6 



The opening screen allows you to select the card to use for the 

test, in case more than one WaveLAN card is present. 

The main selection screen of the utility (Figure 6-1) enables 

you to change the Network ID of the monitoring (local) station 

temporarily for this Link Test Session. You will also use this 

screen to: 

● Search for other stations running Point-to-Point 

diagnostics 

● Start a link test with a selected station. 

Note: Stations with WaveLAN power management enabled are not 

displayed, because these stations can "go to sleep" at 

unpredictable moments, thereby giving unreliable link test 

results. 




Changing Local 

Identifiers 6 

NWID 6 

Name 6 

Search for Other Stations6 

Defaults 

Defaults 

The local station’s WaveLAN Network ID (NWID) and name 

(initially the MAC address) are displayed and may be modified 

if required. The modifications are in force only for the duration 

of the test. When you exit the utility the original values are 

restored. 

to the WaveLAN Network ID set in the network 

configuration file or when the card was configured. If the card 

is not configured the default value is "0100"H. Change the 

Network ID to investigate path conditions in other WaveLAN 

cells. 

to the WaveLAN card’s MAC Address. This name 

will be displayed in the "Other Stations" box on any other 

stations in this network that are running the Point-to-Point 

Diagnostics program. Change it if a more meaningful name is 

required. 

Selecting this option causes a search to be made for all stations 

able to participate in Point-to-Point diagnostics with this 

station. The following conditions must be satisfied: 

● Same frequency band (915 MHz or 2.4 GHz). 

● Same NWID. 

● Within range. 

● Point-to-Point diagnostics running (in stations with older 

network drivers installed). 

The responding stations’ names or MAC addresses are 

displayed in the "Other Stations" box. (see Figure 6-1 on page 

6-3). 

Note: If no stations, or fewer than expected, are listed the problem 

could be: 

● Wrong NWID 

● Utility not started at one or more stations where older 

network drivers are installed. 


Changing the Test 

Partner 6 

● Antenna not properly connected. 

● WavePOINT not powered on. 



● Signal too weak. The antenna is completely shielded by a 

radio-frequency barrier or the stations are too far apart. 

● Noise level too high for signal measurement. The antenna 

of the local or remote station is too close to a noise source. 

● WaveLAN card or antenna defective. 

● Security Feature mismatch. If the security feature option 

has been installed, it is possible that one of the stations 

does not have encryption enabled or that the encryption 

key values are different (The "local" display indicates 

whether or not encryption is enabled for that station). 

● Frequency band mismatch; 2.4 GHz WaveLAN cards will 

not communicate with 915 MHz cards, nor will 2.4 GHz 

cards of different frequencies communicate with each 

other. 

● Can’t find encryption key. If the network is using the 

security feature, the Enabler is installed, and the 

encryption key is present as a parameter in the network 

configuration file, the utility needs to be able to locate the 

network configuration file to access the encryption key. 

The location of the network configuration file is given by 

the WAVELAN.INI file which must be present on the 

utilities diskette. Chapter 3 describes how to create a 

WAVELAN.INI file. 

Use the ‘Up’ and ‘Down’ arrow keys with the Enter key to 

select from the displayed list which remote station is to 

participate in the diagnostic test. After the selection is made 

the program executing at each participating station begins to 

measure signal reception conditions. Based on these 

measurements the utility displays an assessment of the Link 

quality. Link quality can be "Good", "Acceptable" or "Poor". 




The Measurement Data 

Display 6 

Figure 6-2 

6Measurement Data Display 

You can investigate the Link Quality in more detail by pressing 

[Enter] or the Cursor key to display the Measurement Data 

screen (Figure 6-2 on page 6-6). 

The utility displaysmeasurement data for both the local and 

remote stations. For each station six measurements are 

displayed: 

● Packets received - actual and expected. 

● Packets lost 

● Percentage successful packets received 

● Signal Level 

● Signal-to-Noise Ratio (SNR) 

● Signal Quality (SQ) 

The Link Quality assessment (Good, Acceptable, Poor) is 

based on the Percentage successful packets received 

(Successful RX), the SNR, and the Signal Quality (SQ) 

measurements. 


SNR 6 

Signal Quality 6 

Positioning your 

WaveLAN Computer 6 

Logging Measurement 

Data 6 

Signal-to-noise 

Signal 



Ratio is based on the strength of the received 

signal relative to the local noise. The received Signal Level is 

displayed as well as the SNR measurement. 

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. 

Some environments can cause pockets of reduced Signal 

Quality to occur in an unpredictable way. A small relocation of 

the computer or antenna is often enough to give a significant 

improvement. 

If SNR is low (



Figure 6-3 

6Measurements Log File 

Example 

Command Line 

Parameters 6 

-Sx 6 

This 

You can append data to an existing file or save to a new file, 

and you can choose to save the data once only or at regular 

intervals during the test. 

If you are a skilled computer technician, you may wish to use 

one of the following parameter options on the MS-DOS 

command line to: 

● Specify a Socket address 

● Specify a WaveLAN Network ID 

● Specify a station name 

● Select monochrome display mode 

The following parameters are shown in uppercase for clarity. 

You can also use lowercase characters. 

parameter identifies the WaveLAN/PCMCIA card’s 

socket position. Valid values are 


-Ixxxx 6 

-Nxxxxxx........xx 6 

-M 6 

Parameter Usage Example: 6 

Sets 

Sets 

Sets 

: 

Table 6-1 



A B C D E F G H X (Select first card detected) 

The-S parameters suppress display of the diagnostic utility’s 

initial screen 

the WaveLAN Network ID (xxxx is a hexadecimal value 

in the range’0100’H - ’FFFF’H). This value overrides the 

configured Network ID for the duration of the test. You can use 

this parameter to allow the station to run Point-to-Point tests in 

different networks. 

the Station Name. Any Alphanumeric combination up to 

20 characters long is allowed. 

the video mode to monochrome. Used for some 

monochrome monitors and non-standard video adapters. Try 

using this parameter if you have difficulty viewing the display. 

ptpdiag -sa -i2402 

This command will run Point-to-Point diagnostics on a 

WaveLAN card installed in the first PCMCIA socket. 

The WaveLAN Network ID is set to’2402’ for the duration of 

program execution or until changed to another value. The links 

can be tested between this station and other stations or 

WavePOINTs that use this Network ID. 


Chapter 7 

Frequency Select Utility 



About the Frequency Select Utility 7-1 

Do I Need to Use This Utility? 7-1 

Running the Frequency Select Utility 7-3 

Select a New Frequency 7-4 

Command line parameter 7-4


Frequency Select Utility

Do I Need to Use This 

Utility? 7 

Frequency Select Utility7 

About the Frequency Select Utility 

About the Frequency Select 

Utility 7 

The Frequency Select Utility is a MS-DOS based utility that 

allows you to: 

● Check the operating frequency of any WaveLAN card. 

● Change the operating frequency of a WaveLAN 2.4 GHz 

card. 

Note: When you are running a Windows 95 or Windows NT system, 

you can check or change the frequency of your WaveLAN 

Card using the WaveMANAGER/CLIENT utility described in 

Chapter 4. 

The factory installed operating frequency of a 2.4 GHz card is 

2.422 GHz. You can use the Frequency Select Utility in any of 

the following situations: 

● Your existing WaveLAN network (e.g. with WavePOINTs 

and WaveLAN cards) operates at another radio frequency. 

● Your wireless network suffers from interference by other 

wireless devices. 

Earlier versions of WaveLAN ISA and Micro Channel cards 

and WavePOINT access points can operate at one fixed 

frequency only. To comply with local regulations these 

products have been set to operate at one of the following 

frequencies: 



About the Frequency Select Utility 

2.425 GHz (WaveLAN Channel Type_A) 

2.460 GHz (WaveLAN Channel Type_B) 

2.4305 GHz (WaveLAN Channel Type_D) 

You can determine the frequency used by already-installed 

WaveLAN cards by running this utility. 

The frequency of a WavePOINT can be determined from the 

last 4 digits of the model number, printed on a label on the 

back of the unit. Use the following list to convert the model 

number to the associated frequency channel: 

3105-0111 (WaveLAN Channel Type_A) 

3105-0112 (WaveLAN Channel Type_B) 

3105-0114 (WaveLAN Channel Type_D) 

If you are not certain about the frequency used by your 

WaveLAN products, contact your local supplier. 

Note: The Frequency Select Utility is a MS-DOS based utility. 

If you would like to run the utility on a Windows 95/NT 

computer, the computer must have MS-DOS installed. Restart 

the computer in MS-DOS mode, as you can not run the utility 

from an MS-DOS box under Windows. 


Figure 7-1 

7Frequency Select screen 


Running the Frequency Select Utility 

Running the Frequency Select 

Utility 7 

If you have installed the WaveLAN client driver for Card and 

Socket Services, you can run the program from the WaveLAN 

Utilities subdirectory of the hard disk while the WaveLAN 

network driver is running (the driver becomes temporarily 

inactive). Type: 

cd \wavelan\util 

wfreqsel [Enter] 

To run the utility when the Enabler is installed, place the 

Utilities diskette in drive A: of the workstation or server and 

reboot. Type: 

Type: wfreqsel and press [Enter] 

The program will ask you to select the WaveLAN PCMCIA 

card socket. Use the cursor control keys to select the socket, 

and press [Enter]. 



Running the Frequency Select Utility 

Select a New Frequency 7 

Command line parameter7 

Use the cursor control keys to select another frequency from 

the displayed list. 

Press [Enter] to program this operating frequency into your 

card. The WaveLAN card will use the new frequency until the 

Frequency Select Utility is run again. 

Press the [F10] key to quit the utility. 

You can use the parameter option -M on the MS-DOS 

command line to select a "Monochrome Display" mode. Try 

this parameter if you have difficulty viewing the display in 

normal colour mode. 

Example: 

wfreqsel -m 


Chapter 8 

Installation for Apple 

Powerbook Systems 


Installation for Apple Powerbook Systems 


What You Need to Know 8-1 

Removing and Re-inserting your Card 8-2 

Installing in Ethertalk TCP/IP Environments 8-3 

Installing the AppleTalk Software 8-3 

Configuring your WaveLAN Card 8-5 

Classic and Open Transport Environments 8-8 

Which one to Choose? 8-8 

Installing the Classic Networking Software 8-9 

Installing the Open Transport Software 8-10 

Configuring your WaveLAN Card 8-11 

Enabling AppleTalk for Classic 8-12 

Enabling Apple Talk for Open Transport 8-13 

Enabling TCP/IP for Classic 8-14 

Enabling TCP/IP for Open Transport 8-15


Installation for Apple Powerbook Systems

What You Need to Know8 

Installation for Apple Powerbook Systems8 

Introduction 


The Macintosh WaveLAN software has been developed to take 

advantage of Apple’s PC Card Manager and the Apple 

networking software extensions. The WaveLAN drivers for 

Apple Powerbook computers are available in two versions: 

● WaveLAN drivers for Macintosh computers that use the 

networking software for Installing in Ethertalk TCP/IP 

Environments, or 

● WaveLAN drivers for Macintosh computers that use the 

networking software for Classic and Open Transport 

Environments. 

Both type of drivers are available on the WaveLAN software 

diskette that came with your WaveLAN product. You can also 

download these drivers from the WaveLAN website at 

http://www.wavelan.com. 

To decide which driver you will need, please consult the User 

Documentation that came with your Apple Powerbook 

computer to determine what type of networking software 

extensions are supported by your Apple Powerbook Computer. 

When installing and configuring your WaveLAN/PCMCIA 

Card for the very first time, please be aware that to enable your 

system to read the card’s settings, you must power up your 

system first, prior to ‘introducing the card to your Apple 

Powerbook system. 

When you would insert the card, prior to powering up the 

system, the driver software will not be able to read the settings 

of the card, and will display the card's MAC address as all 

zeros. 

When configuring your WaveLAN/PCMCIA card for the very 

first time, proceed as follows: 



Introduction 

Removing and Reinserting 

your Card 8 

1 Power up your computer. 

2 Install the Networking Software 

3 Insert the WaveLAN/PCMCIA card. 

4 Select AppleTalk to enable the card. 

5 Use the WaveLAN Setup Control Panel to configure the 

card. 

Once your WaveLAN/PCMCIA card has been configured, you 

can insert your WaveLAN card either before or after you boot 

your Powerbook System. 

When ‘introducing’ another WaveLAN/PCMCIA card to the 

same system, for example when replacing a defect card, you 

will need to repeat this procedure. 


Installing the AppleTalk 

Software 8 


Installing in Ethertalk TCP/IP Environments 

Installing in Ethertalk TCP/IP 

Environments 8 

The networking software components for EtherTalk and 

TCP/IP environments are included with the System Software 

Installer provided with the Macintosh 5300 and 190 

PowerBook computers. Apple will also make a version of the 

PC Card Manager available for the PowerBook 500 PC Card 

extension module. 

When your Powerbook system does not support the Ethertalk 

networking extensions skip to “Classic and Open Transport 

Environments” on page 8-8. 

Before you can install the WaveLAN networking software, 

you must have Apple's EtherTalk and AppleTalk networking 

software installed. For your convenience, we have included 

version 1.5.1 of Apple's “Network Software Installer” on the 

WaveLAN disk for Apple Powerbook environments. 

You can run this installer to make sure you have the proper 

version installed on your computer. This version of the 

installer has been modified to install “EtherTalk for PC Cards” 

as an option. This will install the required EtherTalk and 

AppleTalk networking software needed to support the 

WaveLAN driver. You will be forced to restart your system if 

you are installing onto your current system disk 




Figure 8-1 

8 

Installing TCP/IP 8 

Figure 8-2 

8 

Installing WaveLAN 8 

The 

To 

TCP/IP networking software is not installed by default, so 

you will need to use the System Software Installer that came 

with your computer to add TCP/IP. Use the Custom Install 

option, and select TCP/IP from the Networking Software 

option list. You will be forced to restart your system if you are 

installing onto your current system disk. 

install the WaveLAN networking software: 

1 Double-click the “WaveLAN® Installer” icon. 

The WaveLAN Installer will: 

● remove earlier versions of the driver, and 

● install this latest version into your system. 

2 When finished, restart your computer. 


Figure 8-3 

8 

Configuring your 




After you restart, you can insert a WaveLAN PC Card into 

either card slot and use the WaveLAN Setup control panel to 

(re-)configure the WaveLAN parameter settings. Balloon help 

is available for each of the items shown in the WaveLAN 

Setup control panel dialog. 

Note: If you are trying to install your WaveLAN PC Card, in some 

cases the configuration software may not work. This is 

typically the case when it concerns a (previously purchased) 

older type WaveLAN/PCMCIA card. 

When the WaveLAN configuration software detects this type 

of card, it will: 

● Display an Alert dialog, and 

● Create a button on the WaveLAN Setup control panel, 

labelled “Update CIS...” 

Use this button to update the Card Information Structure (CIS) 

of your WaveLAN card. This update will allow your 

WaveLAN/PCMCIA card to work with the Macintosh 

software, but should not effect your ability to use the updated 

card in other operating system environments. 




Figure 8-4 

8 

Enabling AppleTalk 8 

Figure 8-5 

8 

You 

can select AppleTalk to use the WaveLAN card by starting 

the Network Control Panel from under the Apple Menu, or by 

double-clicking the “WaveLAN PC Card” icon on the desktop 

when the card is inserted. Then select the “EtherTalk 

Alternative” icon to enable AppleTalk to use the WaveLAN 

card as its network interface. 


Enabling TCP/IP 8 

Figure 8-6 

8 

You 



can select MacTCP to use the WaveLAN card by starting 

the MacTCP Control Panel from under the Apple Menu when 

the card is inserted. Then select the “Ethernet Built-In” icon to 

enable TCP/IP to use the WaveLAN card as its network 

interface. You will need to restart your computer for these 

changes to take effect. 



Classic and Open Transport Environments 

Which one to Choose? 8 

Classic and Open Transport 

Environments 8 

The networking software components for Apple Classic or 

Apple Open Transport environments are included with the 

MacOS System Software Installer provided with the Apple 

PowerBook 1400, 5300, and 190 computers. 

When your Powerbook system does not support the Classic 

and/or Open Transport networking extensions return to 

“Installing in Ethertalk TCP/IP Environments” on page 8-3. 

The installation described in this section covers two types of 

networking software for Apple Powerbooks: 

● Apple Classic, for Apple Powerbook devices based on the 

Motorola 680x0 processor, and 

● Apple Open Transport, for Apple Powerbook devices 

based on the PowerPC processor. 

Before you can install the WaveLAN networking software, 

you must have either the Apple Classic or the Apple Open 

Transport networking software installed. The installer included 

with this release will detect and install the appropriate version 

of the WaveLAN software. 

Note: The 2400 Apple PowerBook does NOT support a Classical 

Driver. 

● Turn to page 8-9 for Installing the Classic Networking 

Software 

● Turn to page 8-10 for Installing the Open Transport 

Software 


Installing the Classic 

Networking Software 8 

Figure 8-7 

8 

Minimum Installation 8 

For 



The Classic TCP/IP networking software is not installed by 

default, so you will need to use the System Software Installer 

that came with your computer to add TCP/IP. Use the Custom 

Install option, and select TCP/IP from the Networking 

Software option list. When finished, restart your computer. 

your convenience, we have included version 1.5.1 of 

Apple's Classic “Network Software Installer” on the 

WaveLAN disk for Apple Powerbook environments. You can 

run this Installer to install the basic networking software on 

your 680x0 computer. 

Network Software Installer version 1.5.1 has been modified to 

install “EtherTalk for PC Cards” as an option. It will install the 

required EtherTalk and AppleTalk networking software needed 

to support the WaveLAN driver 

Note: The Network Software Installer version 1.5.1 does not include 

TCP/IP. 

When finished running Network Software Installer, restart 

your computer. 




Figure 8-8 

8 

Installing the Open 

Transport Software 8 

Figure 8-9 

8 

Apple now installs the Open Transport networking software by 

default with all versions of the MacOS. If your computer does 

not have Open Transport installed, you will need to use the 

System Software Installer that came with your computer, or 

obtain a copy of the latest Open Transport software from 

Apple. 


Installing WaveLAN 8 

Figure 8-10 

8 

Figure 8-11 

8 

Configuring your 


To 



install the WaveLAN networking software: 

1 Double-click the “WaveLAN® Installer” icon. 

The WaveLAN Installer will: 

● remove earlier versions of the driver, and 

● install this latest version into your system. 

2 When finished, restart your computer. 

After you restart your computer, you can insert your 

WaveLAN/PCMCIA Card into either PC Card slot. Use the 

WaveLAN Setup control panel to (re-)configure your settings. 




Figure 8-12 

8 

Enabling AppleTalk for 

Classic 8 

Balloon help is available for each of the items shown in the 

WaveLAN Setup control panel dialog. 

Note: If you are trying to install your WaveLAN PC Card, in some 

cases the configuration software may not work. This is 

typically the case when it concerns a (previously purchased) 

older type WaveLAN/PCMCIA card. 

When the WaveLAN configuration software detects this type 

of card, it will: 

● Display an Alert dialog, and 

● Create a button on the WaveLAN Setup control panel, 

labelled “Update CIS...” 

Use this button to update the Card Information Structure (CIS) 

of your WaveLAN card. This update will allow your 

WaveLAN/PCMCIA card to work with the Macintosh 

software, but should not effect your ability to use the updated 

card in other operating system environments. 

You can select AppleTalk to use the WaveLAN card by starting 

the Network Control Panel from under the Apple Menu, or by 

double-clicking the “WaveLAN PC Card” icon on the desktop 


Figure 8-13 

8 

Enabling Apple Talk for 

Open Transport 8 



when the card is inserted. Then select the “EtherTalk 

Alternative” icon to enable AppleTalk to use the WaveLAN 

card as its network interface. 

You can select AppleTalk to use the WaveLAN card by starting 

the AppleTalk Control Panel from under the Apple Menu, or 

by double-clicking the “WaveLAN PC Card” icon on the 

desktop when the card is inserted. Then select the “Ethernet” 

item from the “Connect via:” menu to enable AppleTalk to use 

the WaveLAN card as its network interface. 




Figure 8-14 

8 

Enabling TCP/IP for 

Classic 8 

Figure 8-15 

8 

You can select MacTCP to use the WaveLAN card by starting 

the MacTCP Control Panel from under the Apple Menu when 

the card is inserted. Then select the “Ethernet Built-In” icon 

to enable TCP/IP to use the WaveLAN card as its network 

interface. You will need to restart your computer for these 

changes to take effect. 


Enabling TCP/IP for 

Open Transport 8 

Figure 8-16 

8 



You can select TCP/IP to use the WaveLAN card by starting 

the TCP/IP Control Panel from under the Apple Menu when 

the card is inserted. 

In the TCP/IP (DHCP) window, select the “Ethernet” item 

from the “Connect via:” menu to enable TCP/IP to use the 

WaveLAN card as its network interface. 

You will need to restart your computer for these changes to 

take effect. 


Appendix A 

WaveLAN/PCMCIA 



Specifications A-1 

Environment Definitions: A-2


WaveLAN/PCMCIA

WaveLAN/PCMCIAA 

Specifications 

Specifications A 

Physical Specifications 

Dimensions PC card: 8.5 cm x 5.4 cm x 0.5 cm (3.4 in. x 2.1 in. x 0.2 in.) 

Dimensions Antenna: 11.8 cm x 6.5 cm x 1.6 cm (4.7 in. x 2.6 in. x 0.6 in.) 

Total Weight: 179 gr (0.39 lb) 

Cable length: 45 cm (18 in.) 

Temperature Range Host Equipment 

Data Communication 

0° to +40° C 

Data Rate: 2Mb/sec. 

Media Access Protocol: Ethernet variety (CSMA/CA) 

Bit Error Rate: Better than 10 -8 

Power Consumption 915 MHz 2.4 GHz 

Sleep Mode: 0.18 W 0.175 W 

Receive Mode 1.48 W 1.575 W 

Transmit Mode 3.00 W 1.825 W 

R-F Specification 915 MHz 2.4 GHz 

Frequency: Fixed Frequency Sub-Band Frequency Selection 

(subject to local radio regulations) 

Modulation Technique: Spread Spectrum - DQPSK 

Output Power: 24.5 dBm 15 dBm 

Receiver Sensitivity -80 dBm -82 dBm 

FCC Regulations: No site license required No site license required 

Range (approximate, depending on environment) 

Open Office: 250 m (800 ft) 200 m( (600 ft) 

Semi-open Office: 60 m (200 ft) 50 m (160 ft) 

Closed Office: 30 m (100 ft) 25 m (80 ft) 

(Office environments are described on next page) 

WaveLAN/PCMCIA User’s Guide A-1


Specifications 

Environment 

Definitions: A 

Open office: A 

Semi-open office: A 

Closed Office: A 

Antennas 

Work 

Completely 

A-2 WaveLAN/PCMCIA User’s Guide 

The range of WaveLAN may vary according to the physical 

environment where the product will be used. Signal strength 

can be affected by closeness to metal surfaces and solid highdensity 

materials. The ranges listed on the previous page may 

provide a rule of thumb to the range that might be expected in 

a typical environment. 

can "see" each other, i.e. there are no physical 

obstructions between them. 

space is divided by shoulder-height, hollow wall 

elements; antennas are at desktop level. 

enclosed work space with non-metallic, nonconcrete 

walls from floor to ceiling.


Driver Installation Examples 

Appendix B 


NetWare Examples B-1 

Installing a Driver for Personal NetWare B-1 

Installing a DOS/ODI Workstation Driver 2-1 

NDIS Examples B-3 

LAN Manager Installation B-3 

Windows v.3.11 Installation B-4


Driver Installation Examples

Installing a Driver for 

Personal NetWare B 

Installing a DOS/ODI 

Workstation Driver 2 

Driver Installation ExamplesB 

NetWare Examples 

NetWare Examples B 

This section describes installation in the following 

environments: 

● Personal NetWare 

● NetWare (workstation) 

Run the Personal NetWare INSTALL program as described in 

the Personal NetWare documentation. From the list of Primary 

Network Interface Cards, select the OEM supplied driver files 

option. 

Place the WaveLAN diskette in drive A: and enter a: when 

asked for a path name for the driver. 

Continue with steps 2 and 3 of the Personal NetWare 

installation procedure. 

If you have installed the WaveLAN Enabler, modify the 

NET.CFG file as described in Chapter 5, “Installation for MS- 

DOS”. 

For NetWare versions 3.12 and 4 the procedure for installing 

the workstation driver is similar to that for Personal NetWare 

(above). 

For earlier versions, proceed as follows 

:Insert the NetWare WSGEN diskette in drive A:. Copy 

NetWare DOS/ODI from the WSGEN diskette support files to 

the root directory of the workstation. Example commands: 

copy a:\netx.com c:\wavelan\ 

copy a:\lsl.com c:\wavelan\ 

copy a:\ipxodi.com c:\wavelan\ 

WaveLAN/PCMCIA User’s Guide B-1


NetWare Examples 

Note: For some NetWare versions, these files are provided on a 

separate “DOS ODI WORKSTATION SERVICES” diskette. 

Edit the workstation's AUTOEXEC.BAT file to include the 

following lines in the order shown here (example): 

C:\WAVELAN\LSL 

C:\WAVELAN\WVLAN05 

C:\WAVELAN\IPXODI 

C:\WAVELAN\NETX or C:\WAVELAN\VLM 

B-2 WaveLAN/PCMCIA User’s Guide 

If you have installed the WaveLAN Enabler, edit the NET.CFG 

file to include WaveLAN configuration parameters as 

described inChapter 5, “Installation for MS-DOS”.

LAN Manager 

Installation B 


NDIS Examples 

NDIS Examples B 

This section provides examples for the following NDIS 

environments: 

● LAN Manager (Microsoft) 

● Windows for Workgroups 

If your NDIS environment is not listed here, please check the 

README.TXT file on the WaveLAN software diskette. 

Use the LAN Manager SETUP utility to install the WaveLAN 

NDIS driver in a LAN Manager environment. The general 

installation procedure is described in the Microsoft LAN 

Manager Installation Guide. This section provides additional 

information specific to WaveLAN driver installation. 

1 Start the LAN Manager SETUP program, and select the 

Actions menu. 

2 Insert your working copy of the WaveLAN diskette in a 

disk drive. 

3 Choose “Import” from the Actions menu, and specify the 

WaveLAN diskette's drive letter when asked. The “Import 

Network Drivers” dialog box is displayed: 

4 Select the WaveLAN driver (use the [Space] key) and exit. 

The driver is copied to directory 

\LANMAN\DRIVERS\WAVELAN (or 

\LANMAN.DOS\DRIVERS\WAVELAN on an MSDOS 

workstation). 

5 Choose View/Modify from the Actions menu, and use the 

Network Drivers dialog box to install the driver. 

6 Choose Save from the Actions menu, to save the new 

driver installation. 



NDIS Examples 

Windows v.3.11 

Installation B 

B-4 WaveLAN/PCMCIA User’s Guide 

7 Edit PROTOCOL.INI (see below, “Changing Installation 

Parameters”). 

Changing Installation Parameters B 

During WaveLAN driver installation parameters are added to 

the file PROTOCOL.INI in directory \LANMAN. Example: 

[WVLAN09_NIF] 

; Protocol.ini entry for WaveLAN Communications Adapter. 

; etc. (can be deleted) 

; 

DriverName = WVLN09$ 

Domain_ID= 0x0000 

Beacon_Key= 0x0000 

Encryption_Key = 0 

If you have installed the WaveLAN Enabler, edit the NET.CFG 

file to include WaveLAN configuration parameter values as 

described in Chapter 5, “Installation for MS-DOS” 

The WaveLAN INSTALL program for Card/Socket Services 

based computers will do this automatically. 

The installation of WaveLAN under Windows for Workgroups 

(Windows version 3.11) can be done from the Windows 

Program Manager screen. 

1 In the Windows for Workgroups Program Manager 

window, Locate the Network group. 

2 Select the Network Setup icon. 

3 From the Network Setup menu, select Drivers.... 

4 From the Network Drivers menu, select Add Adapter.... 

5 From the Add Network Adapter menu, select 'Unlisted or 

Updated Network Adapter'. 

6 Insert the WaveLAN diskette in drive A: and hit Enter (or 

click on the OK button). The 

'WaveLAN (PCMCIA) NDIS 2 Driver' name is displayed.


NDIS Examples 

7 Hit Enter again to install the WaveLAN driver. 

The file PROTOCOL.INI in directory C:\WINDOWS will 

include the following parameters: 

[WVLAN09_PC] 

DriverName = WVLN09$ 

NWID = 0x0100 

Domain_ID= 0x0000 

Beacon_Key= 0x0000 

If you have installed the WaveLAN Enabler, add WaveLAN 

card configuration parameters as described in Chapter 5, 

“Installation for MS-DOS”. The WaveLAN INSTALL 

program for Card/Socket Services based computers will do 

this automatically. 



NDIS Examples 

B-6 WaveLAN/PCMCIA User’s Guide

Appendix C 

WaveLAN Power 

Management 


WaveLAN Power Management 

About WaveLAN Power Management C-1 

Considerations in Using Power Management C-1 

The NetWare Watchdog Mechanism C-2 

Connecting to a Single Server C-3 

Connecting to Multiple Servers C-4 

Power Management Examples C-6 

Restrictions on Using Power Management C-8


WaveLAN Power Management

Table C-1 

Power Management parameter 

Considering Power 

Management C 

WaveLAN Power ManagementC 

About WaveLAN Power Management 

About WaveLAN Power 

Management C 

WaveLAN Power Management allows the WaveLAN PC card 

to be put in a low power-consuming “Sleep” state during 

periods when no active communication is taking place. In this 

state power consumption is about 15% of that used in active 

Receive mode, which can result in significantly improved 

battery life in mobile workstations. 

WaveLAN Power Management is intended to be used in 

Novell NetWare environments in conjunction with the 

NetWare Watchdog mechanism, to reduce power consumption 

while remaining connected to the network. It is controlled by 

two parameters (POWER UP and POWER DOWN) set in the 

NET.CFG file used by the DOS/ODI driver. Format: 

Parameter Range Default Normal** 

POWER DOWN 0 - 65535 sec 0 (= No power mgmt) 420 

POWER UP 0 - 65535 sec 120 (2 minutes) 120 

Normal** - Recommended settings for NetWare running default Watchdog timers 

You can set the values by running the INSTALL program, or by 

editing the NET.CFG file (Chapter 5, “Installation for MS- 

DOS”). 

The Normal Power Management parameter values in the above 

table have been chosen to provide near-optimum power 

management performance in all NetWare environments where 

the default Watchdog timer values are used. 

Before enabling power management you should first check 

with your network administrator that the default Watchdog 

WaveLAN/PCMCIA User’s Guide C-1



The NetWare Watchdog 

Mechanism C 

Figure C-1 

C-2 WaveLAN/PCMCIA User’s Guide 

timer settings are in use. If that is not the case then an 

understanding of the Watchdog mechanism and its relationship 

to WaveLAN power management will be required in order to 

proceed. 

It is hoped that the rest of this appendix will help you and your 

network administrator to understand this relationship and to 

determine the most effective power management settings for 

your environment. 

The Watchdog mechanism in a NetWare server monitors the 

connections with workstations logged on to that server by 

sending a “watchdog” message at regular intervals to each 

workstation. If no response is received from a workstation 

after a specified number of messages, the workstation is 

logged off. This can happen typically as a result of the 

workstation being powered off, or being out of range for a 

sufficiently long period. Figure C-1 shows the Watchdog 

mechanism in action for a station that is powered off after a 

short period of active communication. 

Three server parameters, configurable by a network 

administrator, are shown:

Figure C-2 

Connecting to a Single 

Server C 



Td Delay time before the first Watchdog message is sent. 

Ti Interval between Watchdog messages. 

Nr Number of Watchdog messages (before log off). 

The values shown correspond (in minutes) to the defaults for 

NetWare version 2.2. The default values for other NetWare 

versions are similar. 

For the purposes of this discussion, Tw is the Watchdog time 

and is the result of (Nr-1)*Ti. 

Figure C-2 shows how the connection is maintained when the 

station remains powered on and within range. 

To ensure a station will not miss the critical number of 

watchdog messages, the Power Management parameters are 

set to ensure that: 

● The WaveLAN PC card becomes active during the 

Watchdog time (Tw) 

● The card is active long enough to receive 2 consecutive 

Watchdog messages 




Figure C-3 

Connecting to Multiple 

Servers C 

Calculation: 

Power Up = 2*Ti 

Power Down = Tw - Power Up 


Using the default values for NetWare 2.2 (Ti = 60, Nr = 10), the 

following Power Management values are obtained 

Power Up = 120 (2 min.) 

Power Down = 420 (7 min.) 

Figure C-3 illustrates the effect on power consumption of 

using these settings: 

You can reduce power consumption by increasing Tw (by 

increasing Nr). Td does not affect the Power Management 

settings and thus can be decreased to compensate for an 

increase in Tw, if required. 

Each server in the network runs its own Watchdog mechanism 

and there is no synchronisation between servers. If the 

workstation is logged on to more than one server then the 

following rules apply:



● The PC card must become active during the shortest 

Watchdog time (Minimum Tw) 

● The card active period is long enough to receive 2 

Watchdog messages from the server with the longest time 

between Watchdog messages (Maximum Ti) 

To determine Minimum Tw, calculate (Nr-1)*Ti for every 

server. The lowest value is Minimum Tw. 

Power Management settings: 

Power Up = 2*Maximum Ti 

Power Down = Minimum Tw - Power Up 

If the calculation results in a negative value for Power Down, 

some server settings will have to be adjusted, either to make 

Maximum Ti shorter or Minimum Tw longer (i.e. Nr greater). 



Power Management Examples 

Example1 C 

This 


Power Management Examples C 

The following examples describe the power management 

calculation for single and multiple server scenarios, and how to 

estimate the resulting power consumption. Note that the 

NetWare parameters discussed are part of the network 

operating system, and may be modified only by the Network 

Administrator. 

example shows the Power Management configuration for 

one or more servers running NetWare 3.xx or 4.xx if the server 

uses default Watchdog settings. The NetWare “SET / 

Communications” console command provides the following 

information: 

Number Of Watchdog Packets: 10 

Delay Between Watchdog Packets: 59.3 seconds 

Delay Before First Watchdog Packet: 4 minutes 56.6 seconds 

If a station connects to one server only, or if all servers have 

the same default Watchdog settings, then: 

Power Up = 2 * Maximum Ti 

= 2 * 59.3= 118.6 seconds 

Power Down = Minimum Tw - Power Up 

= (Nr-1)*Ti - Power Up 

= 9 * 59.3 - 118.6 = 415.1 seconds 

NET.CFG file should include the following lines: 

LINK DRIVER WVLAN05 

(other options) 

POWER DOWN415 

POWER UP119 

(other options)

Example 2 C 



Note: The default Power Up value of 120 seconds is acceptable in 

this case, and therefore the POWER UP parameter can be 

omitted. 

During Power Down the power consumption is about 15 % of 

the power consumption during Power Up. In this example the 

average power consumption as a percentage of normal power 

consumption can be estimated as: 

This 

(119 * 100 + 415 * 15) / (119 + 415) = 18125 / 534 = 34 % 

The percentage given is an estimation of reduced power 

consumption for the WaveLAN PC card only. The real effect 

on the battery lifetime will be less because other system 

components such as the screen and hard disk, etc. use power 

also. 

example shows the Power Management configuration for 

multiple servers with different Watchdog settings. 

Server Settings Calculation Results 

Nr Ti 2*Ti Tw 

Server A: 10 120 240 1080 

Server B: 40 60 120 2340 

Server C: 20 180 360 3420 

If server A has Minimum Tw and server C has the Maximum 

Ti, the configuration values become: 

Power Up =2 * Maximum Ti = 360 seconds 

Power Down = Minimum Tw - Power Up = 1080 - 360 = 720 seconds 

In this example the average power consumption as a 

percentage of normal power consumption can be estimated as: 

(360 * 100 + 720 * 15) / (360 + 720) = 46800 / 1080 = 43 % 




Example 3 C 

Restrictions on Using 

Power Management C 

This 


example shows that a near-to-optimum effectiveness can 

be reached if the same Ti value is used on all servers, while the 

lowest Nr value is at least 50. 

Power Management is to be configured for a station that may 

be connected the following NetWare servers: 

Server Settings Calculation Results 

Nr Ti 2*Ti Tw 

Server A: 50 30 60 1470 

Server B: 80 30 60 2370 

Server C: 100 30 60 2970 

Minimum Tw is determined by the Server A settings, while 

the “Maximum” Ti is determined by all servers. The 

configuration values become: 

Power Up = 2 * Maximum Ti = 60 seconds 

Power Down = Minimum Tw - Power Up = 1470 - 60 = 1410 seconds 

In this example the percentage power consumption relative to 

power consumption without Power Management can be 

estimated to be: 

(60 * 100 + 1410 * 15) / (60 + 1410) = 27150/1470 = 18 % 

Note that a station which needs only to log on to Server C 

(with the maximum Nr value, and hence the optimum setting 

for Power Management) has only a minor advantage: 

(60 * 100 + 2910 * 15) / (60 + 2910) = 49650 / 2970 = 17 % 

There are a number of situations where WaveLAN Power 

Management should be used with caution, or not at all. 

If the WaveLAN DOS/ODI driver is used in peer-to-peer 

communication, e.g. for Personal NetWare, Windows for 

Workgroups, communication problems may occur. These can



be resolved by disabling Power Management (POWER DOWN 

= 0). 

The Point-to-Point Diagnostics Utility, when run from a 

remote station, will not "see" stations using Power 

Management. To run Point-to-Point diagnostics you will 

either have to disable Power Management or boot from a 

Utilities Diskette (described in Chapter 5, “Installation for MS- 

DOS” ). 

If other Power Management schemes are installed on your 

computer you will normally have to disable these to run 

WaveLAN power management. However some selective 

Power Management schemes, which operate only on hard 

disks or displays may work in combination with WaveLAN 

Power Management. Use these with caution. 


Appendix D 

Troubleshooting 



Windows 95 & Windows NT D-1 

Verify Card Operation D-1 

Windows does not detect my Card D-2 

Windows NT does not detect my card D-3 

WaveMANAGER/ CLIENT does not start D-3 

Wrong Driver Version D-3 

Upgrading from earlier Driver Versions D-4 

Error Messages (MS-DOS) D-6 

Radio-frequency Network Characteristics D-13 

Signal Interference D-13 

Signal Attenuation D-14 

Problem Determination D-14 

Using the Diagnostics Utility D-15 

Troubleshooting List D-15


Troubleshooting

Verify Card Operation D 

TroubleshootingD 

Windows 95 & Windows NT 

Windows 95 & Windows NT D 

There are several ways to check proper operation of your 

WaveLAN card. 

● Verify the status of the LEDs on the antenna module. 

When the WaveLAN Power LED turns green, the 

operating system has detected the card, and your card is 

functioning properly. 

You may not see the LED activity for the Transmit and 

Receive LED, as these LEDs will only flicker green when 

the WaveLAN/PCMCIA card senses WaveLAN activity in 

the wireless environment. 

● Run the WaveMANAGER/CLIENT program to test the 

wireless connection with another WaveLAN station or 

WavePOINT access point. 

To run the WaveMANAGER/CLIENT you will need to 

install the program as described on page 3-30. 

● When your computer runs the Windows NT operating 

system, you can also use the ‘Event Viewer’ to verfiy 

whether Windows NT loaded your WaveLAN driver 

successfully or not. For more information about the 

Windows NT Event Viewer, please consult the user 

documentation that was shipped with your operating 

system. 

WaveLAN/PCMCIA User’s Guide D-1



Windows does not detect 

my Card D 

Enabling the PC Card 

Controller: D 

Figure D-1 

D 

D-2 WaveLAN/PCMCIA User’s Guide 

When the Windows operating system does not automatically 

detect your WaveLAN/PCMCIA card, you may need to enable 

the PC Card Controller first, to instruct your operating system 

to actively look for PC Cards at startup. 

This is typically the case when you are installing WaveLAN on 

a new computer that was shipped with the Windows 95 

operating system factory-installed. 

1 Click the ‘Start’ button on the Windows Taskbar. 


3 In the Control Panel window, double-click the PC Card ’ 

icon to open the PC Card Properties window. 

4 In the PC Card Properties window (pictured in Figure D-1 

on page -2), double-click one of the PC Card Socket to 

enable the PC Card Controller. 

5 Click the OK button to confirm and close the PC Card 

Properties window.

Windows NT does not 

detect my card D 

WaveMANAGER/ 

CLIENT does not start D 

Wrong Driver Version D 



6 Reboot your computer and turn to Chapter 3, “Installation 

for Windows 95 & Windows NT” to proceed with the 

WaveLAN installation. 

When your computer runs the Windows NT operating system 

(version 3.51 or 4.0) please mind that these versions of the 

Windows NT operating system do not support ‘plug & play’. 

Please read the instructions as described in “What You Need to 

Know” on page 3-1. 

WaveMANAGER/CLIENT can only run on WaveLAN 

equipped computers that use the Windows 95 or Windows NT 

(version 4.0) Operating system. 

When your computer does have a WaveLAN card installed, 

this failure may occur when you used the 

WaveMANAGER/CLIENT installation program to install the 

WaveLAN software, but you did not install the WaveLAN 

driver. 

The Setup.exe file on your diskette, does not install the 

WaveLAN driver. Installing the waveLAN driver is a seperate 

process that is described in Chapter 3, “Installation for 

Windows 95 & Windows NT”. 

When you installed new WaveMANAGER/CLIENT software, 

but you did not upgrade the driver, in some caes you may get 

this error message when trying to launch the 

WaveMANAGER/CLIENT program. 

Older versions of the driver do not always include all 

fiunctionalities required by the WaveMANAGER/CLIENT 

program. 

You are advised when installing the latest version of the 

WaveMANAGER/CLIENT program, to upgrade your 




Upgrading from earlier 

Driver Versions D 

Upgrading WaveLAN under 

Windows NT 4 

Upgrading WaveLAN under 

Windows 95 4 


WaveLAN driver as well, as described in “Upgrading from 

earlier Driver Versions” 

The procedure to upgrading a previous installed driver differs 

according to the Windows Operating Systems installed on your 

computer. 

● Windows NT systems include an ‘Update’ Feature that 

enables you to select another driver for your WaveLAN 

network adapter (see “Upgrading WaveLAN under 

Windows NT” on page -4). 

● Windows 95 systems would require you to un-install the 

old driver prior to installing the new driver, but in most 

cases you will be easier of when you overwrite the old 

driver files with the new ones as described in “Upgrading 

WaveLAN under Windows 95” on page -4 

Windows NT Systems allow easy upgrades of previously 

installed drivers using your new 

To upgrade from a beta version to the official Windows 95 

driver, you need to remove two files from the Windows 

directory: 

The drawback of Windows 95 ‘plug & play’ support is that it 

will keep all driver files stored on the harddisk of your 

computer even though you might not need them anymore. 

Using the ‘Remove’ option from the Network Adapter 

Properties panel will only disable the association between the 

adapter and the referenced driver. 

When trying to install the new driver, Windows 95 woul 

‘realize’ it already has a file with the same name installed, and 

simply re-use the old version file; i.e When Windows 95 

displays the message ‘installing driver’ this would simply 

mean ‘re-installing the old driver’.

Figure D-2 

DView hidden files 



1 Remove the WaveLAN PC card from your computer 

2 Click the “Start” button on the Windows 95 Taskbar 

3 Point to “Programs”, and then click Windows explorer 

4 From the “Explorer” menubar select View, Options 

5 Click the “Show all files” button and click ”OK” 

6 Move to the drive where you have installed Windows 95 

7 Double-click the “Windows” folder to open it 

8 Move to the Windows sub-directory \inf, to locate the file 

wvlan22.inf 

9 Select this file and delete it 

10 Move to the Windows sub-directory \system, to locate the 

file wvlan22.sys 

11 Select this file and delete it 

12 Follow the standard installation procedure as described in 

this document to re-install the WaveLAN hardware and 

software, using the files provided on the official 

WaveLAN software diskette for Windows 95 and 

Windows NT. 



Error Messages (MS-DOS) 

Antenna is not connected D 

Bad initialization parameter 

(type for keyword 

PCMCIA_Socket) D 

Call code not available D 

Card not connected D 

Card in use by another 

program D 

Cause: 

Cause: 

Cause: 


Error Messages (MS-DOS) D 

This section contains the text of error and warning messages 

displayed by the Enabler, driver and configuration utilities. 

Messages appear here sorted in alphabetical order of the text in 

the message body. However, some messages may be displayed 

with the prefix "WaveLAN:" 

The antenna is not connected to the WaveLAN card. 

Action: Connect the antenna 

Cause: The driver has detected an invalid PCMCIA Socket 

parameter value in the PROTOCOL.INI file. 

Action: Correct the PCMCIA Socket parameter and reload 

the driver. Valid values are: A, B, C, D, E, F, G, H, X, 

a, b, c, d, e, f, g, h, x. 

The WaveLAN card has no call code (required in 

Japan). 

Action: Contact your local supplier 

No card inserted in the expected slot, or the card was 

not properly inserted (Note: The driver will still 

load.). 

Action: (Re-)insert the card. 

Cause: Another program was using the WaveLAN card when 

this program attempted to access it. The most likely 

occurrence of this message is when an attempt is 

made to start a diagnostic program while the network 

driver is running (Enabler-based installations). 

Action: Disable automatic start-up of the driver and reboot 

the computer, or boot from a floppy disk. Run this 

program again.

Card not found D 

Card not functioning 

correctly D 

Client Driver Failure nn D 

Cause: 

Cause: 



The Enabler, driver or utility could not detect a 

WaveLAN card, or the driver could not find a card at 

the specified socket. 

Action: Make sure the WaveLAN card is inserted in a 

PCMCIA slot and that the Socket parameter in 

NET.CFG or PROTOCOL.INI correctly identifies the 

slot being used (Enabler based systems). Run the 

INSTALL program (CS/SS based systems). 

Cause: Start-up diagnostics detected a malfunctioning 

component and has determined that the card cannot 

be used. 

Action: This may be a transient or permanent problem. Try 

the program reporting the error again. If the message 

persists, replace the card. If possible, try the card in 

another PC to verify that the problem is in the card 

and not its environment. 

This message is generated by the WaveLAN Client 

Driver usually as a result of a problem with the Card 

and Socket Services interface. ’nn’ is an error code. 

The table on the next page lists the error codes and 

suggests actions to resolve the problem. Your Card 

and Socket Services documentation may contain 

more clues. If you cannot resolve the problem contact 

your support service or Lucent Technologies. In the 

meantime you could try the alternative installation 

procedure using the Enabler 




Code Possible Cause Action to Take 

02 The Client Driver was unable to reserve I/O ports for the 

WaveLAN card when the WaveLAN driver was started 

with the card not present. 

Try rebooting with the card in a PCMCIA socket. 

03 An request for I/O ports for the WaveLAN card failed. Review the resources used by your PC that may be using 

I/O ports. If possible try to temporarily remove a resource 

and try the WaveLAN card again. 

04 The Client Driver was unable to reserve an IRQ line for 

the WaveLAN card when the WaveLAN driver was 

started with the card not present. 


05 An request for IRQ lines for the WaveLAN card failed. Review the resources used by your PC that may be using 

an IRQ line. If possible try to temporarily remove a 

resource and try the WaveLAN card again. 

07 Attempt to start a WaveLAN driver when a WaveLAN Check the network configuration file NET.CFG or 

driver is already active. 

PROTOCOL.INI for multiple occurrences of the WaveLAN 

driver. 

08 Older version of Card Services driver doesn’t support 

starting the WaveLAN driver with the card out. 


09 Internal failure of card or PCIC Controller. Try the card in another machine, or another WaveLAN card 

in this machine, to determine where the problem lies. 

0A Unable to use a previously reserved I/O port. Inform the local support organization or Lucent 

Technologies. 

0B Unable to use a previously reserved IRQ line. Inform the local support organization or Lucent 

Technologies. 

Client driver not available D 

Configuration Install utility 

should be run D 

Cause: 


No client driver or Enabler has been loaded 

Action: Verify that the config.sys file contains one of the 

following statements : 

Device=Enabler.sys 

wavecli.exe 

Cause: The card has not been properly configured, or the 

configuration data has become corrupted. 

Action: Run the utilities SETCONF.EXE and 

INSTCONF.EXE. These utilities ar in directory 

\UTIL on the WaveLAN software diskette.

Could not find driver named 

WVLN09$ D 

Enabler has not been run 

successfully D 

Error opening 

WAVELAN.INI file D 



Cause: The WaveLAN NDIS driver could not find the device 

name in the PROTOCOL.INI file. This is most likely 

caused by an invalid device name in the 

DRIVERNAME= statement in PROTOCOL.INI 

Action: Correct the DRIVERNAME= statement and reload the 

driver. 

Duplicate or out of range IOBase parameter [0300-03f8], check /B= 

options 

Duplicate or out of range IRQ parameter [3,4,5,7,9,10,11,12,14,15], 

check /I= options 

Duplicate or out of range memory parameter [0xC000-0xEF00], check 

/M= options 

Cause: The Enabler "DEVICE" statement in CONFIG.SYS 

contains an invalid parameter value or the same value 

occurs more than once. The error message shows 

which parameter is at fault, and the permitted range of 

values. 

Action: Edit CONFIG.SYS to correct the Enabler "DEVICE" 

line, and reboot. 

Cause: The Enabler was not run, or the computer’s power 

management scheme caused Enabler information to 

be lost. 

Action: Ensure the Enabler is specified correctly in 

CONFIG.SYS. Disable the PC’s power management 

scheme, if used. Reboot 

Cause: In a Card/Socket Services based system, an attempt 

was made to start a utility and the utility could not 

find the WAVELAN.INI file created by the INSTALL 

program. 

Action: Run the INSTALL program again. If you need to run 

the utility from a floppy disk, ensure that 

WAVELAN.INI and the network configuration file 

are also on the disk and that WAVELAN.INI contains 




Error writing new 

configuration to the card D 

Invalid Combination of 

keywords D 

IRQ Conflict or Card not 

functioning correctly D 


the correct path to the network configuration file 

(NET.CFG or PROTOCOL.INI). 

Cause: A hardware malfunction prevented the card 

configuration from being updated. 

Action: This may be a transient or permanent problem. Try to 

install the new configuration again. If the message 

persists, replace the card. If possible, try the card in 

another PC to verify that the problem is in the card 

and not its environment. 

Cause: More than one card location keyword (port, socket or 

slot) is present in the configuration file (NET.CFG or 

PROTOCOL.INI). 

Action: Select one card location keyword to specify the 

correct card location: port (ISA), socket (Micro 

Channel) or slot (PCMCIA). If no location is 

specified, the driver will automatically select the first 

card found. 

Invalid 

= FRAME 

STATION ADDRESS, STATION_ADDRESS 

NWID 

Cause: An invalid parameter value was passed to the driver 

in the NET.CFG or PROTOCOL.INI file. 

Action: Edit NET.CFG or PROTOCOL.INI to correct the 

parameter value, and reload the driver. 

Cause: Card malfunction, or IRQ number is used by another 

program 

Action: Check if the IRQ is already in use by another 

program. If so specify another IRQ for the WaveLAN 

card. If possible try the card in another PC to verify 

that the problem is in the card and not its 

environment.

Memory window not 

available, check /M= 

options D 

Parameter group not 

complete, check command 

line options D 

PCMCIA Access module not 

available D 

PCMCIA Enabler module 

not compatible D 

PCMCIA Interface not 

supported or missing D 



Cause: The memory window specified in the Enabler 

"DEVICE" line in CONFIG.SYS is in use by another 

device (or has not been "excluded" from use by MS 

Windows). 

Action: Select another value for the /M parameter in the 

Enabler "DEVICE" line. Check CONFIG.SYS (and 

SYSTEM.INI) to verify that the memory window 

used is excluded. 

Cause: A parameter is missing from the Enabler "DEVICE" 

line in CONFIG.SYS. All 3 parameters (/B,/M, /I) are 

required. 

Action: Edit CONFIG.SYS to include the missing parameter 

in the Enabler "DEVICE" line, and reboot. 

Cause:No client driver or Enabler has been loaded 

Action: Verify that the config.sys file contains one of the 

following statements : 

Device=Enabler.sys 

wavecli.exe 

Cause: The Enabler that was loaded is not compatible with 

the network driver. 

Action: Make sure that the Enabler and driver are installed 

from the same WaveLAN software diskette. 

Cause: The Enabler was unable to detect a compatible PC 

Card Interface Controller (PCIC) in this computer. 

Action: The WaveLAN Enabler currently supports the Intel 

82365 PCIC only. If your computer has another type 

of PCIC, call one of the support numbers found in the 

README.TXT file on the WaveLAN software 

diskette. Otherwise check your computer’s system 

setup to ensure the PCMCIA interface has been 

enabled. 




Security Feature not 

functioning correctly D 

Security Feature not 

available D 

Software incompatible with 

Card D 

Too many drivers loaded D 

Unrecognized NET.CFG 

keyword on line D 

Unrecognized parameter on 

Command Line D 

Cause: 


Cause: Start-up diagnostics have determined that the 

Security Feature is defective 

Action: Replace the card, or run with Security disabled (see 

next message action). 

Cause: The configuration installed on the card indicates that 

Datalink Security is enabled, but the card is not 

equipped with the Security Feature. 

Action: Replace the card by one that includes the security 

feature, or reconfigure to disable Datalink Security. 

Note: If you decide to disable Datalink Security you 

will have to do it for all WaveLAN stations and 

access points. 

Cause: The program version you are using does not match 

the version of the card installed. 

Action: Use only software from the diskettes that were 

supplied with the installed WaveLAN/PCMCIA card, 

or later releases. 

An attempt was made to load more copies of one 

driver than could be handled by the the driver 

software. 

Action: Edit the autoexec.bat file to remove excessive load 

commands of the same driver. 

Cause: Invalid keyword in NET.CFG or spacing wrong on 

parameter line. 

Action: Check the parameters in NET.CFG. Words that are 

part of a keyword should be separated by a single 

space. 

Cause: The command line contained a string that did not 

match the MS-DOS conventions for program 

filenames or was not a valid command line parameter. 

Action: Correct the command line (see this book).

Utility not compatible with 

Enabler D 

WARNING: possible 

memory window conflict, 

verify /M= option D 

Signal Interference D 


Radio-frequency Network Characteristics 

Cause: The Enabler that was loaded is not compatible with 

the Configuration Install utility. 

Action: Make sure all the programs you use are from the same 

WaveLAN software diskette. 

Cause: The Enabler has detected that the specified memory 

window contains data. 

Action: On some PCs this may be due to memory not 

resetting at boot time. You may want to try another /M 

setting. In any case, check CONFIG.SYS (and 

SYSTEM.INI) to verify that the memory window you 

have specified is not in use by another device (or by 

MS Windows). 

Radio-frequency Network 

Characteristics D 

In general, a radio-frequency Local Area Network behaves in 

much the same way as other types of LAN. However, due to 

the nature of the transmission medium, radio-frequency 

networks are more sensitive to: 

● Signal interference (Noise). 

● Signal attenuation. 

Signal interference (or noise) is radio-frequency signals 

detected by a receiving antenna, that were not transmitted by 

any station in the receiving station’s network. The source of the 

interfering signal may be: 

● Adjacent WaveLAN network with a different Network ID. 

● Another (not WaveLAN) radio-frequency network. 

● Non-network sources such as: 



Problem Determination 

Signal Attenuation D 


● 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 local and can 

be eliminated by relocating the PC. 

Signal attenuation is a loss of signal strength, which occurs 

naturally over distance, but which also can be caused by radiofrequency 

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 will cause some slight degree of attenuation. In most 

cases this does not have a significant effect on network 

performance. 

D 


Problems in a WaveLAN network can be related to: 

● Component failure (of card or antenna). 

● Environment and operation. 

Component Failure D 

Component failure is normally detected by a startup 

diagnostics routine built into programs which use the 

WaveLAN card.

Using the Diagnostics 

Utility D 

Troubleshooting List D 



Environment and Operation D 

Environment and operation-related problems can be caused by 

one or more of the following: 

● Placing the computer in a "noisy" area. 

● Path defects (antenna connection, barriers, distance). 

● Competition from adjacent networks. 

● Network loading. 

You can use the Point-to-Point diagnostic utility to diagnose 

and resolve some environment and operational problems 

The Point-to-Point Diagnostics utility lets you test the 

communications path between two stations. You can use it to 

verify that your WaveLAN PC card is installed and 

operational, and to measure local noise conditions. 

Installing and using the Point-to-Point Diagnostics utility is 

described in Chapter 5. 

The following tables identify some common symptoms of 

environment or operational problems, and suggests the 

direction to take to find a solution. 

Problem Possible Cause Action to Take 




Unable to log on to network Antenna not connected Check antenna connected 

Enabler or Client Driver (WAVECLI.EXE) 

not run 


Reboot - check Enabler runs O.K., or check 

WAVECLI.EXE DEVICE line in CONFIG.SYS 

Different WaveLAN Network ID Check NWID parameter in driver initialisation 

(NET.CFG or PROTOCOL.INI) 

Security mismatch Check: (All stations) Security feature present and 

security enabled and all have same Encryption 

key, or 

Security disabled on all stations. 

Card or antenna defective, or station out 

of range. 

1. Run Point-to-Point diagnostics between this 

station and one known to work. 

2. Run Point-to-Point diagnostics between this 

station and a WavePOINT (or wireless server). 

Operating frequency mismatch Run the WFREQSEL utility to check the 

frequency of this and other cards in the network, 

and correct as necessary. 

Performance less than expected Local noise level high or 

Local traffic (bandwidth nearly full) or 

Station out of range 

Roaming station doesn’t connect 

automatically when powered on. 

Roaming station no longer 

logged on 

Run Point-to-Point diagnostics to establish cause, 

then take appropriate action 

Roaming not enabled at WavePOINTs. Check Installation records. Ask the Network 

Administrator to run WaveMONITOR to check 

that all WavePOINTs are sending Beacons. 

WaveLAN/PCMCIA station and 

WavePOINT have different Domain ID or 

Beacon Key. 

Station’s MAC address not in 

WavePOINTs Access Control Table (if 

Access Control enabled). 

Security feature or encryption key 

mismatch between WaveLAN station and 

WavePOINT. 

Network time-out while station out of 

range. 

Ensure all WavePOINTs and Roaming WaveLAN 

stations are using the same Domain ID and 

Beacon Key. 

Check Access Control Table data or reload 

configuration with Access Control disabled. 

Check security enabled or disabled on all 

WaveLAN stations and WavePOINTs in the 

Roaming Domain. Check that all are using same 

Encryption key. 

Ensure workstation is within range and reboot. 

Extend disconnect timer values in network server. 

PC’s power management scheme in use. Disable the PC’s power management scheme 

WaveLAN power management values not 

compatible with Network timer values. 

Adjust Power Up, Power Down values in Net.CFG 

or PROTOCOL.INI file

Performance loss or 

"Out-of-range" condition 

(e.g. when moving away from 

WavePOINT) 

Windows PC beeps for unusually 

long time when PC card is 

removed or re-inserted 

Windows for Workgroups hangs 

when WaveLAN driver is loaded. 

Computer no longer "beeps" 

when card removed or reinserted 

(Card/Socket Services based 

system). 

Utility unable to detect other 

stations (Enabler-based 

installation with encryption). 



No closer WavePOINT to hand over to. Install another WavePOINT to extend the 

Roaming area. 

Roaming not enabled at the new, closer 

WavePOINT 

Domain ID or Beacon Key mismatch with 

new WavePOINT 

Station’s MAC address not in new 

WavePOINT’s Access Control Table 

Encryption Key mismatch on new 

WavePOINT 

Exact cause unknown but related to 

’TimerCriticalSection=’ statement in 

SYSTEM.INI file 

This is a known problem related to 

’Phantom Binding’ i.e. driver started when 

card not present. 

Card and Socket Services may be using 

an IRQ number which is not available for 

the required function on the specific 

computer. 

The encryption key is given as a 

parameter in the network configuration 

file (NET.CFG or CONFIG.SYS). Another 

file (WAVELAN.INI) points to the location 

of the network configuration file. The utiity 

cannot find WAVELAN.INI and therefore 

the encryption key. 

Check Installation records. Ask the Network 

Administrator to run WaveMONITOR to check 

that WavePOINT is sending Beacons, Signal 

Quality is O.K. and Domain ID correct. 

Check Access Control Table data or reload 

configuration with Access Control disabled. 

Check Security feature status and Encryption key 

of new WavePOINT corresponds to that of other 

WavePOINTs and WaveLAN stations in the 

Domain. 

Use SYSEDIT or NOTEPAD to edit the Windows 

SYSTEM.INI file Change the parameter to: 

’TimerCriticalSection=100’ 

The problem is under investigation. For the time 

being, Windows for Workgroups users should 

ensure that the WaveLAN card is inserted when 

starting Windows. 

Check the Card/Socket Services documentation 

supplied with the computer. Use the CS/SS 

supplied utility to modify the list of available IRQ’s 

Create a WAVELAN.INI file on the Utilities 

diskette (See Chapter 5, “Installation for MS- 

DOS”). 




D-18 WaveLAN/PCMCIA User’s Guide

A 

Antenna Module 1-3 

B 

Beacon Key 3-18 

C 

Communications Quality 4-3, 

4-10 

Configurations, Non-roaming 

Operation 1-5 

Configurations, Roaming 

Operation 1-6 

D 

Diagnostic Counters 4-13 

Domain 1-6 

Domain ID 3-18 

select another 4-12 

Drivers, DOS/ODI 5-12 

E 

Encryption 

enable 3-19 

Encryption Key 3-19 

F 

FCC viii 

Features 1-8 

Figure D-5 

Frequency Selection 5-7, 5-17 

H 

Hot Card Swap 2-3, 2-5 

I 

Information 

FTP Server vii 

Internet World Wide Web vii 

Installation, Card and Socket 

Services 5-2 

Installation, enabler-based 

systems 5-9 

Installation, network operating 

system 5-3, 5-9 

Installation, the enabler 5-10 

Installation, the INSTALL 

program 5-3–5-4 

Installation, verifying the 5-7, 

5-15 

K 

Kit Contents 1-2 

Index 

Index0 

L 

Link Quality Indicator 4-6 

Link Test 4-2, 4-5 

link quality indicator 4-6 

logging measurement 

data 4-14 

resetting diagnostic 

counters 4-7 

selecting another link test 

partner 4-8 

Local Noise Level 4-10 

Logging 4-14 

Logging Measurement Data 

stop 4-16 

M 

Manual Logging 4-14 

Measurement Data 

automatic logging 4-15 

logging 4-14 

logging options 4-15 

manual logging 4-14 

Monitoring Methods 4-1 

Link Test 4-2 

Site Monitor 4-1 

N 

Network 

managing 4-1 

WaveLAN/PCMCIA User’s Guide Index-1

Index 

Network ID 1-5 

NWID 1-5, 3-17 

O 

Other Button 4-12 

P 

Phantom Binding 2-5 

Power Management 1-8 

Power Management, Network 

Timeouts 1-9 

R 

Radio Frequency 

Interference Statement viii 

Remote Noise 4-10 

Roaming 3-17 

S 

Select Another Domain ID 4-12 

Signal Level 4-10 

Signal Quality 6-7 

Site Monitor 4-2, 4-9 

logging measurement 

data 4-14 

selecting another domain 

ID 4-12 

sorting list WavePOINTs 4-13 

SNR 6-7 

SNR (Signal to Noise Ratio) 4-10 

link test 4-7 

Software 1-3 

Station Address 3-20 

Station Name 3-20, 6-4 

Support 

Global vii 

Regional vii 

Swapping PC Cards 2-3 

Index-2 WaveLAN/PCMCIA User’s Guide 

T 

Technical Support vii 

U 

Utilities Diskette 5-16 

W 

WaveLAN Antenna Module 1-3 

WaveLAN Software 1-3 

WaveLAN Technical Support vii 

WaveMANAGER/CLIENT 4-3, 

4-14 

Link Test 4-2 

Site Monitor 4-2 

World Wide Web vii

This book was created by: 

Authors: Hugh Davison and William van der Moolen 

Graphic Design: Hugh Davison and Jek Mistry 

Typesetting: William van der Moolen 

Lucent Technologies Nederland B.V. 

Wireless Communications and Networking Division 

Zadelstede 1-10 

3431 JZ Nieuwegein 

The Netherlands 

An electronic copy of this document can be downloaded from our Library on 

the World Wide Web: http://www.wavelan.com. 

To view or print the electronic document, in Adobe’s Portable Document 

Format (PDF), you will need the freeware ‘Acrobat’ viewer from Adobe Inc. 

(available at http://www.adobe.com). 

Dear reader, 

We value your feedback. If you find errors or omissions in this book, or if 

you can suggest ways to improve its usefulness, I would like to hear from 

you. Please contact me at: 

Telephone: +31 30 609 7471 

Fax: +31 30 609 7556 

E-Mail: moolen@lucent.com 

Sincerely, 

William van der Moolen

008 - 0127326/C 

April 1998 

Copyright © 1998 Lucent Technologies Inc. 

All Rights Reserved

WaveLAN/PCMCIA User's guide - web server

Create successful ePaper yourself

Delete template?

Save as template?