Installing NetWare using MADGEODI for DOS

TechNote

Number:06701-04
Date:November 1994

Installing NetWare using MADGEODI for DOS

This document describes how to provide support for NetWare workstations using the Madge host-resident ODI driver. The information is also to be found is Appendix A of the Smart LAN Support Software Installation Guide version 4.0.

1 The host-resident ODI driver

The Madge host-resident ODI driver for NetWare workstations running DOS is called MADGEODI.COM. It supports all Madge Smart 16/4 Ringnodes. A firmware file called MDGDOS??.BIN is also required (?? is the current version number of the Binary file which is available from the BBS). The Binary file must be stored in the same directory as MADGEODI.COM.

Note

If you are using the Smart 16/4 MC32 Ringnode in a NetWare workstation, we recommend that, instead of using SMART.EXE with the IPX module, you use the MADGEODI driver with Novell's IPXODI.COM. This is because of the Smart 16/4 MC32 Ringnode's hardware architecture.

In conjuction with this chapter you should refer to the NetWare ODI Shell for DOS manual. To load the MADGEODI driver, edit your AUTOEXEC.BAT file by adding the following line after the LSL line:

MADGEODI

The following is a sample setup:

LSL
MADGEODI
IPXODI
NETX

Novell supplies the LSL, IPXODI, and NETX files.

Note

Keep MADGEODI.COM and MDGDOS??.BIN in the same directory on your boot disk.

2 Alternative frame types: SNAP headers

You can configure MADGEODI to support the following:

Standard token-ring frames.
Frames containing an additional SNAP header, which are used with certain protocols such as AppleTalk and TCP/IP.
Both of the above together

In its default state, MADGEODI works with standard token-ring frames. To use frames with SNAP headers, or to use standard frames and frames with SNAP headers together, edit NET.CFG to include TOKEN-RING_SNAP for the frame type, as explained in the NetWare ODI Shell for DOS manual.

3 Source routing

Novell provides a file called ROUTE.COM that provides source-routing support for DOS ODI. If your driver has more than one frame type, these frame types appear as different boards to ODI. If you are only using one frame type, add the following lines to your AUTOEXEC.BAT file before the IPXODI line:

MADGEODI
ROUTE

For more than one frame type, add the following lines as appropriate to the number you require:

MADGEODI
ROUTE BOARD = 1
ROUTE BOARD = 2

4 Multiple Ringnodes

To make MADGEODI support multiple Ringnodes installed in the same workstation, edit NET.CFG. To edit NET.CFG, follow the instructions in the NetWare ODI Shell for DOS manual.

5 Configuring MADGEODI

Configure the MADGEODI driver from the NET.CFG file. Include the parameters you require after the driver's section heading, which is:

link driver madgeodi

PORT nn          The IO location of the required adapter card.

SLOT nn          The physical location of the required adapter card
                 in your MC or EISA computer

FRAME abc        A frame type that you require (you may enter this 
                 more than once)

PROTOCOL abc     A protocol stack that you require (you may enter
                 this more than once)

MAX FRAME SIZE   The maximum packet size to be supported,
nnnn             including protocol and hardware headers, 4216
                 represents a maximum data size of 4 kbytes. The
                 minimum frame size is 623 (512 bytes). nnnn is 
                 specified in bytes.

RECEIVE BUFFER   The size of the internal receive buffer.  Make this
SIZE nnn         at least twice the size of the maximum frame size
                 and no greater than 30 kbytes. This changes the
                 driver's run-time memory usage and may affect 
                 performance slightly. nnn is specified in bytes.

TRANSMIT         The size of the internal transmit buffer. This has
BUFFER SIZE nnn  the same limitations and purpose as the receive 
                 buffer. nnn is specified in bytes.

Table 1 Parameters for the MADGEODI driver.

MADGEODI         Loads the the driver into memory.

MADGEODI U       Unloads the driver from memory.

MADGEODI I       Displays version information.

MADGEODI ?       Displays a list of command-line switches.

MADGEODI H       Displays the current driver configuration and a 
                 sample NET.CFG file.

MADGEODI C       Pre-configures the MADGEODI.COM file. The
                 NET.CFG file is read and the "burnt-in" settings
                 for maximum frame size, receive buffer size, and
                 transmit buffer size are changed to those in the
                 NET.CFG file.  This means that a NET.CFG file is
                 not necessarily needed on every workstation.

MADGEODI D       Re-configures the MADGEODI.COM file to its
                 initial (default) state.

Table 2 Command-line switches for the MADGEODI driver.