*****************************************************************************

                              Array1000SA Family v3.1 

                                      and

                      Adaptec CI/O Management Software v3.2

                                 Readme File
                         
                                February 27, 1998

*****************************************************************************

This file contains the following:

WHAT IS IN Array1000SA FAMILY V3.1

NOTES ON ADAPTEC CI/O MANAGEMENT SOFTWARE V3.2

COMPATIBILITY NOTES FOR ADAPTEC Array1000SA FAMILY PRODUCTS

HARDWARE INSTALLATION NOTES FOR ARO-1130SA

Array1000SA TEST NOTE

Array1000SA UPGRADING NOTES

GENERIC ARRAY CONFIGURATION NOTES

GENERIC ARRAY OPERATIONAL NOTES

WINDOWS-SPECIFIC INSTALLATION & CONFIGURATION NOTES

NETWARE-SPECIFIC INSTALLATION NOTES

UNSUPPORTED FEATURES

KNOWN PROBLEMS

*****************************************************************************

WHAT IS IN ADAPTEC Array1000SA v3.1
===================================

Array1000SA product is a server release of Adaptec's raid product.
The current product supports AIC-7895B2 based systems running Windows NT 4.0, 
Netware 3.12 and Netware 4.1x.

The following features are included:

Support for raid levels 0, 1, 5 and 0/1 (0+1)
Support for INT13 Extensions and VDS
Flash wizard for automatic configuration of proper BIOS
AIC-7895 support
ARO-1130SA support
SAF-TE support



WHAT IS NEW IN Array1000SA FAMILY V3.1
=====================================

Bootable CD-ROM is now supported. The ARO-1130SA supports bootable 
SCSI CD-ROM devices attached to the SCSI channels.

SMART is now supported. (Please refer to installation guide.)

BBS is now supported.

Netware 4.11 now supported.

*****************************************************************************

NOTES ON ADAPTEC CI/O MANAGEMENT SOFTWARE V3.2
==============================================

READING README.TXT DURING CI/O SETUP
------------------------------------
Attempting to read this readme.txt file during CI/O setup may result in a 
delay of up to 3 minutes when exiting the notepad utility.  The setup 
utility will then continue with the setup process.  

USE OF LARGE FONTS
------------------
The use of large fonts is not supported on Windows 3.1, Windows/95 and 
Windows/NT versions of CI/O.

BLINKING CD-ROM LIGHTS
----------------------
CI/O Management Software does not support blinking of the drive light 
on CD-ROM drives.

DEVICE STATUS FIELD
-------------------
In the detailed information dialog for devices other than hard disks and 
CD-ROM drives, the status field is not provided.

USE OF TAB AND ARROW KEYS
-------------------------
The use of Tab and arrow keys to navigate the Configuration window is not 
supported.

DETECTION OF FAILED MEMBERS AND DEVICES
---------------------------------------
Array1000SA device failures are detected when I/O is sent to the device.
Devices attached to SCSI adapters, on the other hand, are tested by default every 3 minutes, or at user defined intervals.

TRUNCATED STRINGS
-----------------
CI/O truncates words that are too long to display in the space available.  
A tilde "~" symbol is inserted in the next-to-last available character space, and the last character of the string fills the last available character 
space.  For example, in a 12 character field, the string "Finance Array #3" 
becomes "Finance Ar~3".  The full text can be read by double-clicking on the object to display the Detailed Information dialog box.

CONFIGS.DAT
-----------
CI/O Management Software automatically creates the configuration file CONFIGS.DAT in the client directory. The file is used by networked clients to store a list of servers to which the client is connected.  If the CI/O software is uninstalled, this file must be manually deleted.

LOG SEVERITY ICON COLORS
------------------------
Highlighting the small severity icons at the beginning of each server 
log entry changes the color of the highlighted icon without changing
the severity level.

HOURGLASS ON TASK COMPLETION
----------------------------
When issuing certain commands, the cursor may still remain as an hourglass 
when the task has completed. To correct this, move the mouse.

CI/O VERSION DEPENDENCIES IN CONNECTING CLIENTS TO SERVERS
----------------------------------------------------------
CI/O v1.0 and v2.x are incompatible with the CI/O v3.x release. In order to use CI/O, upgrade the client to CI/O Management Software v3.2.  Thereafter, the 
following rules apply:

1. At a given server or client all the CI/O sub-components must be at the same 
   version level.
2. The CI/O client application will be capable of interacting with the CI/O 
   server application, if the client major version number is the same as 
   the server, and if the minor version number is equal or greater than that
   of the server.

Examples:
a. A client v2.00 will work with a server v2.00, because they have the same 
   major number.
b. A client v2.50 will work with a server v2.40, because the client minor 
   version number(.50) is greater than the server minor version number (.40).
c. A client v3.00 will not work with a server v2.60, because they have 
   different major numbers.  The client has a major version number of 3 and 
   the server has a major version number of 2.
d. A client v2.14 will work with a server v2.19, because the client minor 
   version number is less than the server version number but within the 
   tenths' digit.

DELETING SERVER ADDRESS
-----------------------
Attempting to delete a server's address from a networked client while the 
server is off-line, will result in a several-second retry period.  During 
this period, the client tries to reconnect to the server. After the retry 
fails, the server address is deleted.

RE-CONNECTING FROM A CLIENT AFTER LOSING CONNECTION TO A SERVER
---------------------------------------------------------------
For certain operations, the networked client will establish an open
connection with the server, and will maintain the connection until the
operation is finished.  The specific cases where this occurs are when the
following two conditions are met:

1) A Reconstruct, Verify, Initialize, or Test All Spares activity is running
   on the server, and

2) The user opens the Activity View or a Watch Box to view the progress of
   the activity.

These activities may take considerable time to complete, and on a busy 
network a connection may be lost.  It should be possible to determine 
whether this situation has occurred by viewing the contents of the Current 
Event Log.

If the above mentioned operations stop, make sure that there exists a good
network connection to the server by double clicking on the server icon. After
reopening the activity window, the progress bar should display the current 
status of the operation.

SYSTEM TIME CHANGE
------------------
Do not change the system time while CI/O is running.
To change the system time one must:
1. Stop all CI/O management components and RPC modules.
2. Change the system time.
3. Restart the CI/O management components and RPCs.

All scheduled activities should be deleted and rescheduled after changing 
the system time. Otherwise, scheduled activities may not run at the 
specified time.

ACTIVITIES SCHEDULED MULTIPLE TIMES
-----------------------------------
A given CI/O activity should not be scheduled more than once to run at a specific time.  Multiple events may otherwise be generated.

SCHEDULING ACTIVITIES FROM DIFFERENT TIMEZONES
----------------------------------------------
When scheduling an activity from a remote client for a server in a different time zone, the activity is scheduled at the server relative to the server's local time.  For example:

                       Client X                 Server Y

Time zone is            PST                      EST
Local Time             08:00 am                 11:00 am
Activity Scheduled for 07:00 pm for server Y
Activity Executed at   04:00 pm                 07:00 pm at Server Y


EVENT SORTING BY THE CLIENT SERVER LOG AND EVENT LOG
----------------------------------------------------
The client sorts events from different servers in different time zones 
after adjusting the timestamp for each event to the client's local time.  
That is, events are sorted correctly by absolute time of occurrence. When 
displayed, however, they are displayed in the client's local time.

PROBLEMS ACCESSING THE SERVER LOG FILE IOMGR.LOG
------------------------------------------------
In extremely rare circumstances, entries in the Server Log file "iomgr.log" 
may become unreadable. This occurs when the file format is no longer as 
expected, perhaps due to client and server software revisions being out of 
sync. Should this happen, the situation will be automatically detected 
and the existing file will be renamed to "iomgrlog.old".  Then, a new log 
file "iomgr.log" will be created and subsequent events entered to that new 
file. Furthermore, an event will be posted in the new log, stating 
"Server Log database cannot be read. Database Reinitialized." 

If only a specific record in the log is found to be in error, the log will
continue to report all valid records.  The entry for that specific log event, 
however, will say "No data available for this entry."

ALL MEMBERS MISSING
-------------------
If all disk drives connected to the array controller's channels are members 
of a single array, and that array goes off-line, then the CI/O display will
change.  This occurs because the array driver unloads from the system.  The
CI/O Management Software will no longer display any array controller, 
channels, or array drives.  If all members of an array are missing, the array and its members are not displayed after a reboot or Rescan.

RESTORING COOPERATION BETWEEN CI/O AND INTEL LANDESK
----------------------------------------------------
Customers using certain versions of Intel LANDesk as their work group management solution may experience problems when simultaneously using Adaptec CI/O Array Management Software.  The situation arises because some versions of Intel LANDesk include an older version of the CI/O software for use in monitoring SCSI adapters via the Desktop Management Interface (DMI.)  The LANDesk product loads the SCSI monitoring software by default.  The CI/O Array Management Software, however, only allows a single copy of CI/O to run on the system at one time.

