This page provides information about:
The MADGEODI driver can be configured from a NET.CFG file. List the options required after the driver's section header which is "LINK DRIVER MADGEODI". If using multiple adapters, remember to include one "LINK DRIVER MADGEODI" section in NET.CFG for each instance of the driver. If not using a NET.CFG file or if no PORT is specified, the driver loads onto the first available adapter. If the driver is loaded a second time, the second LINK DRIVER MADGEODI section must have a PORT parameter.
The parameters that can be specified in the NET.CFG file are:
PORT nnnn
If there are multiple Madge adapters installed in a machine, use this parameter to specify the I/O location of the adapter to use.
FRAME abc
The frame type required. The only valid choices are "TOKEN-RING" (normally used with IPXODI.COM) and "TOKEN-RING_SNAP" (normally used with TCPIP.EXE).
PROTOCOL abc
A Protocol stack that you require (may be entered more than once).
MAX FRAME SIZE n
The Maximum packet size to be supported including protocol and hardware headers (4210 represents a maximum data size of 4Kbytes). The minimum frame size you can specify is 632 (1/2Kbytes). The maximum frame size you can specify is 18000. This frame size should only be used in configurations required to monitor network frames (e.g. Novell's LANalyzer).
PIO
Forces the driver to use PIO, regardless of the adapter's default transfer method. It is recommended to use PIO on a workstation that is using only one protocol, especially if it is using a memory manager.
NODE ADDRESS nnnnnnnnnnnn
The node address parameter allows you to specify the 6-byte node address to be used by the adapter. If you omit this parameter, the adapter uses its unique burnt-in node address. We recommend the burnt-in address whenever possible.
You can use any valid hexadecimal number in the range 400000000000 to 7FFFFFFFFFFF.
Ensure that every adapter in your network has a different node address.
Range : 400000000000 - 7FFFFFFFFFFF Default : burnt-in address of adapter
Abbreviation: (none)
Example : NODE ADDRESS 400012345678
ADAPTER WATCHDOG TIMEOUT nn
Changes the period that the adapter waits before timing out (that is, before shutting itself down). The default is 8 seconds. Increase this if you are using applications that disable system interrupts for long periods. If you do not give a timeout value the Watchdog timer is disabled.
FORCE100
This will force the adapter to use 100 Mbit/s. If the adapter does not support 100 Mbit/s, then this parameter is ignored.
FORCE16
This will force the adapter to use 16 Mbit/s.
FORCE4
This will force the adapter to use 4 Mbit/s.
DTR
This forces the adapter to connect to a DTR-enabled switch port using full duplex (Dedicated) token ring. This is not usually required and is the default behaviour for most switch ports.
CLASSIC
This forces the adapter to connect to a DTR-enabled switch port using standard (Classic) token ring. This is only required when a non full-duplex connection to a switch port is required.
The driver also supports the following command-line switches:
MADGEODI : Loads the driver into memory.
MADGEODI PIO: Forces the driver to use PIO if possible.
MADGEODI U : Unloads the driver from memory if possible.
MADGEODI S : Displays details of MADGEODI drivers currently loaded.
MADGEODI I : Displays version information.
MADGEODI ? : Displays a list of command-line switches.
MADGEODI H : Displays a sample NET.CFG file.
Some older versions of EMM386 do not fully emulate all of the 80386 I/O instructions used by MADGEODI. If MADGEODI detects such a version of EMM386, it will display an error message, and refuse to load.
If you are using MSDOS, the earliest version of EMM386 that MADGEODI can operate safely with is that supplied with MSDOS 6.22. It is version 4.48 of EMM386. Please note that some earlier versions of MSDOS were supplied with a version of EMM386 also called version 4.48, which is not suitable for use with MADGEODI.
The DOS ODI driver can be put into a mode where it receives every frame on the ring and not just those directed to it or broadcast. This mode is known as "Promiscuous mode". The DOS ODI driver will not operate in promiscuous mode unless an application (such as a network analysis tool) requests promiscuous reception of frames. For promiscuous mode operation to work, the adapter must support promiscuous mode and it must not be disabled at the adapter. Promiscuous mode can be permanently disabled on some adapters - see Limiting Frame Reception - Disabling Promiscuous Mode for details.
This release of the driver conforms to ODI spec 4.0. This version of the specification is different to previous versions in the manner that promiscuously received frames are passed to an analyzer application. In previous versions of the specification, the application registered a "receive monitor" function with the driver. The driver would call this function to notify the application of all packets received. In DOS ODI specification version 4.0 there is no receive monitor function. The analyzer application receives frames by registering with the Link Support Layer (LSL.COM) as a pre-scan protocol stack. When the driver receives a frame and presents it to the LSL, the LSL will first pass the frame to the application and then try to pass it to a registered protocol stack.
As a result of this change in the specification, some older analyzer applications will not work. For example, Novell supply a program called TKENH.COM with Lanalyzer for Windows. This program enhances the performance of LZFW on Token-Ring by intercepting promiscuously received packets passed to the LSL and immediately flagging them as unwanted frames. This allows the driver to quickly pass these frames to the receive monitor. With ODI Spec 4.0 drivers, TKENH.COM should not be used as packets need to be processed by the LSL.
When using Promiscuous mode applications, ALWAYS add the following lines to the LINK DRIVER MADGEODI section of NET.CFG:
FRAME TOKEN-RING
FRAME TOKEN-RING_SNAP
Also, to ensure all frames on the network are received, set the MAX FRAME SIZE to the highest possible value.
See Also: