OS/2 version 2.x with NetWare
=============================                                        
                                               LSS 5.0(0), August 1996 
                                               -----------------------
Summary
-------

This  file  provides  information  about loading Madge drivers for OS2 
version 2.x with NetWare  support.

This file has the following sections: 
   1) OS/2 version 2.x and NetWare
   2) Driver Configuration
   3) OS/2 version 2.x and LAN Server 2.0 with NetWare
   4) PCMCIA Hotswapping and APM support with the OS/2 ODI driver.


1) OS/2 version 2.x and NetWare
-------------------------------
The MADGEODI.SYS driver conforms to the ODI specification  for  a  LAN 
driver.  

The  MADGEODI.SYS  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 in conjunction with the information in this file.  

To load the Madge driver, run the OS/2 Install program and  enter  the 
driver  name,  "MADGEODI.SYS"  in the driver name window, when you are 
prompted. The install program adds the driver to your CONFIG.SYS.
  
If  you wish to use source routing, then include the following line in 
your CONFIG.SYS file, (put it 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)


2) Driver Configuration
-----------------------

You can configure MADGEODI.SYS from  a  NET.CFG  file.   (If  you  are 
installing  more  than  one Ringnode, you must use a NET.CFG file.) If 
the file does not exist, or contains no valid driver information, then 
the driver uses the default configuration options. If  it  finds  more 
than one Ringnode, it returns an error.

List the options you require in your NET.CFG file (most of  which  are 
described  in  the  Novell Netware Requester for OS2 manual) following 
the driver's section header. This  is  "LINK  DRIVER  MADGEODI".   The 
options are as follows:

PORT address                The IO location of the Ringnode  you  want 
                            to  load  MADGEODI.SYS  onto (e.g.  PORT = 
                            1a20). Use the PORT option in AT and  EISA 
                            computers.  For details, see the Requester 
                            manual

SLOT slot_num               The  Bus SLOT  of the Ringnode you want to 
                            load  MADGEODI.SYS  onto.   Use  the  SLOT 
                            options  in  Micro-Channel computers.  For 
                            details,see the Requester manual.


BURNT IN ADDRESS nnnnnnnnnnnn  If there are multiple  Madge  Ringnodes 
                            installed in a machine, use this parameter 
                            to  specify  the BIA (node address) of the 
                            Ringnode to use. 

FRAME frame_type            The   type   of   frame   (token-ring   or 
                            token-ring_SNAP) that you want your driver 
                            to  use (Your driver can use more than one 
                            frame  type).   For   details,   see   the 
                            Requester manual.

PROTOCOL abc                A Protocol stack that you require (You can 
                            use  more than one).  For details, see the 
                            Requester manual.

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 Ringnode  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  Ringnode 
                            Abbreviation: (none)

                            Example : NODE ADDRESS 400012345678

MAX FRAME SIZE nnnn         The   Maximum   packet   size   (including 
                            protocol headers) that you want the driver 
                            to support.

MMIO                        Forces a PCI (non-bus master)  ringnode to 
                            operate in memory-mapped IO (MMIO) mode.

PIO                         Forces  the  driver to use PIO, regardless 
                            of the Ringnode's default transfer  method 
                            (DMA  or  MMIO).  It is recommended to use 
                            PIO on a workstation that  is  using  only 
                            one  protocol, especially if it is using a 
                            memory manager.

ALTIO                       This  parameter is only available with the 
                            "ASYNC"  bus  mode  on   Smart   16/4   AT 
                            Ringnodes.     If    your   computer   has 
                            bus-compatibility problems with AT or  ISA 
                            Client  Ringnodes, use the ALTIO parameter 
                            and configure your Ringnode  for  PIO  and 
                            alternate bus-timing.

FORCE16                     This will force the Ringnode to insert 
                            into the Token-Ring at 16 mbps.
                            
FORCE4                      This will force the Ringnode to insert 
                            into the Token-Ring at 4 mbps.
                            
ALTERNATE                   If you are using the Smart 16 Ringnode and 
                            your MADGEODI.SYS fails to load  with  the 
                            "Failed  Verifying  downloaded code" error 
                            message  try  using  this  parameter.   By 
                            default, this parameter is not set.


The  driver uses a maximum frame size that is the lesser of 4210 bytes 
or the size of the LSL buffers (default 1130). This can be  configured 
using  the  LSL  buffers  parameter  and  the  MADGEODI max frame size 
parameter as described below.

example NET.CFG file :-

         link support
            buffers 10 4210

         link driver MADGEODI
            port            a20
            max frame size  4210
            frame           token-ring
            frame           token-ring_snap

         link driver MADGEODI
            port            1a20
            max frame size  4210
            frame           token-ring
            frame           token-ring_snap

         netware requester
            preferred tree  PEACHTREE
            packet burst    off


3) OS/2 version 2.x and LAN Server 2.0 (and/or IBM Extended  Services) 
   with NetWare
