NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  Updated I2O Driver Kit for 4.11
TID #:  2949297
README FOR:  i2odrv4.exe

SUPERSEDES:
i2odrv3.exe

NOVELL PRODUCTS and VERSIONS:
NetWare 4.11

ABSTRACT:

I2ODRV4.EXE contains the latest updated I2O driver files, it supersedes
I2ODRV3.EXE. The file contains a fix for a conflict between Backup Exec and I2O
using a call to MemFree which would prevent one or the other from loading as
well as other performance/stability enhancements. This file is intended for
NetWare 4.11 however the files may be used on NetWare 5 as well. The
installation script will only work on NetWare 4.11.



-----------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO 
NOVELL.  NOVELL MAKES ALL REASONABLE EFFORTS TO VERIFY THIS 
INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT 
IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED 
CLAIMS TO THE VALIDITY OF THIS INFORMATION.
-----------------------------------------------------------------


INSTALLATION INSTRUCTIONS:

Note: If you previously installed I2ODRV1.exe, you will need to remove
BKSTROSM.NLM and SCSIOSM.NLM from the startup subdirectory, and from your
startup.ncf file.  The name of these files has changed to have a *.HAM file
extension.
1 - Always make a backup copy of each of these NLMs you are currently running,
refer to readme for preinstallation instructions.
2 - Insert the floppy into the A: drive and at the Netware Console
Prompt, type "load install".  Press Enter.
3 - Select "Product Options" from the "Installation Options" menu.
4 - Select "Install a product not listed"from the "Other Installation
Actions" menu.
5 - You will be prompted for a source.  Accept the default, A:.  Due to
a limitation of the installation scripting language, installation must
take place from the A: drive.  If, for any reason, you cannot install
from the A: drive, see Item 6.1 in the readme document, Trouble
Shooting--Installing from Alternate Sources.

6 - Select Components.  Use the Up and Down Arrow Keys and the Space Bar to
select the package components appropriate to your installation.  You may return
to this point at any time to add new components to your I2O support.  It is not
possible to automatically remove components at this time.  Component 1 provides
the basic IOP drivers.  Components 2 and 3 provide local disk and other I/O
support.  These components will be installed in your startup directory (with
SERVER.EXE & STARTUP.NCF).
Components 4 through 6 provide LAN support.  They will be installed in
SYS:\SYSTEM.
7 - Intelligent I/O Processor Interface, Primary files.  This
component is required in all installations.  No other component will be
installed until this one is.
8 - Intelligent I/O Processor Block Storage Class OS Specific
Module (OSM).  This component provides support for all devices
registered with the IOP as Block Storage Class devices.  This is the
preferred OSM for handling disk I/O.
9 - Intelligent I/O Processor SCSI Class OS Specific Module.  This
component provides support for all SCSI class devices not claimed by
Block Storage.  Unlike Block Storage, this OSM behaves like a SCSI Host Adapter
Module (SCSI HAM), and will therefore require appropriate Custom Device Modules
(CDMs) for each device.  Ordinarily the appropriate CDMs will be already
installed with Netware, and will load automatically.
10 - Intelligent I/O Processor Ethernet Class OSM.  This component
supports all devices registered with the IOP as Ethernet Class devices.
11 - Intelligent I/O Processor FDDI Class OSM.  This component
supports all devices registered with the IOP as FDDI Class devices.
12 - Intelligent I/O Processor Token Ring Class OSM.  This component
supports all devices registered with the IOP as Token Ring Class
devices.
13 - Press F10 to accept the marked groups.  Installation will begin.
Depending on your selections you will be prompted for 1 or 2
destinations.  Unless you have special reason for doing otherwise, you
should accept the default locations.
14 - If you select an alternate destination for the components
defaulting to your startup directory, you will have to edit STARTUP.NCF
to provide the correct path to these components. Note that it cannot be
guaranteed that any NetWare volumes will be accessible when these
components load.
15 - If you select an alternate destination for the LAN components
(defaulting to SYS:\SYSTEM), it will be necessary to remember and use this path
while configuring your LAN OSMs.
16 - Primary Installation is complete.  Restart the server (Netware only,
rebooting the system is generally not necessary) to initiate I2O
processing.  You may then configure and mount any I2O volumes, and
configure and start any I2O LAN devices, using the standard Netware
tools (Install, etc.).
See Readme.TXT for more details.

ISSUE: 

README.TXT file for version 1.01 Novell Intelligent I/O (I2O) Support for
Novell Netware 4.11.

Contents:

1	Licence Information
2	Hardware Requirements
3	Software/Firmware Requirements
4	Preparing to Install
5	Installation
6	Trouble Shooting
7	Support

________________________________________________________________________
1	Licence Information

1.1	This package is distributed solely for use on Novell Netware Operating
Systems.  Except as noted, it is subject to all the terms and
conditions of your existing Netware Licence.  No separate Licence is
required to use this package, and there is no charge for it.

________________________________________________________________________
2	Hardware Requirements

2.1	Any system capable of running Netware 4.11 or greater.

