CMDGODI.LAN - 32-bit ODI Driver =============================== LSS 7.1(0), September 2000 -------------------------- Contents -------- (1) Summary (2) Associated files (3) Driver overview (4) Supported environments (5) Client 32 overview (6) Loading the driver (7) Required support modules (8) PCMCIA and CardBus support (9) Statistics (10) Lost interrupt alerts (11) Using Madge LLC for Client 32 software. (12) Wake-On-LAN (13) Disabling promiscuous mode (14) Adapter mirroring (failover) (15) Driver parameters (1) Summary ----------- This file contains information relating to CMDGODI.LAN (version 4.00 and above). CMDGODI.LAN is a 32-bit ODI driver for Madge and Olicom token-ring adapters. CMDGODI.LAN runs on Novell NetWare servers (3.12 and above) and on NetWare DOS/Windows 3.1 client workstations (using the Novell Client32 protocol stack). The driver conforms to the Novell C Hardware Specific Module (CHSM) specification version 1.11. The driver supports the following Madge and Olicom token-ring adapters: o Madge Smart 100/16/4 PCI-HS Ringnode o Madge Smart 100/16/4 PCI Ringnode o Madge Smart 16/4 PCI Ringnode Mk3 o Madge Smart 16/4 PCI Ringnode Mk2 o Madge Presto PCI 2000 o Madge Presto PCI Plus o Madge Presto PCI o Madge 16/4 CardBus Adapter Mk2 o Madge 16/4 CardBus Adapter o Madge Smart 16/4 PCMCIA Ringnode Mk2 o Madge Smart 16/4 PCMCIA Ringnode o Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter o Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter o Olicom RapidFire 3140 V2 16/4 PCI Adapter o Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter o Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter o Olicom Token-Ring PCI/II 16/4 Adapter (OC-3137) o Olicom GoCard 3250 Token-Ring 16/4 CardBus PC Card o Olicom GoCard Token-Ring PC Card (OC-3221) (2) Associated files -------------------- The CMDGODI.LAN suite comprises the following files: o CMDGODI.LAN - The driver o CMDGODI.LDI - NetWare and DOS installation script (3) Driver overview ------------------- CMDGODI.LAN is a 32-bit ODI driver written to the Novell CHSM 1.11 specification, part of the Novell Open Data-Link Interface (ODI) architecture. The ODI architecture allows multiple adapters and multiple protocols to co-exist in the same machine. Within the ODI architecture, network drivers are termed Multiple Link Interface Drivers (MLIDs). An MLID consists of a Hardware Specific Module (HSM) plus a Topology Specific Module (TSM) plus a Media Support module. HSMs (e.g. CMDGODI.LAN) are typically provided by network equipment vendors whilst the TSM and MSM modules are provided by Novell. Novell provide TSMs for the common network topologies, the TSM which supports token ring is called TOKENTSM.NLM. The MSM and TSM modules provide support to the HSM and allow the HSM to be operating system independent which is important for providing portability between different client and server environments. A single MLID can support multiple adapters simultaneously. Each token ring adapter may support up to two frame types (TOKEN-RING and TOKEN-RING_SNAP). The frame types required depends upon the protocols loaded in the system. A software layer called the Link Support Layer (LSL) handles communication between multiple protocols and multiple adapters. A protocol is bound to a specific logical board (adapter / frame type combination). When a frame is transmitted by a protocol, the frame is passed to the LSL which then passes the frame to the relevant MLID/ adapter for transmission onto the wire. When a frame is received by an adapter off the wire, the MLID passes the frame to the LSL which then passes the frame to the relevant protocol. (4) Supported environments -------------------------- Historically, 32-bit HSM drivers (.LAN drivers) only executed on NetWare servers (3.12 and above). Novell's Client 32 architecture now provides support for 32-bit HSM drivers on client workstations. The Client 32 architecture makes use of the inherent portability of HSM drivers provided by the MSM and TSM layers. To run an HSM under different operating systems, MSM and TSM modules for each environment must be provided but the HSM remains unchanged. Currently, the following environments are supported: o DOS/Windows 3.1 client (Client 32) o NetWare servers (3.12 and above) Note: Novell no longer support the use of 32-bit HSM drivers under Windows 95. They recommend that you use an NDIS miniport driver instead when using Client 32 for Windows 95. (5) Client 32 Overview ---------------------- (5.1) General ------------- Client 32 is Novell's current NetWare client architecture. It is based on 32-bit networking components (drivers, protocol stacks and clients) and allows 32-bit HSM drivers, such as CMDGODI.LAN to be loaded on client workstations as well as NetWare servers. At the heart of Client 32 is the NetWare I/O subsystem (NIOS). This software layer provides partial NetWare operating system emulation and acts as a loader for NLM format executables such as LAN drivers. It provides the interface between the host operating system and the 32-bit networking components. (5.2) Client 32 for DOS/Windows 3.x ----------------------------------- Under DOS, NIOS is implemented as a single executable called NIOS.EXE. An extended memory (XMS) manager, such as HIMEM.SYS, must be loaded prior to loading NIOS. Once NIOS.EXE is loaded the "LOAD" and "UNLOAD" keywords may be used at the command prompt to dynamically load and unload NLMs (including .LAN drivers and protocols) in extended memory. The use of extended memory (memory above 1Mb) means that the sub-1Mb memory footprint of Client 32 under DOS is very small, typically around 4Kb. NIOS will use upper memory blocks (UMBs) if they are available in preference to conventional memory. UMBs are blocks of memory allocated by a memory manager, such as EMM386, in the 640Kb-1Mb region. To make UMBs available, a memory manager must be loaded and the "DOS=UMB" command must be added to CONFIG.SYS. Refer to your memory manager documentation for more details. 16-bit ODI drivers can be used in the Client 32 environment. A 16-bit ODI driver is loaded as normal into conventional memory and the Novell provided 32-bit virtual LAN driver, PC32MLID.LAN, is used to allow protocols executing in 32-bit protected mode to communicate with the 16-bit driver. This configuration is not recommended - 32-bit ODI drivers give greater performance and conventional memory savings. Novell provide IPX and TCP/IP protocol support with IPX.NLM and TCPIP.NLM. The client requester, CLIENT32.NLM, is used to provide access to NetWare network services. The Client 32 requester is backwards compatible with the NETX and VLM APIs so existing NetWare applications should still function. CLIENT32.NLM supports packet burst transfers for increased performance, file caching and NetWare Directory Services (NDS) functionality. (5.3) Client 32 for Windows 95 ------------------------------ The Client 32 protocol stack and requester for Windows 95 replaces the NetWare client provided by Microsoft. Previously Novell supported the use of 32-bit HSM drivers with Client 32 for Windows 95, however they now recommend that an NDIS miniport driver (native Windows network driver) is used instead. (6) Loading the driver ---------------------- (6.1) Loading the driver (NetWare Server) ----------------------------------------- (6.1.1) Basic usage ------------------- CMDGODI.LAN may be loaded on a NetWare 3.12 or 4.x server. At the server command line, or in AUTOEXEC.NCF, enter the following: LOAD CMDGODI [PORT=<p> | SLOT=<s> | BIA=<b>] [<options>] If this line is entered into the AUTOEXEC.NCF file, the driver will be loaded each time the server boots. If the TOKENTSM.NLM, MSM.NLM and NBI.NLM modules have not already been loaded they will be auto-loaded. It is only necessary to specify a PORT, SLOT or BIA number if more than one adapter exists in the machine. If multiple adapters exist and no PORT, SLOT or BIA parameter is given, you will be prompted to choose a value from a list. "LOAD CMDGODI DISPLAY" can be used to display the adapters in the machine at any time. CMDGODI.LAN can also be installed using the Novell INSTALL.NLM utility (NetWare 3.x and 4.x) or NWCONFIG.NLM (NetWare 5.x). Multiple "LOAD CMDGODI" lines can be used to load the driver onto multiple adapters or to load multiple frame types onto a single adapter. When multiple "LOAD CMDGODI" commands are used, CMDGODI.LAN is only actually loaded into memory once and all subsequent loads cause new boards to be added to the already loaded driver. Example: LOAD CMDGODI PORT=1000 LOAD CMDGODI PORT=2000 (6.1.2) Specifying frame type ----------------------------- To specify the frame type, use the FRAME= parameter on the command line. Both TOKEN-RING and TOKEN-RING_SNAP frame types may be loaded simultaneously on the same adapter. The frame types required depends on the protocols you wish to use. For example, IPX uses TOKEN-RING frames but TCP/IP uses TOKEN-RING_SNAP frames. Example: LOAD CMDGODI PORT=1000 FRAME=TOKEN-RING LOAD CMDGODI PORT=1000 FRAME=TOKEN-RING_SNAP (6.1.3) Protocol binding ------------------------ The BIND command is used to bind a logical instance of the driver to a protocol stack. The NAME= parameter can be used to override the default name (CMDGODI). Example: LOAD CMDGODI PORT=1000 NAME=adapter1 LOAD CMDGODI PORT=2000 NAME=adapter2 BIND IPX TO adapter1 NET=A12002 BIND IPX TO adapter2 NET=A12003 (6.1.4) Using source routing ---------------------------- If you need to use source routing, load Novell ROUTE.NLM. Source routing must be used if NetWare servers are to communicate with workstations across a source routing bridge or switch. In the following example CMDGODI.LAN is loaded onto two adapters with two frame types each and source routing is loaded for each logical board: LOAD CMDGODI PORT=1000 FRAME=TOKEN-RING NAME=adapter1 LOAD ROUTE BOARD=1 LOAD CMDGODI PORT=1000 FRAME=TOKEN-RING_SNAP NAME=adapter1_SNAP LOAD ROUTE BOARD=2 LOAD CMDGODI PORT=2000 FRAME=TOKEN-RING NAME=adapter2 LOAD ROUTE BOARD=3 LOAD CMDGODI PORT=2000 FRAME=TOKEN-RING_SNAP NAME=adapter2_SNAP LOAD ROUTE BOARD=4 (6.1.5) Setting the maximum frame size -------------------------------------- The maximum frame size which CMDGODI.LAN will support on a NetWare server is configured by placing the following line in STARTUP.NCF: SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE=<max frame size> Note that the actual maximum frame size used is limited by the maximum size supported at the configured ring speed. Setting this parameter to a number greater than is actually required wastes memory. (6.1.6) Driver control ---------------------- When the driver is running, the user can choose to shutdown or reset individual boards or adapters without having to unload the driver, using the following console commands: 1) REMOVE NETWORK INTERFACE <logical board #> | <logical board name> This command removes an instance of a logical board which is currently loaded. Since a logical board is a particular adapter/frame type combination, this command stops the adapter from using a particular frame type which was previously loaded. 2) REMOVE NETWORK ADAPTER <filename>,<BoardInstance number> This command removes all logical boards loaded on the specified adapter. The filename specified is CMDGODI. 3) SHUTDOWN NETWORK INTERFACE <logical board #> | <logical board name> This command performs a partial shutdown of the specified logical board. This temporarily suspends usage of the logical board, until a "RESET NETWORK INTERFACE" command is issued to reset the board. 4) RESET NETWORK ADAPTER <filename>,<BoardInstance number> This command resets the specified network adapter at the hardware level. The filename is CMDGODI. 5) RESET NETWORK INTERFACE <logical board #> | <logical board name> This command resets the specified logical board. It can be used to restore operation of a logical board which was suspended using "SHUTDOWN NETWORK INTERFACE". To determine the current configuration of adapters in the machine, type either "CONFIG" or "LOAD CMDGODI DISPLAY" from the console command line. (6.2) Loading the driver (Client 32 for DOS/Windows 3.1) -------------------------------------------------------- You will require the Novell Client 32 for DOS/Windows 3.1 installation disks to install CMDGODI.LAN in this environment. (6.2.1) Installation -------------------- CMDGODI.LAN may be loaded on DOS client workstations with Novell Client 32 software installed. To install CMDGODI.LAN in this environment, run the Novell Client 32 installation utility. When prompted to choose an adapter to use, select "OTHER DRIVERS". When prompted, enter the path where the files CMDGODI.LDI and CMDGODI.LAN can be found. Select "Madge Token Ring C Hardware Support Module" from the driver list to install CMDGODI.LAN. The Novell installation utility will install all required client software and will create a STARTNET.BAT file which contains the commands required to load the driver, protocol and requester. The STARTNET.BAT file should look similar to the following example: SET NWLANGUAGE=ENGLISH NIOS.EXE LOAD LSLC32.NLM LOAD CMSM.NLM LOAD TOKENTSM.NLM LOAD CMDGODI.LAN LOAD SROUTE.NLM LOAD IPX.NLM LOAD CLIENT32.NLM Driver parameters can be specified on the "LOAD CMDGODI.LAN" command line, for example "LOAD CMDGODI.LAN PORT=A20 FRAME=TOKEN-RING". Note that driver parameters are not put in the NET.CFG file. Any file loaded using "LOAD <name>" can be unloaded by typing "UNLOAD <name>" at the DOS prompt. Note that files should be unloaded in the reverse order to which they were loaded. (6.2.2) Using source routing ---------------------------- If the client needs to communicate with servers across a source routing bridge or switch, the source routing support module, SROUTE.NLM, must be loaded using "LOAD SROUTE". If required, SROUTE.NLM should be loaded after loading CMDGODI.LAN and before loading CLIENT32.NLM. (6.2.3) Setting the maximum frame size -------------------------------------- The maximum frame size which CMDGODI.LAN will support on a DOS client workstation is configured by placing the following line in NET.CFG under the "Link Support" section heading: MAX BUFFER SIZE <max frame size> Note that the actual maximum frame size used is limited by the maximum size supported at the configured ring speed. Setting this parameter to a number greater than is actually required wastes memory. (7) Required support modules ---------------------------- This version of CMDGODI.LAN is written to CHSM specification 1.11 and requires support modules (MSM.NLM and TOKENTSM.NLM) which support this specification. In general you should ensure that the latest Support Pack is installed on your NetWare server which will include the latest support modules. (8) PCMCIA and CardBus support ------------------------------ (8.1) PCMCIA and CardBus support (DOS) -------------------------------------- (8.1.1) Required software ------------------------- To use Madge PCMCIA or CardBus adapters in a DOS client workstation requires Card and Socket Services plus a card management utility (enabler) which automatically configures the adapter's IO port and IRQ channel upon adapter detection. To use CardBus adapters, a Card Services compliant to the PC Card Standard version 5.00 (at least) is required. (8.1.2) Using MADGECS --------------------- MADGECS.EXE may be used instead of Card (and Socket) Services if only Madge PCMCIA or CardBus adapters are to be used in the machine (MADGECS does not support non-Madge PCMCIA adapters). MADGECS can give memory savings over other Card and Socket Services and is generally simpler to configure. To use MADGECS with CMDGODI.LAN under DOS, MADGECS must be loaded prior to loading any Client32 software (typically from CONFIG.SYS or AUTOEXEC.BAT). The "CLIENT_32=YES" parameter must be specified, either on the MADGECS command line or in the MADGECS.CFG file. MADGECS must be told to automatically configure the IO and IRQ resources of any Madge PCMCIA or CardBus adapters which are detected by specifying the "AUTOMATIC_CONFIGURATION" parameter. No separate card management utility is required. A sample MADGECS.CFG is given below: ; --- Sample MADGECS.CFG --- EMULATE_SOCKET_SERVICES=YES ; Use MADGECS Socket Services emulation. CLIENT_32=YES ; Support Client32. AUTOMATIC_CONFIGURATION=ONLY_ON_LOAD ; Auto-configure Madge PCMCIA ; adapters which are in the ; machine when MADGECS loads. ; --- End Of File --- [Note that additional parameters may be required to modify MADGECS' internal available IO, IRQ and memory resources list] When MADGECS auto-configures a PCMCIA or CardBus adapter, the configured resources are displayed on the screen. An example MADGECS auto-configuration message follows: "The Madge Smart 16/4 PCMCIA Ringnode at slot 1 has been configured to I/O location 0A20, interrupt 5, memory range CC00-CCFF" See the documentation for MADGECS.EXE for more details. (8.1.4) Using memory managers ----------------------------- If you are using a memory manager such as EMM386, you must be careful to exclude the memory ranges which Card Services is configured to use to prevent conflict. For example, to prevent EMM386 from using the 4k memory region from CC000 to CCFFF, load EMM386 from CONFIG.SYS using "DEVICE=EMM386.EXE X=CC00-CCFF". (8.1.5) Removing PCMCIA and CardBus adapters -------------------------------------------- It is recommended that Madge PCMCIA and CardBus adapters are not removed while CMDGODI.LAN is loaded under DOS - any server connection will be lost, even if the adapter is re-inserted, this may also result in data loss. If an adapter needs to be removed, logout of all servers unload the requester, unload the protocols and unload CMDGODI before removing the adapter. The adapter may of course be re-inserted at a later time and the driver and protocol software re-loaded to regain a network connection. If using MADGECS, the "AUTOMATIC_CONFIGURATION = ALWAYS" parameter must be specified for Madge PCMCIA adapters to be auto-configured upon insertion ("AUTOMATIC_CONFIGURATION = ONLY_ON_LOAD" only configures adapters which are in the machine when MADGECS loads). (8.2) PCMCIA and CardBus support (NetWare Server) ------------------------------------------------- (8.2.1) Required software ------------------------- To use Madge PCMCIA or CardBus adapters in a NetWare Server, Card and Socket Services must be loaded under DOS and the card configured using a configuration utility BEFORE NetWare is loaded. MADGECS.EXE may be used. Refer to the instructions for using PCMCIA adapter under DOS. (8.2.2) Removing PCMCIA and CardBus adapters -------------------------------------------- It is recommended that Madge PCMCIA and CardBus adapters are not removed while CMDGODI.LAN is loaded - any client connections will be lost, even if the adapter is re-inserted, this may also result in data loss. (9) Statistics -------------- HSM drivers maintain driver statistics which can be viewed using MONITOR.NLM on the NetWare server. If the "No ECB available count" statistic is observed to increase frequently, this may indicate that the driver is unable to obtain all the packet receive buffers it wants from the NetWare operating system. An ECB is used every time the driver receives a frame, and if there are insufficient ECBs available, server performance may be degraded. To increase the number of ECBs allocated by NetWare, insert the following lines in the server's STARTUP.NCF file: SET MINIMUM PACKET RECEIVE BUFFERS=<min number of buffers> SET MAXIMUM PACKET RECEIVE BUFFERS=<max number of buffers> To determine the current values of these parameters, type "SET MINIMUM PACKET RECEIVE BUFFERS" or "SET MAXIMUM PACKET RECEIVE BUFFERS" at the server command prompt. The "SET MINIMUM PACKET RECEIVE BUFFERS" parameter should be set to the minimum value which results in the "No ECB available count" staying at zero. Several Custom statistics are provided by CMDGODI.LAN: "Open mode (0:Closed 1:Classic 2:DTR 3:Single" This statistic gives information about the adapter's open status. "Ring speed (Mbit/s)" This statistic gives the ring speed which the adapter has opened at. "Free transmit resources" This is a count of the number of transmit resources currently available (one transmit resource is required per transmit frame). If this count reaches zero, the server queues further transmits until resources become free. Under very heavy load, this counter may remain zero, or a small number, which indicates that the adapter's transmit path is being fully utilised. The standard statistic "Adapter queue depth" is effectively the inverse of this statistic - it is a count of the number of transmits currently held by the adapter or queued by the server. "Free receive resources" This is a count of the number of receive resources currently available. This statistic often remains at its maximum value since the server will typically provide a new receive resource every time the adapter receives a frame. "Ring status - Ring recoveries (claim token)" "Ring status - Single station conditions" "Ring status - Counter overflows" "Ring status - Remove requests received" "Ring status - Auto removal errors" "Ring status - Lobe cable faults" "Ring status - Transmit beacon conditions" "Ring status - Soft errors" "Ring status - Hard errors (ring beaconing)" "Ring status - Signal loss errors" These are counts of the number of times each ring status condition has been reported by the adapter. "Adapter closed/re-opened count:" This is a count of the number of times the adapter has closed and successfully re-opened. "Mirror switch count:" This is a count of the number of Mirror switches which have occured. (10) Lost interrupt alerts -------------------------- On some NetWare Server machines it has been observed that lost hardware interrupt alerts are displayed when running CMDGODI.LAN. These alerts can be harmlessly disabled by adding the following line to your STARTUP.NCF file: SET DISPLAY LOST INTERRUPT ALERTS = OFF (11) Using Madge LLC/NetBIOS for Client 32 software --------------------------------------------------- The Madge LLC and NetBIOS for Client 32 protocols provides IEEE 802.2 (LLC) and NetBIOS protocol support in the Client 32 for DOS/Windows 3.x environment. Since the protocols conform to the ODI architecture, they can be used simultaneously with other protocols (IPX and/or TCP/IP for example) on the same adapter. The Madge LLC for Client 32 protocol provides the standard DOS interface which is used by many applications, such as 3270 emulation software. The Madge NetBIOS for Client32 protocol provides the standard DOS interface which is used by many applications, such as DOS LAN Services. Since the protocols use the Client 32 architecture, they are loaded into extended memory and thus gives significant memory savings over traditional DOS-based LLC and NetBIOS interfaces. For more information, see the documentation for the Madge LLC/NetBIOS for Client32 software. (12) Wake-On-LAN ---------------- Wake-On-LAN is a feature that allows a network adapter to wake-up a PC that has been put into auxillary power mode when the adapter receives a "Magic Packet" from the LAN. For this feature to work you must have a PC that supports Wake-On-LAN and a network adapter that supports Wake-On-LAN. The following adapters support Wake-On-LAN: o Madge Smart 16/4 PCI Ringnode Mk3 o Madge Smart 100/16/4 PCI-HS Ringnode o Madge Smart 100/16/4 PCI Ringnode o Madge Presto 2000 PCI o Olicom RapidFire 3540 HSTR 100/16/4 PCI Adapter o Olicom RapidFire 3139 Token-Ring 16/4 PCI Adapter o Olicom RapidFire 3140 V2 16/4 PCI Adapter o Olicom RapidFire 3140 Token-Ring 16/4 PCI Adapter o Olicom RapidFire 3141 Token-Ring 16/4 PCI Fiber Adapter CMDGODI.LAN does not support Wake-On-LAN on NetWare servers. To enable Wake-On-LAN mode, use the "WOL=YES" or WOL_PME=YES" driver parameter (see "Driver Parameters"). When Wake-On-LAN mode is enabled, CMDGODI.LAN will put the adapter into sleep mode when the driver is unloaded. Once the adapter is in sleep mode the PC may be switched off. The PC will be switched on by the adapter when it receives a "Magic Packet". Note that the adapter will only be put into sleep mode if the driver is properly unloaded. Simply switching off the PC will not suffice. Under DOS, type "UNLOAD CMDGODI" at the command line. Note that any NLMs loaded after CMDGODI (e.g IPX.NLM or CLIENT32.NLM) must be unloaded first. (13) Disabling promiscuous mode ------------------------------- Promiscuous mode is a special reception mode where an adapter will receive all frames on the ring, not just frames which the adapter address-matches. This functionality is used by network traffic monitoring agents. It is possible to permanently disable promiscuous mode on the following adapters: o Madge Smart 100/16/4 PCI Ringnode o Madge Smart 100/16/4 PCI-HS Ringnode o Madge Smart 100 Fiber PCI Ringnode o Madge Presto PCI 2000 o Madge Smart 16/4 PCI Ringnode Mk3 o Madge 16/4 CardBus Adapter Mk2 This is a security feature which can be used to prevent the use of network traffic monitoring agents on selected adapters. To permanently disable promiscuous mode, specify the "KILL_PM=YES" parameter on the CMDGODI command line. WARNING - This parameter should be used with care since once promiscuous mode is disabled it can never be re-enabled. If you wish to disable promiscuous mode in a non-permanent way, use Madge Assist to edit the configuration of your adapter (see ASSIST.TXT for details). (14) Adapter mirroring (failover) --------------------------------- Adapter mirroring is Madge feature which provides fault tolerance against network or adapter problems. Refer to MIRROR.TXT for more details. (15) Driver parameters ---------------------- The following are driver parameters which may be specified on the "LOAD CMDGODI" command line under DOS/NetWare server. "PORT=<n>" ---------- If the computer contains multiple adapters, use this parameter to select the adapter to use by its IO port. If the computer contains multiple adapters and this parameter (or the SLOT or BIA parameter) is not specified, the user will be prompted to enter a value. "SLOT=<n>" ---------- If the computer contains multiple adapters, use this parameter to select the Ringnode to use by its slot number. This is an alternative to the PORT or BIA parameters. The slot number is actually a 'Hardware Instance Number' (HIN) which Novell use to uniquely identify an adapter within the system. The HIN may or may not correspond obviously to a physical slot number, depending on the adapter/computer combination. "BIA=<n>" --------- If the computer contains multiple Madge Smart Ringnodes, use this parameter to select the Ringnode to use by its burned-in address (BIA). This is an alternative to the PORT or SLOT parameters. A burned in address is specified as a 12-digit hexadecimal value, e.g BIA=0000F6690012. "FRAME=<type>" -------------- Use this to specify the frame type (TOKEN-RING or TOKEN-RING_SNAP). "NODE=<n>" ---------- Use this to specify a locally administered node address override for the adapter. A node address override is specified as a 12-digit hexadecimal number in the range 400000000000 to 7FFFFFFFFFFF. If no override is supplied (the normal case), the adapter's unique burned-in address is used. "NAME=<n>" ---------- This parameter can be used in the NetWare operating system environment to set the name of a logical board. "XFER=<PIO16>" -------------- Use this to override the default adapter transfer mode to 16-bit PIO, where supported by the particular adapter. In general, the adapter's transfer mode should be configured using Assist. "RINGSPEED=<4|16|100>" ---------------------- Override the current adapter setting for ring speed (where possible). In general, the adapter's ringspeed should be configured using Assist. "WARN=<YES|NO|1|2>" ------------------- Use this to enable or disable reporting of abnormal ring status and adapter closing and re-opening. Critical condition messages (e.g. adapter check) cannot be disabled. The parameters to the WARN= option are: o YES - Turn on the maximum warning level. o NO - Turn off all warnings. o 1 - Display adapter closed/re-opened warnings. o 2 - Display adapter closed/re-opened warnings AND abnormal ring status warnings. The defaults for this parameter are: o Server - WARN=YES o Client - WARN=NO. "WATCHDOG=<n>" -------------- Use this parameter to override the default watchdog timeout period (in seconds) for Smart adapters. If the adapter doesn't hear from the host within the timeout period, the adapter will remove itself from the ring. A value of zero turns off the watchdog timer. "WOL=YES" "WOL_PME=YES" ------------- Use this parameter to cause the adapter to go into sleep mode when the driver is unloaded. When the adapter receives a "magic wake-up packet" it will turn the PC on. This functionality is only supported on adapters and PCs which support Wake-On-LAN. If the WOL parameter is used the adapter will signal wakeup on the WoL connector (fly lead attached to the motherboard) only, if the WOL_PME parameter is used the adapter will additionally signal wakeup using the PCI bus PME signal. "KILL_PM=YES" ------------- Use this parameter to PERMANENTLY disable promiscuous mode on any of the following adapters: o Madge Smart 100/16/4 PCI Ringnode o Madge Smart 100/16/4 PCI-HS Ringnode o Madge Presto PCI 2000 o Madge Smart 16/4 PCI Ringnode Mk3 o Madge 16/4 CardBus Adapter Mk2 WARNING - This parameter should be used with care since once promiscuous mode is disabled it can never be re-enabled. "TESTXID=<YES|NO>" ------------------ Use this parameter to control whether the adapter should respond to LLC TEST and XID frames. Some infrastructure devices expect token ring adapters to repond to these frames so this parameter should be set to YES (the default) unless you specifically don't want the adapter to do this. "DISPLAY" --------- Display details of adapters in the machine. "LOAD CMDGODI DISPLAY" can be used before or after CMDGODI.LAN is loaded onto any adapters. Adapters currently in use by CMDGODI.LAN are indicated. "HELP" ------ Display help screen. "MIRRORSLOT=<n>" "MIRRORPORT=<n>" "MIRRORBIA=<n>" "LOBE=<n>" "SINGLE=<n>" "BEACON=<n>" ---------------- These parameters are used to configure adapter mirroring for CMDGODI.LAN versions which support this feature. Refer to MIRROR.TXT for more information on adapter mirroring. **** End of CMDGODI.TXT ****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.