Using the Madge OS2 ODI Driver ============================== MARCH 1993 The Madge OS/2 ODI driver (MADGEODI.SYS) conforms to the ODI specification for a LAN driver. The Madge OS/2 ODI driver consists of a single OS2 file: MADGEODI.SYS, which must be loaded as an OS2 device in the CONFIG.SYS file. To install the driver follow the instructions in the NetWare OS/2 Requester manual. To load the Madge driver enter the driver name, "MADGEODI.SYS" in the driver name window when prompted. The install program will add the driver to your CONFIG.SYS. If you wish to use source routing then you will need to include the following line in CONFIG.SYS after the MADGEODI.SYS line and before the IPX.SYS line.: device=c:\NETWARE\route.sys A typical CONFIG.SYS is: DEVICE=C:\NETWARE\LSL.SYS (supplied by Novell) DEVICE=C:\NETWARE\MADGEODI.SYS (Madge OS2 ODI Driver) DEVICE=C:\NETWARE\ROUTE.SYS (supplied by Novell) DEVICE=C:\NETWARE\IPX.SYS (supplied by Novell) The driver uses a default maximum frame size of 4210 bytes (4Kbytes data), which may be reduced by the link support layer (which defaults to 1130 bytes). The default internal buffer sizes are 10Kbytes for both send and receive buffers. The default threshold frame size for using transmit descriptors is 256 bytes. The MADGEODI driver is configurable from a NET.CFG file. The configuration file is mandatory if more than one adapter card is installed. If the file does not exist, or contains no valid driver information then the defaults are used if one adapter is found, and an error is returned if more than one adapter is found. The options required (most of which are described in the Novell Netware Requester for OS2 manual) are listed following the driver's section header which is "LINK DRIVER MADGEODI". The recognized keywords, and their meaning are as follows: PORT address : The IO location of the required adapter card (e.g. PORT = 1a20). For details, see the Requester manual. SLOT slot_num : The IO SLOT of the required adapter card. For details,see the Requester manual. FRAME frame_type : A Frame type that is required (may be entered more than once). For details, see the Requester manual. PROTOCOL abc : A Protocol stack that is required (may be entered more than once). For details, see the Requester manual. MAX FRAME SIZE nnnn : The Maximum packet size to be supported including protocol headers. RECEIVE BUFFER SIZE nnnn [loc]:The size of the internal receive buffer to be used. It should be larger than max frame size and smaller than 64Kbytes. The buffer may be placed in high or low memory. Default is high (that is, greater than 1M). If you require DOS, we advise you not to use low memory. TRANSMIT BUFFER SIZE nnnn [loc] : Corresponds to receive buffer size. DESCRIPTOR THRESHOLD nnnn : This is the level at which descriptors are used for transmission. The default value is 10000 bytes, which should not need to be changed. It may be possible to improve the performance of single-card workstations by lowering this to 256 bytes but this has proved to be application dependent. Multi-card workstations should NOT attempt to change the threshold as the system will almost certainly hang. FUNCTIONAL ADDRESS nnnn : Sets a functional address for use by the driver. The address is in the hexadecimal form C000????????. If the parameter is given as NetWare (instead of a hexadecimal number). The NetWare functional address is C00000800000. example :- link driver MADGEODI port 1a20 receive buffer size 20000 transmit buffer size 20000 max frame size 4202 frame token-ring frame token-ring_snap functional address netware link driver MADGEODI port a20 receive buffer size 20000 low transmit buffer size 20000 high max frame size 1300 end of example.