This driver diskette contains one EISA configuration directory and five other
driver directories for DOS, Windows NT and NetWare. OS/2 driver is under ROOT
directory.

A DOS driver installation file (INSTALL.EXE), which resides in the <DOS>
directory, can help you install the drivers by auto-updating the AUTOEXEC.BAT
& CONFIG.SYS files. A file, DEVICE.LST, is also included to list the device
tested.

The other driver diskette that contains LOCK/UNLOCK driver packages for SCO and
ISC is UNIX-formatted and cannot be read from DOS. Therefore, their
installations are described in this README.TXT file. These two UNIX drivers are
useful to removable media devices.


********************************************************************************
*									       *
*  In this diskette							       *
*  							       *
*									       *
*  This readme file provides information for:				       *
*  0.	 Addendum or Re-emphasizing some of the points that people may need to *
*	 pay more attention to						       *
*  1.	 files under the <CF> directory: EISA Configuration Utility	       *
*  2.	 files under the <CD_APPS> directory				       *
*  3.	 files under the <DOS>						       *
*  4.	 files under the <NETWARE.310>: NetWare 3.10			       *
*  5.	 files under the <NETWARE.31x>: NetWare 3.11/3.12/SFT-III	       *
*  6.	 files under the <NETWARE.40X>: NetWare 4.00/4.01/4.02		       *
*  7.	 files under the root directory for OS/2 v2.0/2.1/2.11/WARP 3.0        *
*  8.	 files under the <WINNT.3X>: Windows NT 3.1/3.5 		       *
*  9.	 UNIX LOCK/UNLOCK utility					       *
*  A.	 ASPICD.EXE options						       *
*  B.	 DEVICE.LST file: list of devices tested			       *
*									       *
********************************************************************************


0. How to do with:
	A. ">1GB HDD support under assorted operating systems"

	The following is the table indicating how to support >1GB HDD under
	assorted operating systems with properly settings on "Max DOS disk
	Capacity" & "DOS 5 Support Enabled/Disabled" options. It also shows
	when the installation of device driver is a MUST under different O.S.

Ŀ
 O.S.		    DC-8x0/3x0   "Max DOS disk  "DOS 5         Tekram     
		    SUPPORT >1G   Capacity"      Support"      driver     
		   		   option	   option	  INSTALLED? 
Ĵ
 DOS		   	 Yes	 	> 1G	    Enabled	     No      
 (Windows & WFWG) 		 		 		 	      
Ĵ
 OS/2 V2.x/3.0 *  	 Yes	 	1G	    Disabled	     Yes     
Ĵ
 WINDOWS NT V3.X     Not Yet	 	1G	    Disabled	     No      
Ĵ
 NETWARE V3.1X    	 Yes	 	1G	    Disabled	     Yes     
Ĵ
 NETWARE V4.0X    	 Yes	 	1G	    Disabled	     Yes     
Ĵ
 SCO UNIX 3.2V4.0 	 Yes	 	1G	    Disabled	     No      
Ĵ
 SOLARIS V2.4	   	 Yes	 	1G	    Disabled	     No      
Ĵ
 UNIXWARE V1.1    	 Yes	 	1G	    Disabled	     No      
Ĵ
 NEXTSTEP V3.1 **    Not Yet	 	1G	    Disabled	     No      


 *  "OS/2 v2.x/3.0 + >1GB HDD" => It needs special care to achieve this. You are
    able to work with >1GB HDD by specifying <1GB capacity for the PRIMARY
    partition and leave the rest of the HDD capacity as the EXTENDED
    partition. Its procedure may look like this:
	1. During installation, specify your own installation partition and not
	   the PRE-DEFINED partition.
	2. You can then create partition for less than 1024MB.
	3. Re-boot the system and install DC-3x0/8x0's OS/2 driver.
	4. Re-boot and use FDISK to create the rest of HDD space as EXTENDED
	   partition.
 ** AHA-1542C has the same constraints for supporting >1GB HDD at this moment.


