1. BENNOV.ZIP Driver
2. README.TXT File Contents

README.TXT Driver File Contents (BENNOV.ZIP)

FILES FOR DOS ODI WORKSTATIONS:
-----------------------------------------------------------------

NOTE: This README file is an explanation of the files contained in
this directory and their usage.  More detailed information can be
obtained about many of these files in either the "NetWare ODI Shell
for DOS" manual (comes with NetWare v3.11 documentation), the
"Novell ODI for DOS User's Guide.", or the "NetWare Workstation for
DOS" manual.


LSL.COM:

This file implements the Link Support Layer for DOS ODI
workstations and is the program generally loaded first when
booting.  It performs a switching function to route packets and
allow communication between the LAN drivers and the communication
protocol.  The LSL allows one network board to service several 
protocol stacks, or several network boards to service the same
protocol stack.  It also provides a buffer pool, packet queuing,
administrative services, and timer functions.


IPXODI.COM:

This is Novell's protocol stack for DOS ODI workstations. It
performs the same functions as IPX.COM does for DOS workstations. 
However it is optional and loaded after and separately from the LAN
driver. This is because other protocols can be loaded in place of,
or along with it.  This is one of the key features of the ODI
environment.

IPXODI.COM actually contains 3 protocols; IPX, SPX and Remote
Diagnostics Responder.  Normally all of these are loaded, but IPX
can be loaded by itself to save memory if the application doesn't
require all three.  The following chart shows how to load
IPXODI.COM without the other two parts of the file:

     TO LOAD              TYPE        MEMORY SAVED
     ------------------------------------------------------
     IPX and SPX only     IPXODI d       4KB
     IPX only             IPXODI a       8KB


NET.CFG:

NET.CFG is an optional, specialized text file that you create with
any ASCII text editor and include on the workstation boot diskette.
It is not generally needed if you are using the default hardware
options.  It will automatically be read and implemented if it is in
the same directory as the driver as you boot your workstation. Thus
it will have to be removed or renamed if you later choose not to
use it and want to boot using the default settings.


The NET.CFG is responsible for setup and configuration of a network
workstation.  Hardware options other than default must be set in
NET.CFG for DOS ODI workstations, and they can also be set here for
DOS IPX workstations.  Also if you are using protocols other than
IPX, or multiple frame types, you will need a NET.CFG to load
these.  You will also need it if you are using Novell's LAN
Workplace.  

NET.CFG overrides the SHELL.CFG file settings, and any options set
in the SHELL.CFG file can be specified in the more versatile
NET.CFG file.  It can change the operating parameters of the
NetWare shell or IPX.  You can use it to change the way the
workstation handles packets, print jobs, DOS versions, 
and search drives.  

Applications such as database, multitasking, or NetBIOS (involved
in peer-to-peer communications or distributed processing) may
require parameter values different from the default values to
properly function on the network.  To find out which parameters you
might need to modify, consult the setup reference for each
application used on your network.  

There are many other NET.CFG options available that are listed in
the "ODI for DOS User's Guide", or the NetWare v3.11 "ODI Shell for
DOS" manual.  These manuals also describe the format and headings
used in creating a NET.CFG file.


AUTOEXEC.BAT:

This is an example of a file that will load your driver and the
other files necessary to bring up your DOS ODI workstation.  It
should be on your workstation boot diskette or hard disk along with
the LAN driver for your adapter, NETX, IPXODI, LSL, and any other
files you wish to load when booting.  This AUTOEXEC file should
work fine for most situations, but you can modify it as necessary
to fit your application.


NETX.COM:

The NetWare shell, NETX, is a TSR that is loaded after the driver
and protocol stack, and enables you to login to the network file
server.  It functionally lies on top of the workstation operating
system, and between the application layer and DOS.  It handles
requests made by the application, and determines whether to pass
them to DOS or the NetWare operating system to be serviced.






EMSNETX.EXE:

It is the NetWare Expanded Memory Shell and it can be run with DOS
ODI workstation drivers.  It loads in place of the NETX shell after
the LAN driver and an EMS-compatible memory manager. See the
documentation for your memory manager for installation
instructions.  All the shell configuration (NET.CFG) parameters
work with the Expanded Memory Shell.


XMSNETX.EXE:

It is the NetWare Extended Memory Shell and it can be run with DOS
ODI workstation drivers.  It loads in place of the NETX shell after
the LAN driver and an XMS third party memory manager you may be
using.  See the documentation for your memory manager for
installation instructions.  All the shell configuration (NET.CFG)
parameters work with the Extended Memory Shell.


DOS ODI UNLOADING:

Unlike DOS/IPX workstation drivers, you can unload DOS ODI files
and drivers without rebooting the workstation.  You may find this
particularly useful if you need to load a different shell in place
of NETX.COM.  The files must be unloaded in reverse of the order
they were loaded.  For example:

     NETX u <enter>
     IPXODI u <enter>
     NE2100 u <enter>
     LSL u <enter>

You may also want to try typing an 'i' in place of the 'u' as
above, which will display useful information on each of these
files.



The following is additional information about EMSNETX.EXE and
XMSNETX.EXE.


EMSNETX.EXE:

This file is the NetWare Expanded Memory shell.  It can be loaded
in place of the NETX shell after the LAN driver and an
EMS-compatible memory manager are loaded.

Expanded memory refers to memory in addition to the 640KB limit of 
conventional memory.  An expanded memory manager swaps memory that
exists between the 640KB and the 1MB range into a window, or memory
page.  This allows DOS applications to access up to 32KB of
expanded memory.    

The NetWare Expanded Memory shell moves most of the shell out 
of conventional DOS memory and puts it in expanded memory.  This
frees up 33KB of memory.  The remaining 7KB of the shell must 
remain in conventional memory to handle interrupts and some data. 
  

The NetWare Expanded Memory shell was written to the specifications
of LIM/EMS (Lotus/Intel/Microsoft Expanded Memory Specification) 
v4.0 memory manager.                        

Expanded memory manufacturers provide Expanded Memory Specification
(EMS)-compatible driver programs.  You must load an EMS-compatible 
driver before loading the NetWare Expanded Memory shell.  

To install the NetWare Expanded Memory shell, you need to  

*     Load a third-party EMS-compatible driver;  
*     Copy the NetWare Expanded Memory shell file, EMSNETX.EXE, 
      to the workstation boot diskette;   
*     Include the filename EMSNETX.EXE in the AUTOEXEC.BAT file 

Because the Expanded Memory Shell operates in expanded memory, 
larger applications can run in the conventional memory space.  
This approach is faster than disk swapping and overlays.The NetWare

Expanded Memory shell works with NetWare v2.1 and above.  

All the shell configuration (NET.CFG) parameters work with the 
NetWare Expanded Memory shell. EMSNETX.EXE can only be used with
DOS 3.0 and above.  The expanded memory shell is not designed to
work on a machine running non-dedicated NetWare.    


XMSNETX.EXE:

This file is the NetWare Extended Memory shell.  It can be loaded
in place of the NETX shell after the LAN driver and an
XMS-compatible memory manager are loaded.  Extended memory refers
to memory above the 1MB range.  Up to 15MB of extended memory is
addressable.    

The NetWare Extended Memory shell moves most of the shell out of 
conventional DOS memory and puts it in extended memory.  This frees
up 34KB of conventional memory.  640KB of the extended memory shell
must remain in conventional memory to handle interrupts and some
data.     

The extended memory shell requires the support of an XMS (Extended
Memory Specification) v2.0 memory manager (or compatible), such as
Microsoft's HIMEM.SYS.  The memory manager makes the first 64KB
(beginning at the 1MB address) of extended memory directly
available to DOS-based applications.     
                        

To install the NetWare Extended Memory shell, you need to  

*    Install a third-party extended memory manager;    
*    Copy the NetWare Extended Memory shell file, XMSNETX.EXE, to 
     the workstation boot disk;  
*    Include the filename XMSNETX.EXE in the AUTOEXEC.BAT file 

Because the Extended Memory shell operates in extended memory,
larger applications can run in the conventional memory space.  This
approach is faster than disk swapping and overlays.  The NetWare
Extended Memory shell works with all versions of NetWare v2.1x and
above.                     

All the shell configuration (NET.CFG) parameters work with the
NetWare Extended Memory shell. XMSNETX.EXE can be used only with
DOS 3.0 and above.  The current VDISK.SYS from IBM is not
compatible with HIMEM.SYS, so do not use the extended memory shell
with VDISK.SYS.  Do not use the extended memory shell on a machine 
running non-dedicated NetWare.    

This shell requires a high degree of IBM compatibility.  Depending
on the brand of IBM compatible you are using, you may experience
keyboard sluggishness or other hardware problems.