(C)Copyright 1998-2006 D-Link(R).
All rights reserved.
===========================================================================

m4cxnw.txt created 12-Jul-2006

Readme File for m4cxnw.lan v8.14.3.3

D-Link DGE-5xx Gigabit Ethernet Adapter Driver
for Novell NetWare 6.0 and 6.5


This file contains
 1  Overview
 2  Required Files
 3  Installation
 4  Parameters

===========================================================================


1  Overview
===========

The M4CXNW.LAN driver is a 32-bit ODI HSM Novell NetWare server driver for
the D-Link DGE-5xx Gigabit Ethernet Adapter.
The driver complies with the CHSM Driver Specification Version 1.11 from
January 29, 1998.
***


2  Required Files
=================

	M4CXNW.LAN	driver
	M4CXNW.LDI	installation script
***


3  Installation
===============

NOTE:	The setting for MINIMUM PACKET RECEIVE BUFFERS in the STARTUP.NCF must
	be increased to at least 120 per adapter (e.g. for three adapters you
	should add "SET MINIMUM PACKET RECEIVE BUFFERS=360" to STARTUP.NCF).
	On SMP systems, you may have to multiply this number with the number
	of active processors.

If the adapter is installed in the machine NetWare detects the new adapter
and tries to install a driver. Press <ENTER> to get a list of all available
drivers and then <INSERT> to install an unlisted driver. Enter the path to
the driver and select M4CXNW.LAN. Choose Yes to copy the driver to
the server. NetWare will now install the driver.

Once the driver has been installed, the adapter parameters or bindings
can be changed in the AUTOEXEC.NCF file using the NWCONFIG tool.
***


4  Parameters
=============

SLOT = [ 1 .. 65535 ]
	Description:	Defines the slot in which the adapter is installed.
	Help:		If you do not enter a slot number, the driver scans
			automatically for network adapters and prompts the
			slot number in which the network card is found at
			the server console.
	Example:
			LOAD M4CXNW ... SLOT=3 ...

FRAME = [ ETHERNET_802.2 | ETHERNET_II | ETHERNET_SNAP | ETHERNET_802.3 ]
	Description:	Sets the frame type used by the network.
	Help:		The NetWare Server and the Workstations must use
			the same frame type. Otherwise they cannot
			communicate with each other.
	Example:
			LOAD M4CXNW ... FRAME=ETHERNET_II ...

NODE = [ xxxxxxxxxxxx ]
	Description:	Overwrites the network card node address.
	Help:		With this parameter, you can overwrite the default
			node address.
			In a network, every network card must have its own
			unique node address.
			Do not change this address unless you are prepared
			to administer local addresses according to the
			IEEE 802.2 specifications.
			The driver defaults to the node address on the
			board, which corresponds to an undefined override.
	Example:
			LOAD M4CXNW ... NODE=40005A123456 ...

MAXFRAMESIZE = [ 512 .. 9014 ]
	Description:	Set the maximum frame size.
	Help:		The value has to be in the range 512 to 9014.
			The default value is 1514.
			Setting the value above 1514 is only effective if you
			use an ETHERTSM.NLM that supports Jumbo Frames and
			if you load the frame type ETHERNET_II as the first
			frame type on the specific adapter.
			When you change this parameter you should change the
			setting for MAXIMUM PHYSICAL RECEIVE PACKET SIZE in
			your STARTUP.NCF accordingly.
	Example:
			LOAD M4CXNW ... MAXFRAMESIZE=9014 ...

HWCSUM = [ ON | OFF ]
	Description:	Controls hardware checksum offloading
	Help:		By default ON the hardware checksum offload for
			IP/TCP/UDP is enabled. There should be no need to
			disable checksum offload.
			Offloading computation of internet checksums is only
			supported by NetWare 5.x or higher.
	Example:
			LOAD M4CXNW ... HWCSUM=OFF ...

QUIET = [ AUTO | ON | OFF ]
	Description:	Suppress driver status messages.
	Help:		By default AUTO will be used which means that
			status messages will not be suppressed if running on
			a server and will be suppressed if running on a
			client.
			OFF means that messages will not be suppressed.
			ON means that messages will be suppressed.

Auto-negotiation

CONTYPE = [AUTO | 100FD | 100HD | 10FD | 10HD ]
	Description:	Set mode for auto-negotiation, speed duplex-mode.
	Help:		The default value will is AUTO.
	Example:
			LOAD M4CXNW ... CONTYPE=10HD ...

FLOWCTRL = [ ON | OFF ]
	Description:	Enable or disable flow control for the port.
	Help:		This parameter can be used to set the flow control
			capabilities for the port. Using the default setting,
                        the  adapter should automatically detect the 
			capabilities of the peer port. 
	Example:
			LOAD M4CXNW ... FLOWCTRL=OFF ...

Interrupt Moderation (Paced Packet Batch)

Interrupt moderation can be used to decrease the CPU load on systems
with high utilization. But the latency of packets will increase. To
enable interrupt moderation you must specify the mode and the interrupt
rate. The parameters IRQPERSEC and MAXIRQPERSEC are mutual exclusive.

MODERATE = [ NONE | RX | TX | BOTH | ALL ]
	Description:	Interrupt moderation mode.
	Help:		By default, NONE will be used which means interrupt
			moderation is disabled.
			If RX is used only receive interrupts are moderated,
			which means if more than the specified rate of
			interrupts occur they will be congested to reach the
			specified rate. But other interrupts may occur without
			any limitation.
			If TX is specified transmit complete interrupts will
			be moderated.
			BOTH will lead to a moderation of receive and transmit
			interrupts.
			By using ALL, all interrupts will get moderated.

IRQPERSEC = [ 1000 .. 15000 ]
	Desription:	Interrupt rate for static moderation.
	Help:		Independent of the interrupt load only at specified
			intervals interrupts occur. This will increase
			latency of receive or transmit path dependent on
			the mode specified using parameter MODERATE.
			This parameter has a different meaning if used
			together with POLL.
	Example:
			LOAD M4CXNW ... MODERATE=TX IRQPERSEC=5000

MAXIRQPERSEC = [ 1000 .. 15000 ]
	Desription:	Interrupt rate for dynamic moderation.
	Help:		Using dynamic interrupt moderation means that
			interrupt moderation will be enabled only if more
			than the specified number of interrupts occur. The
			measured interrupt rate is not limited to receive
			or transmit interrupts as specified in MODERATE.
			All interrupts will be counted. If more interrupts
			occur the interrupts specified in MODERATE are
			moderated. If the number of interrupts goes down
			below the specified level moderation is disabled.
			Using dynamic interrupt moderation has the
			advantage that the latency is increased only
			if interrupt load is high.
	Example:
			LOAD M4CXNW ... MODERATE=BOTH MAXIRQPERSEC=1000

*** End of Readme File ***