The work around consists of disabling either the SCSI monitoring software or the array management software.  The user must decide, therefore, which capability is most important for their system configuration and use.  In general, if the system includes a disk array controller product from Adaptec, we advise that the SCSI monitoring functionality of LANDesk be disabled.

Software Installation Process:
1.  Install Windows/NT and updated Windows/NT Server Pack, per instructions for the Adaptec array controller being used.  If Windows/NT is to be installed upon a "bootable" disk array, the user should refer to instructions on the use of Adaptec ArrayConfig software.
2.  Install CI/O Array Management Software, per the Adaptec instructions.
3.  After rebooting the system, go to the Services dialog box within the Windows/NT Control Panel.   For each of the following, change the entry from Automatic to Manual, and then stop each service:
	CIO Array Management Service 3.2
	CIO ArrayManager RPC Command
	CIO ArrayManager RPC Event
	CIO ArrayManager RPC EventP
4.  Install Intel LANDesk, per the appropriate instructions, and reboot the system.

To Use Adaptec CI/O Array Management Software:
1.  Go to the Services dialog box within the Windows/NT Control Panel.
2.  Stop the CIORAIDManagement service.
3.  For each of the following, start each service:
	CIO Array Management Service 3.2
	CIO ArrayManager RPC Command
	CIO ArrayManager RPC Event
	CIO ArrayManager RPC EventP

To Use the Native SCSI Monitoring Feature within Intel LANDesk:
1.  Go to the Services dialog box within the Windows/NT Control Panel.   For each of the following, change the entry from Automatic to Manual, and then stop each service:
	CIO Array Management Service 3.2
	CIO ArrayManager RPC Command
	CIO ArrayManager RPC Event
	CIO ArrayManager RPC EventP
2.  Start the SCSIDMI and CIORAIDManagement services. 

EVENT NOTIFICATION FOR OFFLINE ARRAYS 
------------------------------------- 
In the rare situation that an array has multiple failures and goes
off-line, a critical event will be posted to notify the user.  In certain
situations, a second event may also be received, stating that the array is moved critical.  The second event should be ignored.

*****************************************************************************

COMPATIBILITY NOTES FOR ADAPTEC Array1000SA FAMILY PRODUCTS
===========================================================

CDR DEVICES
-----------
CDR devices are not supported with this release.

NETWORK CARD CONFIGURATIONS
---------------------------
Some uncommon network card configurations may cause the array configuration 
to hang. If the array configuration utility hangs, check for conflicts with 
the network card configuration.


AHA-2940
--------
Memory errors or other problems may be experienced if both AHA-2940 and 
Array1000SA Family product coexist. To solve this problem, upgrade the 
AHA-2940 BIOS to the most recent version, v1.24 or later. If both ARO-1130SA and 
the AHA2940 are installed in the same system, one of the cards may not be 
visible by the operating system. This problem is caused by the system BIOS. 
Correct this problem by enabling the shadow RAM for all the address ranges 
in the system BIOS setup.

EZ-SCSI 4.0 SUPPORT
-------------------
EZ-SCSI is not supported on Array1000SA products, however, ASPI8DOS.SYS
is required for Netware operations and is provided as part of the product.
If ASPI8DOS.SYS is already installed, it should be upgraded.

ATI VIDEO CARDS
---------------
All ATI SVGA drivers may conflict with CDA1000 drivers under Windows NT. 
Use only standard VGA drivers with an ATI video adapter card under an NT 
environment.

NO DIMM PRESENT
---------------
The BIOS incorrectly reports that a 16MB SIMM is installed when there 
is no SIMM physically present. 

SHARING PCI INTERRUPTS
----------------------
Do not configure the system to share interrupts between the Array1000SA Family 
product and any network interface cards (NICs)in the system. Refer to the 
system BIOS manual for information on how to configure PCI interrupts, or 
change the PCI slot in which the NIC is installed.

PROPER SCSI TERMINATION
-----------------------
It is important to properly terminate both ends of the SCSI bus for the
ARO-1130SA card to function well. Improperly terminated SCSI busses can still
operate under lightly loaded situations (only a couple of drives.)  SCSI 
bus scans will generally work, and find all devices even if termination is 
incorrect. Under heavy workloads, bad termination leads to SCSI bus errors 
and data miscompares. 