2.2 One or more I/O Processors (IOPs) conforming to the I2O Special
Interest Group's (I2O SIG's) specification, version 1.5.  These may be
General Purpose IOPs mounted on the motherboard, or installed in any PCI
slot, or Dedicated IOPs with their own embedded devices.

2.3	One or more devices controlled by an IOP.  These will usually be on
a secondary PCI bus also controlled by the IOP.

________________________________________________________________________
3	Software/Firmware Requirements

3.1	Netware 4.11 with Service Pack 5 or later.  The latest support pack
can be downloaded at http://support.novell.com/misc/patlst.htm#nw411.

3.2	The IOP must be configured to support the devices it is to control.
In the  case of dedicated IOPs this will generally be taken care of by
the device's manufacturer.  In the case of general purpose IOPs, you or
the system reseller will need to obtain Hardware Specific Modules
(HSMs) for each device to be controlled, and download them to the IOP
using a utility provided by the IOP manufacturer.  Follow the
manufacturer's instructions.  This may be done at any time.  For the
purposes of testing new HSMs, and other IOP Modules, it may be desirable
to have Netware I2O support already installed.

3.3	System BIOS conforms to PCI BIOS specification, version 2.1

________________________________________________________________________
4	Preparing to Install

4.1	Items needed.

4.1.1	A blank formatted diskette compatible with your server's A:
drive.

4.1.2	A Windows 95 or other client with a Web Browser to download and
unpack the installation package.


4.2	Obtaining the package.

4.2.1	Insert the blank diskette into the A: drive (or B: if
necessary).

4.2.2	Start your browser and go to http://support.novell.com/

4.2.2	Go to the knowledgebase or file finder and search for I2ODRV2.EXE, 
follow the directions on screen to download the compressed
executable to any convenient local directory.

4.2.3	Open an Explorer or My Computer window on the directory and
double click the I2ODRV2.EXE icon.  By default, the package will
be unpacked onto the A: drive.  You may choose another destination if
you so desire.


4.3	When the package is copied to the floppy, you are ready to begin
installation.

4.4 If you previously installed I2ODRV1.exe, you will need to remove 
    BKSTROSM.NLM and SCSIOSM.NLM from the startup subdirectory, and from
	your startup.ncf file.  The name of these files has changed to have
	a *.HAM file extension.  
________________________________________________________________________
5	Installation

5.1	Insert the floppy into the A: drive and at the Netware Console
Prompt, type "load install".  Press Enter.

5.2	Select "Product Options" from the "Installation Options" menu.

5.3	Select "Install a product not listed"from the "Other Installation
Actions" menu.

5.4	You will be prompted for a source.  Accept the default, A:.  Due to
a limitation of the installation scripting language, installation must
take place from the A: drive.  If, for any reason, you cannot install
from the A: drive, see Item 6.1, Trouble Shooting--Installing from
Alternate Sources.

5.5	Select Components.  Use the Up and Down Arrow Keys and the Space Bar
to select the package components appropriate to your installation.  You
may return to this point at any time to add new components to your I2O
support.  It is not possible to automatically remove components at this
time.  Component 1 provides the basic IOP drivers.  Components 2 and 3
provide local disk and other I/O support.  These components will be
installed in your startup directory (with SERVER.EXE & STARTUP.NCF).
Components 4 through 6 provide LAN support.  They will be installed in
SYS:\SYSTEM.

5.5.1	Intelligent I/O Processor Interface, Primary files.  This
component is required in all installations.  No other component will be
installed until this one is.

5.5.2	Intelligent I/O Processor Block Storage Class OS Specific
Module (OSM).  This component provides support for all devices
registered with the IOP as Block Storage Class devices.  This is the
preferred OSM for handling disk I/O.

5.5.3	Intelligent I/O Processor SCSI Class OS Specific Module.  This
component provides support for all SCSI class devices not claimed by
Block Storage.  Unlike Block Storage, this OSM behaves like a SCSI Host
Adapter Module (SCSI HAM), and will therefore require appropriate Custom
Device Modules (CDMs) for each device.  Ordinarily the appropriate CDMs
will be already installed with Netware, and will load automatically.

5.5.4	Intelligent I/O Processor Ethernet Class OSM.  This component
supports all devices registered with the IOP as Ethernet Class devices.

5.5.5	Intelligent I/O Processor FDDI Class OSM.  This component
supports all devices registered with the IOP as FDDI Class devices.

5.5.6	Intelligent I/O Processor Token Ring Class OSM.  This component
supports all devices registered with the IOP as Token Ring Class
devices.

5.6	Press F10 to accept the marked groups.  Installation will begin.
Depending on your selections you will be prompted for 1 or 2
destinations.  Unless you have special reason for doing otherwise, you
should accept the default locations.

5.6.1	If you select an alternate destination for the components
defaulting to your startup directory, you will have to edit STARTUP.NCF
to provide the correct path to these components. Note that it cannot be
guaranteed that any NetWare volumes will be accessible when these
components load.

5.6.2	If you select an alternate destination for the LAN components
(defaulting to SYS:\SYSTEM), it will be necessary to remember and use
this path while configuring your LAN OSMs.

