(C)Copyright 2003 D-Link Corporation. All rights reserved =========================================================================== Readme File for m4cxnw.lan D-Link DGE-530T Gigabit Ethernet Adapter Driver for Novell NetWare 4.20 This file contains 1 Overview 2 Required Files 3 Installation 4 Parameters 5 History =========================================================================== 1 Overview =========== The M4CXNW.LAN driver is a 32-bit ODI HSM Novell NetWare server driver for the D-Link DGE-530T Gigabit Ethernet Adapter. The driver complies with the CHSM Driver Specification Version 1.11 from January 29, 1998. *** 2 Required Files ================= NBI.NLM use latest version from Novell NEB.NLM use latest version from Novell ETHERTSM.NLM use latest version from Novell MSM.NLM use latest version from Novell 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. Step 1: Update NBI.NLM, NEB.NLM, MSM.NLM, and ETHERTSM.NLM in the SYSTEM directory of the server to the latest versions available for NetWare 4.20 (working versions are provided with this driver). Usually you should install the latest support pack from Novell. If it is not possible to upgrade these NLMs before driver installation (e.g. if no workstation is connected or you are installing a NetWare 4.20 server), you may also 'outcomment' the 'OF:' line in M4CXNW.LDI ('OF' means 'Other Files' that need to be copied during installation). In this case you must provide INSTALL with the full path to the LAN driver (after pressing <INSERT>). If you do not want to replace some of these files, press <ESC> when you are asked if the existing file should be saved. You should also copy NBI.NLM to the directory where SERVER.EXE resides (normally C:\NWSERVER). Step 2: Install the driver M4CXNW.LAN for NetWare v4.20 via INSTALL.NLM. The installation support file M4CXNW.LDI is used to install the driver. If you are not certain how to use this NLM, please refer to its (printed) documentation or use the online help. *** 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=00055D1234 ... MAXFRAMESIZE = [ 512 .. 9018 ] Description: Set the maximum frame size. Help: The value has to be in the range 512 to 9018. 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. Example: LOAD M4CXNW ... MAXFRAMESIZE=9018 ... 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 ... Auto-negotiation Some switches or hubs do not work with auto-negotiation. To work around this problem the driver works in a so called sense mode. In this mode it tries to use auto-negotiation and if it fails it forces full-duplex mode. You can also force the mode using one of the following parameters. AUTONEG_A = [ ON | OFF ] Description: Set mode for auto-negotiation on port. Help: The default value will is ON. Example: LOAD M4CXNW ... AUTONEG_A=ON ... DUPCAP_A = [ BOTH | FULL | HALF ] Description: Define duplex capabilities for the port. Help: If AUTONEG_A is set to ON, this parameter defines the duplex mode capabilities the adapter will show on the port in the auto-negotiation process. Changing this parameter may lead to a failed auto-negotiation process. By default BOTH will be used which means the port is capable to connect with full-duplex or half-duplex. If AUTONEG_A is set to OFF, DUPCAP_A determines if the adapter uses a full duplex or a half duplex connection. The value BOTH is not allowed in this case. Example: LOAD M4CXNW ... DUPCAP_A=FULL ... FLOWCTRL_A = [ SYMORREM | NONE ] Description: Define flow control capabilities for the port. Help: Used as workaround for switches that do not behave standards-compliant. By default, SYMORREM will be used. The values represent the following configurations: SYMORREM: supporting symmetric flow control and asymmetric flow control towards me (possible results: symmetric flow control, asymmetric flow control towards me, no flow control) NONE: supporting no flow control Example: LOAD M4CXNW ... FLOWCTRL_A=NONE ... SPEED_A = [ Auto | 100 | 10 ] Description: Defines the link speed to use. Help: If AUTONEG_A is set to ON, this parameter defines the link speed capabilities the adapter will try to use for the auto-negotiation process. Changing this parameter may lead to a failed auto-negotiation process. By default AUTO will be used which means the port is capable to connect with 10, 100, 1000. If AUTONEG_A is set to OFF, SPEED_A determines the link speed the adapter uses for the connection. The value AUTO is not allowed in this case. Example: LOAD M4CXNW ... SPEED_A=100 ... Other Parameters Please do not try changing these parameters in a production environment unless you have figured out that they fit your needs. The changes can affect the server performance in a postive or negative way. It depends on the purpose of the server. The default settings of the driver should meet the requirements of a normal server. TXDESC1 = [ 20 .. 200 ] Description: Number of transmit descriptors used. Help: It may be useful to decrease this value if there is not enough memory in the server. The default value is 100 on a server and 40 on a client. RXDESC1 = [ 10 .. 200 ] Description: Number of receive descriptors used. Help: It may be useful to decrease this value if there is not enough memory in the server. The default value is 100 on a server and 20 on a client. HWCSUMCAP = [ 00 .. FF ] Description: Limit the capabilities for hardware IP/TCP/UDP checksum offload. Help: It is possible to disable specific checksum offload capabilities. The parameter specifies the allowed checksum offload capabilities for the adapter. It is in hexadecimal format and you have to add the values for the desired capabilities. The default value is FF. 00: Checksum offload not supported 01: TCP checksum verification (RX) 02: UDP checksum verification (RX) 04: IP checksum verification (RX) 10: TCP checksum generation (TX) 20: UDP checksum generation (TX) FF: all checksum offloads the adapter can support Example: LOAD M4CXNW ... HWCSUMCAP=7 ... *** 5 History ========== VERSION 6.05 Problems fixed: - Disabling Flow-Control with parameter 'none' (#10769) - Changed behaviour of LEDs. Known limitiations: - None VERSION 6.04 New Features: - Added value ALL for parameter MODERATE. Known limitiations: - None VERSION 6.03 Problems fixed: - Behaviour of activity LED changed. Known limitiations: - None VERSION 6.02 New Features: - Initial Version. Known limitiations: - None *** End of Readme File ***Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.