*****************************************************************************
Array-1000 Family v2.0
Readme File
June 17, 1997
*****************************************************************************
This file contains the following:
WHAT IS NEW IN VERSION 2.0
COMPATIBILITY NOTES
HARDWARE INSTALLATION NOTES:ARO-1130
HARDWARE INSTALLATION NOTES:AAA-130 Series (AAA-13X)
TEST NOTE
UPGRADING NOTES
GENERIC ARRAY CONFIGURATION NOTES
GENERIC ARRAY OPERATIONAL NOTES
WINDOWS-SPECIFIC : INSTALLATION & CONFIGURATION NOTES
WINDOWS-SPECIFIC : OPERATIONAL NOTES
NETWARE-SPECIFIC : INSTALLATION NOTES
NETWARE-SPECIFIC : OPERATIONAL NOTES
*****************************************************************************
WHAT IS NEW IN VERSION 2.0
==========================
AAA-130 series is added to Array-1000 Family.
Bootable CD-ROM is now supported. The ARO-1130 & AAA-130x 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.
*****************************************************************************
COMPATIBILITY NOTES
===================
RAIDport On Board SYSTEM (MOTHERBOARD) BIOS
-------------------------------------------
Some versions of the RAIDport On Board system motherboards report an unknown
PCI device when the Array-1000 Family product is installed. This message does
not affect the operation of the ARO-1130. The RAID co-processor on the
Array-1000 Family product is reported as the unknown device.
INCOMPATIBILITY WITH PCI2.0 MOTHERBOARD PCI-TO-PCI BRIDGE
-------------------------------------------------------------
The AAA-130x uses an industry standard PCI 2.1 compliant PCI-to-PCI bridge.
Certain systems use PCI-to-PCI bridges on the MOTHERBOARD to get additional
PCI add-in slots. Some earlier systems used PCI 2.0 compliant PCI-to-PCI
bridges(e.g. Digital part numbers DEC21050 or DEC21052) to get these
additional PCI slots. If AAA-130x is installed on BUS1, the secondary side
of a PCI 2.0 PCI-to-PCI bridge an incompatibility may exist. It is
recommended that the AAA-130x be installed on BUS 0(the primary side). Only
a few earlier use PCI 2.0 bridges.
SEAGATE 9-Gbyte ULTRASCSI DRIVE
-------------------------------
Problems have been observed when using early versions of the Seagate 9-GByte
UltraSCSI drive with the Array-1000 Family product. Contact the drive vendor
for an updated firmware revision.
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 hang, check for conflicts with
the network card configuration.
AHA-3985
--------
CI/O Array Management Software (CI/O AMS) and the ARO-1130 or AAA-130x do not
support RAID 0/5 CVT (convertible) arrays created by and used in AHA-3985.
To convert a RAID 0/5 CVT array created with an AHA-3985/3985W adapter
to the Array-1000 Family product :
1. convert the array to RAID 5 CVT (not RAID 0 CVT) BEFORE installing the
Array-1000 Family product.
2. Follow the migration instructions included in the ARO-1130 Installation
and Hardware Guide.
The array will be usable as a RAID 5 array when the ARO-1130
is installed. RAID 0, 1 and 5 arrays from AHA-3985 will be converted
automatically to the ARO-1130 array format. Once the array is converted to
ARO, to create a new spare, use a device which is at least 70MB larger than
the smallest member of the array.
AHA-2940
--------
Memory errors or other problems may be experienced if both AHA-2940 and
Array-1000 Family product coexist. To solve this problem, upgrade the
AHA-2940 BIOSto the most recent version, v1.24 or later. If both AAA-13X and
the AHA2940 are installed in the same system, one of the card may not be
visible by the 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.
WINDOWS NT INSTALLATIONS USING EZ-SCSI 4.0
------------------------------------------
EZ-SCSI 4.01 includes ASPI8DOS.SYS v1.26 which is incompatible with the
ARO-1130. The Array-1000 Family product requires ASPI8DOS.SYS v1.3.1(included
on Array-1000 Family v2.0 Manager Set diskette or higher). Also, some
utilities of the EZ-SCSI 4.01 and 4.01a (e.g. CD Player, CD Writer,
SCSIBench) donot work with Array-1000 Family product. It is recommended to
uninstall EZ-SCSI software before installing Array-1000 V 2.0 software. Later
revisions of EZ-SCSI will support Array-1000 Family product.
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 SIMM PRESENT
---------------
The Bios incorrectly reports that a 16MB SIMM is installed when there
is no SIMM physically present. A 1 OR 4 MB SIMM must be installed for proper
functioning.
SHARING PCI INTERRUPTS
----------------------
Do not configure the system to share interrupts between the Array-1000 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-1130 card to function properly. Improperly terminated SCSI busses often
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 miscompare.
Refer to motherboard/system documentation for termination instructions.
SCANNERS
--------
Scanners are not supported in this release.
REMOVABLE DEVICES AS PART OF A RAID ARRAY
-----------------------------------------
Removable storage media devices can't be a part of a RAID array, although
they can exist in the system as individual devices.
CI/O AMS VERSION DEPENDENCIES IN CONNECTING CLIENTS TO SERVERS
--------------------------------------------------------------
CI/O AMS v1.0 is incompatible with the v2.0 release. In order to use CI/O
AMS, upgrade the client to V @.0. From v2.0 onwards the following rules will
apply:
1. At a given server or client all the CI/O sub-components must be the same
version.
2. The CI/O AMS application will be capable of interacting with the CI/O AMS
server application, if the client major version number is the same as on
the server, and if the minor version number is equal or greater than that
of the server.
Examples:
a. client 2.00 will work with server 2.00(same major number).
b. client 2.50 will work with server 2.40(client minor version number(.50)
is greater than server minor version number .40)
c. client 3.00 will not work with server 2.60(different major numbers, client
has a major version number 3 & server has 2).
d. Client 2.14 will work with server 2.19 (client minor version numbers is
less than the server version number but within the tenths' digits).
*****************************************************************************
HARDWARE INSTALLATION NOTES:ARO-1130 Series
===========================================
BOOTABLE CD-ROM
---------------
Version 2.0 supports bootable CD-ROM. However if the RAIDport motherboard
does not support bootable CD-ROM and ARO-1139 bootable CD-ROM support is
ENABLED, system will hang before boot. AIC-78xx V 1.26 or higher required.
TERMINATION
-----------
If the SCSI bus is not properly terminated, per the instructions in the
system motherboard and ARO-1130 Installation and Hardware Guide, intermittent
system problems may be experienced (ie : workstations locking up or very
slow operation or data miscompare). If this symptoms are observed, recheck
the device termination. Also, read the termination information included in
the system motherboard documentation. When combining Wide SCSI and Narrow
SCSI devices on the SCSI bus, read the motherboard documentation carefully
to determine how to terminate the devices and the SCSI bus.
RAIDport ON BOARD MOTHERBOARD SCSI SELECT TERMINATION SETTINGS
--------------------------------------------------------------
With RAIDport On Board motherboards and , the AIC-78xx BIOS SCSI Select
utility runs when there is no Array-1000 Family product installed,
and the Array-1000 SCSI Select utility runs if an Array-1000 Family
product is installed.
Setting SCSI Connector Termination
----------------------------------
A. AIC-78xx BIOS SCSI Select utility:
This utility gives the user 3 possible termination choices:
Termination of Motherboard SCSI Connector
Narrow Wide
(Low Byte) (High Byte)
1 Low On High On
2 Low Off High On
3 Low Off High Off
B. Array-1000 BIOS SCSI Select utility:
This utility gives the user 2 possible termination choices:
Termination of Motherboard SCSI Connector
Narrow Wide
(Low Byte) (High Byte)
1 Low On High On
2 Low Off High Off
Termination devices and power sources:
------------------------------------------
1. Passive termination (resistors in a single in line package (SIP)) are a
common, low-cost method of SCSI termination.
2. Active termination ( circuits which pull up or pull down voltage actively
in order to force accurate termination) is a more expensive, but more
accurate, approach supported on some RAIDport On Board motherboards (see
motherboard documentation). Active termination is highly recommended. It
is recommended not to mix active & passive termination at two ends of the
bus.
3. External Termination Plugs (both Active and Passive) are available which
connect directly to the SCSI Bus. This makes drive swapping much easier,
since termination does not change as drives are removed or added.
4. Termination Power - Many SCSI devices have the option of supplying
termination power to the SCSI bus (which should be enabled). All
terminators require termination power, which is supplied as one of the
SCSI bus signals.
It is a good idea to supply termination power to the SCSI bus from all
devices in case one of the termination power sources fails, since there
will still be termination power on the SCSI bus coming from another
source.
*****************************************************************************
HARDWARE INSTALLATION NOTES:AAA-130x
=========================================
ADAPTEC 7800 FAMILY MANAGER SET
-------------------------------
The Windows NT, Array1000 Family v2.0 driver (CDA1000.sys v2.0) 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-1130 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 behaviors. If loaded without command line
parameters, NetWare will list valid slot numbers.
ARO-1130 will be listed in the parameter list. Do not select it.
*****************************************************************************
TEST NOTE
---------
Array-1000 BIOS will not boot unless at least one device is attached to the
Array-1000 family product. The products's BIOS will run its self-test
diagnostic, however. Therefore, the Array-1000 Family product will complete
its power-on self-test.
*****************************************************************************
UPGRADING NOTES
===============
BOOTABLE BIOS FLASH DISK
------------------------
The flash utility used to update the Array1000 Family BIOS must be copied to
a bootable diskette (See DOS documentation to make a diskette bootable) or
boot from either an MS-DOS or a PC-DOS systemdiskette immediately prior to
use of the flash utility.
BOOTING AFTER FLASHING BIOS
---------------------------
Cold-rebooting the system is recommended after running the RAID
host adapters BIOS flash upgrade utility (the utility automatically
performs a warm reboot when it completes). Under some conditions the
system may hang if it is not cold-rebooted (power switch
turned off and on).
*****************************************************************************
GENERIC ARRAY CONFIGURATION NOTES
=================================
MAXIMUM NUMBER OF ARRAYS
-----------------------
Array-1000 Family products support a maximum of four arrays per card.
SUGGESTIONS ON 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.
CONFIGS.DAT
-----------
CI/O Array Management Software creates the configuration file CONFIGS.DAT
automatically on servers and on networked clients. The file is used on
networked clients to store a list of to which the client is connected.
If the CI/O software is uninstalled this file must be manually deleted.
SWAPPING DEVICES
----------------
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.
*****************************************************************************
GENERIC ARRAY OPERATIONS 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 arrays 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.
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. Also please 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 spare(dedicated or pool).
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 spare (dedicated or pool).
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 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.
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."
DELETING SERVER ADDRESS
-----------------------
Attempting to delete a server's address from a networked client, while the
server is off-line, will result in a 70 second retry period during which an
attempt to connect to the server is made. After70 seconds, the server
address will be deleted.
SCHEDULING EVENTS AND TIMEZONES
-------------------------------
When scheduling an event at a remote client for a server that is in
another timezone, the event is scheduled at the server relative to
server's local time. For example,
Client X Server Y
Timezone is PST EST
Local Time 08:00 am 11:00 am
Event Scheduled for 07:00 pm for server Y
Event Executed at 04:00 pm 07:00 pm at Server Y
SORTING AND DISPLAY BY THE CLIENT SERVER LOG AND EVENT LOG
----------------------------------------------------------
The client sorts events from different 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.
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.
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
VERIFY AND RECONSTRUCT PRIORITY
-------------------------------
The Verify and Reconstruct operations can take a long time to complete.
For large arrays, from minutes to several hours. By default,
these operations are assigned a Low or Medium priority to minimize the
impact to other server activity. For faster operation, change the priority
to High.
USE OF LARGE FONTS
------------------
The use of large fonts is not supported on Windows 3.1, 95 and NT versions
of CI/O AMS.
BLINKING CD-ROM LIGHTS
----------------------
CI/O Array Management Software does not support blinking the drive light
on CD-ROM drives.
ALL MEMBERS MISSING
-------------------
If all SCSI drives connected to the computer's SCSI
channels are members of a single array and that array goes off-line,
CI/O Array Management Software does not display any controller, SCSI
channels, or drives. If all members of an array are missing, the array and
its members are not displayed in CI/O Array Management Software after
rebooting or when performing a re-scan.
*****************************************************************************
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
Array-1000 Family products bus.
IF NT SETUP HANGS
-----------------
During NT Setup, sometimes the system may hang while the NT
Setup floppy #3 is being used for copying the SCSI disk device driver. A
workaround is to boot to 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 NT installation CD,
some systems will issue an error message,
"Boot: Couldn't find NTLDR"
If this happens, boot from the NT floppies, and proceed to load OS from
the CD according to Microsoft instructions.
"1024 CYLINDERS" ERROR DURING NT INSTALLATION
---------------------------------------------
When attempting to load Windows NT on a bootable array larger than 8 Gbytes,
or containing drive members larger than 1 GBytes capacity, NT may generate
an error stating that the installation drive is greater than 1024 cylinders.
NT will only allow the creation 1 GByte partitions.
Therefore, the user will only be able to make a 1 Gbyte partition.
To use a larger partition under NT:
1. Disconnect all other devices.
2. Load NT.
3. Reconnect all other devices.
BOOT ORDER NT VERSUS ARRAY CONFIG
---------------------------------
During installation NT does not show the device in BOOT Order, instead it
shows the array with the lower SCSI Id (on lower channel) first. To remedy :
1. Disconnect all devices other than the members of the BOOT array, so that
only one disk is presented in the NT installation.
2. Configuring the BOOT array in ArrayConfig such that the lowest SCSI Id on
the lowest channel is the member of the BOOT array.
3. Reconnect all other devices.
"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 Array-1000 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 Array-1000 driver diskette and the
installation will succeed.
READING README.TXT DURING CI/O AMS SETUP
----------------------------------------
Attempting to read this readme.txt file during CI/O AMS 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.
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.
SYSTEM TIME CHANGE
------------------
Do not change the system time while the CI/O AMS is running.
To change the system time one must:
1. Stop all CI/O AMS management components and RPC modules.
2. Change the system time.
3. Restart the CI/O AMS 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.
BOOT ORDER IN 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.
*****************************************************************************
WINDOWS-SPECIFIC : OPERATIONAL NOTES
====================================
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.
PORTMAP APPLICATION
-------------------
When exiting CI/O AMS, the PORTMAP application may become visible.
PORTMAP is not a user application. To make it invisible: minimize, then
restore the CI/O AMS window; or exit the PORTMAP application and restart
CI/O AMS.
*****************************************************************************
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 Array Management Software for NetWare,
do not unload CDA1000.dsk while IOMGR.nlm is still loaded. Unstable
behavior may result.
INCORRECT WARNING MESSAGE
-------------------------
During installation NetWare 4.1 & 4.11 may post an incorrect warning messages,
"xxxxxx could not be loaded Control will be xxxxxxx", ignore the message.
*****************************************************************************
NETWARE-SPECIFIC : OPERATIONAL NOTES
=====================================
Under NetWare 4.11, the CI/O AMS may incorrectly allow the creation of
dedicated spares with a size smaller than the other array members. Only
drives having a capacity equal or greater than members of existing array
should be allocated for dedicated spares.
*****************************************************************************
END OF
Array-1000 Family v2.0
Readme File
*****************************************************************************