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

Files in this diskette:

ASPI126.SYS  ----- ASPI driver for DC-123/DC-126/DC-126B
ASPI226.SYS  ----- ASPI driver for DC-226
HDDRIVER.SYS ----- Disk driver for SCSI disk/removable cartridge/
                   re-writable optical disk
CHKDRIVE.EXE ----- Disk device driver checking utility
TRMFDISK.EXE ----- Disk partition utility
ASPICD.EXE   ----- Device driver for CD-ROM
<NETWARE.311> ---- Netware V3.11 driver (DC-226):
                      . DC-226.DSK   -- DC-226 driver
                      . ASPITRAN.DSK -- ASPI interface driver
                   Duplexing Utility for Netware 3.1x
                      . GENCCM.EXE   -- utility for generating CCM sector
<NETWARE.310> ---- Netware V3.10 driver (DC-226):
                      . DC-226.DSK   -- DC-226 driver
                      . ASPITRAN.DSK -- ASPI interface driver
readme/SCO UNIX -- Installation procedure of SCO UNIX driver (DC-226)
readme/ISC UNIX -- Installation procedure of ISC UNIX driver (DC-226)

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

Outline of this readme.txt file:
O.    Introduction to ASPI drivers
I.    Install the ASPI driver
II.   Install the HDDRIVER.SYS
III.  TRMFDISK.EXE
IV.   CHKDRIVE.EXE
V.    ASPICD.EXE
VI.   Tape System supports
VII.  Readme file Netware
VIII. Readme file of SCO UNIX
IX.   Readme file of ISC UNIX

O. Introduction to ASPI drivers

DOS uses the ASPI driver to communicate with the SCSI host adapter and allow
access to additional SCSI devices connected to the host adapter.

The ASPI driver is typically installed under the following situations:
@  two adapters coexist (refer to Sec. I: Install the ASPI driver)

@  more than two hard disk drives are already installed, if logical link is
   enabled, then more than "three" (refer to Sec. II: Install the
HDDRIVER.SYS)

@  install removable media (refer to Sec. II: Install the HDDRIVER.SYS)

@  interface to Tape & CD-ROM systems (refer to Sec. V & VI)