5.7	Primary Installation is complete.  Restart the server (Netware only,
rebooting the system is generally not necessary) to initiate I2O
processing.  You may then configure and mount any I2O volumes, and
configure and start any I2O LAN devices, using the standard Netware
tools (Install, etc.).

________________________________________________________________________
6	Trouble Shooting

6.1	Installing from Alternate Sources.  The installation script contains
one unavoidable non-relative file reference.  If you must install from
a location other than A:, do the following:

6.1.1	Unpack or copy the installation files and directories to their
destination.

6.1.2	With any text editor edit the file I2O.IPS found at the root
level of the installation set.

6.1.3	Find the following line:
		Command "A:\\Tools\\ICMD"	;Use our version of ICMD extensions.

6.1.4	Change 'A:' to whatever path the server will use to access the
installation.  Use double backslashes wherever a single backslash occurs
in the path (e.g. Command "G:\\I2O_Inst\\Tools\\ICMD"	...).

6.1.5	Save the altered script, and proceed with installation.

6.2	I2OPCI reports IOP(s) present, but does not report "Ready to Load
OSMs".  This has been seen in a few hardware configurations where the
system BIOS is not correctly routing the IOPs interrupts.  Try the
following:

6.2.1	Edit STARTUP.NCF in your boot directory.  Add "-P" to the I2OPCI
load line.  This will cause I2OPCI to run in polled mode.  Polled mode
is not significantly slower than interrupt mode, and in some cases may
actually be faster.

6.2.2	Restart the server.  If the problem goes away, you may operate
in this mode indefinitely.  Contact your system vendor for an updated
BIOS.

6.3	I2OPCI does not report an IOP that you know is present.  This
usually means that the IOP is not configured correctly.  Use your vendor
supplied configuration utility to check the IOP's configuration.

6.4	A Native (non-I2O) driver is competing with an OSM for a device.
Devices controlled by an IOP should generally be hidden from the system
(a matter of configuring the PCI bridge that is a component of an IOP
subsystem).  Most IOP setup utilities do this automatically.  A few do
not.  Use your IOP vendor supplied utility to hide all devices
controlled through an IOP.	  

6.4.1	In the case of LAN devices, if they cannot be hidden, the
conflict can be resolved by editing AUTOEXEC.NCF, and deleting the lines
loading and binding the competing driver.  In the case of SCSI
devices, editing STARTUP.NCF is usually not helpful, because Netware
will still detect the device and attempt to load an appropriate driver.

6.5	An OSM does not report a device it should be controlling.  This is
usually an IOP configuration error.  Use your IOP vendor supplied
utility to check the following:

6.5.1	The appropriate HDM is loaded.

6.5.2	The device is assigned to the IOP, and is marked as
"Controlled", and "Hidden".

6.5.3	Some HDMs and devices (such as RAID's) may require a special
configuration dialog before they will operate.  Make sure this is done.


________________________________________________________________________
7	Support

7.1 Contact Novell Technical support or http://support.novell.com for further 
information.




Self-Extracting File Name: i2odrv4.exe

Files Included            Size          Date            Time
..\
     I2ODRV4.TXT   (This file)  
         I2O.IPS         18785     8-14-1998      4:29:08 am
..\STARTUP\
    BKSTROSM.HAM         18441     3-17-1999      7:43:10 am
      I2OPCI.DDI          2462    11-23-1998      7:48:42 am
      I2OPCI.NLM         11622      3-5-1999     10:44:08 am
        IOPX.NLM        125950     3-17-1999      7:25:24 am
       MPS14.PSM            23     4-27-1998      9:01:00 am
         NBI.NLM         28094     3-11-1998      6:54:26 pm
        NWPA.NLM         93851     7-31-1998      5:54:42 am
     SCSIOSM.HAM         16076      3-5-1999     11:02:02 am
..\SYSTEM\
    ETHEROSM.LAN         24374     3-15-1999      3:57:04 am
    ETHEROSM.LDI          7918     2-19-1999     10:45:54 am
    ETHERTSM.NLM         12005     4-30-1998      9:23:06 am
     FDDIOSM.LAN         25228     3-15-1999      3:58:42 am
     FDDIOSM.LDI          7688     2-19-1999     10:48:02 am
     FDDITSM.NLM         12301     4-30-1998      9:26:56 am
    FIBRETSM.NLM         11199     7-22-1997     11:04:00 am
         MSM.NLM         76720      6-9-1998      5:06:58 am
    TOKENOSM.LAN         24484     3-15-1999      3:40:22 am
    TOKENOSM.LDI          7887     2-19-1999     10:40:38 am
    TOKENTSM.NLM         12235     4-30-1998      9:34:14 am
..\TOOLS\
        ICMD.MSG          6298    12-17-1997      3:44:08 am
        ICMD.NLM         22251    12-17-1997      3:44:30 am
     STARTUP.BKS            19     8-14-1998      4:41:02 am
     STARTUP.PRM            30      4-6-1998      8:31:28 am
     STARTUP.SCS            18     8-14-1998      4:41:06 am



-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their respective
owners.  Consult your product manuals for complete trademark information.
-----------------------------------------------------------------

