For Public Distribution:

Hayes(r) Microcomputer Products, Inc.    LANstep(r) Technical Note

                                     "Installing Network Interface
                                                Card (NIC) Drivers"

File Number LS-3B                                      September 1993

Summary Follows:

This Hayes Technical Note: 

* explains what NIC (network interface card) drivers are for, where 
  you can get them and how to install them.

* provides two examples of NIC driver installation and testing; one 
  for Xircom Ethernet and SMC ARCNET.


Background Information

In the constant evolution of network communication protocols, the 
International Standards Organization's Open Systems Interconnection 
(ISO/OSI) model has been referenced frequently. This model provides a 
framework for the implementation of communication protocols in seven 
layers. Most vendors have agreed to support the OSI model in one form 
or another. No matter which model eventually becomes the ultimate 
industry standard, the goal remains the same: to achieve hardware and 
software compatibilities amongst all non-proprietary vendors. What 
this means for the end user of this technology is that any 
off-the-shelf hardware or software will work together, provided it 
conforms to the common standards. Utopia perhaps, but nevertheless it 
is still a goal of the open systems community. Hayes LANstep has been 
designed to operate in this community.


Notes About NDIS:

3Com/Microsoft LAN Manager Network Driver Interface Specification 
(NDIS) is a specification for writing hardware-independent drivers at 
the data link (media access method) layer of the OSI model. In order 
to be network card independent, LANstep has adopted this 
specification. It provides a standardized way of writing drivers for 
network adapters and communication protocols. The benefits of such a 
standard for the industry are numerous. It allows LANstep and other 
network operating systems (NOS) to support any adapter card, and it 
precludes the need for constant maintenance of card drivers by the 
NOS developer. 


Protocol Manager and PROTOCOL.INI

The NDIS specification consists of a Protocol Manager driver which 
provides a standardized way for multiple Adapter Interface and 
protocol drivers to obtain configuration information and "bind" 
together into the desired protocol hierarchy. The Protocol Manager 
accesses all configuration information from a central file, 
PROTOCOL.INI. The network interface card manufacturer will usually 
provide the different operating system drivers (DOS & OS/2) for their 
cards and a PROTOCOL.INI file with specifications for only one layer, 
the Adapter Interface layer (also know as the Media Access Control 
(MAC) layer). This layer contains a set of parameters usually 
specific to the card itself. These parameters will generally be set 
at default values optimized for that particular card or family of 
cards. These values can be changed and tuned based on the 
recommendations of the manufacturer and NDIS driver specification. 
For a more detailed explanation of this file, refer to "Appendix C; 
Understanding the PROTOCOL.INI File" of the LANstep Manager's Guide.


Where Can I Get NIC Driver Files?

While most NIC vendors supply driver software with the card, there 
may be an occasion where you don't have any drivers for a card you 
wish to use with LANstep. In this case, you can obtain the necessary 
driver software from three sources:

* LANstep master diskettes
* LANstep Supplementary Network Driver diskette(s)
* direct from the NIC manufacturer


From the LANstep Master Diskettes

At the time this document was printed, the LANstep master diskettes 
included driver files for the following NICs:

Ethernet:
* 3Com EtherLink 501
* 3Com EtherLink II 503
* 3Com EtherLink Plus 505
* 3Com EtherLink 16 507
* 3Com Etherlink MC 523
* Hayes EtherMate
* Western Digital EtherCard

Token-Ring:
* IBM Token-Ring


From a LANstep Supplement Diskette

As other NICs enter the market, Hayes provides, when possible, 
copies of the driver files for these NICs. There are a number of ways 
to obtains these newer driver files. If you have a modem, call the 
Online With Hayes BBS (1-800-USHAYES) and look for the needed driver 
file(s) in the File Library section and a README file that tells you 
how to convert these files into Supplementary Diskettes. You may also 
obtain (via modem) these same files from the Hayes Forum (GO HAYES) 
on CompuServe, or simply contact Hayes Customer Service Department 
(404) 441-1617 (USA) or (519) 746-5000 (Canada) for availability.


From the Manufacturer

This is another good source, since the manufacturer, more than 
anyone else, should have the most current version of the driver files 
needed for a specific card. Frequently, NIC vendors have BBSs you can 
call and download the file(s). Or, just call the manufacturer 
directly and obtain the NDIS drivers.

IMPORTANT: Unless the driver(s) come directly from Hayes, they may 
only be used on Locally Booted Workstations, i.e., the NSS or locally 
booted DOS Workstations.


About Our Examples

The remainder of the Technical Note outlines the procedure for 
installing NIC drivers for two different types of network cards. Each 
procedure differs slightly, so by reading over both, you'll soon have 
a better understanding of how to properly install NIC drivers.



Example #1: Installing a NIC Driver for Xircom Ethernet

In this example, we're going to install a Xircom Pocket Ethernet 
Adapter in a laptop system, which typically doesn't have a slot 
available for a regular Ethernet card. Our laptop is configured to 
boot from C: when not connected to the LAN, and will boot as a 
locally booted DOS Workstation from a diskette when used on the LAN. 
This is a typical configuration for a traveling salesman. This means 
some memory is saved when not booting onto the network, since the 
NDIS drivers are only loaded when needed.

Xircom provides three NDIS driver files with their Pocket Ethernet 
Adapter:

* PE_NDIS.DOS: the DOS driver
* PE_NDIS.OS2: the OS/2 driver
* PROTOCOL.INI: the Adapter Interface layer of PROTOCOL.INI


Creating A DOS Workstation Boot Diskette

The first series of steps in this procedure is to create a floppy 
diskette that can be used to boot the laptop as a LANstep workstation.

Note: This procedure assumes you are using a laptop system with a 
hard disk (C:) and a single floppy disk drive. However, you'll see 
that floppy drive A: and B: are referenced; this can be done on most 
laptops under DOS, since A: and B: are both recognized as the same 
physical drive.

Step 1:
        Boot the laptop from the normal DOS drive (usually C:).

Step 2:
        Insert a blank floppy in drive A:.

Step 3:
        Format the floppy as a bootable disk with the DOS FORMAT 
        command:

		 FORMAT A:/S

        The /S switch tells the FORMAT program to make the diskette a 
        bootable one.

Step 4:
        Remove the diskette and label it DOS WS Boot Disk. Insert
        the LANstep Network Workstation Setup diskette.

Step 5:
        From the C: prompt, enter:

		B:INSTALL

	DOS responds with the message:

		Insert diskette for drive B:
		and strike any key when ready

Step 7:
        Select Locally booted DOS Workstation from the menu; press 
	Enter.

Step 8:
        Select Install on Diskette A: and press Enter.

Step 9:
        The following message appears:

			Locally booted DOS WS Setup

		Copying DOS Workstation files...

		Insert diskette for drive A: and strike any 
		key when ready


	After this, insert your original formatted diskette (the one
	labeled DOS WS Boot Diskette) in drive A: and press Enter. You may
	have to alternate your diskettes four or five times until you
	receive a "4 files copied" message before the last prompt. Make
	sure the Network Workstation Setup disk is the last diskette left
	in your drive after being prompted to insert a diskette in drive
	B:. 

Step 10:
        From the next menu, select Ethernet and press Enter.

Step 11:
        A list of Ethernet card drivers appears:

	* 3Com EtherLink  501
	* 3Com EtherLink II 503
	* 3Com EtherLink Plus 505
	* 3Com EtherLink 16 507
	* 3Com Etherlink MC 523
	* Hayes EtherMate
	* Western Digital EtherCard
	* Other network cards

Step 12:
        Since Xircom is not in this list, select Other network cards 
	and press Enter.

Step 13:
        Select Manually install a network card driver and press 
	Enter.

Step 14:
        The following message appears:

		Follow the instructions that came with the network card
		to install the network card driver program.

	You will need to edit the PROTOCOL.INI file to include 
	certain entries specific to this network environment. 

	Refer to Chapter 5 of the Manager's Guide for details.

Step 15:
        Insert your DOS WS Boot Diskette in drive A: and view its 
	contents by entering;

		DIR

	at the DOS prompt.

Step 16:
        Ensure that the following files in the list are on your DOS 
	WS Boot Diskette:

		COMMAND.COM
		PROTMAN.SYS
		NETUSE.COM
		LOGIN.COM
		NETRDR.EXE
		NETROOM.BAT
		CONFIG.SYS
		AUTOEXEC.BAT

	If, for any reason, you do not have these files on your boot 
	diskette (or C: drive if booting from hard disk), repeat the 
	installation procedure beginning from Step 5.


