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 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 directory: EISA Configuration Utility * * 2. files under the directory * * 3. files under the * * 4. files under the : NetWare 3.10 * * 5. files under the : NetWare 3.11/3.12/SFT-III * * 6. files under the : 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 : 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. : It contains EISA configuration file, overlay file, and advanced setup utility for MCS or other ECUs. 1.1. : (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 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. : 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. : 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. : 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. : 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. : 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. : 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 NOTE: if the diskette is of 720KB (3"1/2), replace the above commands with: cd /dev mv dsk/f0 dsk/f0.org ; mknod dsk/f0 b 2 164 mv rdsk/f0 rdsk/f0.org ; mknod rdsk/f0 c 2 164 1. At the prompt, type: installpkg 2. Press to choose to install from floppy driver 0 3. Press to install the driver 4. Press to choose the SCO UNIX is being installed 5. To have the newly built UNIX take effect, reboot the system 6. Restore the original filename modified in step <0> accordingly: cd /dev mv dsk/f0.org dsk/f0 mv rdsk/f0.org rdsk/f0 [Driver removal] To remove the driver, you can follow the procedures: 1. At the prompt, type removepkg 2. Type the corresponding number of: "EISASC Lock/Unlock Driver Package" 3. Press to remove the driver 4. To have the newly built UNIX take effect, reboot the system [Removable media support] This driver supports removable media like Magneto Optical drive. Upon successful installation, two utility files rmount and rumount will be found under /etc to replace original "mount" and "umount" commands. These two files lock/unlock medium before/after file system is mounted/un-mounted, preventing accidental replacement of medium. 9.2. ISC UNIX V 3.2 [Driver Installation] To install the driver, insert the working copy of the UNIX driver diskette in drive A: 1. At the prompt, type sysadm 2. Enter SYSTEM ADMINISTRATION and choose softwaremgmt option by typing: 5 3. Enter softwaremgmt and choose installpkg option by typing: 1 4. Enter density of the diskettes you are installing from and choose 360 KB (5"1/4 double density) option by typing: 2 5. Press to install the driver 6. Press to choose the ISC UNIX is being installed 7. Press to reboot the system To ensure the driver is properly installed, type the following command to check the driver listing: displaypkg [Driver Removal] To remove the driver, you can follow the procedures: 1. At the prompt, type removepkg 2. Type the corresponding number of: "EISASC Lock/Unlock Driver Package" 3. Press to remove the driver 4. Press to reboot [Removable Media Support] This driver supports removable media like Magneto Optical drive. Upon successful installation, two utility files rmount and rumount will be found under /etc to replace original "mount" and "umount" commands. These two files lock/unlock medium before/after file system is mounted/un-mounted, preventing accidental replacement of medium. A. ASPICD.EXE option setting for compatible CD-ROMs If your CD-ROM is compatible with other manufacturer and not recognized, you have to add one more option, i.e., /t:XXX. XXX is short for compatible manufacturer name. For example, if your DEC CD-ROM CDU-541 is compatible with SONY CDU-541 and not recognized by the previous command, you can try add one more option as follows: device=c:\aspi\aspicd.exe /d:cdrom0 /t:SON B. DEVICE.LST => This file shows a list about the devices tested and also special notices for some specific devices.