Fluke 2680A User Manual page 257

third-party networking software may use packet drivers. For information on packet
drivers, contact the networking software supplier.
Both ODI and NDIS are multi-protocol, packet driver standards. They both allow
operation of more than one set of protocol software "over" the driver at the same
time. Use of this feature will be discussed in the protocol section below.
The ODI standard was defined by Novell for use with the NetWare line of
networking software. It supports the native IPX/SPX protocol of NetWare and
other protocols, such as TCP/IP.
NDIS was defined by 3COM and Microsoft for use with the LAN Manager
networking software. It has since become commonly used by other network
operating systems, including the Windows built-in networking software. It also
supports multiple protocols, including IPX/SPX and TCP/IP.
ODI and NDIS drivers are usually loaded automatically by Windows, but may be
included in a DEVICE= line in the config.sys file.
The built-in Windows networking driver is controlled by the Network applet in the
Control Panel. With other networking software, the setup information for NDIS
drivers is contained in a file called protocol.ini that must be in the same
directory from which the driver is loaded. This file contains sections describing the
driver characteristics and the protocols that may be operating over the driver. For
example, a driver characteristic section might look like this:
[EtherLinkII]
DRIVERNAME=ELNKII$
INTERRUPT=5
TRANCEIVER=INTERNAL
IOADDRESS=0x300
While a protocol section might look like the following:
[NETMANAGE]
DRIVERNAME=NETMNG$
BINDINGS=EtherLinkII
These two protocol.ini file sections describe a hardware driver characteristic
for a 3COM EtherLink II hardware card and specifies that the Net Manager
protocol stack should bind with the EtherLink II driver.
The setup information for ODI drivers is contained in a file called net.cfg that
must be in the Novell directory (the driver must be there too). This file contains
sections describing the driver characteristics and the protocols that may be
operating over the driver. For example, a driver characteristic section might look
like the following:
Link Support
Buffers 8 1589
MemPool 4096
Appendices
Network Considerations
H
H-9