1. Z5995r02.exe Driver
2. ReadCIO.txt File Contents

ReadCIO.txt Driver File Contents (Z5995r02.exe)

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

                Adaptec CI/O Management Software, v4.02

                             Readme File
                         
                            June 23, 1999

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

This file contains notes on Adaptec CI/O Management Software v4.02

  - NEW FEATURES IN V4.02

  - NOTES AND CLARIFICATIONS ON ADAPTEC CI/O MANAGEMENT SOFTWARE V4.02


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

NEW FEATURES IN V4.02
=====================
An updated 32-bit user interface, featuring:
   - A graphical tree-style mapping capability
   - Fully updated dialogs and child windows
   - New Create Array wizard
   - Ability to start GUI in "iconized" mode
   - Critical event notification on Windows/NT, even with GUI closed
Support for the Adaptec ARO-1302U160 array controller
New features include:
   - Cache management for all supported RAID levels
   - Cache optimization wizard



NOTES AND CLARIFICATIONS ON ADAPTEC CI/O MANAGEMENT SOFTWARE V4.02
==================================================================

SCHEDULED ACTIVITIES
--------------------
The Test All Spares activity is scheduled by default to run once
per day.  If deleted from the Activity Scheduler, that task is 
automatically reinserted upon reboot of the system.

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


PROBLEMS ACCESSING THE HISTORIC EVENT LOG FILE IOMGR.LOG
--------------------------------------------------------
In extremely rare circumstances, entries in the Historic Event Log 
file "iomgr.log" may become unreadable, perhaps due to client and 
system 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."


USE OF CI/O WITH WINDOWS/NT
---------------------------
A conflict has been found between ARCServeIT v6.6 Workgroup Edition 
for Windows NT and CI/O Management Software v4.0x.  When the 
ARCServeIT Message Engine is started before CI/O's Portmapper 
service, then the following message is observed:
  "Unable to register(TEV_TEV_VER, tcp)"
A fix to ARCServeIT is available from that vendor for this condition.
Or, as a work-around, the system administrator should manually start 
the "CIOArrayManager RPC Event" service first.  This causes the 
"NobleNet Portmapper" and "CIOArrayManager RPC Command" services to 
start.  Finally, the "ARCServIT Message Engine" service can be
started.


USE OF CI/O WITH ADAPTEC ARO-1302U160 CONTROLLERS
-------------------------------------------------
Previously-used drives should be freshly formatted or initialized 
before being connected to the ARO-1302U160 controller.  Otherwise, 
the ARO-1302U160 controller may not properly reconcile the fragments 
left over from previously created arrays.

The "Make first Virtual Device" command, used to modify the boot 
order of arrays, will only operate upon the last array in the boot-
order list.  It will change the identifier of the array with the 
highest-numbered virtual device identifier to zero, thus making it 
the lowest-numbered identifier.  The operation will be ineffective on 
arrays with intermediate identifiers.  By repetitive use of the 
command, however, the boot sequence can be ordered as desired.

If all disk drives connected to the ARO-1302U160 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 operation.

In the rare circumstance that an array created on an ARO-1302U160 
controller has multiple device 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 critical.
The second event should be ignored.

Reactivation of an off-line array may only be performed in certain 
situations.  Specifically, the array must have had at least one 
member recognized by CI/O since the last system reboot.  If the 
command fails, CI/O will post an error message.  In this case, a 
system reboot is required before the array may be reactivated.

If a RAID 0/1 array experiences multiple device failures, and 
reconstruct initiates from multiple defined spares, then an incorrect 
event may be observed.  The event will state that an array member is 
down, but will reference the device ID of the spare.

Upon Reconstruct of a critical RAID 0/1 array using a Pool Spare, the 
new member may be marked as "down" (red arrow through the icon) until 
reconstruct completes.

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

                              END OF

                Adaptec CI/O Management Software v4.02

                            Readme File
                         
**********************************************************************