I. Install the ASPI driver

   O. Two ASPI drivers available, ASPI126.SYS for DC-123/126/126B &
      ASPI226.SYS for DC226.

      With ASPI driver installed, you can run or install the following drivers:
        TRMFDISK.EXE    --- Disk partition utility in this diskette
        HDDRIVER.SYS    --- Disk driver in this diskette
        AFDISK.EXE      --- Disk partition utility from ADAPTEC
        APSIDISK.SYS    --- DIsk driver from ADAPTEC
        SYTOS PLUS      --- Tape backup program from SYTRON CORP.
        SYTOS V3.x      --- Tape backup program from SYTRON CORP.
        ARCserve/Solo   --- Tape backup program from Cheyenne CORP.

       (Other utilities/drivers conform to ASPI standard may also be used.)

      Before installing, copy the driver and utility into a proper directory,
      e.g. C:\ASPI.

   1. Install the DC-123/DC-126/DC-126B or DC-226 properly

   2. Add a line in config.sys

        device=c:\aspi\aspi126.sys      for DC-123/DC-126/DC-126B
        device=c:\aspi\aspi226.sys      for DC-226

   3. One or two adapters can be installed as either primary or secondary.
      Examples of configuration and device driver installation are:

      (a). One adapter

        DC-123 or DC-126 or DC-126B

                device=c:\aspi\aspi126.sys

        DC-226

                device=c:\aspi\aspi226.sys

      (b). Two adapters

        Primary controller   = DC-123 or DC-126 or DC-126B
        Secondary controller = DC-126 or DC-126B

                device=c:\aspi\aspi126.sys

        Primary controller   = DC-226
        Secondary controller = DC-226

                device=c:\aspi\aspi226.sys

        Primary controller   = IDE(AT bus)/ST506 or ESDI
        Secondary controller = DC-126 or DC-126B

                device=c:\aspi\aspi126.sys

        Primary controller   = IDE(AT bus)/ST506 or ESDI
        Secondary controller = DC-226

                device=c:\aspi\aspi226.sys

        Primary controller   = DC-123 or DC-126 or DC-126B
        Secondary controller = DC-226

                device=c:\aspi\aspi126.sys
                device=c:\aspi\aspi226.sys

        Primary controller   = DC-226
        Secondary controller = DC-123 or DC-126 or DC-126B

                device=c:\aspi\aspi226.sys
                device=c:\aspi\aspi126.sys

        Primary controller   = ADAPTEC HOST adapter
        Secondary controller = DC-123 or DC-126 or DC-126B

                device=c:\aspi\aspi4dos.sys             ( from adaptec )
                device=c:\aspi\aspi126.sys

        Primary controller   = ADAPTEC HOST adapter
        Secondary controller = DC-226

                device=c:\aspi\aspi4dos.sys             ( from adaptec )
                device=c:\aspi\aspi226.sys

        Primary controller   = DC-226
        Secondary controller = ADAPTEC HOST ADAPTER

                device=c:\aspi\aspi226.sys
                device=c:\aspi\aspi4dos.sys             ( from adaptec )

        Primary controller   = DC-123 or DC-126 or DC-126B
        Secondary controller = ADAPTEC HOST ADAPTER

                device=c:\aspi\aspi126.sys
                device=c:\aspi\aspi4dos.sys             ( from adaptec )


   4. Other combinations are possible if:
        a. Adapter BIOS address does not conflict
        b. Adapter I/O address does not conflict
        c. Install the jumper properly for DC-XXX controller as primary
           or secondary controller. Refer to DC-XXX user manual for proper
           jumper setting.

   5. Two options might be helpful when other adapters are installed with
      DC-123/126(B)/226. Since some other adapters might fail to response the
      checking command issued by the DC-xxx, the system or the other adapter
      could hang. This problem does not happen to all the adapters. But if it
      does, please try the following options:
        a. /p: scan the primary controller only, this is for the case that you
               install the DC-xxx as primary and other card as secondary.
        b. /s: scan the secondary controller only, this is for the case that you
               install the DC-xxx as secondary and other card as primary.