Refer to motherboard/system documentation for termination instructions.

SCANNERS
--------
Scanners are not supported by C I/O.

REMOVABLE DEVICES AS PART OF A RAID ARRAY
-----------------------------------------
Removable storage media devices cannot be part of a RAID array.


*****************************************************************************

HARDWARE INSTALLATION NOTES FOR ARO-1130SA SERIES
===============================================

BOOTABLE CD-ROM
---------------
The Array1000SA Family v3.1 supports bootable CD-ROM.  If the RAIDport 
motherboard does not support bootable CD-ROM and ARO-1130SA bootable CD-ROM 
support is ENABLED, however, the system will hang before boot.  An AIC-78xx 
BIOS of v1.26 or higher is required.

*****************************************************************************

HARDWARE INSTALLATION NOTES FOR ARO-1130SA Series
===============================================

ADAPTEC 7800 FAMILY MANAGER SET
-------------------------------
The Windows NT, Array1000 Family v3.1 driver (CDA1000.sys v3.1) has been 
tested with the Family Manager Set driver, V 1.30 and later versions.
For NetWare, examine autoexec.ncf to ensure that cda1000.dsk is loaded 
BEFORE aic78xx.dsk, or NetWare will hang on power up.  Older aic78xx.dsk 
drivers are compatible, as long as the ARO-1130SA PCI slot is not specified 
on the command line (LOAD AIC7870.DSK slot=Z). If there is an AIC-78X0 
based card e.g. a AHA2940 in the system, Z must point to that card's slot 
and not to the ARO-1130's slot. If it does point to the ARO-1130's slot, 
it will result in unpredictable behavior. If loaded without command line 
parameters, NetWare will list valid slot numbers.  The ARO-1130SA will be 
listed in the parameter list. Do not select it. 

HARDWARE INSTALLATION - ARO-1130SA CARD CONFIGURATION INFORMATION
-----------------------------------------------------------------
When installing or re-installing the Array1000xA hardware into the system, SELECT OPTION "YES" for Reset System Configuration. This ensures all configuration/resources are built properly for the current hardware in the system.

*****************************************************************************

Array1000SA TEST NOTE
--------------------

Array1000SA BIOS will not boot unless at least one device is attached to the 
Array1000SA family product. The products's BIOS will run its self-test 
diagnostic, however. Therefore, the Array1000SA Family product will complete 
its power-on self-test. 


*****************************************************************************
GENERIC ARRAY CONFIGURATION NOTES
=================================

MAXIMUM NUMBER OF ARRAYS
-----------------------
Array1000SA Family products support a maximum of four arrays per card.

SUGGESTIONS ON DISK DRIVE WRITE CACHING
---------------------------------------
Most disk drives allow write caching, which greatly speeds up writes to disks. 
This feature enables an application program to continue executing once write 
data is successfully sent to a drive.  In very rare cases a deferred write 
error can occur (for example, because of a parity error within the drive 
cache memory.)  A deferred write error means data has been incorrectly written
and is no longer available to the I/O system. The error is unrecoverable. 
If the consequences of this potential problem are unacceptable, the drives 
should be put in the "write cache disabled" mode.

HOT SWAPPING DEVICES ON ARRAY CONTROLLERS
-----------------------------------------
Hot swapping a device with another device of different type having the same 
SCSI IDs (replacing a CD-ROM with disk or vice versa) is not supported. 

ARRAYCONFIG -PARTITION NOT DELETED WHEN ARRAY DELETED
-----------------------------------------------------
ArrayConfig deletes the Array, not the partition (warns that partition exists, but does not delete.)  To erase old data, the array must be initialized before use (Note: it is a good idea to initialize all new arrays regardless of the origin of the drives.)

*****************************************************************************

GENERIC ARRAY OPERATIONAL NOTES
===============================

INITIALIZING THE ARRAY
----------------------
If the user has created the array without initializing it, and reboots the 
system, the state of the array will be reported as:
	"New array needs init, needs system reboot"
A reboot at this point is not required.  One can initialize the array, and 
the array will become fault tolerant.

VERIFY AND RECONSTRUCT PRIORITY
-------------------------------
The Verify and Reconstruct operations can take a long time to complete. 
For large arrays, this could take from minutes to several hours. By default, 
these operations are assigned a Low or Medium priority to minimize the 
impact to other server activities.  For faster operation, change the 
priority to High from within the CI/O Management Software.

