1. novell.zip Driver
2. ISA.TXT File Contents

ISA.TXT Driver File Contents (novell.zip)

                *************************************  
                LAN9000 DOS ODI driver for ISA boards  
                *************************************


Versions:
========
LAN9000.com	   05/22/00	  v4.23	    Supports LAN91C110+83C183 ISA boards		

LAN9000.COM         08/13/98      v4.20     Supports ISA and FEAST boards.

***************************
Driver configurable options
***************************

For instructions on using the LAN91C110 ISA evaluation board see the section at the 
end of the file.

IO BASE
-------

May be set by including the following line in NET.CFG file

Port xxx                        ;typical values are 300, 320, 340, 360

Please refer to the 91C9X or FEAST Data Sheet (Base Register) for the 
complete set of options.

Defaults to 300, be sure the board is set to the same IO address, otherwise
the driver won't find the board. In order to change the IO address of the 
board you need to use the ISMC9000 setup utility.

INTERRUPT NUMBER
----------------

May be set by including the following line in NET.CFG file

Int x                           ;where x can be 2, 3, 10, 11

Defaults to SCEC's EEPROM configuration if not present

NODE ADDRESS
------------

The board has got a unique IEEE address. However it may be overwritten by
including the following line in NET.CFG:

Node Address xxxxxxxxxxxx

Where xxxxxxxxxxxx is a 12 digit hex Number (non multicast or broadcast)
Defaults to board's IEEE unique address if not present

NOTE:    For the 91C110 ISA evaluation boards this option is REQUIRED, since
(91C110) the 91C110 does not have an EEPROM where to store the Node Address
         this is the only place to store this address. Fail to do so will 
         cause th 91C110 to use address 00000000000 which is invalid.

FRAME TYPE
----------

May be set by including the following line in NET.CFG

Frame <type>

where <type> is ETHERNET_802.3, ETHERNET_802.2, ETHERNET_II, ETHERNET_SNAP
Defaults to ETHERNET_802.2 if not present. You must use a frame type 
supported by the server you are trying to attach in order to conect to it.

MEDIA TYPE SELECTION
--------------------

The user may select which media type the SCEC will be working with.
This option is specified via parameter passing using the NET.CFG file.
The keyword is "MEDIA_TYPE". The value following the keyword must be one 
of the following:

"AUTO"     for automatic selection.
"10BASET"  for 10BaseT.
"AUI"      for AUI interface.
"MII"      for MII interfae (FEAST only). 

The 4.10 version also support the following keywords:
"UTP"      for 10BASET
"BNC"      for AUI interface (For boards with BNC, it will enable it)
"10BASE2"  for AUI interface (For boards with BNC, it will enable it)

Note that NO "=" FOLLOWS the MEDIA_TYPE keyword.
If the MEDIA_TYPE keyword is not present the driver will use the adapter's
EEPROM default.

If using MII, and the board has an autonegotiating PHY, it can be programmed
byusing the MIIPHY.EXE utility.

NOTE:       The 91C110 only supports MII media type. Any other selection
(91C110)    will be ignored and overwritten by the driver to use MII.

FULLDUPLEX
----------
The presence of this keyword sets the 91C100, 91C110 and 91C95 and 91C96 
chips to operate in full duplex mode. It is not supported in earlier devices
of the LAN9000 family. Note that the PHY must be also programmed to operate 
in full duplex mode in order for the board to work (applicable to FEAST chips 
only).

The absence of this keyword implies that the operation will be half duplex.

ETXOFF and ERXOFF
-----------------
This options allow to turn off performance optimization routines of the 
driver. The options work fine in 10Mbps, for which they were optimized.
For 100 Mbps we recomend turning this features off by inserting this 
Keyword (see sample NET.CFG)


			     To load the driver type:
			     ========================

				    lsl
				    lan9000
				    ipxodi
				    netx (or VLM, included zipped in SMSCVLM.EXE in this disk)

WINDOWS SUPPORT FOR NETWORKS THROUGH ODI DRIVERS (AFTER finishing the above)
----------------------------------------------------------------------------

*  To run Windows For Workgroups with complete Netware (Novell) Network 
   support configure it through Network Setup to use Novell Netware type of 
   Networks. You should always login in DOS before starting Windows.
   <i.e.: check the "Install Windows support for the following Network only:"
    and select Novell Netware (4.0 for VLMs and 3.X for NETX)>
   During the installation Windows setup will ask you for several Netware
   support files. These can be found in the WFW311 subdirectory

*  To run Windows For Workgroups with complete Netware (Novell) Network 
   support AND Microsoft Windows Network support Simultaneously configure 
   it through Network Setup in the following way:
   	- Check "Install Microsoft Windows Network"
	- Check "Install support for an additional network"
	  and select "Novell Netware..." Use shell 3.X for NETX and 
	  4.0 for VLMs
	- Select Drivers and Add adapter. Select "Unlisted or updated..."
	  and click OK. Type the path to WFW311 directory in the box. 
      Select "SMC9000 Ethernet PCMCIA..." click OK. You'll see it 
      appends the comment [ODI/NDIS3] to indicate it will give NDIS 
      support through the ODI driver. Close and save everything. 
      During the installation Windows setup will ask you for several 
      Netware support files. These can be found in the WFW311 
      subdirectory. Aferwards it will prompt to reboot, do it. When 
      rebooting you should have support for both networks.

Notes on LAN91C110 16bit FEAST usage
---------------------------------

As of this release this new addition to the LAN9000 family has been tested
with the ISA evaluation board only.

Since the 91C110  does not have support for an external EEPROM the node 
address on ISA boards has to be manually entered in the NET.CFG (or else 
have external logic copy it to the chip on power up). PCMCIA cards will 
not be affected by this since the Node Address is stored in the CIS for 
them.

Also FEAST110 only has MII support. Any attempt to use other MEDIA_TYPE 
will be ignored by the driver and MII will be used.

The PHY attached to a 91C110 in the ISA evaluation board is a 10/100
autonegotiating PHY. The DOSODI driver currently does not have 
autonegotiation support embedded in it. In order to perform autonegotiation 
or force speed/duplex mode you need to use the MIIPHY.EXE utilty. type 
MIIPHY ? for instructions.