II. Install the HDDRIVER.SYS

   HDDRIVER.SYS is for installing valid DOS partitions as logical drives with
   those disk drives not being installed under the host adapter BIOS. That
   means HDDRIVER.SYS will be used to recognize those drives not defined
   by host adapter BIOS.

   For instance, your DC-XXX BIOS might see SCSI ID 0 & 1 for C:, in logical
   link case, and ID 2 for D:. So if you want to install some more hard disk
   drive(s), SCSI ID could be 3-7, then HDDRIVER.SYS must be installed,
   e.g.
       two more fixed disks want to be installed, SCSI ID = 5 & 6:
       a) install HDDRIVER.SYS, and the ASPI drivers will take over the drives
          of SCSI ID 5 & 6 from now on,
       b) do the low-level format, if necessary,
       c) install TRMFDISK.EXE, if newly added drive(s) is used by other card
          before,
       d) => DOS sees drives of SCSI ID = 0, 1, & 2,
             ASPI sees drives of SCSI ID = 5 & 6.

       if one more adaptor needs to be installed:
       a) set this adaptor as "secondary",
       b) set the "Hard disk device C: (D:)/Disk parameter setup" as
          "non-installed".



   HDDRIVER.SYS can also control fixed disk, removable cartridge and
   re-writable optical disk.

   1. Add a line AFTER ASPI driver

      device=c:\aspi\aspi226.sys ( or aspi126.sys )
       --> device=c:\aspi\hddriver.sys /d n1 n2 n3 ... n8

      HDDRIVER.SYS can control up to 8 physical drives
      or up to 16 partitions ( logical drives )
      It is recomended that DOS 4.x or DOS 5.x be used. DOS 3.x can also be
      used, but logical drive capacity is limited under 32M bytes.


   2. About /d option
      If you want to reserve logical drive for a physical disk, use /d option,
      e.g. device=c:\aspi\hddriver.sys /d n1 n2 n3 ... n8

        n1 logical drives is reserved for 1st physical drive
        n2 logical drives is reserved for 2nd physical drive
        n3 logical drives is reserved for 3rd physical drive
        ....
       (nx -> x = 1 .. 8 & value of nx is between 0 and 9)
       (the ordering of physical drives starts from primary -> secondary & SCSI
        ID 0 -> 7)

      *************************************************************************
      The following is an example of two host adaptors with 8 physical drives
      and two fixed disk drives (SCSI ID 0 & 1), set as C: and D:,
      respectively:
           i) Adapter 0 (Primary)
              SCSI ID 7: This SCSI Controller
              SCSI ID 0: Fixed Disk  (C:)
              SCSI ID 1: Fixed Disk  (D:)
              ( both C: & D: are controlled thru WD-1003 emulation mode, and
                thus ignored by ASPI driver )

              SCSI ID 2: Fixed Disk   --> 0 logical drives reserved (n1=0)
              SCSI ID 3: Fixed Disk   --> 0 logical drives reserved (n2=0)
              SCSI ID 4: Removable
                         Cartridge    --> 2 logical drives reserved (n3=2)
              SCSI ID 5: Fixed Disk   --> 0 logical drives reserved (n4=0)
              SCSI ID 6: Rewritable
                         Optical Disk --> 3 logical drives reserved (n5=3)

              ( drives of SCSI ID 2-6 now are controlled by ASPI driver )

           ii) Adapter 1 (Secondary)
              SCSI ID 7: This SCSI Controller
              ( the "Hard disk device C: (D:)/Disk parameter setup" is set as
                "Non-installed" )

              SCSI ID 2: Fixed Disk   --> 0 logical drives reserved (n6=0)
              SCSI ID 4: Fixed Disk   --> 0 logical drives reserved (n7=0)
              SCSI ID 6: Removable
                         Cartridge    --> 9 logical drives reserved (n8=9)

              ( drives of SCSI ID 2, 4, & 6 now are controlled by ASPI driver )

           Therefore, the line you add in the "config.sys" would be like
           this:
           device=c:\aspi\aspi226.sys ( or aspi126.sys )
           --> device=c:\aspi\hddriver.sys /d 0 0 2 0 3 0 0 9
      *************************************************************************

      If "nx=0" or without /d option  ==> The driver will check the valid
      logical drive(s) for those removable media at boot time, if with
      disk or cartridge in them. If without, there will be no logical drive
      reserved, i.e. nx=0.

      Since some of the Fixed Disk drives might have more than one logical
      drives, the limitation of maximum 16 partitions should be taken care
      of.


   3. For removable media ==>
      Use DOS 4.x or DOS 5.x SHARE utility for automatic LOCK/UNLOCK.
      This can be done by adding "share.exe" in your "autoexec.bat" file.
      LOCK/UNLOCK would be very important for data integrity.

      If "share.exe" file is added, then the system will LOCK your medium when
      opening a file and UNLOCK it when you close it. This will prevent
      the data from being destroyed by improper operation on your devices.


   4. Disk parameter setup
      Since HDDRIVER.SYS will scan the parameters from master boot record of
      your drives automatically, you can install any other drives used in
      other SCSI adapters before without any inconsistency. And therefore,
      there is no need to set drive parameters explicitly.

      If you want to transfer the DC-XXX drives to any other adapters, please
      select a proper parameter translation method. Refer to TRMFDISK.EXE
      section for details.

   5. Logical drive's sequence
      HDDRIVER.SYS scans drives starting from adapter #0, SCSI ID = 0,
      primary partition, and then extended partition.

      The SCSI ID used for drive C: D: or linked drives will not be recognized
      by HDDRIVER.SYS, if DC-126/DC-126B/DC-226 is configured as primary
      controller. But if the adapter is set as secondary, you have to install
      HDDRIVER.SYS and also set the options of C:/D: as "non-installed" in your
      DC-XXX in order to sense the drives hooked on this adapter.

      For DC-123, which can only be configured as primary controller, the
      SCSI ID #0 (drive C:) and #1 (drive D:) are always excluded by
      HDDRIVER.SYS

        e.g.
        logical drives
                A:      floppy
                B:      floppy
                C:      INT 13h controlled hard disk ( SCSI or IDE .. )
                D:      INT 13h controlled hard disk
                E:      Adapter 0 SCSI ID 1, primary DOS
                F:      Adapter 0 SCSI ID 1, extneded DOS's logical drive
                G:      Adapter 0 SCSI ID 1, extended DOS's logical drive
                H:      Adapter 0 SCSI ID 5, primary DOS
                I:      Adapter 1 SCSI ID 2, primary DOS

      CHKDRIVE.EXE utility can be used to check the logical drives controlled
      by HDDRIVER.SYS. Refer to CHKDRIVE.EXE section.


   6. For removable media, the cartridge can be retrieved at any time if
      no file is opened. Cartridge change is transparent to user. The DOS
      logical drives information will be updated automatically every time you
      change the cartridge, if the one you change is different from the
      previous one.


