*********************************************************************
Release Notes for Adaptec 2100S, 3200S and 3400S SCSI RAID Controllers
as of August 14, 2000

Controller & Utility Software:
  - Firmware Version: 320H
  - I2OBIOS Version: 1.35
  - SMOR Version: 1.12 Build 32
  - Storage Manager Version: 3.03
  
Documentation:
  - Quick Start Guide, DO-1010-001
  - 2100S Installation Guide, DO-1013-001
  - 3000S Installation Guide, DO-1014-001
  - Storage Management Software, DO-1011-001
  - Storage Manager Pro, DO-1012-001

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

Please review this file for important information about compatibility
issues and differences in operation that were discovered after our
product documentation was printed.

NOTE: The latest firmware and product documentation (in Adobe Acrobat
      PDF format) will be available for download at
      http://www.adaptec.com.

In the case of conflict between various parts of the documentation
set, this file (READ.ME) contains the most current information.

The Release Notes are divided into the following sections and topics:

1. General Information
    - RAIDUTIL
    - Storage Manager
    - Storage Manager on ROM (SMOR)

2. Operating Systems
    - Linux
    - Novell NetWare 4.x, 5.x
    - SCO UnixWare 7.x
    - Windows 95/98
    - Windows NT 4.0 (with Service Pack 6 or higher)
    - Windows 2000

3. Peripheral Devices

4. Motherboards and Computer Systems
    Notes of motherboard- or system-specific compatibility issues.


============================================================
General Information:

* Do not install Storage Manager Pro in the root directory of your 
  system. This will result in the application failing to start.

* You cannot view the README information from Storage Manager when the
  application is running in the Adaptec Bootable CD environment. If
  you want to view the README text, select that option from the
  Adaptec install utility menu.
  
* The operating temperature range for SCSI RAID controllers with a
  battery module is 10 - 40 degrees C. This applies only to
  controllers that have a battery module installed.

* If you want to save a configuration file or perform a flash upgrade
  while running Storage Manager from the Adaptec CD-ROM boot
  environment, ensure that the floppy disk for your system is mounted
  before attempting to use these features.

* Storage Manager and RAIDUTIL will not allow you to use a
  "redirected" drive in a disk array. The drive will appear to be
  available, but any attempt to include the drive results in an error
  message. You can use SMOR to perform this action. This problem will
  be fixed in a future release.

* The Adaptec SCSI RAID CD does not boot reliably in Compaq Deskpro
  systems using an IDE CD-ROM drive. This problem may occur in other
  systems if the mass storage controller, system BIOS and/or CD-ROM
  firmware does not support bootable CD media.
  
* If you experience problems with your video display or mouse when
  using the Adaptec CD as the boot media for a system, you can use the
  following to specify your hardware when the command prompt is
  displayed: Type: 
  
  bootcd [options] <Enter>
  
  options: m=<mouse type> s=<video server type> mon=<monitor value> p=<port>
  
           <mouse type> man (for manual configuration) or
                         serial: generic, thinking, logitech, logitechcc, 
                         msnew, msintelli, mousesystems, mmseries, mmhittab
            non-serial: alpsps/2, atibm, geniusnmps/2, geniusnsps/2, 
                        thinkingps/2, logibm, logimman+ps/2, msintellips/2, 
                        msbm, usb
                         
            <port> is a number from 1 to 4 representing com1..com4 
                   (for serial mice)
  
            <video server type> man (for manual configuration) or 
                                vga16 svga s3 mach32 mach8 8514 p9000 agx 
                                w32 mach64 i128 s3V 3dlabs
              
            <monitor value> can be a number from 0 to 11:
             
      0 - 640x480 @ 60 Hz                         6 - 1024x768 @ 70 Hz
      1 - 800x600 @ 56 Hz                         7 - 1280x1024 @ 60 Hz
      2 - 1024x768 @ 87 Hz int (no 800x600)       8 - 1280x1024 @ 74 Hz
      3 - 1024x768 @ 87 Hz int, 800x600 @ 56 Hz   9 - 1280x1024 @ 76 Hz
      4 - 800x600 @ 60 Hz, 640x480 @ 72 Hz        10 - 1600x1200 @ 70 Hz
      5 - 1024x768 @ 60 Hz, 800x600 @ 72 Hz       11 - 1600x1200 @ 76 Hz
  
