HP Vectra VL6 7 Administrator's Manual

Network

Administrator Guide

Online Guide

Rev. 5.0

Date: 8/97

How to use this online guide

Click the Go Back button in the toolbar to go back to your previous place in the guide.

page in the guide.

Click the Previous Page button in the toolbar to go to the previous page in the guide.

Click the First Page button in the toolbar to go to the opening screen of the guide.

Testing Your Audio Setup

If You Are Running Windo

Solving Problems with Sound

Connecting Audio Devices to

Click a bookmark name (to the left of the screen) to go to the topic corresponding to that bookmark. Clicking a right-pointing triangle , for example, will reveal the subordinate bookmarks. Clicking a downward pointing triangle will hide the subordinate bookmarks.

Topic

Click underlined red text to go to the topic indicated.

Underlined red text is text that is “linked” to another topic in the guide.

Notice

The information contained in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard

Company.

Intel

®

is a registered trademark and LANDesk is a trademark of Intel Corporation.

Magic Packet

TM

is a trademark of AMD Corporation.

Microsoft

®,

MS

®

and MS-DOS

®

are U.S. registered trademarks of Microsoft

Corporation. Windows TM is a trademark of Microsoft Corporation.

Novell

®

is a registered trademark of Novell, Inc.

OS/2 TM is a trademark of International Business Machines Corporation.

Hewlett-Packard France

Grenoble Personal Computer Division

Technical Marketing

38053 Grenoble Cedex 9

France



1997 Hewlett-Packard Company

English 3

Associated Documentation

The following HP publications will also be useful to you.

• The User’s Guide supplied with your PC.

4 English

Contents

How to use this online guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2

Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3

Associated Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4

1 Setting Up the Network Connection

Setting Up the Network Connection . . . . . . . . . . . . . . . . . . . . . . .

10

Configuring the HP Ethernet Family Adapter in SETUP . . . . . . 11

Using SETUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

Controlling the Network Security Features . . . . . . . . . . . . . . . . . . . . . . 11

Controlling the Remote Power Function . . . . . . . . . . . . . . . . . . . . . . . . . 11

Network Driver Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12

Driver Installation - LAN Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

The LAN Activity Light . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14

Tips for Setting Up the HP Ethernet Family Adapter . . . . . . . . .

15

Troubleshooting and Error Messages . . . . . . . . . . . . . . . . . . . . . .

16

Running HPIEDIAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

What You Can Do With HPIEDIAG . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

Getting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

English 5

2 Installing Novell NetWare Drivers

Installing Novell NetWare Drivers . . . . . . . . . . . . . . . . . . . . . . . . . 20

ODI DOS Client Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

ODI Driver with DOS Requester . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

ODI Driver with DOS Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23

Starting a NetWare Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25

ODI OS/2 Client Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

ODI Driver for Windows for Workgroups Clients . . . . . . . . . . . . 29

Windows for Workgroups OEM Information Files . . . . . . . . . . . . . . .

33

Parallel Transferring ODI DOS Client Driver . . . . . . . . . . . . . . . . 34

Parallel Transferring ODI Driver with DOS Requester . . . . . . . . . . .

35

Parallel Transferring ODI Driver with DOS Shell. . . . . . . . . . . . . . . .

37

Starting a Parallel Transferring NetWare Client. . . . . . . . . . . . . . . . .

38

NET.CFG Options for Novell NetWare . . . . . . . . . . . . . . . . . . . . . 39

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

39

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

40

Sample NET.CFG File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41

3 Installing Microsoft Network Drivers

Installing Microsoft Network Drivers . . . . . . . . . . . . . . . . . . . . . . 44

Network Driver Interface Specifications (NDIS). . . . . . . . . . . . . 45

LAN Manager 2.x DOS and OS/2 Client Driver . . . . . . . . . . . . . . . 46

Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

47

NDIS 2.01 Driver for Windows for Workgroups 3.1 . . . . . . . . . . . 49


49

6 English

NDIS 2.01 and 3.0 Drivers for Windows for Workgroups 3.11 . . 50


50

NDIS 3.0 Driver for Windows NT 3.5 . . . . . . . . . . . . . . . . . . . . . . . 52


52

Miniport Driver for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Installing Miniport Driver for Windows NT 3.51 . . . . . . . . . . . . . . . .

53

Installing Miniport Driver for Windows NT 4.0 . . . . . . . . . . . . . . . . .

54

NDIS 2.01 and 3.1 for Windows 95 . . . . . . . . . . . . . . . . . . . . . . . . . 55


55

4 Installing Other Network Drivers

Installing Other Network Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . 58

NDIS 2.01 Driver for Artisoft LANtastic 6.0 . . . . . . . . . . . . . . . . . 59


59

NDIS 2.01 Driver for Banyan VINES Client. . . . . . . . . . . . . . . . . . 62


62

NDIS 2.01 Driver with DEC PATHWORKS 5.0 Client. . . . . . . . . . 64

NDIS 2.01 Driver with FTP PC/TCP 2.x for DOS/Windows. . . . . 65

NDIS 2.01 Driver for IBM LAN Services 4.0 . . . . . . . . . . . . . . . . . 68


68

NDIS 2.01 Driver with IBM Warp Connect . . . . . . . . . . . . . . . . . . 70

NDIS 2.01 Driver for PC-NFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72


72

NDIS 2.01 Driver with Other Networking Products. . . . . . . . . . . 73

English 7

5 Configuring for Remote Boot

Configuring for Remote Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Setting Up a Novell NetWare 3.x and 4.x Server for Remote Start 79

How to Create a Boot Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

79

Remote Program Load on NetWare 3.x and 4.x . . . . . . . . . . . . . . . . .

82

Remote Boot on Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90


90

Remote Boot under Windows NT Server 4.0 . . . . . . . . . . . . . . . . 92


92

DHCP/TFTP Boot under Windows NT. . . . . . . . . . . . . . . . . . . . . . 94

6 Driver Options - Software Keywords

PCNET Driver-Specific Keywords . . . . . . . . . . . . . . . . . . . . . . . . . 96

Common Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Operating System Keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Novell NetWare DOS & OS/2 ODI Client Keywords . . . . . . . . . . . . . .

99

NDIS 2.01 Driver Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

100

NDIS 3.x Driver Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

100

Artisoft LANtastic Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

101

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

8 English

1

Setting Up the Network Connection

NOTE

1 Setting Up the Network Connection



This section describes the procedure to make a LAN Disk using either the Windowsbased HP Master Diskette Creation utility or MS-DOS.

To setup the network connection:

• connect the LAN cable to the PC as described in the User's Guide supplied with your PC.

• check the configuration of the interface before installing the LAN drivers.

HP LAN drivers are supported on Vectra PCs only. This does not apply to drivers for

Microsoft Windows NT 4.0 and Microsoft Windows 95.

10 English


Configuring the HP Ethernet Family Adapter in SETUP

Configuring the HP Ethernet Family Adapter in SETUP

Reconfigure the HP Ethernet Family Adapter using SETUP if you:

• want the PC to start from the LAN server

• want to change the remote power settings

• want to disable the HP Ethernet Family Adapter

If you don't need to change the configuration, install the LAN drivers required to use the PC on the LAN.

Using SETUP

You must use the PC's SETUP program to change the HP Ethernet Family Adapter settings. You can:

•

Set the Security features

•

Control the Remote Power function

•

Enable or Disable the HP Ethernet Family Adapter.

Controlling the Network Security Features

The Security features allow you to enable starting from the network if you want the

PC to start from a LAN server.

You can also disable other boot options to prevent the PC from booting should the network or server fail.

Controlling the Remote Power Function

The HP Ethernet Family Adapter has the ability to power up the PC upon the receipt of a special sequence (known as a Magic Packet™) from the network.

The Remote-Wake mode allows the PC to resume (or Wake-Up) normal functioning when it is in SLEEP (SUSPEND) mode.

The Remote-Power mode allows the PC to start when it is switched off.

English 11

NOTE


Network Driver Software


The HP Ethernet Family Adapter is based on the AMD PCnet family of network adapters. The following drivers are included:

•

Novell NetWare 3.x,4.x ODI under DOS, OS/2 and Windows for Workgroups.

•

Microsoft Network Device Interface Specification (NDIS 2.01) compatible networks, including:

❒ Artisoft LANtastic

❒ Banyan VINES

❒ DEC Pathworks 5.0

❒ FTP PC/TCP 2.x

❒ IBM LAN Services 4.0

❒ IBM Warp Connect

❒ Sun PC-NFS 5.0

❒ Microsoft LAN Manager 2.x

❒ Windows for Workgroups 3.1 and 3.11

❒ Windows 95

•

Microsoft Network Device Interface Specification (NDIS 3.x) compatible networks, including:

❒ Microsoft Windows for Workgroups 3.11

❒ Microsoft Windows NT 3.5


❒ Windows 95

•

Microsoft Network Device Interface Specification (NDIS 4.x) compatible networks, including:


If your network operating system is not listed above, refer to its manuals to install the driver.

Due to the evolving nature of the driver software, there may be a README.TXT file in driver subdirectories on the LAN Disk. Please check if a README.TXT file exists for the driver you are installing and read it. The information contained in this file supersedes any information given in this manual.

12 English

NOTE



Driver Installation - LAN Disk

In most cases, driver installation instructions assume that the HP Ethernet Family

Adapter drivers use a directory structure which has been setup to correspond with the paths that network operating systems search for during the installation process.

Consequently, a “LAN Disk” is provided with your PC containing the directory structure you need for automatic installation. This LAN Disk can be made up of one or two diskettes, according to the LAN adapter provided with your PC.

When your PC is not supplied with a separate LAN Disk, the network drivers are stored on your hard disk or on a “Drivers CD-ROM” in different subdirectories.

If you have the “Drivers CD-ROM”, you can install the network drivers from the CD-

ROM.

If the network drivers are on the hard disk, you have to create the LAN Disk using the Windows Master Diskette Creation utility.

This HP Ethernet Family Adapter LAN Disk can then be used to install the network driver for your particular network operating system. We recommend that you make a note of the directories present on each disk.

This diskette will be referred to as the “LAN Disk” in the installation procedures.

If you download the HP Ethernet Family Adapter drivers from the World Wide Web, follow the instructions provided to expand the driver directory structure either onto your hard disk or onto flexible disks.

The installation instructions, detailed in other documents, are intended to provide examples for easy installation. However, the procedure for your particular network configuration may vary. Refer to the network software's user’s manuals for specific instructions to load additional drivers from proprietary diskettes.

Driver Installation for the HP Net Vectra

The HP Net Vectra has no flexible disk drive. When using the driver installation procedures for the Net Vectra, all references to flexible disks should be mapped to a virtual disk drive.

English 13

NOTE


The LAN Activity Light

The LAN Activity Light

The HP Ethernet Family Adapter provides two lights to indicate status.

The LAN Activity Light is on the front panel of some Vectra PC. It is used to indicate when the PC is accessing the LAN and is occasionally referred to as a “Virtual Hard

Disk Activity Light”.

To program this light signal, the line LED2=0x90h was added in all the configuration files on your LAN disk (for example NET.CFG and PROTOCOL.INI). If you change or remove this line, the LAN Activity Light will stop working.

A second kind of light is found on the back panel of your PC, one beside each of the

UTP connectors. This light indicates the link status and it is lit when there is a valid connection from the interface to a hub port.

14 English


Tips for Setting Up the HP Ethernet Family Adapter

Tips for Setting Up the HP Ethernet Family Adapter

If you want to: You need to: What happens:

Run SETUP

Save your SETUP selections

Reset the PC.

When the message

<Setup=F2> appears, press the F2 key.

From anywhere in the SETUP program, press ESC until the

Exit menu appears.

Know the PC’s MAC address.

Reset the PC.

When the <Setup=F2> message appears, press the

Esc key.

Use the Vectra PC as a client on the LAN.

Run SETUP.

Set an Administrator

Password.

Check the HP Ethernet Family

Adapter configuration.

Make a LAN Disk and install the drivers.

Allow the PC to start from the operating system on the LAN.

Check the LAN interface.

Run SETUP.

Set an Administrator

Password.

Enable Start from Network.

Make a LAN Disk and install the drivers. Configure your server to remote boot your PC.

Run the diagnostic utility as described later.

The SETUP menu will appear.

You will be asked to confirm that you want to save the settings. Press the Enter key.

The PC will restart.

The MAC address is displayed with the summary information

(only when the Ethernet interface is enabled).

When you power-on the PC, you will be able to log onto the

LAN server.

When you power-on the PC, it will start from the LAN server.

Refer to “Troubleshooting and

Error Messages” on page 16 .

English 15

CAUTION


Troubleshooting and Error Messages

Troubleshooting and Error Messages

This section explains how to troubleshoot the HP Ethernet Family Adapter using the HPIEDIAG utility.

HPIEDIAG is an interactive diagnostic program. It includes easy to run diagnostics for testing the LAN interface and the network links.

•

If the PC is supplied with a LAN Disk or the “Drivers CD-ROM”, the HPIEDIAG utility is in the \DIAG subdirectory.

•

If the PC has preinstalled software on the hard disk, the HPIEDIAG utility is on the PC's hard disk in the

LANDRV\DIAG

directory.

To display information on the LAN drivers and utilities, start Windows and click on the README icon in the HPUTILS Window.

The README file explains how to copy the files to a diskette. Use the LAN Disk to run the HPIEDIAG utility. For more information, refer to “Driver Installation -

LAN Disk” on page 13.

Running HPIEDIAG

Make sure your network software and drivers are not running. This may require editing configuration files and restarting the operating system.

HPIEDIAG is a DOS program and should be run either under MS-DOS (preferably) or in a DOS window :

•

If you use Windows 3.x, you must exit Windows to run HPIEDIAG.

•

If you use Windows 95, shut down and restart Windows 95. When the PC displays

“Starting Windows 95”, press F8 and select “Safe mode command prompt only”.

•

If you use Windows NT, shut down and restart your system under MS-DOS.

16 English


Running HPIEDIAG

To run HPIEDIAG:

1 Insert the diskette containing the HPIEDIAG utility in drive A.

2 Make drive A the current drive, type: A:

3 Change to the \DIAG directory, type: CD \DIAG

4 Start the HPIEDIAG utility, type:

HPIEDIAG

HPIEDIAG automatically detects the presence of the HP Ethernet Family Adapter, and displays the settings of the interface: I/O address, IRQ, DMA channel, and MAC address:

HP Ethernet Family Adapter Diagnostic

Ethernet Family Adapter Status

I/O Address Interrupt Level

FCE0h IRQ 10

DMA Channel

N/A

MAC Address

080009xxxxxx

Main Menu

Interface Test

Link Test

Exit Program

Example HPIEDIAG screen.

•

Use the or key to move the highlight to the menu item Interface Test ,

Link Test

or

Exit Program

.

•

Use the key to display help about the highlighted item.

•

Use to select the highlighted item.

•

Use the key to return to the previous menu.

What You Can Do With HPIEDIAG

HPIEDIAG displays the HP Ethernet Family Adapter's I/O address, IRQ, DMA channel, and MAC address. The main screen allows you to start the interface test and link test.