III. TRMFDISK.EXE

     Valid DOS partition are created with DOS FDISK or TRMFDISK.EXE.

     For those drives can not be recognized by DOS, that also means you need to
     install ASPI driver at this moment, TRMDISK.EXE is used to do the job.

     TRMFDISK.EXE is a DOS compatible disk partition program, you have to
     install ASPI driver before running this utility, i.e. add a line in
     "config.sys" file:
        device=c:\aspi\aspi126.sys      for DC-123/DC-126/DC-126B
        device=c:\aspi\aspi226.sys      for DC-226

     You can choose the desired translation method by simply typing
     TRMFDISK.EXE at the DOS prompt. Its four options are shown below:

     a) Automatic translation method (default)
        This method reads parameter from master boot record and uses it. If no
        parameter exists in master boot record, the ADAPTEC translation method
        will be used.

     b) ADAPTEC translation method
        Heads     = 64
        Sectors   = 32
        Cylinders = xxx depends on drive's capacity

     c) TEKRAM translation method
        This is the DC-XXX's BIOS default translation method
        Heads     = 8/16
        Sectors   = 26/32/48/63
        Cylinders = xxx depends on drive's capacity

        (the head # and Sector # will be calculated automatically, and can not
         be modified manually)

     d) Mylex translation method
        Heads     = 16
        Sectors   = 63
        Cylinders = xxx depends on drive's capacity


     After partitioning the disk, it is necessary to reboot the system for
     proper operation.

     It would be helpful if your drives are used before and partitioned by one
     of the above methods.

     For removable devices, you can use /d option to reserve logical drives.
     After partitioning the disk, just make a disk change ( i.e. retrieve the
     cartridge and then insert again ) to DOS. You can use CHKDRIVE.EXE to
     check if the partition has been changed.

IV. CHKDRIVE.EXE

    This utility can be used to check physical drive and logical status.
    Drive status can be:
        reserved by /d option
        unformatted
        usable

    A unformatted logical drive must be formatted by DOS FORMAT utility first.


V. ASPICD.EXE

   This driver is for CD-ROM devices:
   1. Add a line after ASPI driver
      device= c:\aspi\aspi226.sys
      -> device= c:\aspi\aspicd.exe  /d:trmcd

      note: aspicd.exe still needs one execution file "mscdex.exe" from Micro-
            soft. Add a line in "autoexec.bat" file:
      -> c:mscdex.exe /d:trmcd /m:10