USE OF PAUSE I/O
----------------
Pause I/O is a feature which enables replacement of SCSI devices in an 
operational enclosure that is not specifically designed with Hot Swap 
capability. Although it temporarily stops I/O transactions on the
SCSI bus, it cannot assure the same level of protection from electrical
noise during device replacement as Hot Swap hardware.  As indicated in the
following procedures which use Pause I/O, only a single change such as a
device removal OR a device insertion (but not both) should be made with
each use of this feature.

Do not replace a non-downed drive in a paused array. The proper procedure 
is to down the drive, and then replace it. Failure to do so may lead to 
data corruption.

RESCAN & PAUSE/RESUME
---------------------
The following are the limitations to the current release:
1. For a multiple channel environment, users cannot presently change existing 
   array configurations on the fly through use of Pause/Resume or rescan.
2. Geometry of a drive is not updated when a smaller single member is 
   replaced with a larger single member and vice versa. Should this single 
   to single replacement occur, the potential for data corruption is 
   possible.
3. Singles cannot be replaced with array members and be reported back to the 
   O/S and application layer properly. This means that in the event of a 
   channel failure a user cannot replace a single with an array member to 
   make his array configuration complete and usable again during runtime.
4. Configuration changes of devices from CD to TAPE, TAPE to CD, SINGLE to 
   CD/TAPE, or Array member to CD/TAPE, is not supported.

REPLACING AN ACTIVE ARRAY MEMBER
--------------------------------
The software automatically responds to the event of one failed array member 
by using a spare, if available, and notifying the user. To replace an array 
member in active use, the following steps must be performed:
1)  Down the Array Member Device in all cases.
2)  If a hot-swap enclosure is not used, Pause I/O.
3)  Remove the Array Member and allow I/O to resume.
4)  If not using a hot-swap enclosure, Pause I/O.
5)  Insert the replacement device and allow I/O to resume.
6)  It may be necessary to low level format the removed, downed spare prior
    to re-use.

REPLACING A SPARE
-----------------
To replace a spare drive that is recognized as good by the software, 
the following steps must be used:
1)  Delete the spare. 
2)  If a hot-swap enclosure is not used, Pause I/O.
3)  Remove the Spare and allow I/O to resume.
4) If a hot-swap enclosure is not used, Pause I/O.
5)  Insert the replacement device and allow I/O to resume.  Via CI/O, mark 
    this new device as a dedicated or pool spare.

Under some unlikely circumstances, a spare may be recognized as down by
the software. This is indicated by a lightning bolt symbol on the spare
icon. This is unlikely, because if a spare fails a test by the software,
it is normally deleted. A spare may be marked as down, for example, if
I/O is paused and the user mistakenly removes the spare and reinserts it.
When I/O resumes, a rescan occurs, and the spare will be marked as down.

To replace a spare drive that is marked as down, the following steps must
be used:
1)  If a hot-swap enclosure is not used, Pause I/O.
2)  Remove the Downed Spare and allow I/O to resume.
3)  If a hot-swap enclosure is not used, Pause I/O.
4)  Insert the replacement device and allow I/O to resume.
5)  Via CI/O, mark the new device as a dedicated or pool spare.

OTHER NOTES ON REPLACING DRIVES
-------------------------------
1) When hot-swapping a drive that supports tagged command queuing (TCQ) with 
   a drive that does not support this feature (at the same SCSI ID), a 
   re-scan may not detect the swap of the drive. The system could possibly 
   send commands with tags to the new drive, causing a system hang. The 
   workaround is to perform the hot-swap while the server is down and/or off.
   Contact the drive manufacturer to determine if the drive supports TCQ.

2) When an array member fails, replace it with a good drive with the same 
   SCSI ID to reconstruct the array. The information about the new array 
   member will not be written to the member's reserved sectors until a manual 
   Reconstruction command is issued after re-scanning the system. (The member
   might show up as a "single" disk if the system is immediately rebooted after
   the re-scan.) 

3) It is recommended that old/down/defective disk drives be removed from the
   system as soon as possible. Any removed drives that are reused must be low-
   level formatted before reuse. 


*****************************************************************************

WINDOWS-SPECIFIC INSTALLATION & CONFIGURATION NOTES
===================================================