-----------------------------
RAIDUTIL (Command Line Interface):

* RAIDUTIL, a command line storage management utility, 
  allows you to create and manage your disk arrays from a
  command prompt on the following platforms:

    BSDi 4.x
    FreeBSD 4.x
    Linux (see Linux section for details)
    MS-DOS 6.22 or higher
    Novell NetWare 4.11, 4.2 and 5.x
    SCO UNIX 3.2v4.2
    SCO ODT 3.0 and OpenServer 5
    SCO UnixWare 7.x
    Windows NT 4.0
    Windows 2000
    
* RAIDUTIL for Red Hat Linux requires specific kernel versions. Refer
  to the Linux section under Operating Systems for a list of kernel
  versions supported by this release.
  
* BSDi, FreeBSD, and SuSE Linux versions are available only as
  downloads from the Adaptec web site. Contact your technical support
  representative for availability. All UNIX versions include a man
  page for the command line parameters.

* The RAIDUTIL -L command under NetWare will return an incorrect maximum
  transfer rate for Ultra160 devices. The reported value is 80 MB/sec
  instead of 160 MB/sec.  You can verify the actual bus speed using
  Storage Manager or SMOR. This problem will be fixed in a future
  release.
  
* SCO UNIX 3.2v4.2 and OpenServer 5
  
  Running RAIDUTIL with the -e soft parameter generates an error and
  non-fatal core dump.
  
  Running RAIDUTIL with the -A parameter returns data headings but does
  not display any data values.

-----------------------------
Storage Manager:

* Uninstall both Storage Manager & Storage Manager Pro before
  attempting to reinstall the software. Storage Manager must be
  installed before Storage Manager Pro to ensure that all services are
  running and communicating correctly.

* If a drive is removed from an array enclosure when no I/O is
  occurring, Storage Manager will flag the drive icon correctly, but
  report an incorrect (Optimal) status. If you perform a rescan of the
  bus, the status is updated correctly.

* Storage Manager does not properly recognize when an enclosure with a
  failed drive is disconnected and reattached. This is not a
  recommended procedure. You should replace the drive and ensure the 
  drive and array are Optimal before you disconnect the enclosure.
  
* Do not attempt to use the Save Configuration feature during a Build
  process. Incorrect information will be saved and the configuration
  will not be loaded correctly when you subsequently use the Load
  Configuration feature.

* To change the event log filter level, you must exit the event log
  window and then select event log again from the device information
  window. This will be fixed in a future release.
  
* When Storage Manager is running from the Adaptec CD-ROM boot
  environment, the timestamps in the Event Log will default to
  Greenwich Mean Time (GMT) not the local time for your location.
  
* The Print function in the Event Notification pop-up window does not
  work. This problem will be resolved in a future release.

* You cannot use Storage Manager Remote Communication to monitor a
  controller on another operating system platform from a SuSE Linux 6.4 
  client system.
  
* Do not attempt to perform an array expansion from a remote
  client running Storage Manager. This operation should be performed
  only through Storage Manager on the host system to which the array
  is connected.
  
* Changes to the Background Task Priority setting are not saved for
  multilevel (0/1 and 0/5) arrays. The setting is saved correctly for
  individual RAID 0, 1 or 5 arrays. For multilevel arrays, the
  background task priority will always be the default value. This will
  be fixed in a future release.

* Storage Manager running on a UNIX client may become unresponsive
  during an attempt to make a remote connection. If this occurs, turn
  off the Num Lock key and enter any IP address information using the
  number keys on the top row of the keyboard. In some cases, enabling
  the Num Lock key and entering the IP address from the numeric keypad
  causes Storage Manager to stop responding.

* Storage Manager may not prompt you to reboot your system after you
  flash a firmware image to the controller. Always shutdown your
  operating system and restart your computer after you download flash
  image files through Storage Manager to ensure the new code is
  effective.

* The Array Group Information dialog and Logical Configuration window
  are not updated correctly after stopping a Verify operation. For the
  Array Group information window, click OK to close the window and
  then open it again. This new window will display the correct status.
  For the Logical Configuration window, select File--Read System
  Configuration to update the device status.

* Adaptec Storage Manager is not available for BSDi or FreeBSD
  systems. However, you can use SMOR or the RAIDUTIL command line
  utility to configure disk drives and RAID subsystems for computers
  that use these operating systems. See the Storage Management
  Software User's Guide for additional information about using SMOR
  and RAIDUTIL.
  
* The current version of the Communications Engine can support only
  one remote connection to a server. If you attempt to establish
  multiple remote connections to the same server, the Communications
  Engine will fail with an Invalid Page Fault error. This will be
  fixed in a subsequent release.

* When using Storage Manager under SCO UNIX or UnixWare you might
  experience a problem using the Help-Glossary hyperlinks. If this
  occurs, place the pointer slightly below and to the right of the
  highlighted link. Clicking to select in this location should cause
  the link to be activated.

-----------------------------
Storage Manager on ROM (SMOR):

* When creating a RAID-1 array, SMOR will allow mirroring to a disk
  that is smaller than the source data disk. This can result in loss
  of data. Ensure that both disks have equal capacity when creating a
  RAID-1 array.
  
* When using an ATI 3D RAGE video card, exiting SMOR may cause video
  display to become garbled. This is a problem with the video card and
  can be fixed by switching power to the computer off and then on.

* If you get a read error message while updating the Adaptec controller
  ROM BIOS using an image file stored on an IDE or SCSI disk drive,
  copy the image file to a floppy disk and try the operation again.

============================================================
Operating Systems:


* If you are using I2ODDL.SYS with the ASPICD.SYS driver, only those
  CD-ROM drives attached to the first channel (channel 0) of the
  controller are detected.
  
* Adaptec-qualified I2O Drivers for the following operating systems are
  provided in this release:

  - Linux (see Linux section for specific kernel versions)
  - Novell NetWare 4.x and 5.x
  - SCO UNIX 3.2v4.2
  - SCO UNIX OpenServer 5.x
  - Windows 2000
  - Windows NT 4.0
  - Windows 95/98
  
  I2O Drivers for the following operating systems are available as
  downloadable packages. Contact your technical support representative
  for availability.
  
  - BSDi 4.x
  - FreeBSD 4.x
  - SuSE Linux 6.3 and 6.4
  
  Please contact your operating system vendor for availability of
  generic I2O OSMs for platforms that are not listed.

-----------------------------
Linux

* This release of Adaptec software supports the following Linux
  kernels:

    2.2.12-20     2.2.12-20smp
    2.2.14-5.0    2.2.14-5.0smp

* There is an error in the Linux kernel for Red Hat 6.2 on Intel
  processors that can result in data corruption. Please refer to the
  RH62FIX.TXT file for information on obtaining and using a kernel
  patch that corrects this problem.

* The Adaptec I2O driver is not copied correctly when you install an
  upgrade from Red Hat Linux 6.0 to 6.1. This results in a
  kernel panic when you restart the system. Use the following
  procedure to avoid this problem.
    
  Before installing the upgrade:
  
  1. Mount the Adaptec Red Hat 6.1 driver disk.
    
      mount -t msdos /dev/fd0/mnt/floppy
  
  2. Extract the driver using the following commands:
  
      cd/lib/modules
      mkdir -p 2.2.12-20/scsi
      gzip -cd /mnt/floppy/modules.cgz | cpio -i 2.2.12/dpti2o.o
      mv 2.2.12-20/dpti2o.o 2.2.12-20/scsi
      
     For systems that use symmetric multiprocessing (SMP):
     
      cd/lib/modules
      mkdir -p 2.2.12-20smp/scsi
      gzip -cd /mnt/floppy/modules.cgz | cpio -i 2.2.12smp/dpti2o.o
      mv 2.2.12-20smp/dpti2o.o 2.2.12-20smp/scsi
  
  3. Modify or verify that your scsi_hostadapter entries in your local
     /etc/conf.modules file are numbered starting with 1:
  
     For example:
     alias scsi_hostadapter1 eata.dma
     alias scsi_hostadapter2 dpt_i2o
  
  4. Reboot and install the Red Hat 6.1 upgrade as described in the
     Adaptec redhat61.txt HowTo file.
  
* Storage Manager for Linux 6.x requires kernel version 2.2.12-20 or
  2.2.14-5.0. See the Linux section under Operating Systems for specific 
  kernel versions that are supported.

* Storage Manager for Linux with the GNOME desktop environment does
  not automatically update the Percent Complete status of Build,
  Rebuild or Verify operations when the Storage Manager window does
  not have the focus. When the window receives the focus it will begin
  updating the completion status.
  
  You can change the default behavior of the desktop to give new
  windows immediate focus by changing the setting in the Window
  Manager configuration options for the Enlightenment window manager.

* If you are using Red Hat Linux 6.x issuing a halt command can cause
  the system to fail during the shutdown process. This problem occurs
  on various motherboards and Adaptec controller combinations.
  
  Adaptec has determined that this problem does not occur if you disable
  Advanced Power Management (APM) services. If you encounter this 
  problem, recompile the Linux kernel with the APM option disabled.
  
* Use SMOR or the command line utility to update the firmware on a
  SCSI RAID controller. Flash updates of the firmware using Storage
  Manager can result in an inoperative controller. This problem will
  be fixed in a future release.
  
* To ensure remote communication support is available for Storage
  Manager, type the following from a command line:
  
    dptscom -FORCERUN

-----------------------------
Novell NetWare:

* If event broadcast to a Windows NT user/client is enabled under
  NetWare 5, the NetWare Broadcaster will generate multiple event
  messages on the Windows NT client for a single event condition. Adaptec
  recommends using the Storage Manager Event Log viewer to view event
  messages for a NetWare server in place of broadcast messages. This
  problem will be fixed in a future release of the Event Broadcast
  module for NetWare.
  
* Using a DPT SmartRAID IV or SmartCache IV controller and Adaptec
  SCSI RAID controller in the same system will result in the following
  problems if the DPT controller does not have a hard disk attached:
  
    RAIDUTIL -L will not list any devices attached to the
    SmartRAID/SmartCache IV controller. The command will scroll blank
    lines and then Adaptec SCSI RAID devices will be listed.
  
    A Storage Manager session from a remote client will not display
    any devices attached to the controllers and the remote session
    will freeze after the hardware scan. You will have to terminate
    the storage manager remote session to recover from this condition.
  
* The Novell SCSIOSM driver for I2O cards does not support tape or
  CD-ROM devices on Adaptec SCSI RAID controllers. The standard Novell
  block storage OS Services Module (OSM) will work for hard disk
  drives. Contact your technical support representative for
  availability of an updated NetWare OSM.

-----------------------------
SCO OpenServer 5:

* The Storage Manager e-mail function does not work on OpenServer 5.
  All other Broadcaster functions are available. Adaptec is working to
  resolve this problem in a future release.

* OpenServer 5.05 will not boot from an Adaptec SCSI RAID controller on an 
  Abit BH6 motherboard. Use an alternate controller as the boot device for 
  this system.

-----------------------------
SCO UnixWare 7:

* Use SMOR to perform a flash update of the controller firmware. Flash
  updates using Storage Manager or RAIDUTIL will result in an error
  message. Adaptec is working to resolve this problem for a future
  release.

* You cannot install the operating system onto an array if any
  non-RAID drives are present. The following workaround for this
  problem will allow you to install UnixWare 7.10 on an array and also
  have non-RAID drives after the installation.
  
  1. Remove any non-RAID drives from the system. Leave the RAID drives
     installed.
  
  2. Install the operating system on the disk array.
  
  3. Reinstall the non-RAID drives.

  During the next system boot UnixWare will assign the array a "ghost"
  address of 0.0.0 and disable whatever drive was previously assigned
  to 0.0.0. You will see a message about this change during the boot
  process.
  
* To ensure correct operation with tape devices, update your UnixWare
  installation to version 7.10. Versions prior to 7.10 may experience
  problems communicating with tape devices attached to Adaptec SCSI RAID 
  controllers.
  
* An I2O driver patch is available from SCO that allows you to to boot from 
  an Adaptec controller.
  
  Apply the I2O Mass Storage HBA Supplemental Level Support (PTF7067E).
  This patch is only for UnixWare 7.0.1 and 7.1.0. The patch is
  available from: http://www.sco.com/support/ftplists/uw7list.html

-----------------------------
Windows 95/98:
  
* Do not put your system in Standby mode with an Adaptec SCSI RAID
  controller installed. If you attempt to enter Standby mode the
  Adaptec controller may be left in an indeterminate condition
  resulting in an unusable system until you power off and power on
  the computer. This will be fixed in a future release.

* If you attempt to correct an Adaptec controller entry under Other
  Devices in the Device Manager using the Update Driver function your
  system may hang during the restart sequence. If this occurs the
  device update is not completed and the device will still be
  identified incorrectly. You may need to manually copy the Adaptec
  miniport driver (DPTI20.MPD) to the Windows \SYSTEM\IOSUBSYS
  directory.

  Adaptec has determined that this indicates a problem with Windows 95/98 
  and the motherboard chipset (Intel FX and BX types) when attempting
  to identify the Adaptec controller. Contact your motherboard
  manufacturer for a chipset driver patch.
  
  NOTE: The controller will function normally even if there is no
        patch available.

* The I2ODDL.SYS driver may fail to load when there are no hard disk
  drives attached to the Adaptec SCSI RAID controller or if the
  Adaptec I2O BIOS is disabled. This driver is required for CD-ROM
  support under MS-DOS.
    
-----------------------------
Windows NT 4.0:

* Ensure you have installed the latest Service Pack from Microsoft for
  Windows NT 4 before you install an Adaptec SCSI RAID controller and
  Adaptec drivers.
  
-----------------------------
Windows 2000
  
* When the system restarts from Hibernate mode, a Dr. Watson error
  referencing the Event Logger service (DPTELOG.EXE) is reported. Use
  the Services control panel to restart the service and the system
  will operate normally. You can avoid this problem by stopping the
  service before entering Hibernate mode. This will be fixed in a
  future release.
  
* If you are upgrading to Windows 2000 from Windows NT 4 and an Adaptec
  SCSI RAID controller is part of your configuration, run the
  W2KPREP.EXE utility before you start the upgrade. If necessary this
  utility makes a single modification to the Windows NT registry to
  ensure a successful upgrade with an Adaptec controller. W2KPREP.EXE is
  on the Adaptec SCSI RAID CD-ROM or the Windows 2000 diskette created
  from the CD-ROM.


============================================================
Peripheral Devices

* Seagate ST136475FC disk drives with microcode version 003 can cause
  erratic system operation when under I/O load. This can result in the
  operating system failing to respond to user input.
  
  Adaptec has tested microcode version 0415 which resolves this problem.
  This microcode is not yet released by Seagate.
  
* nStor CR8F enclosures using Seagate ST39173FC disk drives may
  experience a condition that prevents some or all of the drives from
  being recognized by an Adaptec controller. If this condition occurs, 
  use SMOR to change the SmartROM Configuration "Scan Delay" parameter
  from Default to 10. This will cause the controller to wait 10
  seconds before scanning the bus for devices.

* Ricoh Model 6200S CD-R drives may not operate correctly with
  Adaptec SCSI RAID controllers.
    
  When you initiate a recording test using Adaptec EZ CD Creator
  (version 3.5), the test will fail and abort the recording session.
  You should be able to record data to a CD successfully if the Create
  function is used instead of the combined Test/Create operation.


============================================================
Motherboards and Computer Systems:

* A Dell PowerEdge 1300 system will hang during Windows NT boot if a
  2100S controller is installed in PCI slots 4 - 6. To avoid this
  problem, install the Adaptec SCSI RAID controller in slots 1 - 3
  only.

* Iwill BD100 motherboards using Award BIOS 4.51PG (Iwill release
  31310A) are not compatible with Adaptec controllers that have more than
  64MB of cache memory.
  
* A computer system or motherboard does not need to be I2O compliant
  to support Adaptec SCSI RAID controllers. However, a machine that is
  not I2O compliant may display "Unknown PCI Device in Slot x" during
  it's system power-on self test (POST). Even if your system displays
  "Unknown PCI Device in Slot x" or something similar, your system or
  motherboard may still be compatible with Adaptec SCSI RAID controllers.

* Abit BH6 and BX6 Motherboards

  - These motherboards are not compatible with the Adaptec 3000S controller
    when a Battery Backup Module is attached.
  
* AOpen

  - AOpen MX3W motherboard (Intel Celeron and Award 6.00PG BIOS) does
    not reboot successfully when Windows NT 4 Service Pack 5 or 6a are
    installed. The system will operate normally when no service pack
    has been applied.
  
* Compaq

  - Deskpro EN series systems (Compaq BIOS 686T3) will report a
    "101-Option ROM Checksum error" during startup if an Adaptec 
    2100S is installed in a higher PCI slot than an Adaptec 29160
    SCSI adapter. To avoid this problem install the 2100S in a
    lower slot number than the Adaptec 29160 controller.
  
  - Proliant systems do not complete initialization of Adaptec SCSI
    RAID controllers that have less than 16MB or more than 128MB of cache
    installed on one controller or a total of 128MB of cache installed
    across multiple controllers. This problem may be corrected by a
    newer BIOS version, contact Compaq for information about obtaining 
    a BIOS upgrade.

* Dell

  - For Dell PowerEdge 1300 systems, ensure that the Adaptec SCSI RAID
    controller is installed in PCI slots 1 - 3 only. Using slots 4 - 6
    can result in the system failing to boot properly.
    
* Intel

  - Systems using an Intel CC820 motherboard are unable to boot from
    CD-ROM when the CD-ROM drive is attached to an Adaptec SCSI RAID
    controller.
  
  - Systems using an Intel CC820 motherboard and Adaptec SCSI RAID
    controller may not be able to access SMOR during system boot. If
    this occurs, reboot the system and when the second "Hit Ctrl-A"
    message appears, use the Alt+D key combination to start SMOR. If
    you are still unable to start SMOR, contact your technical support
    representative.
    
  - Systems using an Intel SC450NX motherboard and 2100S controller
    will take an extended period of time (approximately 2 minutes) to
    initialize. After the controller initializes, the system will
    continue to boot normally.

  - An Intel OCPRF100 system will not boot using the onboard Symbios
    SCSI controller when an Adaptec SCSI RAID controller is
    installed in PCI slot 6. If you want to boot from a disk drive
    using the onboard Symbios controller:
    
      Install the controller in any other available slot.
    
      Set the SMOR SmartROM Configuration parameter Bootable Devices 
      to Disabled.
    
  - Systems using Intel SC450NX, MB440LX, N440BX, NL440BX and AK450NX
    motherboards will not boot successfully if:
    
      There are two or more Adaptec SCSI RAID controllers and the
      total cache across all controllers is greater than 320MB.
    
      One controller with more than 128MB of cache is installed.
    
    This cache limitation is caused by the Intel system BIOS; ensure
    that you are using the most recent BIOS version.

* On some Asus motherboards if an Adaptec SCSI RAID controller is found
  first, any subsequent DPT SmartRAID IV controllers are ignored by SMOR
  if they have a RAID accelerator is attached. This problem does not occur
  when a DPT SmartRAID IV controller is the first one found or when using
  a DPT PM3754U2 controller.

* Adaptec SCSI RAID controllers are PCI Bridge devices, and if properly
  recognized by the motherboard or system BIOS, will be identified as
  a "PCI Bridge Adapter" (or something similar) during your system power
  on self-test.

<-End of Release Notes->