VI. Tape System supports

    After installing the ASPI driver, refer to Section I: Install the ASPI
    driver, your DC-XXX can support the following tape backup systems under DOS:

        SYTOS PLUS      --- Tape backup program from SYTRON CORP.
        SYTOS V3.x      --- Tape backup program from SYTRON CORP.
        ARCserve/Solo   --- Tape backup program from Cheyenne CORP.


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

VII. Readme file of Netware

"DC226.DSK" & "ASPITRAN.DSK" are drivers supporting DC-226 under Netware
V3.1x. Sever-based backup and removable media are supported [V3.11 only].
Refer to README file under <Netware.31x> for further details.

"GENCCM.EXE" is the Duplexing Utility for Netware V3.1x. It uses the Novell
CCM (Common Configuration Method) to enable the recognition of secondary ISA
disk controller. Please also refer to its "readme" file under <NETWARE> for
furhter details.

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

VIII. Readme file of SCO UNIX

This SCO UNIX driver is in the SCO/ISC UNIX drivers diskette. Currently the
supported OS versions are 3.2v1, 3.2v2 and 3.2v4.

<DRIVER INSTALLATION>

To install the driver, insert the working copy of the UNIX driver diskette in
drive A:.

A) At the prompt, type

        installpkg

   >> NOTE : As some minor bug in the command "installpkg"(for 3.2v2),  <<
   >>        it may take a while for the system to response, and DO NOT <<
   >>        hit any key during this period.                            <<

B) press <Enter> to install from floppy driver 0

C) press <Enter> to install the driver

D) press <Enter> to choose the SCO UNIX is being installed

E) select which OS version you are using

F) select item according to your system configuration

G) type two "y" to make the newly built kernel as the default boot unix

H) reboot the system


<DRIVER LISTING>

To ensure the driver is installed, type

        displaypkg


<DRIVER REMOVAL>

To remove the driver,

A) At the prompt, type

        removepkg

B) type the corresponding number of:

   "DC226 SCSI Controller Driver Package"

C) press <Enter> to remove DC226 driver

D) press <Enter> to reboot


<REMOVABLE MEDIUM SUPPORT>

This driver supports removable media like Magnetic Opticals.
Upon successful installation, two utility files "rmount" and "rumount"
will be found under /etc to replace original "mount" and "umount".
These two files lock/unlock medium before/after file system is
mounted/un-mounted, preventing accidental replacement of medium.

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

IX. Readme file of ISC UNIX


This Interactive UNIX driver is in the SCO/ISC UNIX diskette.

<DRIVER INSTALLATION>

To install the driver, insert the working copy of the UNIX driver diskette in
drive A.

A) At the prompt, type

        sysadm

B) Enter "SYSTEM ADMINISTRATION" & choose "softwaremgmt" option by typing:

        5

C) Enter "softwaremgmt" and choose "installpkg" option by typing:

        1

D) "Enter density of the diskettes you are installing from" & choose 1.2 MB
   ("5 1/4" high density) option by typing:

        1

E) press <Enter> to install the driver

F) press <Enter> to choose the ISC UNIX is being installed

G) select item according to your system configuration

H) press <Enter> to reboot the system


<DRIVER LISTING>

To ensure the driver is installed, type

        displaypkg


<DRIVER REMOVAL>

To remove the driver,

A) At the prompt, type

        removepkg

B) type the corresponding number of:

   "DC226 SCSI Controller Driver Package"

C) press <Enter> to remove DC226 driver

D) press <Enter> to reboot


<REMOVABLE MEDIUM SUPPORT>

This driver supports removable media like Magnetic Opticals.
Upon successful installation, two utility files "rmount" and "rumount"
will be found under /etc to replace original "mount" and "umount".
These two files lock/unlock medium before/after file system is
mounted/un-mounted, preventing accidental replacement of medium.