1. <CF>: It contains EISA configuration file, overlay file, and advanced setup
	 utility for MCS or other ECUs.

	1.1. <MCS>: (advanced utility already included)
		    a. DC-820B => copy both the !TRM820B.CFG and TRM820B.OVL
				 into your ECU diskette.
		    b. DC-320E => copy both the !TRM320E.CFG and TRM320E.OVL
				 into your ECU diskette.
	1.2. <OTHER>: (other ECUs, such as AMI ... etc.)
		    a. DC-820B => copy both the !TRM820B.CFG and ACF20SU.EXE
				 into your ECU diskette.
		    b. DC-320E => copy both the !TRM320E.CFG and ACF20SU.EXE
				 into your ECU diskette.
	Note:
	Both the !TRM320E.CFG and !TRM820B.CFG of \CF\OTHER subdirectory work
	without TRM320E.OVL and TRM820B.OVL under ALL ECUs. The original
	functions of TRM320E.OVL and TRM820B.OVL are supported by ACF20SU.EXE.

2. <CD_APPS>: This directory contains files to support "Audio + Photo"
   functions for CD-ROM devices under Windows environment. Please refer to the
   README.CD in this directory for installation.

3. <DOS>: It contains ASPI drivers and utilities for both DC-320E and DC-820B.

	3.1. ASPIBME.SYS : ASPI driver for DC-320E/820B
	3.2. DISKDRV.SYS : ASPI driver for HDD and removable media devices
	3.3. TFDISK.EXE  : DOS compatible disk partition utility
	3.4. TOOLBME.EXE : low-level format, mirroring initialization, disk
			   image copy/compare, & error logging utilities
	3.5. CHKDRIVE.EXE: logical drives status checking utility
	3.6. ASPICD.EXE  : CD-ROM driver
	3.7. INSTALL.EXE: This is a DOS driver installtion utility that helps
			  you install the device drivers for HDD, removable
			  media, CD-ROM, and tape by auto-updating the
			  CONFIG.SYS and AUTOEXEC.BAT files.

4. <NETWARE.310>: It contains drivers for Netware v3.10.

	4.1. NV310BME.DSK: disk driver / ASPI manager.
	4.2. BELOW16.DSK: memory allocator for memory below 16 Meg.
	4.3. ASPITRAN.DSK: ASPI transport layer driver.

5. <NETWARE.31X>: It contains drivers for Netware v3.11/v3.12/SFT-III.

	5.1. NV31XBME.DSK: disk driver / ASPI manager.
	5.2. ASPITRAN.DSK: ASPI transport layer driver.

6. <NETWARE.40X>: It contains drivers for Netware v4.00/v4.01/4.02.

	6.1. NV40XBME.DDI: installation configuration file.
	6.2. NV40XBME.DSK: disk driver / ASPI manager.
	6.3. ASPITRAN.DSK: ASPI transport layer driver.

7. OS/2: It contains 4 files under the root directory of this driver
	 diskette and is for OS/2 versions 2.0/2.1/2.11/WARP 3.0.

	7.1. README.OS2 : Procedures for driver Installation and Removal
	7.2. TRMSCSI.EXE: Execution file for DDINSTAL
	7.3. TRMSCSI.ADD: SCSI Device Driver
	7.4. TRMSCSI.DDP: SCSI Device Driver Profile

8. <WINNT.3x>: It contains drivers for Windows NT v3.1/3.5

	8.1. README.NT	 : Procedures for driver Installation and Removal
	8.2. OEMSETUP.INF: Setup Information File
	8.3. DCSCSI.SYS  : SCSI Driver
	8.4. DCSCSI	 : Setup Tag File (Due to the constraint from NT, this
					   file must be resided under ROOT
					   directory. This is the reason why
					   you'd find another exact file under
					   the ROOT directory.)