English 17

Interface Test

Link Test

Exit Program


Running HPIEDIAG

Use this option to do a quick test of the interface's hardware and configuration.

During this test, no packets are sent or received over the network, so the network cable does not have to be attached to the interface.

It is recommended that you use this option any time you change the interface's configuration. The test takes very little time to run and provides the most complete verification that the interface's hardware and configuration are correct.

This option tests the interface's ability to send and receive packets over the network.

For this test, the network cable must be attached to the interface.

The test sends IEEE 802.2 Test packets out on the network. Another node on the network must act as the responder.

To be a responder, the node must be able to respond to the IEEE 802.2 Test packets with IEEE 802.2 Test Response packets. Any HP Hub Plus, HP SNMP-managed bridge, or HP router will respond correctly.

The program automatically finds a responder on the network.

This option terminates the HPIEDIAG session.

Error Messages

For a list of all error messages and their explanations, refer to the README file in the \DRVMSG subdirectory of either the LAN Disk or the C:\LANDRV directory of the

PC's hard disk drive.

Getting Support

For access to HP support refer to chapter 6 of the User's Guide supplied with your

PC.

18 English

2

Installing Novell NetWare Drivers

NOTE

2 Installing Novell NetWare Drivers



This document explains how to install the Novell NetWare Open Data Link Interface

(ODI) drivers required to use the PC with a Novell NetWare LAN.

•

If the PC is supplied with the HP LAN Disk, use this disk to install the LAN drivers.

•

If the PC has preinstalled software on the hard disk, the LAN drivers are supplied on the PC's hard disk in subdirectories in the

\LANDRV

directory.

When you start your PC for the first time you will be asked to select which type of network you want to use with your PC. According to your selection the appropriate drivers and files will be automatically installed. If you want to install network software at any other time, follow the procedure described below.

If you want to use the DOS-based Vectra PC as a client on the LAN, refer to the steps given under “ODI DOS Client Driver” on page 21 . Alternatively, refer to the steps given under “Parallel Transferring ODI DOS Client Driver” on page 34 .

If you want to use the OS/2-based Vectra PC as a client on the LAN, refer to the steps given under “ODI OS/2 Client Driver” on page 26 .

If you want to use the Windows for Workgroups 3.11-based Vectra PC as a client on the LAN, refer to the steps given under “ODI Driver for Windows for Workgroups

Clients” on page 29 .

Before installing the network drivers, connect the HP Ethernet Family Adapter to the LAN and set up (configure) the HP Ethernet Family Adapter.



20 English

NOTE


ODI DOS Client Driver


The Novell ODI driver for DOS is used with many Novell products. It is also used by

DOS and Microsoft Windows 3.x computers to gain access to Novell servers through one of the following:

❒ NetWare DOS Requester (using Virtual Loadable Modules or VLMs) or

❒ NetWare DOS Shell (using NETX.EXE)

Both NetWare clients use an ODI driver to enable them to use the HP Ethernet

Family Adapter to access the LAN medium. File service to all versions of NetWare servers is possible from either the DOS Requester or DOS Shell clients. Access to enhanced services provided by later versions of NetWare servers may require using the DOS Requester. Other Novell products, like Personal NetWare and LAN

Workplace for DOS, also use the DOS ODI driver.

The DOS ODI driver is contained within the NOVELL\DOSCLNT directory of your LAN

Disk, the contents of this directory are:

\NOVELL\DOSCLNT\PCNTNW.COM

\NOVELL\DOSCLNT\PCNTNW.INS

\NOVELL\DOSCLNT\NET.CFG

To install the ODI driver with DOS Requester (VLM.EXE), refer to page 22 .

To install the ODI driver with DOS Shell (NETX.EXE), refer to page 23 .

For more information about Netware DOS Client, refer to the Netware Client for

DOS and MS Windows User’s Guide and Netware Client for DOS and MS

Windows Technical Reference manuals provided with your Novell software.

For more information about the NET.CFG file, refer to the Novell NetWare manuals and to “NET.CFG Options for Novell NetWare” on page 39 .

When the DOS ODI driver is used, it will locate the HP Ethernet Family Adapter and read its settings automatically.

English 21



ODI Driver with DOS Requester

To install the ODI driver for DOS, follow the instructions below:

1 Locate the Novell DOS Requester “NetWare Client for DOS and MS Windows” diskettes. These could be labeled “WSDOS_1” and “WSWIN_1”. To create these diskettes from the NetWare CD ROM, follow the NetWare documentation included with the CD-ROM.

2 Run the NetWare client installation program.

a Insert the number 1 diskette into the drive and run the INSTALL program. For example, if the NetWare diskette is in drive A, then type:

A:\

INSTALL b Follow the Novell instructions to fill in the first three fields of the form.

c It is recommended to answer Yes when asked if you want to allow the Novell install program to modify the start-up files. This will make the NetWare client start up automatically and attach to the server every time the computer is rebooted. If

No

is entered, the commands to start up the NetWare client will have to be entered manually.

d If Windows is installed on the computer, it is recommended to answer Yes to allow the Novell install program to add Windows support.

3 When asked to select the driver for your network board, remove the Novell diskette and insert the LAN Disk. Press to bring up the Network Board window.

4 Select A:\NOVELL\DOSCLNT then press .

5 The line HP Ethernet Family Adapter with LAN Remote Power will be highlighted. Press to select the driver (PCNTNW.COM).

22 English

NOTE



6 The Novell INSTALL program will display a window with the settings for the card.

The following parameters will be shown:

Optional Bus Identifier

Optional Media Frame Type(s)

Optional Node Address

Optional Media Type

Optional LAN activity LED

Press without selecting to override any parameters and proceed with the remainder of the steps in the NetWare DOS Requester INSTALL program.

7 The installation of the DOS ODI driver and NetWare client software is complete.

Refer to page 25 for information on how to start a NetWare client.

The ODI driver default frame type is ETHERNET_802.2. NetWare 286 and 386 servers use frame type ETHERNET_802.3 as their default, but NetWare 4.0 uses both ETHERNET_802.2 and ETHERNET_802.3 types. The HP Ethernet Family

Adapter supports both Ethernet frame types.

ODI Driver with DOS Shell


1 To begin the installation you require the Novell DOS Shell installation diskette labeled 'WSGEN' and the LAN Disk.

2 Create a directory on the DOS boot drive (for example C) for the HP and NetWare files using the following commands at the DOS prompt:

C:

MKDIR C:\NOVELL

English 23

NOTE



3 Copy the DOS ODI Driver and NET.CFG File. For example, if the LAN Disk is in

Drive A use the following commands:

COPY A:\NOVELL\DOSCLNT\PCNTNW.COM C:\NOVELL

COPY A:\NOVELL\DOSCLNT\NET.CFG C:\NOVELL

The contents of the NET.CFG file are given below:

LINK DRIVER PCNTNW

BUSTYPE PCI1

FRAME ETHERNET_802.3

LED2 90

4 Copy the following files from the Novell installation diskette labeled “WSGEN” to the

C:\NOVELL

directory:

LSL.COM (must be version 2.11 or later)

IPXODI.COM (must be version 2.20 or later)

NETX.EXE

These files are either in the root or the DOSODI directory on the NetWare diskette.

5 The installation of the DOS ODI driver and NetWare client software is complete.

Refer to page 25 for information on how to start a NetWare client.

The DOS Shell can only access a server's bindery. If you want access any enhanced

NetWare Directory Services, you should use the DOS Requester (VLM).

24 English

NOTE

NOTE



Starting a NetWare Client

To start a NetWare client, execute the following commands at the DOS prompt:

Steps 1 and 2 are only necessary if you did not allow the Netware Client Installation program to modify your configuration files.

1 Change to the directory where the required files are located (for example

CD

\NOVELL

).

2 Type:

LSL

PCNTNW

IPXODI and either,

NETX or

VLM

(If you use VLM.EXE, the CONFIG.SYS file must include LASTDRIVE=Z to work correctly.)

You will be in the LOGIN directory of the server to which the PC is connected.

3 Type LOGIN server/user server is your server name user is your user name on that server

(If you are not sure of your server name, type SLIST the available servers.)

to display a list of

If you want the PC to be able to log onto the server when it starts, add the commands listed above to the PC's AUTOEXEC.BAT file. Otherwise create another batch file and run it when you want the PC to be able to log onto the server.

English 25


ODI OS/2 Client Driver


An OS/2 computer gains access to NetWare servers by using the Requester for OS/2.

The Requester needs the OS/2 ODI driver to enable it to use the HP Ethernet

Family Adapter to access the LAN medium.

The OS/2 ODI driver

PCNTNW.OS2

is contained in the LAN Disk in the

\NOVELL\OS2CLNT

directory.

To install the ODI driver for OS/2, follow the instructions below:

1 Boot the computer into OS/2. Enter OS/2 into full screen mode by double-clicking on the Command Prompts icon in the OS/2 System window and then double clicking on the OS/2 Full Screen icon.

2 If you are installing OS/2 Requester from the NetWare Requester Disk, go to the steps given under “Installing OS/2 Requester from NetWare Requester Disk” on page 26.

If you are installing OS/2 Requester from the NetWare WSOS2_1 Disk, go to the steps given under “Installing OS/2 Requester from NetWare WSOS2_1 Disk” on page 27.

Installing OS/2

Requester from

NetWare Requester

Disk

To install from the NetWare Requester disk, follow the steps below:

1 Insert the NetWare Requester diskette into the drive and run the INSTALL program. For example, if the diskette is in drive A, then type the following commands:

A:\

INSTALL

2 Choose the Requester on Workstation under the Installation menu.

3 When the Select Options for CONFIG.SYS window appears, type the driver name

PCNTNW.OS2

into the field labeled Network Interface Card driver .

4 Select any other CONFIG.SYS options you wish to modify. When finished click on the

Save

button.

26 English



5 Click on the YES button when asked if PCNTNW.OS2 is a third party NIC driver.

6 When the window Install Third Party NIC Driver appears, remove the Novell diskette then insert the LAN Disk.

7 When asked for the File to Install type in the name (PCNTNW.OS2) and path of the ODI driver. For example, if the LAN Disk is in drive A, the name and path is

A:\NOVELL\OS2CLNT\PCNTNW.OS2

. Click on the

OK

button.

The installation of the OS/2 ODI driver is now complete.

Installing OS/2

Requester from

NetWare WSOS2_1

Disk

To install from the NetWare Requester disk, follow the steps below:

1 Insert the NetWare WSOS2_1 diskette into the drive and run the INSTALL program. For example, if the diskette is in drive A, then type the following commands:

A:\

INSTALL

2 Choose the Requester on Workstation under the Installation menu.

3 When the Choose the ODI LAN Driver window appears, enter the name

PCNTNW.OS2

. Click on the

Continue

button.

4 When the window titled Copy ODI LAN Driver Files appears, it will have the line

Default ODI LAN Driver: PCNTNW.OS2

with the

Copy only the default driver button selected. Click on the OK button.

5 The INSTALL program will now prompt for the driver diskette with the message:

Insert diskette labeled WSDRV_1 or a diskette containing thirdparty drivers

.

Insert the LAN Disk. Click the OK button.

6 The Copy Requester Files window will be displayed. Click the

OK

button to copy the OS/2 ODI driver into the NetWare Requester directory on the OS/2 drive.

7 After the software installation process has completed, select This workstation in the Configuration menu to edit the NET.CFG file.

English 27

NOTE



8 Click on the Edit button to open the edit window.

Edit the NET.CFG file to match the HP Ethernet Family Adapter configuration

(refer to “Sample NET.CFG File” on page 41 if necessary). Create a link driver section for the HP Ethernet Family Adapter as shown below:


BUSTYPE PCI1


LED2 90

9 Click on the

SAVE

button when all the link driver parameters are correct.

10 The installation and changes made will not take effect until the computer is rebooted. Use the OS/2 shutdown procedure to restart the OS/2 system safely.

The installation of the OS/2 ODI driver is now complete.

The OS/2 ODI driver default frame type is ETHERNET_802.2. NetWare 286 and 386 servers use frame type ETHERNET_802.3 as their default but NetWare 4.0 uses both

ETHERNET_802.2 and ETHERNET_802.3 types.

28 English

NOTE


ODI Driver for Windows for Workgroups Clients


Windows for Workgroups is designed to support file and print sharing with multiple types of servers at the same time, such as Novell and Microsoft. Both Novell and

Microsoft protocols can use the ODI driver to access the LAN adapter and the LAN medium.

Microsoft Windows for Workgroups computers can attach to Novell servers through the Novell NetWare Client for DOS and MS Windows, which is also known as the

Novell DOS Requester.

To attach to Windows NT or LAN Manager servers, Windows for Workgroups provides software called the Microsoft Windows Network.

This section contains instructions for installing Windows for Workgroups with the

Novell DOS ODI driver.

The ODI driver PCNTNW.COM

is contained in the LAN Disk directory

\NOVELL\DOSCLNT\ .

When you start your PC for the first time you will be asked to select which type of network you want to use with your PC. According to your selection the appropriate drivers and files will be installed automatically. If you want to install network software at any other time (for example having deleted your hard disk), follow the procedure described below.

To install the ODI driver, follow the instructions below:

1 Check that you have the items necessary for installation:

•

The Windows for Workgroups 3.11 disks.

•

The NetWare Client for DOS Requester (VLM.EXE).

•

The LAN Disk for the HP Ethernet Family Adapter.

English 29



2 Windows for Workgroups must be installed to allow the Novell client to install its

Windows support. However, the Windows for Workgroups network setup requires the Novell client to be installed to complete the configuration successfully.

a Insert diskette 1 of Windows for Workgroups into the diskette drive. To start the installation, type the following at the DOS prompt:

A:

SETUP b Select

Custom Setup

when prompted for the type of setup to run.

c Select Networks...

when the Network Setup windows appears.

d Select

No Windows support for networks

and then click on the

OK

button.

e Select

Continue

when the Network Setup window reappears.

f Choose the Make all modifications for you button in the Windows Setup window to make changes to CONFIG.SYS and AUTOEXEC.BAT automatically, and select

Continue

.

g Select

Return to MS-DOS

when the Windows for Workgroups installation is completed.

3 The Netware Client for DOS and Windows should now be installed.

a Insert diskette 1 of the NetWare Client into the diskette drive. To start the installation, type the following at the DOS prompt:

A:

SETUP b Select

YES

to update the AUTOEXEC.BAT file. c Select

YES

to install the NetWare Windows support.

d Press to continue the installation.

e Insert the LAN Disk when the

Insert The Driver Disk

window appears and press .

f When the driver name HP Ethernet Family Adapter with LAN Remote

Power appears, press ENTER to continue with the rest of the NetWare client installation.

30 English



4 Having completed the installation, the computer must be rebooted and Windows for Workgroups restarted.

It is not necessary to login or attach to a NetWare server, but the NetWare DOS

Requester must have been successfully initialized.

5 In Program Manager, double-click on the Network Setup icon in the Network group to configure Windows for Workgroups networking.