----------------------------------------------------------------------
Novell provide support for OS/2  version  2.x  workstations  that  are 
running LAN Server version 2.0 and/or Extended Services in combination 
with  NetWare.   Read Novell's documentation for the NetWare Requester 
and install either the LANSUP.SYS driver, or the ODINSUP.SYS driver.

LANSUP.SYS
----------
Use this method if you are using IBM Extended Services.

1 Insert the NetWare Requester disk into your A: drive.
2 Type A:INSTALL [ENTER]

or  if the NetWare Requester is already installed on your workstation, 
select the NetWare Install icon from the Novell Icon View.


3 In the LAN adapter driver selection box, select LANSUP.SYS. (Earlier 
  versions of the  NetWare  Requester  called  this  TOKENEE.SYS,  and 
  CMGRLAN.SYS.)

4 Create  a  NET.CFG file using the NetWare Install utility.  Include 
  the following lines: 

link driver lansup 
 frame token-ring
 node address  <Node  Address>  

where  <Node  Address>  is  the address of your Ringnode.

ODINSUP.SYS
-----------

Use this method if you are not using IBM Extended Services.

1 Insert the NetWare Requester disk into your A: drive.
2 Type A:INSTALL 

or if the NetWare Requester is already installed on your  workstation, 
select the NetWare. Install icon from the Novell Icon View.

3 In  the  LAN  adapter  driver  selection  box, type the  path of the 
  MADGEODI.SYS driver on the Madge CD.  (For  the  location  of  the 
  files on your release disks, refer to the README file.)

4 When  the screen displays a message requesting you to insert a  disk 
  into the A: drive, specify the path to the driver on the CD. (You may 
  copy the driver from the CD onto a disk)

5 Edit your CONFIG.SYS file by commenting out the following line:

  DEVICE=C:\IBMCOM\MACS\MDGND.OS2

6 Locate the following lines in your CONFIG.SYS file:

  DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

  and:
  
  DEVICE=C:\NETWARE\LSL.SYS

After whichever of these two lines appears latest in the file, add the 
line:

DEVICE=C:\NETWARE\ODINSUP.SYS

7 Save the changes to your CONFIG.SYS file.

8 In your NET.CFG file, locate (or create, if it  doesn't  exist)  the 
  section  "link  driver  madgeodi". Ensure that this section contains 
  the following information:


link driver madgeodi
        frame token-ring
        frame token-ring_snap

9 In your NET.CFG file, locate (or create) the section  link  support. 
  Ensure that this section contains the following information:

  link support
    buffers 15 4210

  Also add the following section:

  protocol odinsup
    bind MADGE

10 Save the changes to your NET.CFG file.

11 Edit your PROTOCOL.INI file (usually in the C:\IBMCOM directory) by 
   replacing every instance of the line:

   bindings=MDGND_NIF

   to:

   bindings=MADGE

12 Add the following line to the end of the file:

   [MADGE]

     DriverName = MADGE

13 Save the changes to your PROTOCOL.INI file.

14 Shut down and reboot your system.


4) PCMCIA Hotswapping and APM support with the OS/2 ODI driver.
---------------------------------------------------------------

This  release  of  the  OS/2  ODI  driver  has support for PCMCIA hot- 
swapping and Power Management Suspend/Resume  events.  These  features 
are enabled by default with no extra configuration required.

The Hotswapping  feature  applies  to  the  Madge  Smart  16/4  PCMCIA 
Ringnodes.   The card may be removed (ejected) and replaced (inserted) 
without losing network connections.  To do this, either logout of  the 
network  or  go  to  a  DOS/OS/2 command prompt and remove all network 
drives from the  search  path;  then  eject  the  card.   A  different 
manufacturer's  PCMCIA  card  may then be inserted and used.  When the 
Madge card is re-inserted, it will be re-initialized (this  will  take 
approximately  five seconds).  Network resources can then once more be 
used.  The card can be re-inserted in any PCMCIA slot.  To  allow  one 
Madge  PCMCIA  card to be removed and a different Madge PCMCIA card to 
be inserted, a NODE ADDRESS option must be used when loading  MADGEODI 
so  that  both  cards will be able to access the network with the same 
node address.

If MADGEODI.SYS is loaded in  PCMCIA  machine  with  no  Madge  PCMCIA 
Ringnode  inserted,  the  driver  will  load  normally.  When a PCMCIA 
Ringnode is inserted it will be initialized for network use.  In  this 
case,  a NODE ADDRESS option must also be used so IPX.SYS will be able 
to determine the node address  of  the  ringnode  even  before  it  is 
inserted.

The Power Management option works in conjunction with APM.SYS.  When a 
machine is put into "suspend" mode the Ringnode will be  shutdown  and 
when the machine is "resumed" the card will be re-initialized.


                 ****** End of NWAREOS2.TXT ******