9. UNIX LOCK/UNLOCK driver package installation: These two drivers for SCO/ISC
   UNIX are in the other diskette. Since the UNIX driver diskette is
   UNIX-formatted, it is unrecognizable under DOS.

   (** If you want to check the files in the UNIX driver diskette, you can use
       the following commands: cpio -ivtI /device_name.
       E.g. Under SCO UNX 3.2.4:
	    => cpio -ivtI /dev/rdsk/f0d9d (for 360KB 5"1/4 diskette)
	    => cpio -ivtI /dev/rdsk/f03d  (for 720KB 3"1/2 diskette)
       For other UNIX systems, you may use the same command but have to use the
       corresponding device_name for your driver diskette
    **)

	9.1. SCO UNIX V.3.2.2 (** similar function is default supported by SCO
			       UNIX V.3.2.4 **)
	     [Driver installation]
	     To install the driver, insert the working copy of the UNIX driver
	     diskette in drive A:

		0. To prepare the installation for 360KB (5"1/4) driver
		   diskette, you must type:
		   cd /dev
		   mv dsk/f0 dsk/f0.org ; mknod dsk/f0 b 2 132
		   mv rdsk/f0 rdsk/f0.org ; mknod rdsk/f0 c 2 132
elow e 132
		   m    sk/f0 .defaultow e 1,npacitow     faultow e 1,npacit    	   m    sk    ohis
		 te /dev
		n360KB (5"1/4y   [Driow e 1,o	   diskette,Iw e w. SCO cin360KB (5"g

9(** If you want to chepare thA:kette,IwRsk/f0 IaSuOsKB (5on for 360KB ( o,
   U
9(5on for .1/2.11/d+
Eriver w e w. ung devicm  for 360KBA
elow e 132
		   m    sfof t m,oation]
	     To install the driver, insert the workio"f./nd utile th the !TRM820B.CFG and TRM82pn]
	        *
ette contains one EISA configuration   rectory and f    other
	        rectories for DOS, Windows NT and NetWare. OS/2
	      ]
und   ROOT
	 rectory.

A DOS
	      ]nstallation file (INSTALL.EXE), which resides in the <DOS>
	 rectory, can help you ]nstall the 	     s by auto-updating the AUTOEXEC.BAT
& CONFIG.SYS files. A file, DEVICE.LST, ]
also ]ncluded to list the 	evice
tested.

Th  other
	        *
ette that contains LOCK/UNLOCK
	      packages for SCO and
ISC ]
UNIX-formatted and cannot be read from DOS. Th refore, their
]nstallation
are 	escribed in th]
README.TXT file. Th se two
UNIX 	     s are
useful to removable media 	evices.


********************************************************************************
*									       *
*  In th]
  *
ette							       *
*  							       *
*									       *
*  pn]
readme file provides information for:				       *
*  0.	 Addendum or Re-emphasizing some of the points that people may need to *
*	 pay more attention to						       *
*  1.	 files
und   the <CF>   rectory: EISA Configuration Utility	       *
*  2.	 files
und   the <CD_APPS>   rectory				       *
*  3.	 files
und   the <DOS>						       *
*  4.	 files
und   the <NETWARE.310>: NetWare 3.10			       *
*  5.	 files
und   the <NETWARE.31x>: NetWare 3.11/3.12/SFT-III	       *
*  6.	 files
und   the <NETWARE.40X>: NetWare 4.00/4.01/4.02		       *
*  7.	 files
und   the root   rectory for OS/2
v2.0/2.1/2.11/WARP 3.0        *
*  8.	 files
und   the <WINNT.3X>: Windows NT 3.1/3.5 		       *
*  9.	 UNIX LOCK/UNLOCK
utility					       *
*  A.	 ASPICD.EXE option
						       *
*  B.	 DEVICE.LST file: list of 	evices tested			       *
*									       *
********************************************************************************


0. How to do with:
	A. ">1GB HDD support
und   assorted operating systems"

	Th  following is the table indicating how to support
>1GB HDD und  
	assorted operating systems with properly se