ERROR MESSAGES WHILE SETTING UP NT
----------------------------------
During NT setup, if the message "Setup is unable to locate the hard drive 
partition prepared by the MS-DOS portion of setup" or the message " xxxx MB 
disk y at Id z on bus 0 on cda1000.sys does not contain a partition suitable 
for starting Window NT" appears, do the following: 
1. Re-boot using the ArrayConfig disk. 
2. Using ArrayConfig utility, ensure that the array to be used as the NT 
   boot device includes the drive with the lowest SCSI target id on the 
   Array1000SA Family products bus.

IF MICROSOFT WINDOWS/NT SETUP HANGS
-----------------------------------
During installation of Microsoft Windows/NT, the system may hang while  
the Windows/NT Setup floppy is being used to copy the SCSI disk device 
driver.  A workaround is to boot from a DOS boot-disk, create a DOS 
partition on the array using FDISK, and then install Windows/NT on the 
array.

CD-ROM BOOT SYSTEM ERROR
------------------------
When attempting to boot from the Windows/NT installation CD, some systems 
will issue an error message:
	"Boot: Couldn't find NTLDR"
If this happens, boot from the Windows/NT floppies, and proceed to load the 
O/S from the CD-ROM according to Microsoft instructions.


"NO ACCESSABLE BOOT DEVICE" MESSAGE DURING BOOTUP
-----------------------------------------------
When booting the NT installation CD, systems may issue the message:
	"NO-ACCESSABLE BOOT DEVICE"
This indicates that the NT CD-ROM does not contain Array1000SA drivers. 
To avoid this failure:
1. Re-boot the NT CD-ROM.
2. At the prompt "Setup is inspecting your computers hardware configuration", 
   press the <F6> key.
3. NT will later request the Array1000SA driver diskette and the 
   installation will succeed.

NT DISK ADMINISTRATOR
---------------------
When creating a new array on a system running under Windows NT, 
the array is not listed as "usable" in the NT Disk
Administrator until initialized. This is normal Windows NT
functionality.

BOOT ORDER IN WIN/NT VS. ARRAY CONFIG
-------------------------------------
During installation, NT does not show the devices in the boot order.
Instead, it shows the arrays with the lower SCSI id (on lower channel)
first. To remedy this:
1. Disconnect all devices other than members of the boot array,
   so that only one device is present in the NT installation.
2. Configure the boot array in ArrayConfig such that the lowest
   SCSI id on the lowest channel is a member of the boot array.
3. Reconnect all other devices.

CONFIGURING A WINDOWS CLIENT TO MANAGE NETWARE SERVERS
------------------------------------------------------
See this topic under NetWare-specific Installation notes.

*****************************************************************************

NETWARE-SPECIFIC INSTALLATION NOTES
===================================

LARGER THAN 4GBYTE ARRAYS
-------------------------
When installing NetWare on an array 4GByte or larger, the install program 
erroneously reports that the DOS partition is too small. It however does 
allow to continue installation. Ignore this error message.

CONFIGURING A WINDOWS CLIENT TO MANAGE NETWARE SERVERS
------------------------------------------------------
To run the WinRPC for SPX system, the Windows NetWare environment should be 
patched to the latest level from Novell. The patchs should be at
the "DOSUP9" and "WINUP9" level, or greater. Novell patches are available on
CompuServe and the ftp.novell.com FTP site on the Internet.

The following list shows the range of versions of NetWare client components
that have been successfully tested. Do not use versions older than the oldest
shown below:

NetWare component   Oldest version

LSL.COM             9/10/93   2.05
IPXODI.COM          10/7/93   2.12
NETX.EXE            11/17/93  3.32
NETWARE.DRV         10/27/92  2.00
VNETWARE.386        11/19/93  1.04
VIPX.386            1/19/94   1.13
NWCALLS.DLL         11/2/93   4.04
NWIPXSPX.DLL        11/2/93   4.04

UNLOADING CDA1000.DSK
---------------------
When running  CI/O Management Software for NetWare, do not unload 
CDA1000.dsk while IOMGR.nlm is still loaded. Unstable behavior may result. 

*****************************************************************************

UNQUALIFIED FEATURES 
====================
1. CI/O support for external storage controllers.
2. CI/O support for SCSI host adapters.
3. CI/O support for DMI and SMNP.

*****************************************************************************

KNOWN PROBLEMS
==============
1. CD-ROM Changer is not supported under Netware

2. A dedicated spare may become single after a rescan. If it happens the
   customer should redefine it as spare

*****************************************************************************

                                  END OF

                           Array1000SA Family v3.1

                                   and

                   Adaptec CI/O Management Software v3.2
          
                                Readme File
                         
*****************************************************************************
