    HOW TO INSTALL THE REMOTE OFFICE CLIENT WITH NETWARE 2.2 AND HIGHER
    -------------------------------------------------------------------

  The batch file named "ROSTART.BAT" illustrates how to run the Remote office
  client with Novell's Netware product.

  Netware uses the ODI interface into Remote Office.  This interface
  may require modification to the net.cfg file located in the Remote
  Office directory.  By default, it will look similar to one of the
  following examples:

  If the host you are dialing into is on an ethernet lan:

     Link Driver ODIROF-E
        frame ETHERNET_802.3              {driver #1}
     ;   frame ETHERNET_802.2             {driver #2}
     ;   frame ETHERNET_II                {driver #3}
     Protocol IPX
        bind #1

  If the host you are dialing into is on a Token-Ring lan:

	Link Driver ODIROF-T
    	frame TOKEN-RING
	;   frame TOKEN-RING_SNAP

	Protocol IPX
    	bind #1


  The Remote Office install procedure creates a file called ROSTART.BAT
  in the Remote Office directory.  This BAT file may be used to load the
  Remote Office client.  If you wish, the modules loading in Rostart.bat
  can be folded into another BAT file.  The load sequence is as follows:

  Ethernet:                            Token-Ring:
  roffice                              roffice
  lsl                                  lsl
  odirof-e                             odirof-t
  ipxodi                               route
  ro {login} {host}                    ipxodi
  netx (or vlm)                          ro {login} {host}
  login                                netx  (or vlm)
                                       login

  For Token-Ring environments, ROUTE.COM must be loaded after ODIROF-T.

  The Remote Office login must occur before NETX (or VLM) is loaded.

