=============================================================================
                             INTRODUCTION
=============================================================================

Congratulations on purchasing your new Adaptec AHA-3985 Multichannel PCI RAID
Adapter.  This board provides RAID solutions at an unprecedented
price/performance.  

NOTE:  If you are having trouble booting your AHA-3985, please check if your
system motherboard provides PCI-PCI bridge support.  The AHA-3985 will not
function in systems without bridge support.  If you believe your system does
have bridge support, refer to the 'Troubleshooting Guide' at the end of this
readme.

=============================================================================
                             INSTALLATION
=============================================================================

This disk contains Adaptec's Novell and DOS Drivers and Utilities for the
AHA-3980/3985 RAID Host Adapter.   The AHA-3980 has two SCSI channels and the
AHA-3985 has three SCSI channels. 

DOS drivers are only necessary for connecting to a CD-ROM, typically used for
installation of NetWare.  If you already have NetWare installed, or will be
installing NetWare from floppy, you do not need to install the AHA-3985 DOS
drivers.

NetWare drivers are used by the RAID driver and for connecting standard
NetWare devices to the  AHA-3980/3985 host adapter.  RAID Utilities are
included for creation and management of the RAID devices.  

WARNING: The AHA-3980/3985 is currently not supported for operating systems
other than NetWare.  If you attempt to install an operating system with
embedded driver support for the Adaptec AIC-7870, such as OS/2 2.1 or NT 3.5,
it will find the three AIC-7870 chips on the AHA-3985 and attempt to load
the driver.  Although this embedded driver may load, it is untested and 
unsupported for use on the AHA-3985 and WILL NOT provide any RAID
functionality.


All the files on the floppy are compressed except INSTALL.BAT, README.TXT
and EXPAND.EXE in the root directory.  INSTALL.BAT will install the files on
the C: drive.
          To install NetWare version 3.1x files type
                   install 3 
          at the a: prompt.

          To install NetWare  version 4.xx files type
                   install 4 
          at the a: prompt. 

INSTALL.BAT will create C:\AHA398X and then copy DOS and the appropriate
version of NetWare files.

WARNING: IF PREVIOUS INSTALLATION EXISTS, THIS BATCH FILE WILL OVERWRITE
THE EXISTING INSTALLATION. IT IS USER'S RESPONSIBLITY TO BACKUP PREVIOUS
INSTALLATION.

=============================================================================
                     FILES COPIED TO C:\AHA398X
=============================================================================

c:\aha398x\readme.txt           This file
c:\aha398x\dos\readme.txt       Readme for DOS drivers
c:\aha398x\dos\config.sys       Template for CD-ROM driver installation
c:\aha398x\dos\autoexec.bat     Template for CD-ROM
c:\aha398x\dos\aspi8dos.sys     ASPI driver
c:\aha398x\dos\aspicd.sys       ASPI CD driver
c:\aha398x\dos\aspidisk.sys     ASPI Disk driver
c:\aha398x\dos\afdisk.exe       ASPI Partitioning utility
c:\aha398x\dos\afdisk.hlp
c:\aha398x\dos\afdisk.cwa
c:\aha398x\dos\3980cfg.exe      SCSISelect executable
c:\aha398x\netware\readme.txt   Readme for NetWare drivers
c:\aha398x\netware\aha3980.dsk	
c:\aha398x\netware\aspicd.dsk
c:\aha398x\netware\aruadmin.nlm
c:\aha398x\netware\arumon.nlm
c:\aha398x\netware\aru.msg
c:\aha398x\netware\arulib.nlm
c:\aha398x\netware\arusched.nlm
c:\aha398x\netware\aruver.nlm
c:\aha398x\netware\arucvt.nlm
c:\aha398x\netware\arurec.nlm
c:\aha398x\netware\arufmt.nlm
c:\aha398x\netware\arudrv.def
c:\aha398x\netware\aha3980.ddi  (NetWare 4.x only)
c:\aha398x\netware\mcim.dsk
c:\aha398x\netware\ardrvr.dsk
c:\aha398x\netware\aspitran.dsk

=============================================================================
                        TROUBLESHOOTING GUIDE
=============================================================================

NOTE:  This troubleshooting guide is currently written for the AHA-3940.
Since many of the issues of bridge support are common with the AHA-3985, it
is applicable.  Future versions of this readme will be written specifically
for the AHA-3985.  The PCICHK.EXE and CFBRIDGE.SYS files referred to are
available on the Adaptec Tech Support BBS.


               AHA-3940 Supplemental Troubleshooting Guide 
               -------------------------------------------

This file contains additional troubleshooting tips that may not have been
included in the User's Manual.  It is intended to assist those who are having
difficulties getting their system to boot up with the AHA-3940.  In addition,
you should find in your kit a diskette containing two files, PCICHK.EXE and
CFBRIDGE.SYS.  These two files will be very useful in assisting you
troubleshoot your problem.

After you have installed your host adapter, you should be looking for the
following things as the system boots up:

          Adaptec BIOS Header Message.
          Inquiry information such as the make and model number of 
               SCSI devices that the Adaptec BIOS detected.
          Message indicating whether or not the BIOS installed 
               successfully.

Here is an example of what you should be seeing on your screen as the system
boots up:

          Adaptec AHA-3940/3940W BIOS v1.14
          (c) 1994 Adaptec, Inc. All Rights Reserved.

          Press <Ctrl><A> for SCSISelect (TM) Utility!

          SCSI ID #0 - Seagate  12550N          - Drive C:      (80h)
          SCSI ID #2 - Quantum  Maverick 540S   - Drive D:      (81h)
          SCSI ID #3 - Toshiba  CD_ROM:XX3355
          SCSI ID #4 - Archive  VIPER  150   21247

          BIOS Installed Successfully!

If you don't see the Adaptec BIOS Header Message at all, then:

   System BIOS may not have PCI to PCI bridge support.  Call your system
   manufacturer.

   System BIOS may not be properly assigning the I/O and memory space for
   PCI agents and bridges.  Call your system manufacturer for a possible
   update on the motherboard BIOS.

   The slot for your AHA-3940 may not be enabled; check your CMOS Setup
   program to see if there is an option there to enable a PCI device in
   slot X.  If you are not sure which slot you have the host adapter in,
   then just enable PCI device in all the slots displayed in your CMOS Setup
   program.  Note that on the Phoenix BIOS, only one slot is displayed at
   a time.  You can change the displayed slot on the screen by pressing a
   key.  Refer to the motherboard manual.
 
   Try booting from a DOS bootable diskette.  Insert the diskette containing
   PCICHK.EXE and then type PCICHK at the DOS prompt.  PCICHK.EXE is a DOS
   program that will check for the most common PCI compatibility problems
   found on motherboards.  If PCICHK.EXE finds no PCI to PCI Bridge
   initialized, then the AHA-3940 may not work at all in your system. 

   If you plan to use the AHA-3940 as a NON-BOOT host adapter, then you still
   may be able to use the AHA-3940 in your system.  If this is the case, then
   locate the diskette containing CFBRIDGE.SYS.  Copy CFBRIDGE.SYS to your
   DOS boot disk.  Create a CONFIG.SYS which will load CFBRIDGE.SYS as the
   first device driver during boot up.  The file, CFBRIDGE.SYS, is a DOS
   device driver that will attempt to initialize and configure the PCI to PCI
   Bridge and the 7870 devices behind it.  If it loads successfully, then the
   AHA-3940 can be used as a secondary host adapter.  You will need to
   install additional software necessary for your operating system to support
   the AHA-3940 and your SCSI devices.  Note that the CFBRIDGE.SYS driver
   will work ONLY on systems where the motherboard BIOS is properly routing
   all the PCI INTx# lines to the system interrupt controller.

If the Adaptec BIOS Header Message appears, but the message Host Adapter
Configuration Error comes up, then:

   Check interrupt channel(s) assignment in your CMOS Setup program; make
   sure the PCI slot for the AHA-3940 is assigned to an available IRQ.
   (This is typically how you would configure interrupts if your system BIOS
   is from Phoenix or Award.)

   If your system has a combination of ISA or EISA boards and PCI boards, you
   need to mark the IRQs used by ISA/EISA boards as USED so that the system
   BIOS will not try to assign these IRQs to PCI devices.  The other IRQs
   should be marked as AVAILABLE.  (This is typically how you would configure
   interrupts if your system BIOS is from AMI.)

   Check if there are interrupt jumpers on the motherboard.  If so, then make
   sure the IRQ setting in the CMOS Setup program matches the motherboard
   jumper settings.

   Check the documentation for your system if it supports interrupt channels
   other than INT A#; if not, then only channel A on the AHA-3940 can be
   utilized.  Channel B on the AHA-3940 is routed to INTB# on the PCI bus and
   channel A is routed to INT A# on the PCI bus.

   All PCI interrupts must be level sensitive.

   Try booting from a DOS bootable diskette.  Insert the diskette containing
   PCICHK.EXE and then type PCICHK at the DOS prompt.  Check to see if the
   interrupt test passed for the 7870 devices.  

If you don't see the Inquiry information from the SCSI devices then:

   Slot is not bus mastering.

   Slot is not enabled for master; check CMOS setting and enable all slots
   for bus mastering.

  Check cabling, connections, and physical hardware setup.

  Check if chipset is OPTI or SiS; if so, call Adaptec Tech Support for more
  information.

If you have SCSI devices attached to both channel A and channel B, but do not
see any Inquiry information from those devices attached to channel B, then:

   Move the SCSI devices on channel B to channel A.  If all the SCSI devices
   come up, then the cable used for channel B could be bad.  Also, check
   termination.

   Check if system supports interrupt channels other than INT A#.  Channel B
   on the AHA-3940 is routed to INT B# on the PCI bus.  Load ASPI8DOS.SYS and
   pay attention to the interrupt level value that it reads for channel B on
   the AHA-3940.  If its 0, then the system may not be capable of supporting
   any interrupt channels on the PCI bus other than INT A#.  The other
   possibility is that the system BIOS may not be properly routing the INT B#
   line to the system interrupt controller.  In either case, only channel A
   on the AHA-3940 is usable.

   Try booting from a DOS bootable diskette.  Insert the diskette containing
   PCICHK.EXE and then type PCICHK at the DOS prompt.  Check to see if the
   interrupt test passed for the 7870 devices.

If the Adaptec BIOS installs successfully, but hangs as the operating system
loads, then:

   Check if there are interrupt jumpers on the motherboard.  If so, then make
   sure the IRQ setting in the CMOS Setup program matches the motherboard
   jumper settings.

   All PCI interrupts must be level sensitive.

   Try booting from a DOS bootable diskette.  Copy ASPI8DOS.SYS from the
   EZ-SCSI diskette to your boot diskette.  Create a CONFIG.SYS which will
   load ONLY ASPI8DOS.SYS during boot up.  Pay attention to the messages from
   ASPI8DOS.SYS, especially the Inquiry information from the SCSI devices.
   Run PCICHK.EXE to get more information and make note of all the tests that
   passed or failed.

If the Adaptec BIOS installs successfully and finds all your devices, but
ASPI8DOS.SYS is not finding any 7870 devices, then:

   Call Adaptec Tech Support or BBS for an updated version of ASPI8DOS.SYS.
   Use EZ-SCSI 3.11 or later.

If ASPI8DOS.SYS loads successfully and you see the Inquiry information from
all of your SCSI devices, but are still having some problems, then:

   Call your system manufacturer to verify if system has full PCI to PCI
   bridge support. 

   Call Adaptec Technical Support.  Prior to calling, please be sure to have
   the following information:

      Chipset manufacturer (e.g. SiS, Intel, OPTi, ALI, UMC, VLSI, EFAR, etc.)
      and chipset number.

      System BIOS manufacturer and BIOS version (e.g. AMI, Award, Phoenix,
      etc.)

      Processor and speed (e.g. Pentium, 486, etc.)

      Video Card/Chip used.

      Adaptec BIOS version.  This is indicated in the Adaptec BIOS Header
      Message.

      All information reported by PCICHK.EXE.