Step 17:
        Get the Xircom diskette(s); in a directory (usually disk #1) 
	named \NDIS are three files:

		PE_NDIS.OS2
		PE_NDIS.DOS
		PROTOCOL.INI

Step 18:
        Since this is a DOS Workstation, you will need to copy the 
	DOS version of the driver, PE_NDIS.DOS and the PROTOCOL.INI file
	to the DOS WS Boot Disk. Insert the Xircom driver diskette and
	enter:

		COPY A:\NDIS\PE_NDIS.DOS B:\

	In this example, A: is the Xircom driver diskette and B:
	is the DOS WS Boot Disk.

Step 19:
        When the copy has finished, copy the second file:

		COPY A:\NDIS\PROTOCOL.INI B:\

Step 20:
        Using a plain ASCII text editor, update both the CONFIG.SYS 
	and PROTOCOL.INI files on the DOS WS Boot Disk.The CONFIG.SYS file
        should be changed to include these two lines:

		DEVICE=PROTMAN.SYS
		DEVICE=PE_NDIS.DOS

	These lines add two device drivers: PROTMAN.SYS for the
	Protocol Manager and PE_NDIS.DOS for the NIC.

Step 21:
        Now, using the text editor, modify the PROTOCOL.INI file. 
	The old file looks like this:

		[XIRCOMNET]
        		DRIVERNAME = XIRCOM$
        		INTERRUPT = 7
        		PRINTERPORT = LPT1

	Update it, so the new PROTOCOL.INI file looks like this:

		[protocol manager]
        		DRIVERNAME = PROTMAN$
		[INTERKNL]
        		DRIVERNAME = INKNL$
        		BINDINGS = XIRCOMNET
		[XIRCOMNET]
        		DRIVERNAME = XIRCOM$
        		INTERRUPT = 7
        		PRINTERPORT = LPT1

	These lines are always required by LANstep:

		[protocol manager]
	        	DRIVERNAME = PROTMAN$
		[INTERKNL]
        		DRIVERNAME = INKNL$


	This line is always "BINDINGS=x" where x is the name in brackets
	in the PROTOCOL.INI file supplied with the NIC:

        	BINDINGS = XIRCOMNET
		[XIRCOMNET]

	In technical terms, this is the name of the Adapter Interface
	Layer.

Step 22:
        Reboot your DOS Workstation with your DOS WS Boot Disk and 
	connect to the LANstep network. Your Login prompt will appear.

        



Example #2: Installing a NIC Driver for SMC ARCNET

In this example, the NSS contains an SMC ARCNET card. The LANstep 
system has already been installed. This card is not on LANstep's list 
of supported cards and there are no NDIS drivers supplied with the 
card. However, Hayes has produced a Supplementary Network Driver disk 
for the SMC ARCNET family of cards provided by SMC.


Get the Driver Files First

You can obtain this diskette (or files to create your own) by 
calling the Online With Hayes BBS at (800) USHAYES or Hayes Customer 
Service at (404) 441-1617 (USA) or (519) 746-5000 (Canada).

Step 1:
        If you obtained the files from the Online With Hayes BBS, 
	follow the instructions in the README file to create a
	Supplementary Network Driver diskette. 

Step 2:
        Login as Super_User. From the main office, select the 
	Management console icon and press Enter.

Step 3:
        Select LAN configuration and press Enter.

Step 4:
        Select Network card support and press Enter.

Step 5:
        Select Install network card drivers from Network Driver disk 
	and press Enter

	The screen displays the following message:

		Please insert the first Network Driver diskette in drive
		A:. Press Esc to quit, any other key to continue.

Step 6:
        Insert the Supplementary Network Driver disk in the drive 
	and press Enter. The next screen displays a list of network cards
	for which support was installed

Step 7:
        The following question is then displayed:

	        Did the network card installed in your NSS
        	appear in the above list?

	Type a Y and press Enter. Then the screen displays a list of 
	supported network cards.

Step 8:
        Select the card installed and press Enter. 

Step 9:
        When the PROTOCOL.INI file appears, modify the parameters in 
	the adapter interface layer to match the settings for your network
        adapter in the NSS.

	Because the driver is from a Hayes disk, there is no need to
	modify the PROTOCOL.INI file as in the previous example.


Step 10:
        Press F5:SAVE to save the file. 

Step 11:
        Press Escape as necessary to return to Super_User's Office

Step 12:
        Logout and reboot the NSS. 


This PROTOCOL.INI file is now saved for the NSS. When a LANstep 
workstation is configured or a network booted workstation is created, 
they get their own copy of this file, which can be customized to suit 
the settings of the network interface card in a particular 
workstation. This customization is done through the workstation 
configuration activities from the Management Console icon. Refer to 
chapter 6 of the LANstep Manager's Guide, if you are setting up a 
network booted DOS Workstation, and chapter 7 if you are setting up a 
LANstep Workstation.


Conclusion

The previous examples illustrate two common types of NDIS driver 
additions. However, if your particular situation is different, the 
objectives still remain the same. Hayes will provide NDIS drivers for 
network interface cards in one of two forms, Network Driver Diskettes 
or Supplementary Network Driver diskettes.

As network card manufacturers continue to create and supply NDIS 
drivers to Hayes, they will become available for use in one of the 
above two forms. In the meantime, there is an automated procedure 
available within LANstep to add other network card drivers to your 
LANstep network. By adopting the NDIS specification, LANstep has 
provided a means of supporting any current and future generations of 
network interface cards, thus achieving network card independence.



Hayes is a registered trademark and LANstep is a trademark of Hayes
Micrcomputer Products, Inc.

Other trademarks appearing in this document are trademarks of the
respective companies

(Copyright) 1993 Hayes Microcomputer Products, Inc.
USA