To connect to Novell servers only, go to the steps given under refer to the steps given under “Connecting to Novell Servers Only” on page 31 .

To connect to both Novell and Microsoft servers then go to the steps given under refer to the steps given under “Connecting to Novell and Microsoft Servers” on page 32.

Connecting to Novell

Servers Only

To configure Windows for Workgroups for connection to Novell servers:

1 Select

Networks...

at the Network Setup window.

2 Choose the Install Windows support for the following network only button in the Networks window.

3 Highlight the

Novell Netware (Workstation Shell 4.0 and above)

line in the drop-down listbox and select

OK

.

4 Select

OK

in the Network Setup window.

5 Select NO in the Windows Setup window to leave the NetWare Client software untouched.

6 Select Restart Windows in the last window for all the changes to take effect.

The installation is now complete.

NOTE Login to the NetWare server before starting Windows for Workgroups.

English 31



Connecting to Novell and Microsoft Servers

To configure Windows for Workgroups for connection to Novell and Microsoft servers:

1 Select Networks...


2 Choose the button

Install Microsoft Windows Network

in the Networks window.

3 Choose the button Other under the line You can also install Windows support for an additional network .

4 Highlight the

Novell Netware (Workstation Shell 4.0 and above)

line in the drop-down listbox and select

OK

.

5 Select Drivers...


6 Select Add Adapter...

at the Network Drivers window.

7 Highlight the

Unlisted or Updated Network Adapter

line in the listbox and select

OK

.

8 Insert the LAN Disk.

9 Type

A:\WFW311\

in the Path field of the Install Driver window.

10 Highlight the line

HP Ethernet Family Adapter with LAN Remote Power

and select OK . If this line does not appear then “Windows for Workgroups OEM

Information Files” on page 33.

11 Select Close at the Network Drivers window.

12 Select

OK

in the Network Setup window.

13 Enter the user, workgroup, and computer names at the Microsoft Windows

Network Names window and select OK .

14 Select

NO

in the Windows Setup window to leave the NetWare Client software untouched.

15 Select Restart Windows in the last window for all the changes to take effect. The installation is now complete.

NOTE Login to the NetWare server before starting Windows for Workgroups.

Logins to Microsoft servers occur automatically after they have been configured in the “Connect Network Drive” window.

32 English

NOTE



Windows for Workgroups OEM Information Files

Windows for Workgroups 3.11 network adapter setup uses the file OEMSETUP.INF to determine the driver information for the HP LAN adapter installed in your computer. Information from the OEMSETUP.INF file is used by the network adapter setup program to install the drivers into the Windows directory and to create a PROTOCOL.INI file with the correct parameters.

When Windows for Workgroups installs a driver from a vendor diskette, it also stores a copy of the vendor's OEMSETUP.INF file in the Windows system directory.

The OEMSETUP.INF file is renamed OEMnn.INF, where “nn” is two decimal digits

(00, 01, 02, and so on). There is no checking for duplicate information.

When the Windows for Workgroups network adapter setup program is run from the

Control Panel network icon, it scans all the OEMnn.INF files for any network drivers. This scan can become confused if multiple OEMnn.INF files contain identical information (perhaps being copies of the same original OEMSETUP.INF file).

To correct this situation and allow installation of the ODI driver from the LAN Disk, any copies of the HP OEMSETUP.INF file from previous installation attempts must be deleted from the Windows directory.

To rectify any problems in finding the ODI driver, delete all OEMnn.INF files that are identical to the OEMSETUP.INF file on the LAN Disk.

English 33


Parallel Transferring ODI DOS Client Driver


The Parallel Transferring ODI DOS Client Driver is a high performance, optimized version of the ODI driver for DOS. It achieves extra performance by utilizing the

LAPP capability of the HP Ethernet Family Adapter.

It is only recommended to use this driver where extra performance is essential.

Otherwise the standard ODI DOS driver should be used.

It can be used by DOS and Microsoft Windows 3.x computers to gain access to

Novell servers through one of the following:

❒ NetWare DOS Requester (using Virtual Loadable Modules or VLMs) or

❒ NetWare DOS Shell (using NETX.EXE)

The Parallel Transferring DOS ODI driver is contained within the

NOVELL\LAPPCLNT directory of your LAN Disk.

To install the Parallel Transferring ODI driver with DOS Requester (VLM.EXE), refer to page 35 .

To install the Parallel Transferring ODI driver with DOS Shell (NETX.EXE), refer to page 37 .

For more information about the NET.CFG file, refer to the Novell NetWare manuals and “NET.CFG Options for Novell NetWare” on page 39 .

34 English



Parallel Transferring ODI Driver with DOS Requester

To install the Parallel Transferring ODI driver for DOS, follow the instructions below:

1 Locate the Novell DOS Requester “NetWare Client for DOS and MS Windows” diskettes. These could be labeled “WSDOS_1” and “WSWIN_1”. To create these diskettes from the NetWare CD ROM, follow the NetWare documentation included with the CD-ROM.

2 Run the NetWare client installation program.

a Insert the number 1 diskette into the drive and run the INSTALL program. For example, if the NetWare diskette is in drive A, then type:

A:

INSTALL b Follow the Novell instructions to fill in the first three fields of the form.

c It is recommended to answer Yes when asked if you want to allow the Novell install program to modify the start-up files. This will make the NetWare client start up automatically and attach to the server every time the computer is rebooted. If

No

is entered, the commands to start up the NetWare client will have to be entered manually.

d If Windows is installed on the computer, it is recommended to answer Yes to allow the Novell install program to add Windows support.

3 When asked to select the driver for your network board, remove the Novell diskette and insert the LAN Disk. Press to bring up the Network Board window.

4 Enter A:\NOVELL\LAPPCLNT then press .

5 The line

HP Ethernet Family Adapter with LAN Remote Power (LAPP)

will be highlighted. Press to select the driver (PCLAPP.COM).

English 35

NOTE



6 The Novell INSTALL program will display a window with the settings for the card.

The following parameters will be shown:

Optional Bus Identifier

Optional Media Frame Type(s)

Optional Node Address

Optional Media Type

Optional LAN Activity Light

Press without selecting to override any parameters and proceed with the remainder of the steps in the NetWare DOS Requester INSTALL program.

7 The installation of the Parallel Transferring DOS ODI driver and NetWare client software is complete. Refer to page 38 for information on how to start a Parallel

Transferring NetWare client.

The ODI driver default frame type is ETHERNET_802.2. NetWare 286 and 386 servers use frame type ETHERNET_802.3 as their default, but NetWare 4.0 uses both ETHERNET_802.2 and ETHERNET_802.3 types. The HP Ethernet Family

Adapter supports both Ethernet frame types.

36 English

NOTE



Parallel Transferring ODI Driver with DOS Shell


1 To begin the installation you require the Novell DOS Shell installation diskette labeled 'WSGEN' and the LAN Disk.

2 Create a directory on the DOS boot drive (for example C) for the HP and NetWare files using the following commands at the DOS prompt:

C:

MKDIR C:\NOVELL

3 Copy the DOS ODI Driver and NET.CFG File. For example, if the LAN Disk is in

Drive A use the following commands:

COPY A:\NOVELL\LAPPCLNT\PCLAPP.COM C:\NOVELL

COPY A:\NOVELL\LAPPCLNT\NET.CFG C:\NOVELL

The contents of the NET.CFG file are given below:

LINK DRIVER PCLAPP

BUSTYPE PCI1


LED2 90

4 Copy the following files from the Novell installation diskette labeled “WSGEN” to the C:\NOVELL directory:

LSL.COM (must be version 2.11 or later)

IPXODI.COM (must be version 2.20 or later)

NETX.EXE

These files are either in the root or the DOSODI directory on the NetWare diskette.

5 The installation of the Parallel Transferring DOS ODI driver and NetWare client software is complete. Refer to page 38 for information on how to start a Parallel

Transferring NetWare client.

The DOS Shell can only access a server's bindery. If you want access any enhanced

NetWare Directory Services, you should use the DOS Requester (VLM).

English 37

NOTE

NOTE



Starting a Parallel Transferring NetWare Client

To start a Parallel Transferring NetWare client, execute the following commands at the DOS prompt:

Steps 1 and 2 are only necessary if you did not allow the Netware Client Installation program to modify your configuration files.

1 Change to the directory where the required files are located (for example

CD

\NOVELL ).

2 Type:

LSL

PCLAPP

IPXODI and either,

NETX or

VLM

(If you use VLM.EXE, the CONFIG.SYS file must include LASTDRIVE=Z to work correctly.)

You will be in the LOGIN directory of the server to which the PC is connected.

3 Type LOGIN server/user server is your server name user is your user name on that server

(If you are not sure of your server name, type SLIST the available servers.)

to display a list of

If you want the PC to be able to log onto the server when it starts, add the commands listed above to the PC's AUTOEXEC.BAT file. Otherwise create another batch file and run it when you want the PC to be able to log onto the server.

38 English


NET.CFG Options for Novell NetWare


For each workstation driver you configure, select a custom set of supported values from the PCnet configuration options. If a driver configuration is different from the default settings or if you are using multiple protocols, you should create a NET.CFG file.

The NET.CFG file is a configuration file that contains section headings and options that deviate from the established defaults of the ODI software.

You may also need to see the documentation specific to your protocol for additional

NET.CFG information.

Use any DOS text editor to create the file. Specify only options that will change from the defaults.

Conventions

Main section headings must be left-justified and are not case sensitive. The heading must precede the options you want to include in that section. Options are not case sensitive and must be preceded by a tab or hard spaces.

Precede comments with a semicolon (;). End each line with a hard return. Write all numbers in decimal notation except where noted otherwise.

English 39

NOTE



Options

The following chart lists the driver options defined by the DOS ODI software. The options available for the PCnet driver (PCNTNW) and IPX protocol stack are shown in a sample NET.CFG file. Protocol stacks other than IPX may have additional options not listed here. Refer to the other protocol's documentation for more information.

Link Driver drivername

DMA [#1|#2] channel_number

INT [#1|#2] interrupt_request_number

MEM [#1|#2] hex_starting_address [hex_length]

PORT [#1|#2] hex_starting_address [hex_number_of]]

NODE ADDRESS hex_address

SLOT number

FRAME frame_type

PROTOCOL name hex_protocol_IDframe_type

SAPS number

LINK STATIONS number

ALTERNATE

MAX FRAM SIZE number

CONNECTOR DIX

Link Support

BUFFERS communication_number [size]

MEMPOOL number[k]

Protocol protocol name

BIND #board_number

The PCnet driver has these NET.CFG options.

•

NODE ADDRESS

•

FRAME

•

PROTOCOL

•

FDUP

For the HP Ethernet Family Adapter, the DMA, INT, and PORT are not required for the driver. In some cases, using these keywords would be a violation of the bus specification. Otherwise, all other keywords may be used with the PCnet Family.

Refer to Chapter 6 “Driver Options - Software Keywords” for complete description of these options.

40 English



Sample NET.CFG File

The following is an example NET.CFG file for the HP Ethernet Family Adapter:


;Specify bus type for the HP Ethernet Family Adapter.

BUSTYPE PCI1

LED2 90

;To change FRAME type to Ethernet_II

FRAME Ethernet_II

PROTOCOL IPX 8137 ETHERNET_II

NetWare DOS Requester

FIRST NETWORK DRIVE = F

Note that there is a remark line preceded by a semicolon before each option line in the sample to indicate the option change.

English 41



42 English

3

Installing Microsoft Network Drivers

NOTE

3 Installing Microsoft Network Drivers



This document explains how to install the network drivers required to use the PC with a network.

•

If the PC is supplied with a LAN Disk, use this to install the LAN drivers.

•

If the PC has preinstalled software on the hard disk, the LAN drivers are supplied on the PC's hard disk in subdirectories in the

\LANDRV

directory.

If you want to use the PC as a LAN Manager client, “LAN Manager 2.x DOS and OS/2

Client Driver” on page 46 .

If you want to use the PC under Windows for Workgroups, “NDIS 2.01 Driver for

Windows for Workgroups 3.1” on page 49 or “NDIS 2.01 and 3.0 Drivers for Windows for Workgroups 3.11” on page 50 .

If you want to use the PC under Windows NT, “NDIS 3.0 Driver for Windows NT 3.5” on page 52 or “Miniport Driver for Windows NT” on page 53 .

If you want to use the PC under Windows 95, “NDIS 2.01 and 3.1 for Windows 95” on page 55 .

Before installing the network drivers, connect the HP Ethernet Family Adapter to the LAN and set up (configure) the HP Ethernet Family Adapter.



44 English

NOTE


Network Driver Interface Specifications (NDIS)

Network Driver Interface Specifications (NDIS)

Microsoft NDIS (Network Driver Interface Specifications) 2.01 and 3.x are driver specifications developed by Microsoft Corporation to offer a standard driver interface for all adapters. A standard driver interface provides flexibility to support not only multiple network adapter cards but also multiple protocol stacks. As a result, many operating systems have incorporated the NDIS interface to make configuration and installation of network adapters easy and independent of the network adapter used.

Included in this guide are instructions to install the HP Ethernet Family Adapter driver for the following environments:

•

Microsoft LAN Manager 2.x (NDIS 2.01)

•

Microsoft Windows for Workgroups 3.1 (NDIS 2.01)

•

Microsoft Windows for Workgroups 3.11 (NDIS 2.01 and 3.0)

•

Windows NT 3.5 (NDIS 3.0)

•

Windows NT 3.51 (Miniport NDIS 3)

•

Windows NT 4.0 (Miniport NDIS 4)

•

Windows 95 (NDIS 2.01 and 3.1)

Some of the custom installation procedures provided here are either an abbreviation or a duplication of the software manufacturers installation guidelines.

English 45


LAN Manager 2.x DOS and OS/2 Client Driver


The hardware for the Microsoft LAN Manager environment may be configured to run as an OS/2 client, enhanced MS-DOS client, or a basic MS-DOS client. Refer to the Microsoft documentation for hardware and software requirements. The PCnet

Family NDIS 2.01 driver is located in the MSLANMAN.DOS and MSLANMAN.OS2 directories.

The directory structure provided on the LAN Disk has been set up for automatic installation. This section provides a brief explanation regarding driver installation.

Follow the guidelines in the Microsoft LAN Manager Installation Guide for more details about installing the PCnet Family driver from the LAN Disk.

LAN Manager has a SETUP program that may be used to import and configure drivers. The SETUP utility for LAN Manager will install the PCnet NDIS driver that is provided on the LAN Disk. SETUP requires that two information files be present in order to install the drivers: NIF, and PROTOCOL.INI. These files are located in the MSLANMAN.OS2 and MSLANMAN.DOS directories of the LAN Disk.

The NIF file provides the information that the SETUP utility needs to coordinate and install the various drivers that are available. Information that is contained in the two files includes driver names, paths on the LAN Disk where the driver is stored, and the type of driver.

The PROTOCOL.INI file is used by the LANMAN Protocol manager and NETBIND program at startup time. This file contains the NDIS and Transport specific parameters for the network. Both NDIS (PCnet driver) and Transport (NETBEUI) have their own PROTOCOL.INI, and when SETUP installs NDIS and Transport, the two PROTOCOL.INI files will be merged into one file.

46 English

File Examples



Installation Procedure

To install the PCnet Family NDIS Client or Server driver, follow the instructions given below:

1 Insert the LAN Disk into the flexible disk drive.

2 From the LAN Manager subdirectory, run LAN Manager SETUP to begin installation.

3 Use the ALT key on your keyboard and the highlighted letter(C) to pull down the

Configuration menu.

4 From the Network Adapter Drivers dialog box, select the HP Ethernet Family

Adapter from the menu, if shown. Otherwise, select Other Driver to import the HP

Ethernet Family Adapter driver from the LAN Disk.

5 Then, enter the disk drive letter for the LAN Disk.

6 Select the HP Ethernet Family Adapter and choose OK.

7 Select the desired protocol from the Network Protocol dialog box and choose OK.

8 In the Workstation Configuration dialog box, select the HP Ethernet Family

Adapter and choose OK.

9 Follow the remaining instructions from LAN Manager to complete the installation.

During installation, LAN Manager will automatically make modifications to

CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI files. Below is an example of these files for the HP Ethernet Family Adapter.

CONFIG.SYS:

DEVICE=C:\LANMAN.DOS\DRIVERS\PROTMAN\PROTMAN.DOS /i:C:\LANMAN.DOS

DEVICE=C:\LANMAN.DOS\DRIVERS\ETHERNET\PCNTND\PCNTND.DOS

AUTOEXEC.BAT:

SET PATH=C:\LANMAN.DOS\NETPROG;%PATH%

NET START WORKSTATION

LOAD NETBEUI

NET LOGON BEVERLY.SMITH

English 47



PROTOCOL.INI:

[PROTMAN]

DRIVERNAME=PROTMAN$

DYNAMIC=YES

PRIORITY=NETBEUI

[NETBEUI_XIF]

DRIVERNAME=netbeui$

SESSIONS=6

NCBS=12

BINDINGS="PCNTND_NIF"

LANABASE=0

[PCNTND_NIF]

;---------------------------------------------;

; HP Ethernet Family Adapter ;

;---------------------------------------------;

DRIVERNAME=PCNTND$

BUSTYPE=PCI1

LED2=0x90

Keyword Examples

Changing Transmit and Receive Buffers

Insert the following statements in PROTOCOL.INI under the PCnet (PCNTND) driver section:

RXBUFFERS=4

TXBUFFERS=8

Designating BUSTYPE keyword

Remove the I/O Address and insert the BUSTYPE keyword in PROTOCOL.INI under the PCnet (PCNTND) driver section.

Refer to Chapter 6 “Driver Options - Software Keywords” for complete description of these options.

48 English


NDIS 2.01 Driver for Windows for Workgroups 3.1

NDIS 2.01 Driver for Windows for Workgroups 3.1

The PCnet NDIS drive also supports Windows for Workgroups 3.1 environment. The installation for the NDIS 2.01 driver is menu driven through the Windows interface.

The PCnet driver and other relevant files are located in the WFW31 subdirectory.


Follow the guidelines in the Microsoft Windows for Workgroups User's Guide for more details about installing the PCnet Family driver from the LAN Disk.


To install the PCnet Family NDIS 2.01 driver, follow the instructions given below:

1 Insert the LAN Disk in the system's flexible disk drive.

2 From the Main group in Windows, choose the Control Panel icon.

3 In the Network Settings dialog box, choose the Adapters button and the Network

Adapters dialog box should appear.

4 Choose the

Add

button to install the PCnet driver from the LAN Disk.

5 In the list of network adapters, select the

Unlisted or Updated Network

Adapter option.

6 Enter the drive letter and the \WFW31 path to load the PCnet Family NDIS driver:

For example,

A:\WFW31\

7 Select the HP Ethernet Family Adapter and choose OK .

8 A setup dialog box appears displaying the default settings. For the HP Ethernet

Family Adapter, no settings need to be specified .

9 Choose the

Close

button in the Network Adapters dialog box, then choose the

OK button in the Network Settings dialog box. The installation is complete.

Follow the subsequent Windows instructions to restart the computer and activate the driver.

English 49


NDIS 2.01 and 3.0 Drivers for Windows for Workgroups 3.11


When you start your PC for the first time you will be asked to select which type of network you want to use with your PC. According to your selection the appropriate drivers and files will be installed automatically. If you want to install network software at any other time, follow the procedure described below.

Microsoft's Windows for Workgroups 3.11 supports both NDIS 2.01 and NDIS 3.0 drivers. The HP Ethernet Family Adapter provides both NDIS drivers to run under the Windows for Workgroups 3.11 environment. Note the format and procedure to install the NDIS drivers for Windows for Workgroups 3.11 is different from that of

Windows for Workgroups 3.1.

The directory structure provided on the LAN Disk has been setup for automatic installation. This section provides a brief explanation regarding driver installation.

Follow the guidelines in the Microsoft Windows for Workgroups 3.11 User's

Guide for more details about installing the PCnet Family driver from the LAN Disk.


To install the PCnet NDIS 2.01 and/or NDIS 3.0 drivers, simply follow the instructions given below:

1 Insert the LAN Disk into the system's flexible disk drive.

2 In the Windows for Workgroups 3.11 Program Manager, double click on the

Windows Setup icon from the MAIN window.

3 From the Windows Setup dialog box, select the Change Network Settings from the

Options menu to install PCnet drivers from the LAN Disk.

4 From the Network Setup dialog box, select the

Drivers...

button to install the

PCnet NDIS 2.01 and NDIS 3.0 drivers.

5 Then, in the Network Drivers dialog box, select Add Adapter button to install the

PCnet device drivers.

50 English



6 Now, in the Add Network Adapter window, choose the Unlisted or Updated

Network Adapter

from the menu and then select

OK

.

7 Enter the flexible disk drive letter for the LAN Disk and specify the

\WFW311 subdirectory to install the PCnet drivers: For example,

A:\WFW311\

Then select

OK

.

8 The HP Ethernet Family Adapter will appear under the Network Adapters list.

Simply select OK to continue.

9 Then, you will be asked for information on the Twisted Pair keyword option, refer to “Driver Options - Software Keywords” for more details.

For the HP Ethernet Family Adapter, no values need to be specified for the

I/O address, interrupt channel and DMA channel since these are configured automatically by the software.

10 Then, select

OK

to exit. Windows for Workgroups 3.11 will ask you to reboot the machine once installation is completed.

The installation for Windows for Workgroups 3.11 is now completed.

English 51


NDIS 3.0 Driver for Windows NT 3.5

NDIS 3.0 Driver for Windows NT 3.5

The LAN Disk also includes the NDIS 3.0 driver for the Windows NT environment.


Follow the guidelines in the Microsoft Windows NT User's Guide for more details about installing the PCnet Family driver from the LAN Disk.


To install the PCnet NDIS 3.0 driver, simply follow the instructions given below to navigate through the menu driven functions in Windows NT.


2 From the Control Panel in the Windows NT Main window, double click on the

Network icon to install the HP Ethernet Family Adapter.

3 In the Network Settings dialog box, choose Add Adapter .

4 In the Add Network Adapter dialog box, select the adapter card list menu and

Select

<Other> Requires disk from manufacturer

from the list.

5 In the next window, specify the drive letter and path for the files.

For example:

A:\WINNT3X\

6 Select the


from the dialog box.

7 Verify that the BUS_TO_SCAN parameter is set to PCI1 for an HP Ethernet

Family Adapter.

For the HP Ethernet Family Adapter, no I/O address, IRQ or DMA channel values need to be specified.

8 Close the Setup dialog box and exit from the Add Network adapter dialog box to complete the installation. Follow any subsequent instructions from Windows NT to reboot your system, if required.

For additional guidelines, refer to the Microsoft Windows NT documentation.

52 English


Miniport Driver for Windows NT


The LAN Disk also includes the Miniport driver for the Windows NT environment.

The directory structure provided on the LAN Disk has been set up for automatic installation. This section provides a brief explanation regarding driver installation for Windows NT 3.51 and Windows NT 4.0. Follow the guidelines in the Microsoft

Windows NT User's Guide for more details about installing the PCnet Family driver from the LAN Disk.

Installing Miniport Driver for Windows NT 3.51

To install the PCnet Miniport driver, simply follow the instructions given below to navigate through the menu driven functions in Windows NT.


2 From the Control Panel in the Windows NT Main window, double click on the

Network icon to install the HP Ethernet Family Adapter.

3 In the Network Settings dialog box, choose Add Adapter .

4 In the Add Network Adapter dialog box, select the adapter card list menu and

Select

<Other> Requires disk from manufacturer

from the list.

5 In the next window, specify the drive letter and path for the files.

For example:

A:\WINNT351\

6 Select the


from the dialog box.

7 Close the Setup dialog box and exit from the Add Network adapter dialog box to complete the installation. Follow any subsequent instructions from Windows NT to reboot your system, if required.


English 53



Installing Miniport Driver for Windows NT 4.0

To install the Miniport driver, follow the instructions given below to navigate through the menu driven functions in Windows NT.


2 Select Start, Settings, Control Panel, Network.

3 In the Network dialog box, choose the

Adapter

tab and then select

Add...

4 In the Select Network Adapter dialog box, select

Have disk...

5 In the next window, specify the drive letter and path where the files may be found:

A:\WINNT40\

6 Select the HP Ethernet Family Adapter from the dialog box.

7 Follow any subsequent instructions from Windows NT to reboot your system, if required.


54 English


NDIS 2.01 and 3.1 for Windows 95


Microsoft Windows 95 supports both NDIS 2.01 and NDIS 3.1 drivers. The HP

Ethernet Family Adapter provides both NDIS drivers to run with Windows 95.

The directory structure provided on the LAN Disk has been setup for automatic installation. This section provides a brief explanation regarding the driver installation.


To install the PCnet NDIS 2.01 and/or NDIS 3.1 drivers, follow the instructions given below:

1 From the Settings menu, start the Control Panel.

2 To run the Network configuration utility, double click on the Network icon.

3 Click on the

Add

button.

4 In the Select Network Component Type window, choose

Adapter

then click on the Add button.

5 To install the driver provided on the LAN Disk, click on the

Have Disk

button.

6 In the

Install from disk

window, specify the drive letter and path for the files on the LAN Disk. For example:

A:\W95\

Then select

OK

.

A new Select Network Adapter window is displayed.

7 Click on HP Ethernet Family Adapter with LAN Remote Power in the Drivers list and then click on the OK button.

8 The selected driver now appears in the driver list and no specific configuration is needed. Click on the

OK

button.

9 Windows 95 will ask the you to do a Shutdown to make the changes effective.

Click Yes to shut down and restart.

The installation for Windows 95 is now complete.

English 55



56 English

4

Installing Other Network Drivers

NOTE

4 Installing Other Network Drivers



This document provides installation instructions to install the PCnet Family NDIS

2.01 driver for the following environments:

•

Artisoft LANtastic

•

Banyan VINES

•

DEC PATHWORKS 5.0

•

FTP PC/TCP 2.x

•

IBM Warp Connect

•

IBM LAN Services 4.0

•

Sun Microsystems PC-NFS 5.0

•

Other DOS and OS/2 Networking Products

The directory structure provided on the LAN Disk has been set up for automatic installation. This document provides a brief explanation regarding driver installation. Follow the guidelines in the OEM documentation for more details on how to install a driver from the LAN Disk.

•

If the PC is supplied with a LAN Disk, use this to install the LAN drivers.

•

If the PC has preinstalled software on the hard disk, the LAN drivers are supplied on the PC's hard disk in subdirectories of the C:\LANDRV directory.

Some of the custom installation procedures provided here are either an abbreviation or a duplication of the software manufacturers installation guidelines.


Microsoft Windows NT 4.0 and Microsoft Windows 95

58 English


NDIS 2.01 Driver for Artisoft LANtastic 6.0


Artisoft LANtastic 6.0 uses the NDIS 2.01 specification. To install the NDIS 2.01 driver in LANtastic versions earlier than 6.0, please contact your Artisoft representative. The NDIS 2.01 driver itself is provided in the NDIS\DOS directory.


To install a driver for LANtastic 6.0, start from the DOS system prompt. Follow the steps listed below:

1 Insert Disk 1 of LANtastic 6.0 into your flexible disk drive (for example, A). At the

DOS prompt type:

A:\install

This starts the LANtastic installation process.

2 Artisoft's installation program will then search for Microsoft Windows on your system. If Windows is not found, press at the message to run the install program under DOS and go to the steps given under See “Installation for DOS” on page 60.

Otherwise, if Windows is found, Windows will be started. Go to the steps given under See “Installation for Windows” on page 61.

English 59



Installation for DOS

After pressing at the message to run the install program under DOS:

1 Some Artisoft initialization messages will appear on the screen. Press continue.

2 If this is the first installation, you will be prompted for

Station Name

and

Target

Directory

. Then, select

KEEP all previous LANtastic setup information

.

3 Select any additional LANtastic features you wish to install (see Artisoft

LANtastic manuals for more information). Press to continue.

4 At Select Network Adapter, select

NDIS Support for Network Adapters

.

5 Insert the HP Ethernet Family Adapter disk into the flexible disk drive and then press to continue.

6 Insert the appropriate Artisoft LANtastic 6.0 disks when prompted. Press

to continue.

7 Select

OK to perform the installation

and press .

8 Information will appear on the screen. Press to continue.

9 Insert the appropriate Artisoft LANtastic 6.0 disk when prompted. Press to continue.

10 You will see the “Installation Complete” and “Need to reboot your computer” messages. Press to continue. Remove the disk from the flexible disk drive. Press to reboot.

11 During the boot sequence you will see the message:

AMD PCNet Family Ethernet Adapter

NDIS v2.01 MAC Driver, version x.xx

Drivername

Station Address and other configuration information.

12 Next, you will see some LANtastic configuration messages.

The installation of the NDIS 2.01 driver for Artisoft LANtastic 6.0 is now complete.

60 English

Installation for

Windows



After the install program has started Windows:

1 You will see the Artisoft Install message. Click OK to continue.

2 If this is the first installation, you will be prompted for

Station Name

, and

Target

Directory

. Then, select

KEEP all previous LANtastic setup information and click

OK

to continue.

3 Select any additional LANtastic features you wish to install (see Artisoft

LANtastic Manuals for more information). Click OK to continue.

4 At Select Network Adapter, select

NDIS Support for Network Adapters

and click

OK

to continue.

5 Insert the HP Ethernet Family Adapter disk into the flexible disk drive and then click OK to continue.

6 Insert the appropriate Artisoft LANtastic 6.0 disks when prompted. Click

OK

to continue.

7 Select OK to perform the installation and click OK to continue.

8 Information will appear on the screen. Click OK to continue.

Insert the appropriate Artisoft LANtastic 6.0 disk when prompted. Click

OK

to continue.

9 You will see the Installation complete and Need to reboot your computer messages. Click OK to continue. Remove the flexible disk from the drive. Click OK to reboot.

10 During the boot sequence you will see the message:

AMD PCNet Family Ethernet Adapter

NDIS v2.01 MAC Driver, version x.xx

Drivername

Station Address

and other configuration information.

11 Next, you will see some LANtastic configuration messages.

The installation of the NDIS 2.01 driver for Artisoft LANtastic 6.0 is now complete.

English 61


NDIS 2.01 Driver for Banyan VINES Client


The PCnet driver may be configured to run in the Banyan VINES environment for client-based systems only.


The steps to load the driver are as follows:

1 Compile all the files necessary for VINES. For ease of use, all of these files were placed in the

C:\NDIS

subdirectory.

2 Create PROTOCOL.INI, CONFIG.SYS, and AUTOEXEC.BAT (refer to the example below).

a Modify the PROTOCOL.INI to reflect the changes necessary for the appropriate LAN card section.

b Modify the AUTOEXEC.BAT and CONFIG.SYS to reflect changes in the

DIRECTORY of where the files are to be placed.

3 Run the VINES PCCONFIG to configure the NDIS Ethernet Driver: a Select

Network Card Settings

. Then in the list provided, select

NDIS

Ethernet

.

b Verify that the interrupt level matches the one used by the driver (check that the “bindings” parameter is PCNTND: bindings = PCNTND

).

c Save and exit from PCCONFIG.

4 Restart the PC.

5 At the DOS prompt type BAN


62 English

File Examples



The modifications to CONFIG.SYS, AUTOEXEC.BAT, and PROTOCOL.INI are shown below as an example for HP Ethernet Family Adapter:

CONFIG.SYS:

FILES=20

BUFFERS=20

DEVICE=C:\NDIS\PROTMAN.DOS /I:C\NDIS

DEVICE=C:\NDIS\PCNTND.DOS

AUTOEXEC.BAT:

PATH=C:\DOS

PROMPT $P$G

C:

CD \NDIS

BAN

PROTOCOL.INI:

; PROTOCOL.INI section for the HP Ethernet Family Adapter

[PCNTND]


BUSTYPE=PCI1

LED2=0x90

English 63


NDIS 2.01 Driver with DEC PATHWORKS 5.0 Client

NDIS 2.01 Driver with DEC PATHWORKS 5.0 Client

The installation procedure for a DEC PATHWORKS 5.0 client is as follows:

1 Verify that you have DOS and at least a minimal installation of Windows on your

PC.

2 Insert your Lan Manager setup diskette in your diskette drive (for example A:), and make that drive the current drive the active drive by typing

A:

3 Run SETUP by typing SETUP

4 Select

Configure PC

.

5 Select the drive you are installing the client from:

A:\

if you want to install it from the diskette drive, or select

Network

if you want to install it from the DEC

PATHWORKS server.

6 Select the protocol you want to use ( netbeui , for example).

7 In the adapter list, select

Other

, and fill in the blanks with the following information:

Adapter Name = HP Ethernet Family Adapter with LAN Remote Power

NDIS driver path = A:\NDIS\DOS

NDIS driver File = PCNTND.DOS

NDIS driver Name = PCNTND$

8 Then follow the SETUP program, until the

Edit PROTOCOL.INI

screen, please verify that it contains the following information:

;------------------------------------;


;------------------------------------;

DriverName = PCNTND$

BUSTYPE = PCI1

LED2 = 0x90

Make any changes if necessary and then save the file.

9 Follow the SETUP program for the rest of the installation, and refer to the

PATHWORKS Client Installation Guide if you have any difficulties.


64 English

NOTE


NDIS 2.01 Driver with FTP PC/TCP 2.x for DOS/Windows


The NDIS 2.01 driver

PCNTND.DOS

is located on the LAN Disk in directory

\NDIS\DOS .

The HP NDIS 2.01 drivers are self-configuring, which means the driver will automatically locate and read the HP Ethernet Family Adapter's configuration. Only the DRIVERNAME and BUSTYPE parameters need to be present under the

[PCNTND] section in the PROTOCOL.INI file.

To install the NDIS 2.01 driver with FTP PC/TCP, follow the instructions below:

1 Install the FTP PC/TCP for DOS/Windows software, following the installation guide provided with the software and ensuring that the DIX Ethernet driver

(ETHDRV) is selected as the PC/TCP kernel

Ensure that you note the directory into which FTP PC/TCP is installed. It is assumed that FTP PC/TCP will be installed in the

C:\FTP

directory. However this may not be the case and it may be necessary to substitute any further references to C:\FTP with the correct directory for your installation.

2 Insert the LAN Disk into the flexible disk drive (drive A for example), then enter the following command at the DOS prompt:

COPY A:\NDIS\DOS\PCNTND.DOS C:\FTP

3 Insert the FTP DOS/Windows diskette into the diskette drive and enter the following commands at the DOS prompt:

COPY A:\PROTMAN.DOS C:\FTP

COPY A:\PROTMAN.EXE C:\FTP

COPY A:\NETBIND.COM C:\FTP

Verify that the PC/TCP packet driver to NDIS driver converter module

DIS_PKT.GUP is in the same directory (in this example,

C:\FTP

).

4 Use the PROTOCOL.FTP file located in the directory where PC/TCP is installed as a template and with reference to the example shown below, create a customized PROTOCOL.INI for the computer.

English 65



Sample PROTOCOL.INI file:

[PROTMAN]

; Protocol manager drivername = PROTMAN$

[PKTDRV] drivername = PKTDRV$ intvec = 0x60 bindings = PCNTND_NIF

[PCNTND_NIF]

; HP Ethernet Family Adapter

DRIVERNAME = PCNTND$

BUSTYPE = PCI1

LED2 = 0x90

The PROTOCOL.INI file must include a section describing the LAN adapter (the

PCNTND

section) and a section describing each of the network products being run. Each network product section (e.g. NFS-NDIS) must include a BINDINGS statement.

5 The CONFIG.SYS file must be modified to contain the DEVICE

statements that load the required drivers (the Protocol Manager, HP NDIS 2.01, and packet driver converter).

Add the following statements near the end of the CONFIG.SYS file:

DEVICE = C:\FTP\PROTMAN.DOS /I:C:\FTP

DEVICE = C:\FTP\PCNTND.DOS

DEVICE = C:\FTP\DIS_PKT.DOS

Please refer to the FTP PC/TCP for DOS/Windows Installation Guide for more information about how to customize the CONFIG.SYS file for FTP PC/TCP software.

❒ The

DEVICE

statement for the PROTMAN driver must come before the other network driver DEVICE statements.

❒ The /I: parameter in the DEVICE statement for the PROTMAN file identifies the path to the PROTOCOL.INI file (in this example C:\FTP ).

66 English



6 Before running any network application (such as FTP or TELNET), PC/TCP must be started. Add the following lines near the beginning of the AUTOEXEC.BAT file:

SET PCTCP=C:\FTP\PCTCP.INI

C:\FTP\NETBIND

C:\FTP\ETHDRV

7 The changes made to the PROTOCOL.INI, CONFIG.SYS and AUTOEXEC.BAT will not take effect until your computer is rebooted. Reboot your computer in order to activate the FTP PC/TCP software.

The installation of FTP PC/TCP is now complete.

English 67


NDIS 2.01 Driver for IBM LAN Services 4.0


The PCnet driver may also be configured to run under the IBM LAN Server environment. Although the IBM LAN Server software uses the same NDIS driver as the Microsoft LAN Manager network operating system, the IBM LAN Server software requires a unique NIF file from Microsoft's LAN Manager. This NIF file is included on the LAN Disk.


Follow the guidelines in the IBM LAN Adapter and Protocol Support

Configuration Guide for more details about installing the PCnet Family driver from the LAN Disk.


To install the driver for IBM LAN Services 4.0 (LAN Requester), follow these steps:

1 Insert the LAN Disk into the flexible disk drive.

2 Open the LAN Services folder (or run “MPTS”).

3 Run OS/2 LAN Services Installation/Configuration.

4 When the Basic or Advanced Installation/Configuration dialog box is displayed, choose

Advanced

.

5 When the Install Type dialog box is displayed, choose Install or Configure this workstation.

6 When the Installation and Configuration dialog box is displayed, choose

Configure a component

. Then choose

OK

.

7 When the Configure dialog box is displayed, choose LAN Adapter and Protocol

Support and choose Configure . Then choose OK .

8 In the LAPS Configuration dialog box, choose Other Adapters.

68 English



9 At the Copy Additional Network Adapter Drivers dialog box, type the path:

A:\IBM

Then choose OK .

10 When the Copy Diskette dialog box is displayed, choose OK .

11 Choose the


from the

Network Adapters list box, by highlighting the entry. Then choose

Add

to add the

HP Ethernet Family Adapter to Current Configuration list box.

12 Highlight the appropriate protocols in the Protocols list box. Then choose Add to add them to the Current Configuration list box.

You have finished installing the driver for IBM LAN Services 4.0.

Editing

PROTOCOL.INI to

Change the

Configuration

To change the configuration, you can edit keyword entries in the PCNTND_NIF section of PROTOCOL.INI. Here is a sample of the PCNTND_NIF section in

PROTOCOL.INI:

[PCNTND_NIF]


BUSTYPE=PCI1

LED2=0x90

For keyword descriptions, refer to Driver Options - Software Keywords.

English 69


NDIS 2.01 Driver with IBM Warp Connect


To install the NDIS 2.01 driver under IBM Warp Connect, follow the instructions below:

1 When you install IBM Warp Connect, you are asked whether you want to install network support.

If you have already installed Warp Connect without network support, continue with step 2.

If you are installing Warp Connect now, reply Yes to install network support, and go directly to step 6.

2 In the OS/2 System folder, open the OS/2 Warp Connect Install/Remove folder.

3 Click on Warp Connect Selective Install for Networking .

4 Choose Install the product on this workstation (local install) .

5 Select

Easy Installation

.

6 Follow the instructions. You will be offered various network configuration options; consult the Warp Connect User’s Guide for information and continue installation.

7 In the Select Network Adapter window, click on the

Other Adapter

window.

8 When asked for the file location, enter A:\IBM and insert the LAN Disk into the flexible drive. Click OK .

9 The HP Ethernet Family Adapter driver will be shown in the Drivers Found window. Select

Ethernet

as Type of LAN.

You should now see the HP Ethernet Family Adapter highlighted in the list of adapters in the Select Network Adapter window.

10 Insert the Warp Connect CD-ROM. Then click OK .

11 Click

OK

in the Select Network Adapter window to accept the adapter.

12 Click OK again and then click OK a second time in the configuration window.

70 English



13 Click the Install button in the Ready to Install window.

14 Click

OK

to confirm shutdown.

15 Leave the Warp Connect CD-ROM in the CD-ROM drive.

After rebooting, files from the CD-ROM will be needed to install the networking components of the operating system.

16 Reboot the computer.


English 71


NDIS 2.01 Driver for PC-NFS

NDIS 2.01 Driver for PC-NFS

The PCnet Family NDIS 2.01 driver (PCNTND.DOS) may also be installed for the

PC-NFS environment.


Follow the guidelines in the Sun Microsystems PC-NFS Manuals for more details about installing the PCnet Family driver from the LAN Disk.


To install the PCnet Family NDIS 2.01 driver, follow the instructions given below:

1 Create a directory called PCNTND on the PC-NFS diskette, which contains the

QUICKNDIS utility.

2 Copy the files located in the

\NDIS\DOS

directory on the LAN Disk to the

\PCNTND directory on the PC-NFS diskette.

3 Run the PC-NFS QUICKNDIS utility and choose the HP Ethernet Family

Adapter with LAN Remote Power installation from the menu.

4 A message will appear asking for the current boot drive. Enter the current boot drive and press .

5 In the next dialog box, press Y to save the current PROTOCOL.INI as

PROTOCOL.OLD. Ignore this step if this dialog box does not appear.

6 In the adapter card list box, select the Custom option to install the PCnet NDIS driver for PC-NFS.

7 Follow the dialog boxes and enter the pathname A:\PCNFS to install the NDIS driver.

8 Next, enter the PCNTND for the NIF file name and press .

Installation of the PCnet Family NDIS 2.01 driver for PC-NFS is now complete.

72 English

NOTE


NDIS 2.01 Driver with Other Networking Products


The NDIS 2.01 driver is a 16-bit driver used by many DOS and OS/2 networking products to gain access to the LAN.

The NDIS 2.01 driver for DOS and Windows (PCNTND.DOS) is located on the LAN

Disk in directory

\NDIS\DOS

.

The NDIS 2.01 driver for OS/2 (PCNTND.OS2) is located on the LAN Disk in directory

\NDIS\OS2

.

The HP NDIS 2.01 drivers are self-configuring, which means the driver will automatically locate and read the HP Ethernet Family Adapter's configuration. Only the DRIVERNAME and BUSTYPE parameters need to be present under the

[PCNTND] section in the PROTOCOL.INI file.

English 73



To install the HP Ethernet Family Adapter NDIS 2.01 DOS or OS/2 driver, follow the instructions below:

1 Completely install the networking product.

If the product requires that a driver be given and it cannot read the NDIS 2.01 driver off this disk, then pick any other driver to install. In steps 4 and 5 below, when editing the PROTOCOL.INI and CONFIG.SYS files, change all occurrences of that driver's name to

PCNTND

.

2 Create a directory on the computer, for example

C:\NDIS2

, using the following commands:

C:

MKDIR C:\NDIS2

3 Copy the NDIS 2.01 driver file from the LAN Disk to this directory.

For DOS computers with the LAN Disk in the flexible drive (for example A) use the command:

COPY A:\NDIS\DOS\PCNTND.DOS C:\NDIS2

For OS/2 computers with the LAN Disk in the flexible drive (for example A) use the command:

COPY A:\NDIS\OS2\PCNTND.OS2 C:\NDIS2

4 Locate the PROTOCOL.INI file within the networking product's directory created in step 1 and edit this file with a text editor.

The PROTOCOL.INI file must include a section describing the LAN adapter (that is, a [PCNTND] section) and a section describing each of the network products being run. Each network product section must include a BINDINGS statement.

An example section for the HP Ethernet Family Adapter is shown below:

;------------------------------------;


;------------------------------------;


BUSTYPE = PCI1

LED2 = 0x90

For a further description of the parameters used by the HP Ethernet Family

Adapter NDIS 2.01 driver, refer to Driver Options - Software Keywords.

74 English



The driver's PROTOCOL.INI file must be merged with the networking product's

PROTOCOL.INI.

BINDINGS statements must be created to identify the HP Ethernet Family

Adapter NDIS 2.01 driver to the networking product's protocol modules.

An example PROTOCOL.INI file that supports 3+Open might look like the following:

; 3Com 3+Open <--- Networking Product

[TCPIP] bindings = PCNTND

; HP Ethernet Family Adapter <--- Driver

[PCNTND]


BUSTYPE = PCI1

LED2 = 0x90

5 Use a text editor to modify the CONFIG.SYS file to include DEVICE statements for the PROTMAN.DOS (or PROTMAN.OS2), for the PCNTND driver, and any of the drivers for the networking product being used.

An example portion of a DOS CONFIG.SYS file that supports the HP Ethernet

Family Adapter and 3Com 3+Open is shown below:

DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\PROTMAN.DOS

DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\PCNTND.DOS

DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\NEMM.DOS

DEVICE=C:\3OPEN\DOSWKSTA\LANMAN\DRIVERS\TCPDRV.DOS

6 To activate the modified PROTOCOL.INI and CONFIG.SYS files, reboot the computer.

When the boot process is complete, run NETBIND.EXE. This file is included with the networking product software. It is recommended that a call to

NETBIND.EXE be added to the AUTOEXEC.BAT file.

The installation process is now complete.

English 75



76 English

5

Configuring for Remote Boot

NOTE

5 Configuring for Remote Boot



This chapter describes how to configure a server to remote boot a client Vectra equipped with an HP Ethernet Family Adapter. The following protocols are supported:

•

Remote Start on Novell servers

•

Remote Boot on Windows NT and Windows NT 4.0

•

DHCP/TFTP Boot on Windows NT

Some protocols may not be available on your computer.

78 English


Setting Up a Novell NetWare 3.x and 4.x Server for Remote Start

Setting Up a Novell NetWare 3.x and 4.x Server for Remote

Start

To remote boot a client PC, remote boot services must be installed on a Novell

NetWare server and a Boot Image must be created and installed on the server.

A Boot Image is a file on the server that appears to a client Vectra as a “bootable disk”. A “bootable disk” is a disk containing the operating system and other related files.

A Boot Image can be used to remotely start any client Vectra; that is, any Vectra PC connected to the network that does not act as the server.

The creation of a remote boot image disk is described in detail in the “Preparing the

Network for Use” chapter of the Novell NetWare Getting Started: Supervisors

Guide .

This section summarizes this procedure.

How to Create a Boot Image

You will need at least one PC with a flexible disk drive to generate a Boot Image for the server to replicate. This PC is referred to as the Administrator Workstation.

All the details you need to generate the Boot Image can be found in the DOSGEN section of your Novell NetWare manual. The following explanation is a summary of the process.

1 Make a bootable diskette on any PC. To do this, insert a blank diskette in drive A and type:

FORMAT A: /S

English 79



2 Install the drivers on the bootable diskette as follows: a Copy the following files onto the bootable diskette:

LSL.COM

PCNTNW.COM

IPXODI.COM

VLM.EXE

*.VLM

NET.CFG

Note:

•

The PCNTNW.COM and NET.CFG files are in the subdirectory

\NOVELL\DOSCLNT\

on the LAN Disk.

•

The LSL.COM and IPXODI.COM files are in the

\DOSODI

directory on the

Novell WSGEN diskette.

•

VLM.EXE and the *.VLM files are supplied on the Novell diskette.

b Create an AUTOEXEC.BAT file on the bootable diskette that will enable the

PC to log onto the network.

The AUTOEXEC.BAT file could, for example, include the following lines:

PROMPT $P$G

LSL

PCNTNW

IPXODI

VLM

F: the first network drive use F: for a Vectra with disk drives, use

A:

for a diskless Vectra

LOGIN server/user server is the name of the server that the user will log onto; it isn’t necessarily the same server from which the client Vectra is remotely-booted.

user is the name that identifies the user on that server.

80 English



3 Test the bootable diskette by using it to log onto the server. (To do this, you must use F: not A:

in the AUTOEXEC.BAT file.)

4 Generate the Boot Image on the server using DOSGEN. Refer to the Novell

NetWare manual for details. (The name of this Boot Image file will always be

NET$DOS.SYS): a Start the Administrator Workstation.

b Log onto the LAN as

SUPERVISOR

.

c Type MAP F:=SYS:SYSTEM d Type MAP G:=SYS:LOGIN e Change to the

SYS:LOGIN

directory by typing

G: f Insert the bootable diskette into drive A.

g Run DOSGEN by typing F:DOSGEN

DOSGEN will create a Boot Image file called NET$DOS.SYS (containing a copy of the files on the bootable diskette) in the SYS:LOGIN directory.

5 Make the NET$DOS.SYS file in SYS:LOGIN shareable by typing FLAG

NET$DOS.SYS S

6 If required, give the Modify capability to the remote boot user in SYS:LOGIN by typing

GRANT M TO Username

At this point, the PC should be able to start from the server without using the PC's flexible or hard disk (the server should already be set up).

If a Login script Username has been assigned to the user, it will be executed at the end of the AUTOEXEC.BAT file created above.

English 81



Remote Program Load on NetWare 3.x and 4.x

This section explains how to configure the NetWare 3.x and 4.x server to support remote start of an HP Vectra PC with an HP Ethernet Family Adapter.

Installing the Remote

Boot Services on the

Server

To install the remote boot services on the NetWare 3.x and 4.x server, you need the following files:

❒ RPL.NLM. This is a NetWare loadable module. It acts as a protocol stack, as defined in the IBM Remote Program Load User's Guide . It is used on networks that have diskless workstations installed.

RPL.NLM will respond to the following frames: frame.

SEND.FILE.REQUEST RPL.NLM will respond with a

FILE.DATA.RESPONSE frame.

❒ RBOOT.RPL. This is the bootstrap program for LAN adapters using the Novell

ROM kit which is used by the remote start program in HP Vectra PCs equipped with the HP Ethernet Family Adapter).

❒ BOOTCONF.SYS. An ASCII text file that can be used to specify the Boot Image file used by a workstation.

You should use the RPL.NLM and RBOOT.RPL files supplied on the Novell diskettes. (If you don't have these files, use the RPL.NLM and RBOOT.RPL files supplied on the LAN Disk, in the subdirectory

...\RPL\NOVRPL\

).

You must create the BOOTCONF.SYS file using the procedure described in “How to

Create the BOOTCONF.SYS File” on page 86 .

RPL.NLM should be installed in the SYS:SYSTEM directory of the file server.

RBOOT.RPL and BOOTCONF.SYS should be installed in the SYS:LOGIN directory on the server.

82 English



BOOTCONF.SYS File

Syntax

The syntax for each Boot Image file line in the BOOTCONF.SYS file is:

0xMAC_address=Bootimage.sys[bind parameters] where:

MAC_address is a string of hexadecimal digits where wildcard characters (* and ?) can be used.

Bootimage.sys

is the renamed name of a NET$DOS.SYS file, which is associated with the MAC_address.

The last line of the BOOTCONF.SYS file should show the default value.

In this example BOOTCONF.SYS file, the last line shows the default value

DEFAULT.SYS:

0x080009311265 = MYBOOTIM.SYS

0x080009?????? = HP.SYS

0x0060B0?????? = HP.SYS

where:

❒ MYBOOTIM.SYS is a boot image particular to the workstation which has the MAC address 080009311265.

❒ HP.SYS is a boot image file specific to the HP Ethernet Family Adapter. HP has two MAC address identifiers, the original 080009 and the newer 0060B0. Users may require one or the other or both depending on when they acquired their LAN adapters.

❒ DEFAULT.SYS is the boot image file for all other LAN adapters.

BIND Parameters . The bind parameters are optional parameters that allow you to override the BIND time parameter of RPL.NLM “Loading the Remote Program Load

Services” on page 87 with parameters specific to a particular workstation that is being booted.

English 83



The BOOTCONF.SYS bind parameters are as follows:

ACK Use this parameter if you wish to configure the RPL module to

ACKnowledge FILE.DATA.RESPONSE frames sent by RPL.NLM.

RPL.NLM will send FILE.DATA.RESPONSE frames in a burst mode by default. This parameter allows pacing by the workstation if the

HP Ethernet Family Adapter cannot keep up with RPL.NLM.

GNS

NOACK

NOGNS

(RBOOT.RPL) to use a frame type other than the default to access the file server.

Valid frame types are:

FRAME=802.2. Default

FRAME=EII. ETHERNET_II protocol. (Only use on

ETHERNET networks.)

FRAME=SNAP. SNAP protocol.

If FRAME=EII or FRAME=SNAP is selected, RPL.NLM forces the bootstrap program to do a “Get Nearest Server” (GNS).

This parameter specifies that you wish the workstation to do a Get

Nearest Server request when the appropriate bootstrap program is downloaded.

Normally, RPL.NLM will supply the bootstrap program with the file server information so that it does not need to do a Get Nearest

Server request. Using the GNS parameter may cause the workstation to find a server other than one where RPL.NLM is located.

This parameter will override the ACK parameter specified in the

BIND command ( refer to page 87 ).

This parameter will override the GNS parameter specified in the

BIND command ( refer to page 87 ).

84 English



NOPROTECT This parameter will override the PROTECT parameter specified in the BIND command ( refer to page 87 ).

PROTECT This parameter tells RPL.NLM to configure the bootstrap program so that it will protect itself in the workstation's memory. It does this by adjusting the Memory Size variable in the BIOS data area

(40:13) to reflect the amount of memory that it uses. Using this parameter will reduce the amount of memory that the workstation has available for DOS by about 12 KB.

It is recommended that the PROTECT parameter is not used unless absolutely necessary.

PS=SERVER This parameter tells the bootstrap program to attach to a NetWare file server other than the one where RPL.NLM is loaded. “SERVER” is the name of a NetWare file server that contains the Image file for the workstation.

REP string1|string2 This parameter allows you to replace all occurrences of string1 with string2 in the Disk Image File. The “|” (ASCII 07C hex) delimiter is required to separate the string values.

Use the REP parameter to dynamically reconfigure a Disk Image

File during the RPL process. It is useful for tailoring files such as

AUTOEXEC.BAT or CONFIG.SYS to a specific workstation.

The rules for using REP are as follows (refer to the Novell NetWare manuals for more details):

•

The search is case sensitive. The bootstrap program will search for string1 exactly as it is entered in BOOTCONF.SYS.

•

All occurrences of string1 will be replaced with string2 in the Disk

Image File.

• string2 must be equal to or shorter than string1.

•

If string2 is shorter than string1, the Disk Image File will be padded with ASCII blanks when substitution is made.

• string2 must not contain embedded ASCII blanks. The FIRST blank that is encountered is interpreted as the end of the string.

English 85



How to Create the

BOOTCONF.SYS File

Several Boot Images can coexist on the server. Each Boot Image can be renamed differently to NET$DOS.SYS and can be linked to a MAC address. This relationship is made by creating a BOOTCONF.SYS file.

When RPL.NLM loads, it searches in the SYS:LOGIN directory of the file server for a

BOOTCONF.SYS file.

Creating the BOOTCONF.SYS file:

1 Determine the MAC address of each Vectra PC.

•

For the HP Ethernet Family Adapter, reboot the PC and press when

Setup=F2

appears.

•

For other Vectra PCs, run a diagnostic program on the client Vectra to identify the MAC address.

2 Start the Administrator Workstation.

3 Log onto the LAN as

SUPERVISOR

.

4 Make the Boot Images you want to use as described in the section entitled “How to Create a Boot Image” previously in this document. Rename the Boot Image file for each bootable diskette.

5 Create or modify the BOOTCONF.SYS file using an ASCII editor. (The syntax of the BOOTCONF.SYS file is described earlier in this document)

6 When all the Boot Image and BOOTCONF.SYS files are ready, make the SYS files in SYS:LOGIN shareable by typing:

FLAG *.SYS S

7 If required, give the Modify capability to the remote start user in SYS:LOGIN by typing:

GRANT M TO username

86 English



Loading the Remote

Program Load

Services

Before loading RPL.NLM, create the BOOTCONF.SYS file as described above and install the Novell server with an 802.2 frame type and then load RPL.NLN.

Load RPL.NLM in the same manner as any other NetWare NLM. At the server command line prompt, type:

LOAD RPL

(there are no parameters associated with loading RPL.NLM)

Then bind RPL.NLM with your driver. For example:

BIND RPL to board [ACK],[FRAME=xx],[GNS],[NODEFAULT],

[PROTECT],[PS=SERVER] where:

BIND

This is the command used to link the LAN drivers to the communications protocol. (Refer to the Novell NetWare manual for details)

RPL board

The name of a NetWare loadable module protocol used for remote boot.

The name of any NetWare LAN server driver that is configured for the IEEE 802.2 frame type.

The IEEE 802.2 frame types are as follows:

ETHERNET_802.2 Ethernet (802.3) using an 802.2 envelope.

TOKEN_RING Token-Ring (802.5) using an 802.2 envelope.

FDDI_802.2 FDDI using an 802.2 envelope.

BIND Parameters . The parameters specified between square brackets [ ] are optional, not case sensitive, can be separated by blanks or commas, and may be entered in any order.

NOTE GNS is required if you have an SFT III installation.

English 87



The possible parameters are as follows:

ACK Use this parameter if you wish to configure the RPL module to

ACKnowledge FILE.DATA.RESPONSE frames sent by RPL.NLM.

RPL.NLM will send FILE.DATA.RESPONSE frames in a burst mode by default. This parameter allows pacing by the workstation if the

HP Ethernet Family Adapter cannot keep up with RPL.NLM.

GNS

(RBOOT.RPL) to use a frame type other than the default to access the file server.

Valid frame types are:

FRAME=802.2. Default

FRAME=EII. ETHERNET_II protocol. (Only use on ETHERNET networks.)

FRAME=SNAP. SNAP protocol.

If FRAME=EII or FRAME=SNAP is selected, RPL.NLM forces the bootstrap program to do a “Get Nearest Server” (GNS).

This parameter specifies that you wish the workstation to do a Get

Nearest Server request when the appropriate bootstrap program is downloaded.

Normally, RPL.NLM will supply the bootstrap program with the file server information so that it does not need to do a Get Nearest

Server request. Using the GNS parameter may cause the workstation to find a server other than one where RPL.NLM is located.

This is mandatory for an SFT III installation.

RPL.NLM to respond to a FIND frame unless the node address of the workstation is found in the

BOOTCONF.SYS file. It is provided for security reasons.

The workstation will not boot until the system administrator inserts

- in the BOOTCONF.SYS file - the node address and associated Disk

Image File name(s) to use when booting the workstation.

88 English



PROTECT This parameter tells RPL.NLM to configure the bootstrap program so that it will protect itself in the workstation's memory. It does this by adjusting the Memory Size variable in the BIOS data area

(40:13) to reflect the amount of memory that it uses. Using this parameter will reduce the amount of memory that the workstation has available for DOS by about 12 KB.

It is recommended that the PROTECT parameter is not used unless absolutely necessary.

PS=SERVER This parameter tells the bootstrap program to attach to a NetWare file server other than the one where RPL.NLM is loaded. “SERVER” is the name of a NetWare file server that contains the Image file for the workstation.

English 89


Remote Boot on Windows NT


This section explains how to setup the remote boot service on a Windows NT server to boot client Vectras equipped with an HP Ethernet Family Adapter.

The installation and setting up of the Remote Boot service is described in Windows

NT 3.x online installation help.

The procedure below is based on the INSTALL.HLP HELP file, except that step 4 has been added for the correct automatic setup of the HP Ethernet Family Adapter so that you do not have to do the setup described in “Creating Remoteboot

Configurations for New Adapters” in the INSTALL.HLP documentation.


To install the remote boot service to boot HP Ethernet Family Adapter clients:

1 Install the Remoteboot service: a In Control Panel, choose the Network icon.

b If the DLC protocol isn't already installed, in the Network settings dialog box, choose Add Software button, and install the DLC protocol.

c In the Network settings dialog box, choose Add Software button. Select the

Remoteboot Service. Assuming that your NT default directory is \WINNT35 , install it in \WINNT35\RPL directory.

2 To install MS-DOS files for remoteboot workstations: a Check that the

RPL\RPLFILES

directory is shared on the remoteboot server. It should have the share name RPLFILES.

b Copy all the MS-DOS files, including the system files io.sys

and msdos.sys

, to the RPL\RPLFILES\BINFILES\DOSxxx directory, where xxx is the version number (supported version are 330, 401, 500, 600, 622). The file ibmdos.com

should be renamed as msdos.sys

, and ibmbio.com

as io.sys

.

c Remove any attributes such as S, A, H from your system files.

To install Windows for Remoteboot Workstations, refer to the relevant section of the online installation help.

90 English



3 To start the Remoteboot service: a In Control Panel, choose the Services icon.

b Select the Remoteboot service, and start it. You may configure it to start automatically by selecting the startup button.

4 To install the Bootblock and configurations for the HP Ethernet Family Adapter: a Open a DOS box in your NT AS.

b Insert the LAN Disk in the flexible disk drive. Make this drive the current drive.

c Change to the \RPL\NT35AS

directory of your flexible disk drive by typing cd

\RPL\NT35AS d Type HPIASRPL C:\WINNT35\RPL assuming C:\WINNT35\RPL is the drive and directory where the Remoteboot service is installed.

e You have now prepared your server, by copying all the files you need to run the

Remoteboot services from the LAN Disk.

5 Setting up the Remoteboot:

To install other protocols as IPX, or TCP/IP, or to manage your profiles and workstations, please refer to the Windows NT online installation help.

English 91


Remote Boot under Windows NT Server 4.0


The installation and setting up of the remote boot service is described in the

INSTALL.HLP on-line help file provided by Windows NT Server 4.0.

The procedure below is based on the INSTALL.HLP HELP file, except that step 4 has been added for correct automatic setup of the HP Ethernet Family Adapter so that you do not have to do the setup described in “Creating Remoteboot

Configurations for New Adapters” in the INSTALL.HLP documentation.


To install the remote boot service to boot HP Ethernet Family Adapter clients:

1 Install the remote boot service: a Select Start, Settings, Control Panel, Network.

b If the DLC protocol isn't already installed, choose the Protocol tab in the

Network dialog box, and Add...

to install the DLC protocol.

c Choose the Services tab in the Network dialog box, and Add...

to install the remote boot service. Assuming that your NT default directory is

\WINNT40

, install it in the

\WINNT40\RPL

directory.

2 Install MS-DOS files for remote boot workstations: a Check that the RPL\RPLFILES directory is shared on the remoteboot server. It should have the share name RPLFILES.

b Copy all the MS-DOS files, including the system files io.sys

and msdos.sys

, to the

RPL\RPLFILES\BINFILES\DOSxxx

directory, where xxx is the version number (supported version are 330, 401, 500, 600, 622). The file ibmdos.com

should be renamed as msdos.sys

, and ibmbio.com

as io.sys

.

c Remove any attributes such as S, A, H from your system files.

To install Windows for remote boot workstations, refer to the relevant section of the NT Server 4.0 online installation help.

92 English



3 Start the remote boot service: a In the Control Panel, choose the Services icon.

b Select the remote boot service, and start it. You may configure it to start automatically by selecting the startup button.

4 Install the boot block and configurations for the HP Ethernet Family Adapter: a Open a DOS box under Windows NT Server.

b Insert the LAN Disk in the flexible disk drive. Make this drive the current drive.

c Change to the \RPL\NT40

directory of your flexible disk drive by typing cd

\RPL\NT40 d Type HPIASRPL C:\WINNT40\RPL assuming C:\WINNT40\RPL is the drive and directory where the remote boot service is installed.

e You have now prepared your server, by copying all the files you need to run the remote boot services from the LAN Disk.

5 Set up the remote boot:

To install other protocols as IPX, or TCP/IP, or to manage your profiles and workstations, please refer to the Windows NT Server installation on-line help.

English 93


DHCP/TFTP Boot under Windows NT

DHCP/TFTP Boot under Windows NT

This protocol will be available on your server only if you installed Intel LanDesk

Configuration Manager.

For more information on installing and configuring Intel LanDesk Configuration

Manager refer to the Intel online documentation.

94 English

6

Driver Options - Software Keywords

6 Driver Options - Software Keywords

PCNET Driver-Specific Keywords

PCNET Driver-Specific Keywords

BUSTYPE

If this keyword is specified with one of the options mentioned below, the driver software will only scan the specified bus for the presence of the PCnet family device. If this keyword is not specified the driver software will scan all the buses.

FDUP

This keyword will set the 10BASE-T port to operate in Full-duplex mode. This facility is only available when connected to a Hub which has Full-duplex capability.

TP

When present, this keyword will force the PCnet device into using the 10BASE-T port. The PCnet controller will use the 10BASE-T port even if no link beat pulse is generated from the 10BASE-T hub.

PCNET Driver-Specific Keyword Matrix

Keyword Name Syntax Range Default

Bus Type to Scan BUSTYPE

BUS_TO_SCAN

PCI

PCI1

PCI2

Not Present (All)

- PCI1 is used for mechanism 1.

- Numerical values required with

LANtastic driver: 00 (ISA), 01 (PnP), 10

(VESA), 11 (PCI), 12 (PCI1), 13 (PCI2).

Not Present

(represents All buses)

Full Duplex FDUP OFF

Twisted Pair TP

UTP

AUI

OFF

Present or Not Present Not Present

96 English


Common Keywords

Common Keywords

Common keywords are those keywords that may be used by any of the operating systems to configure an HP Ethernet Family Adapter. However, each of the operating systems has its individual syntax, which is shown below in the Operating

System Keywords section.

I/O Address

An I/O address keyword may be used to specify the I/O address of the PCnet adapter. There are different formats for I/O Address settings in the each network operating system environment. Refer to the Operating System Keywords for correct format and usage.

For all of the PCnet Family adapters, the I/O address does not need to be specified. The driver software will be able to scan for this information on the bus.

Interrupt Channel (IRQ)

Each network operating system environment has different formats and syntax for interrupt settings. Refer to the Operating System Keywords for correct format and usage of interrupt settings.

The driver will use the interrupt selected by the PCI System BIOS.

DMA Channel

The syntax for DMA keywords may be different according to the operating system. Refer to the Operating System Keywords for correct format and usage for

DMA settings.

The driver will use the DMA channel selected by the PCI System BIOS.

English 97


Common Keywords

Common Keyword Matrix for the HP Ethernet Family Adapter

Keyword Name

I/O Address

Interrupt Channel (IRQ)

DMA Channel

0000 - FFFF h

Range

0 - 15 (INTA#)

N/A

Default

Found by scan.

Determined by the PCI BIOS

Found by scan.

Determined by the PCI BIOS

N/A

98 English


Operating System Keywords


This section provides matrices for some additional keywords that may be used to configure the PCnet drivers based on the different driver environments. In addition, the correct syntax is provided for the Common Keywords described previously.

Novell NetWare DOS & OS/2 ODI Client Keywords

Keyword

Name

I/O Address

Interrupt

DMA

Ethernet

FRAME type

Syntax Description Range Default

IOP

IRQ

Described previously in “Common Keyword Matrix for the HP Ethernet

Family Adapter” on page 98.

DRQ

FRAME Refer to Ethernet Frame type from the

IEEE Specification.

Ethernet_802.2

Ethernet_802.3

Ethernet_SNAP

Ethernet_II

Ethernet_802.2

English 99



NDIS 2.01 Driver Keywords

Keyword

Name


I/O Address IO Address

PORT

IOBASE

Interrupt INTERRUPT

INT

DMA DMA

DMACHANNEL



Transmit

Buffers

Receive

Buffers

Maximum

Multicasts

TXBUFFERS

RXBUFFERS

Transmit and Receive buffer sizes may be increased or decreased using Transmit and

Receive Buffer keywords. Increasing the

TXBUFFERS and RXBUFFERS values may increase performance, but will also decrease the amount of DOS memory available for programs.

Power of 2 4

Power of 2 4

MAXMULTICASTS To designate the maximum number of multicast addresses for the device.

N/A 10

NDIS 3.x Driver Keywords

Keyword

Name


I/O Address IO Address

Interrupt INTERRUPT



DMA

Net

Address

DMACHANNEL

Bus type designation

BUS_TO_SCAN Described previously in “PCNET Driver-Specific Keyword Matrix” on page 96.

NETADDRESS This keyword allows you to specify or overwrite the IEEE or Mfr address. This must be edited in PROTOCOL.INI or NT registry.

Any valid

IEEE address.

Not

Present

100 English



Artisoft LANtastic Keywords

Keyword

Name

Syntax

I/O Address IOBASE

Interrupt IRQ

DMA DMA

@switch-file @switch-file

Description Range Default



None

HELP HELP

VERBOSE VERBOSE

REMOVE REMOVE

BUSTYPE BUSTYPE

Multiplex

Interrupt

MPX

Specifies that further switches are to be taken from a switch file. Any switches after

N/A the @switch-file name will be used, and the switch settings take precedence over any settings in the switch file. Switch files may be invoked from within switch files.

Instructs PCNTLC.EXE to display information about the valid command line switches. For example: PCNTLC /Help

N/A

Causes the PCNTLC.EXE driver to be installed and detailed information about the configuration of the PCNTLC.EXE driver to be displayed. Refer to the messages section of the LANtastic manual for a detailed description of the VERBOSE output.

N/A

This command removes the PCNTLC.EXE driver from memory. TSR programs must be removed in the opposite order they were loaded. For example if PCNTLC.EXE was loaded followed by AILANBIO, then

AILANBIO must be removed before PCNTLC.

N/A

Described previously in “PCNET Driver-

Specific Keyword Matrix” on page 96.

00(ISA)

01(PnP)

10(VESA)

11(PCI)

12(PCI1)

13(PCI2)

Command used for a communications interface between TSR programs

C0-FF h

Not

Enabled

Not

Enabled

Not

Enabled

Not

Present

C7

English 101



102 English

Glossary

10BASE-T 10-Mbs Baseband

Twisted Pair. Covered by Section 14 of IEEE 802.3. Uses IEEE 802.3 protocol, point-to-point twisted pair cabling and repeaters to provide network services. No defined maximum node count, maximum cable distance is 100 m.

100BASE-T Refers to a 100Mbit/s network technology over Category 5

UTP cable that is compatible with the

IEEE 802.3 standard. This technology, which upgrades the

CSMA/CD protocol to 100Mbit/s, is sometimes referred to as 802.3u or

Fast Ethernet.

100VG-AnyLAN Refers to the 100

Mbit/s network technology over voice grade cable that is compatible with the IEEE 802.12 standard. This technology guarantees access to any end node that requests to transmit, while ensuring priority access to end nodes that require consistent, continuous access for applications such as full-motion video or video conferencing.

Access Protocol The set of traffic rules that network workstations obey to avoid data collisions when sending messages and packets over shared network media - sometimes referred to as the Media Access Control (MAC) protocol. Common examples include

Carrier Sense Multiple Access

(CSMA) and Token Passing.

adapter An accessory board, that connects to the system board via an accessory board slot.

address A unique location in memory.

administrator A network user who is responsible for setting up, configuring, maintaining, and managing the network.

ANSI American National Standards

Institute. This organization has, among other achievements, given its name to the character set encoding scheme used in Windows. The ANSI character set contains 256 characters and is a superset of ASCII. However, the upper 128 characters differ from those in the Extended ASCII character set.

AppleTalk A proprietary Apple LAN capable of transmitting data at a rate of 230-Kbs over shielded twisted pair wire. AppleTalk is based on a bus topology and is built into all Apple

Macintosh computers and laser printers. The most common cabling scheme used with AppleTalk is known as LocalTalk.

API Application Programming

Interface. A set of routines that an application program uses to request and carry out lower-level services performed by the operating system.

ASCII American Standard Code for

Information Interchange. ASCII was defined in 1965 as a character set of

128 characters and the codes to represent them on a computer. Many modern operating systems use a character set based on ASCII.

Extended ASCII (used in DOS), ANSI

(used in Windows), and Unicode

English 103

Glossary

(used in Windows NT) all include

ASCII as a subset.

AUI Attachment Unit Interface. An

IEEE specification for a node or connection interface to an external medium attachment unit (MAU).

AUI Cable A cable used to connect an external transceiver to a computing device. The AUI cable is also sometimes known as the transceiver cable.

backbone Generally, a coax or fiber optic cable used as the main transmission medium for connecting network areas called workgroups.

base address The first address in a series of addresses in memory: that is, the beginning location of a section of code or data. It is often used to describe the start of a network interface card's (NIC) I/O: that is, the

I/O base address.

baseband A network that transmits signals as a pulse rather than as variations in a carrier wave (signal).

BIOS Basic Input Output System.

BIOS is built-in software typically contained in a ROM (Read Only

Memory) chip that determines what a computer can do without accessing programs from disk. On IBM PCs,

BIOS contains code required to control the keyboard, display screen, disk drives, serial communications, etc. A Plug and Play BIOS supplements the BIOS functions with routines that support Plug and Play operations.

bit Binary digit. A bit is the smallest unit of information represented on a computer. A bit can contain either a zero (0) or a one (1).

boot image A boot image is a file on a server that appears to a client PC as a bootable disk.

Boot PROM or Boot ROM Boot

Programmable Read Only Memory. A memory chip that allows the network workstation to communicate with the network file server and to read a DOS boot program from the server. These diskless workstations are then capable of operating on the network without having a disk drive.

bootable disk A disk from which an operating system can be launched automatically by the computer when the computer is switched on. The disk contains the operating system and other related files.

broadband A network that transmits signals as variations of carrier waves rather than directly as pulses. Broadband networks provide greater network bandwidth capacity, but are also more complex.

broadcast To send a message to all workstations connected on the network.

buffer A temporary storage space.

Data may be stored in a buffer before, during, or after a data transmission.

Buffers are often used to compensate for the difference between the speed of data packet transmission and the speed of data packet processing.

English 104

Glossary bus An electrical connection over which information is transported. bus topology A network topology in which all devices are connected to a central cable called the bus or backbone. Bus networks are relatively inexpensive and easy to install.

Ethernet, a very popular LAN, uses a bus topology.

byte A group of eight consecutive bits that are treated as one unit.

channel A path between a sender and receiver that carries one stream of information. A two-way path is called a circuit.

client A client PC is any PC connected to a network that does not act as a server.

Client/Server Architecture A networking architecture in which each computer or process on the network is either a client or server. A server is a powerful computer or process dedicated to managing disk drives (file server), printers (printer server), or network traffic (network server). Clients are normally less powerful PCs or workstations on which users run applications and issue requests to servers for resources.

coax cable A type of network medium. Coaxial cable contains a copper inner conductor surrounded by plastic insulation and then a woven copper or foil shield. It is commonly used in cable television and Ethernet networks.

CRC Cyclic Redundancy Check. A

CRC is calculated by the Media

Access Control (MAC) transmit process and checked by the MAC receive process of a workstation to ensure integrity of the frame contents.

CSMA Carrier Sense Multiple

Access. CSMA is a medium-sharing scheme in which network workstations listen on the network medium and transmit only if the cable is not in use. CSMA is often combined with a collision detection scheme for more efficient data transmission.

CSMA/CD Carrier Sense Multiple

Access with Collision Detection. An enhancement to CSMA in which a network station stops transmitting if it detects a collision on the network cable.

Demand Priority Protocol A request-based, deterministic protocol

- a network end node connected to a

100VG hub makes a request (or

"demand") to transmit, and then can transmit only when authorized by the hub. Under hub control, the Demand

Priority Protocol guarantees network access for any end node that requests to transmit data.

DLL Dynamic Link Library. A library of shared functions that applications can link in at runtime rather than at compile time.

DMI Desktop Management

Interface. The DMI allows management applications access to management data defined in MIF files.

105 English

Glossary domain A collection of network servers and resources in a logical grouping.

driver A software program that controls the underlying network hardware (such as adapters and controllers) or implements the protocol stacks_Stack through which higher-level applications can communicate with the network hardware.

DMTF erased.

Desktop Management Task

Force. A body which defines desktop management standards.

EEPROM Electrically Erasable

Programmable Read Only Memory.

An EEPROM is a special type of

PROM that can be electronically

802.3 group.

Ethernet Address Also known as the IEEE address, this is a unique numeric identifier of a node on an

Ethernet LAN.

Extended ASCII The Extended

ASCII character set encoding scheme was defined by IBM in 1981 to be used by the IBM PC. It contains 256 characters and is, as the name suggests, a superset of ASCII.

fiber optic A data transmission method that uses light pulses sent over glass or plastic threads (fibers).

Message transmission is close to the speed of light.

flash memory A special type of

EEPROM that can be erased and reprogrammed inside a computer.

Conventional EEPROMs require a special device called a PROM reader.

Flash memory is non-volatile and does not lose its contents when power is turned off.

EISA Extended Industry Standard

Architecture. A PC system bus that is an alternative to IBM's Micro Channel

Architecture (MCA). EISA is a bus architecture designed for IBM PCs and compatibles using an Intel 386 or

486 microprocessor. An EISA bus is

32 bits wide and supports multiprocessing. The main difference between EISA and MCA is that EISA is backwards compatible to the ISA bus (also known as the AT bus), while

MCA is not.

Ethernet A LAN protocol originally developed by Xerox in cooperation with DEC (Digital Equipment

Corporation) and Intel. Ethernet uses a bus topology and supports data transmission rates of 10 Mbs. It has also been standardized by the IEEE frame A group of bits that include data plus one or more addresses. A frame generally refers to a link layer

(OSI Model layer 2) protocol.

full-duplex A method of two-way communication over a single physical link. Offers advantages over halfduplex by allowing both parties to talk simultaneously. Can be used to double communication speeds between a PC and a special network

Hub.

English 106

Glossary half-duplex A method of two-way communication over a single physical link. Only one party can transmit at a time, the other party remaining silent to avoid interference. To provide twoway communication, each party takes it in turns to transmit. This is the method of communication most often used between a PC and a network

Hub.

hub A general term frequently used instead of repeater.

IEEE Institute of Electrical and

Electronics Engineers. Founded in

1963, the IEEE is an organization composed of scientists, engineers, and students. The IEEE is best known for its work in establishing standards for the computer and electronics industry.

IEEE 802 A committee of the

Institute of Electrical and Electronics

Engineers (IEEE). IEEE 802 was organized to establish standards for the physical and electrical connections used in LANs.

IEEE 802.3 A subcommittee of the

Institute of Electrical and Electronics

Engineers (IEEE) 802 committee.

IEEE 802.3 was organized to establish standards for Ethernet, a 10-Mbps baseband LAN.

IEEE 802.12 A subcommittee of the Institute of Electrical and

Electronics Engineers (IEEE) 802 committee. IEEE 802.12 was organized to establish standards for demand priority LANs.

interrupt A signal that suspends a program temporarily while transferring control to the operating system when input or output is required. Interrupts are given priority levels such that higher priority interrupts are processed first.

I/O Input/Output.

I/O Mapped The NIC registers are located in the I/O address space.

I/O Port or I/O Address An addressable location on the Intel 386 microprocessor to and from which hardware control information can be written and read.

IPX Internet Packet Exchange. IPX is Novell NetWare's native transport protocol. It is used to transfer data between server and/or client programs running on different network nodes. IPX packets are not related to packets used in other systems such as Ethernet or token ring.

IRQ Interrupt Request. An IRQ is a computer instruction used to interrupt a program for an I/O task.

Each hardware device raises interrupts on a predetermined IRQ

(numbered 0 through 15). The microprocessor associates specific interrupts with different interrupt service routines (ISR).

ISA Industry Standard Architecture.

The ISA bus is the system bus originally used on the IBM PC/XT and

IBM PC/AT computers. The version of the bus used on the AT is often

107 English

Glossary referred to as the AT bus. The XT bus is 8 bits wide and the AT bus is 16 bits wide. The AT bus has become a de facto industry standard.

ISR Interrupt Service Routine. A sequence of software instructions that are executed as a result of a hardware interrupt.

jumper A plastic and metal shorting bar that slides over two or more electrical contacts to set certain conditions. Older (legacy) ISA network adapter cards require the user to set the DMA channel and IRQ using jumpers on the card itself.

Newer network cards no longer require the user to set jumpers. The

DMA channel, IRQ, and so on, can be set with software or are set automatically using Plug and Play.

legacy A term used to refer to older hardware and software still in use. In the Plug and Play context, legacy means the installed base of adapter cards that do not conform to the Plug and Play standard.

LocalTalk The cabling scheme supported by the AppleTalk network protocol for Apple Macintosh computers. LocalTalk is a 230-Kbs medium access method which is relatively slow, but popular because it is inexpensive and easy to install and maintain.

keyword A word reserved for special use by a program.

kilobyte A unit of information consisting of 1,024 bytes.

Abbreviation: KB.

LAN Local Area Network. A generalpurpose communications network that interconnects a variety of devices within a limited geographical area. A

LAN might connect computers on adjacent desks, within a building, or within several buildings of a campus.

LAN activity light A light on the front panel of some Vectra PCs which indicates when the PC is accessing the network.

Loopback Test A diagnostic test in which a transmitted signal is returned to the sending device after passing through all, or a part of, a network.

Loopback provides a way of comparing the transmitted signal with the returned signal for integrity.

MAC Media Access Control. The

MAC sublayer defines the mediumindependent capability for frame transmission and reception using the

CSMA/CD_CD access method.

MAC address A 12-digit hexadecimal number that identifies a specific network node and allows messages to be directed to that node only. Because the IEEE has assigned identifiers for each hardware manufacturer, no two pieces of equipment have the same address.

Your MAC address is unique.

English 108

Glossary

MAC driver Media Access Control driver. A driver responsible for the lowest level of network device control. A MAC device driver deals directly with the network adapter.

Magic Packet™ The HP Ethernet

Family Adapter has a unique IEEE address (MAC address). This address repeated 16 times in-a-row within a valid network packet was chosen to serve as a wake-up call for the remote power control.

MAU Medium Attachment Unit. The physical and electrical interface between a workstation or repeater and the actual medium. The MAU is connected to the station by an attachment unit interface (AUI). A different MAU is required to support each different type of medium (cable type).

MCA Micro Channel Architecture.

MCA is the architectural basis for

IBM's Micro Channel bus which is used in high-end models of IBM's

PS/2 series of computers.

media Plural of medium.

medium The network medium is the cabling or wiring used to carry network signals. Common types include coax, fiber optic, and twisted pair.

memory mapped The NIC registers are located in the memory address space.

MIF Management Information

Format. MIF files describe collections of standardized instrumentation attributes defined by the DMTF working groups.

Miniport Miniport drivers implement the hardware-specific operations necessary to manage a

Network Interface Card (NIC).

Operations common to all lowest level

NIC drivers are generally provided by the NDIS library, so that the driver is smaller, faster and easier to write than the old “full” NIC drivers. Only miniport NIC drivers can take advantage of the enhancements and functionality planned for future versions of the NDIS library.

NDIS Microsoft NDIS (Network

Driver Interface Specification) 2.01 and 3.x are driver specifications developed by Microsoft Corporation to offer a standard driver interface for all network adapters. A standard driver interface provides flexibility to support not only multiple network adapter cards but also multiple protocol stacks (like ODI). As a result, many operating systems have incorporated the NDIS interface to make configuration and installation of network adapters easy and independent of the network adapter used.

NetBEUI NetBIOS Extended User

Interface transport. A network transport commonly used in Microsoft networks.

109 English

Glossary

NetBIOS Network Basic Input

Output System. NetBIOS was originally developed by IBM and Sytek to interface a network operating system with specific hardware.

Today, many vendors either provide a version of NetBIOS to interface with their hardware or emulate its session layer communications in their network products.

network server mode A security feature that prevents unauthorized use of an input device (like a keyboard or mouse) while your computer is running as an unattended network server.

ODI Open Data-Link Interface. ODI supports multiple protocols and adapters and is Novell's network device driver interface standard.

OSI Model Open Systems

Interconnection Reference Model.

OSI is a network model developed by the International Standards

Organization (ISO) which divides network functions into seven connected layers (physical, data link, network, transport, session, presentation, application). Each layer builds on the services provided by those below.

packet A unit of information that is transmitted over the network. A packet consists of a preamble, a destination address, a source address, data being transmitted, and a code

(such as CRC) for testing correct transmission of the packet.

NetWare A series of network operating systems and related products developed and sold by

Novell, Inc.

network A way of connecting multiple computers to facilitate the sharing of files and resources.

NIC Network Interface Card. An expansion card that can be inserted into a computer so that the computer can be part of a network. Most NICs are designed for a particular type of network, protocol, and medium, although some can be used in multiple network environments.

NLM node

NetWare Loadable Module.

NLMs are applications and drivers that run in the NetWare server that can be loaded and unloaded on the fly.

In a network, a node can be a computer or some other device such as a printer.

PCI Peripheral Connect Interface.

The PCI local bus is a high performance, 32-bit or 64-bit bus with multiplexed address and data lines. It is intended for use as an interconnect mechanism between highly integrated peripheral controller components, peripheral add-in boards, and processor/memory systems.

Peer-to-Peer Architecture A network architecture in which each node on the network has equal responsibility: that is, any station can contribute resources to the network while still running local application programs.

English 110

Glossary

Plug and Play Referred to as PNP, a specification originated by Microsoft for hardware and software architecture that allows for automatic device identification and configuration.

PROM Programmable Read Only

Memory. A memory chip that can be written to only once. The difference between a PROM and a ROM is that a

PROM is manufactured blank, whereas a ROM is programmed during manufacturing. To write data to a

PROM, a special device called a PROM programmer (or burner) is needed.

Programming a PROM is often referred to as burning a PROM.

protocol A formalized set of rules that describes how data should be exchanged between two entities.

Protocols are typically divided into modular layers, where each layer performs a specific function for the layer above. Protocols allow products from different vendors to communicate on the same network. One of the most popular LAN protocols is Ethernet.

Another common LAN protocol is

IBM's token-ring network.

protocol stack The collection of software modules that implements a particular network protocol (such as

TCP/IP).

RAM Random Access Memory. Any type of computer memory that can be accessed randomly. RAM is the most common type of memory found in computers. RAM comes in two basic types: SRAM (Static RAM) and DRAM

(Dynamic RAM). SRAM and DRAM differ in the technologies used to store their data. SRAM is faster, and hence, more expensive than DRAM.

RAM is volatile in nature and will not retain its contents when power is turned off. In common usage, RAM is often referred to as main memory which is used to store programs and data.

Redirector A software module that is loaded into every network station. It captures application program requests for file and peripheral services and routes them through the network: that is, the redirector transforms client-side requests into network requests.

registry A database maintained by

Microsoft Windows 95 for storing hardware and software configuration information. The registry is used heavily in Plug and Play systems.

repeater A repeater is used to extend the physical topology of the network, allowing two or more cable segments to be coupled together. No more than four repeaters are permitted between any two stations.

ring topology A network topology in which all devices are connected together in the shape of a closed loop.

Ring networks are relatively expensive and difficult to install.

However, they are robust (one failed device will not cause the entire network to fail). Most ring networks use a token-passing protocol that allows a device on the ring to send messages out when it receives a special bit pattern called a token.

111 English

Glossary

ROM Read Only Memory. Computer memory on which data have been prewritten. Once data are written to a

ROM it cannot be changed and can only be read. Unlike main memory

(RAM), ROM maintains its contents when power is turned off. ROM is referred to as being non-volatile, whereas RAM is volatile.

server Any computer on a network that makes file, print, or communication services available to other network stations.

Setup program hub.

Used to inform the computer about its configuration, for example the amount of memory installed. The setup program is stored in flash memory on the system board.

SPX Sequenced Packet Exchange.

SPX is an enhanced set of commands implemented on top of IPX that provides for more functions (such as guaranteed packet delivery).

star topology A network topology in which all devices are connected to a central hub. Star networks are relatively easy to install and manage, but network bottlenecks can occur since all data must pass through the

TCP/IP Transmission Control

Protocol/Internet Protocol. The

Internet protocol stack_Stack that defines a wide range of network services allowing heterogeneous network system operation. TCP/IP is the default wide area network protocol used by both Microsoft

Windows 95 and Windows NT.

topology The geometric map of a

LAN. Common LAN topologies include the bus, ring, and star.

transceiver A hardware device that links a node to a baseband network cable and functions as both transmitter and receiver.

twisted pair wiring Cable comprised of two wires twisted together at six turns per inch to provide electrical shielding. Some telephone wiring uses twisted pair wiring.

Unicode An international character set encoding scheme defined by agreement between the International

Standards Organization and Unicode,

Inc., a non-profit consortium set up by a group of major computer companies, including Apple

Computer, Inc., Sun Microsystems,

Inc., Xerox Corp., and IBM

(International Business Machines

Corp.). Unicode employs a 16-bit coding scheme that allows for 65,536 distinct characters, enough to support all significant world languages, including several archaic or arcane languages such as Sanskrit and Egyptian hieroglyphs. Unicode also includes representations for punctuation marks, mathematical symbols, and dingbats, with room left for future expansion. Unicode includes ASCII as a subset.

VxD Virtual Device Driver. A lowlevel software component that manages a single resource, such as a display screen or a serial port.

English 112

No results