***************************************************************** * * * * * SCSI Software Drivers/Utility Diskette * * * * Copyright (c) 1993, 1994 BusLogic Inc. * * * * Release 2.0 6/4/1994 * * * * * ***************************************************************** The files for BusLogic Software Drivers are contained on one or two diskettes, depending upon the configuration of your driver package. These files are supplied on 3.5" diskette formats. The diskettes contain the software device drivers and configuration files for the BusLogic family of SCSI host adapters: BT-445, BT-54X BT-64X, BT-74X, BT-946. Included are: DISK #1 Drivers for - MS-DOS V3.3x and above - Netware/386 V3.11 and V3.12 - Netware/386 V4.00 and V4.01 - IBM OS/2 V1.30 - IBM OS/2 V2.0 and V2.1 Configuration files for - EISA Model 'B' Host adapter - EISA Model 'C' Host adapter - Micro Channel Host adapter The following are the list of files on these diskettes: INSTALL EXE 49904 6-07-94 11:36a ; Device Drivers Installation utility README TXT ; This README file DOS ; Driver/Utility for DOS NW31x ; Driver for NetWare386 v3.11 & v3.12 NW4x ; Driver for NetWare 386 v4.00/v4.01 OS213 ; Driver/Utility for IBM & MS OS/2 1.3 OS22X ; Driver for IBM OS/2 2.x CONFIG ; Configuration for MCA & EISA adapter Sub-directory of \DOS BTDOSM SYS 27040 6-07-94 11:35a ; BusLogic DOS Device Manager BTMDISK SYS 8812 6-07-94 11:36a ; BusLogic Extended Hard Disk Driver BTCDROM SYS 15065 6-07-94 11:37a ; BusLogic SCSI CD-ROM Driver BTFDISK EXE 38176 6-07-94 11:36a ; BusLogic Extended Hard Disk utility MSCDEX EXE 25361 9-30-93 6:20a ; Microsoft CD-ROM Extention utility Sub-directory of \NW31X BT31X DSK 26538 05-12-94 5:02p ; Netware V3.11/V3.12 Disk Driver BTASPI DSK 312 07-23-92 3:10p ; BusLogic ASPI Support Manager Sub-directory of \NW4X BT4X DSK 27171 05-12-94 5:05p ; Netware V4.00/v4.01 Disk Driver BT4X DDI 6139 03-17-94 11:08a ; Driver Description File BTASPI DSK 312 07-23-92 3:10p ; BusLogic ASPI Support Manager Sub-directory of \OS22X BTSCSI ADD 20162 04-07-94 4:03p ; OS/2 2.x SCSI Adapter Driver BTSCSI DDP 148 04-22-93 1:28p ;Device Driver Profile Sub-directory of \OS213 IBM MS Sub-directory of \OS213\MS SPARE001 SYS 6152 7-20-93 4:00p Sub-directory of \OS213\IBM GO CMD 1358 4-15-93 1:45p IBM_130 IBM_130 ISA IBM_130 MCA CDROM Sub-directory of \OS213\IBM\IBM_130 BASEDD01 SYS 33404 7-22-91 9:20a BASEDD02 SYS 36236 7-22-91 9:20a FLOPPY01 SYS 18173 7-22-91 9:28a ABIOS BID 15053 11-14-91 12:00p DISK TSD 9066 11-14-91 12:00p ESDI-506 BID 10946 11-14-91 12:00p FLOPPY02 SYS 16644 11-14-91 12:00p IOCONFIG SYS 4607 11-14-91 12:00p IORUN SYS 1359 11-14-91 12:00p IOS1X SYS 15289 11-14-91 12:00p STDDISK VSD 4432 11-14-91 12:00p SPARE001 SYS 6152 7-20-93 4:00p Sub-directory of \OS213\IBM\IBM_130.ISA COP_ISA CMD 1353 3-11-93 3:38p HARD_ISA CMD 412 1-29-93 2:57p SECONDAR CMD 793 4-15-93 1:50p Sub-directory of \OS213\IBM\IBM_130.MCA COP_MCA CMD 1436 3-11-93 3:38p HARD_MCA CMD 445 1-29-93 2:56p SECONDAR CMD 863 4-15-93 1:53p Sub-directory of \OS213\IBM\CDROM CDFS IFS 34855 11-14-91 12:00p CDROM TSD 3775 11-14-91 12:00p DENON VSD 6098 11-14-91 12:00p STDCDROM VSD 4997 11-14-91 12:00p UCDFS DLL 12240 11-14-91 12:00p Sub-directory of \CONFIG !BUS4201 CFG 8745 2-22-93 6:53p ; EISA cfg. file for BT-74x model 'B' !BUS4202 CFG 8745 2-22-93 6:53p ; EISA cfg. file for BT-74x model 'C' @0708 ADF 5861 3-08-93 2:44p ; MCA configuration file for BT-64x ******************************************************************* * * * BusLogic DOS Manager Version 3.11 * * * ******************************************************************* There are four programs (BTDOSM.SYS, BTMDISK.SYS, BTCDROM.SYS, BTFDISK.EXE), that support DOS Version 3.3x or above. These programs can be applied to all of the BusLogic SCSI host adapters. 1) BTDOSM.SYS v3.11 BTDOSM.SYS is the BusLogic DOS Device Manager that supports ASPI (Advance SCSI Programming Interface). The DOS application program uses the ASPI DOS Manager to communicate with the SCSI host adapter and to allow access to additional SCSI devices connected to the host adapter: - When the system is configured with more than two hard disk drives - When the system has more than one SCSI host adapter installed - When the configured SCSI hard disk has a Target ID other than 0 or 1 - When you want to support a SCSI tape device, and - When you want to support programs that use virtual memory (i.e., Microsoft Windows 3.1, Quarterdeck QEMM 386, Qualitas 386MAX). Configuring the BTDOSM.SYS DOS Device Manager: In order for the BusLogic ASPI DOS Manager files to be loaded whenever the system is booted, the CONFIG.SYS file must contain the following DEVICE=command. The format is as follows: DEVICE = [path]BTDOSM.SYS [optional switches] Example: CONFIG.SYS: BUFFERS = 20 FILES = 20 DEVICE = C:\BTDOSM.SYS /p330 /p334 /d rem : first & second cards DEVICE = C:\BTMDISK.SYS COMMAND LINE OPTIONAL SWITCHES: The following options are available at this time. You may add it into the BTDOSM.SYS driver to change the parameters of the host adapter. /p - Sets the I/O port address that the driver will use to communicate with the host adapter. This value is in HEX. Valid address are 330 (default), 334, 230, 234, 130,and 134 /d - This Option will display useful information about the attached SCSI target device. /l - This Option will enable support for SCSI logical units(LUNs) other than zero. The driver can recognize all eight possible SCSI LUNs on each target. /n - Valid bus on time can be between 02 and 15 usecs. The value is in decimal. Default time is 11 usecs. /f - Valid bus off time can be between 01 and 64 usecs. The value is in decimal. Default time is 4 usecs. /i - This option will disable the loading of the embedded INT 13 module. When specified, INT 13 calls are routed through the host adapter BIOS instead of INT 13 handler in BTDOSM.SYS (only for SCSI disks installed with the host adapter BIOS). /m - For NetWare 386 server installation from CDROM, you must add this option to BusLogic DOS Device Manager. During NetWare installation of BusLogic (BT4X) from the parameter menu. You must HIDE the CDROM Target-ID. SCSI tartgets to hide from NetWare Continue to complete the standard NetWare installation 2) BTMDISK.SYS V3.11 To access the SCSI hard disk devices that have a SCSI ID other than 0 or 1, you must install this extented hard disk driver. Otherwise, DOS cannot recognize them. The CONFIG.SYS file must contain the DEVICE=command. The format is as follows : DEVICE = [path]BTMDISK.SYS Example : DEVICE = C:\BTDOSM.SYS /p330 /d DEVICE = C:\BTMDISK.SYS The BTMDISK.SYS Extented Hard Disk Driver can support more than one BusLogic SCSI host adapter per system. COMMAND LINE OPTIONAL SWITCHES: /r<# of reserved logical drives> : This determines the number of logical drives that will be reserved for removable media. Valid value are 1 to 24. If not specified, the default number of reserved logical drives is 1. 3) BTCDROM.SYS v3.11 BusLogic SCSI CD-ROM device driver is compatible with Microsoft CD-ROM Extendtion v2.21. It required BTDOSM.SYS device driver loaded first. BusLogic SCSI CD-ROM device driver command line option switch: DEVICE=[path]BTCDROM.SYS [/D:MSCDxxx] [/L] Parameter: [path] Specified the pathname where the BusLogic CD-ROM Device Driver resides. (e.g. C:\BLCD_ROM) [/D:MSCDxxx] Specifies the name that Microsoft CD-ROM Extended (MSCDEX) use to find the CD-ROM Device Driver. You will use this name in configuring your AUTOEXEC.BAT file. [/L] Enable SCSI Logical Unit Number (LUN) support. If enable (LUN) option, you must enable (LUN) support in BTDOSM.SYS device driver. Example: BusLogic BTDOSM.SYS and BTCDROM.SYS device driver in CONFIG.SYS file. DEVICE = C:\BTDOSM.SYS /p330 /d DEVICE = C:\BTCDROM.SYS /D:MSCD002 The Microsoft CD-ROM Extention "MSCDEX.EXE" utility is required for DOS application to access the CD-ROM data files or sound. Syntax: MSCDEXE [/D:device name] [/L:drive letter] [/M:value][/V][/E] Parameter: [/D:device name] Must be same as the name specifies on BTCDROM.SYS command. [/L:drive letter] Assign DOS drive letter for CD-ROM [e.g., E,F,G,..] [/M:value] Number of sector buffers reseved for MSCDEX utility Switches: [/V] Display memory usage [/E] Use expanded memory if available Setup MSCDEX for DOS: Assume "MSCDEX.EXE" utility is on drive C: root directory, Device named for BusLogic BTCDROM.SYS device driver is "MSCD002", Drive letter referent by DOS = E:, number of sector buffers use by MSCDEX is 10, use Expanded memory if available, and display memory usage. Method #1: Auto load MSCDEX.EXE utility at boot time. You must add the following line to Autoexec.bat file C:\MSCDEX /D:MSCD002 /L:E /M:10 /V /E Method #2: Execute MSCDEX utility only when needed. At DOS comand prompt type the following C:\MSCDEX /D:MSCD002 /L:E /M:10 /V /E Support CD-ROM drives : 1. SONY CDU-541, CDU-561, CDU-6211 2. CHINON CDS-431, CDX-431, CDS-535, CDX-535 3. TOSHIBA XM-3301B, XM-3401B 4. HITACHI CR-3750 5. TEXEL DM-3024, DM-5024 6. NEC CDR-38, CDR-73, CDR-74, CDR-83, CDR-84, CDR-741, CDR-841 7. PANASONIC CDR-532 8. IBM 9. PIONEER DRM-600, DRM-604 10. Other CD-ROM drives which support SCSI-2 command sets Multisession Photo CD-ROM drives : 1. SONY CDU-6211 2. CHINON CDS-535, CDX-535 3. TOSHIBA XM-3401B 4. TEXEL DM-5024 5. NEC CDR-38, CDR-741, CDR-841 4) BTFDISK.EXE v3.11 The BusLogic Extented Hard Disk can be used to partition the SCSI disk devices, that has a SCSI ID of 0 through 7. Used the standard DOS FDISK utility to partition a hard drive with SCSI ID 0 or 1 attached to the first SCSI host adapter. This program is very similar to FDISK.EXE in DOS; however, it only supports SCSI hard disks, note that BTDOSM.SYS must be loaded first. To invoke BTFDISK.EXE, type BTFDISK at the DOS prompt. No optional switches are needed. ********************************************************************* * * * BusLogic NetWare V3.11/V3.12 Disk/ASPI Device Drivers Ver. 2.27 * * * * and * * * * BusLogic NetWare V4.00/V4.01 Disk/ASPI Device Drivers Ver. 1.27 * * * ********************************************************************* The following paragraphs describe the features and command line options supported by BusLogic's Netware 3.11/3.12 and Netware 4.00/4.01 drivers - BT31X.DSK and BT4X.DSK respectively. The examples contained in these paragraphs reference BT31X.DSK, our Netware 3.11/3.12 driver. If you are in a Netware 4.00 or 4.01 environment, please substitute BT4X.DSK wherever BT31X.DSK is referenced below. Also, please substitute Netware 4.x wherever Netware 3.1x is referred to. BusLogic's ASPI Support Manager, BTASPI.DSK, remains the same for both the Netware 3.1x and Netware 4.x platforms. NOTE!! Netware 4.00/4.01 contains a BusLogic device driver in the Red Box shrinkwrap - BT40.DSK. The driver on this diskette - BT4X.DSK is an update to that shrinkwrap driver. If you choose to use the update driver, you should copy it ALONG WITH the file BT4X.DDI (located in the same directory - NW4X - on the BusLogic Software Driver diskette) to whatever disk directory the older BusLogic driver (BT40.DSK) resides in. Note the name change: BT40.DSK changed to BT4X.DSK. You may also have to change existing STARTUP.NCF files which reference the old file name to reference the new driver. For new installations, you may install the update driver directly by choosing the INSERT option from the INSTALL menu when prompted for additional disk drivers - or you may install this driver when installation is completed as described immediately above. ALERT!!! If you are installing Netware 4.00/4.01 from CDROM, you MUST use the EXCLUDE_IDS command line switch (described in detail below) DURING Netware installation on the CDROM you are installing from!! BusLogic's Netware 3.11/3.12 driver - BT31X.DSK,version 2.27 - and BusLogic's Netware 4.00/4.01 driver - BT4X.DSK, version 1.27 - both include support for SCSI-II Tagged Queuing. BusLogic's Netware device drivers support BusLogics' ISA, EISA, Microchannel, VESA (Local Bus), and PCI Bus SCSI host adapters. BTASPI.DSK is BusLogics'ASPI Support Manager for Netware/386. In addition to standard NetWare disk support, the drivers provide the following features: 1) Removable device support (including fixed disk, MO, and CD-ROM) 2) ASPI support 3) NetWare ready support 4) Scatter/gather support 5) ISA host adapter support in a greater-than-16MByte-memory environment. ASPI support ------------ To use the BusLogic driver without ASPI support, simply load the BusLogic driver BT31X.DSK: load bt31x To enable BusLogic ASPI support, load BT31X.DSK followed by a load of of the BusLogic ASPI Support Manager BTASPI.DSK: load bt31x load btaspi BTASPI.DSK may only be loaded once regardless of how many times you load BT31X. "Over16Meg" Switch ------------------ If you wish to run one or more ISA (BT-542B) BusLogic host adapters in a system with more than 16 MBytes of memory, Then you must use the following switch on the FIRST load of the BusLogic driver. load bt31x Over16Meg The presence or absence of this command line switch on subsequent loads of the driver will be ignored. When the "Over16Meg" switch is invoked, the following line should be added to your STARTUP.NCF file to enlarge the pool of available buffers below 16 MBytes: set Reserved Buffers Below 16 Meg=200 "Exclude_IDs" Switch -------------------- If you wish to exclude one or more Disk or CDROM SCSI devices from being reported to Netware when they are found by the BusLogic driver, you may use this option to do so. These devices can then be reserved for ASPI Netware applications such as: - Disk array software that needs to present several SCSI devices as a single logical device to the operating system - Third party software that controls CD-ROM devices through an ASPI interface. To specify which devices to hide on this host adapter, enter one or more SCSI target ID separated by commas. For example, enter: load bt31x Exclude_IDs = 1,2 This would hide SCSI target 1 and target 2 from the operating system. *** Netware 3.11 only *** New SBackup Required ----------------------------------------------- NOTE: Under Netware 3.11, to run Novell's SBackup, you must download a later version from CompuServe. The version shipped with NetWare V3.11 looks specifically for Adaptec's Aspitran module and will not work with any other ASPI manager such as BTASPI.DSK from BusLogic. To download the new version, type "go novlib" in CompuServe. Then browse on keyword "Sbackup" in file library 1 to find the appropriate file. Note: This applies to Netware 3.11 ONLY. Other versions of Netware come with BusLogic-compatible versions of SBackup. "Enable_TQ" Switch ------------------ Tagged Queuing is an advanced SCSI-II feature which allows overlapped commands to a SCSI device, thus enhancing performance. The BusLogic SCSI Host Adapters provide support for this feature. However, many SCSI devices do not, and both the host adapter and the SCSI device must support Tagged Queuing in order to take advantage of this feature. The BusLogic SCSI Disk Driver defaults to Tagged Queueing DISABLED for all devices on all BusLogic Host Adapters. Use the ENABLE_TQ switch to enable Tagged Queueing on a given BusLogic Host Adapter: load bt31x Enable_TQ This will only affect those SCSI devices connected to this Host Adapter which also support Tagged Queueing. The maximum number of Tagged requests outstanding is specified by MaxActive switch described below. "MaxActive" Switch ------------------ This switch allows you to modify the maximum number of outstanding requests per device allowed at any one time: load bt31x MaxActive=2 Modification of this parameter will allow you to tune the driver for maximum performance based on your specific configuration. Valid values are 1 through 60. If this switch is not specified, the default is value is 1. If you specify the MaxActive switch in conjunction with the Enable_TQ switch, the MaxActive switch will actually control the maximum number of Tagged Queue requests outstanding: load bt31x Enable_TQ MaxActive=4 If you specify the MaxActive switch without specifying the Enable_TQ switch, the MaxActive switch will actually control the maximum number of non-tagged requests outstanding (queued at the Host Adapter, rather than at the device, level). In this case, best performance may be achieved by using the default value. For Disk Array applications, assignment of larger values to MaxActive may result in optimal performance. "LongTimeout" Switch --------------- This switch allows you to increase the amount of time the driver's watchdog timer routine will wait before attempting to abort a CCB which has not finished. The default (if this switch is not invoked) is 10 seconds. If the switch is invoked, the timeout value is increased to 60 seconds. Only special hardware applications which anticipate long periods of time during which a device may remain busy will find this switch useful. In general, it should be ignored. load bt31x LongTimeout "No_Rescan" Switch --------------- This switch should be used in conjunction with ASPI applications when specifically recommended by the ASPI software vendor/supplier. Otherwise, it should be IGNORED. *** ASPI Developers *** : This switch has the effect of causing the ASPI Get Device Type SRB to return table-driven information about the devices detected during an initial scan. Using the switch will inhibit the ASPI manager from going back out on the SCSI bus to look for the specified device on behalf of this SRB type. The absence of the switch causes the ASPI manager to issue a SCSI inquiry on behalf the the specified device. Syntax is as follows: load bt31x no_rescan "Verbose" Switch --------------- This switch has the effect of enabling display information about specific driver configuration options. ******************************************************************* * * * BusLogic SCSI Adapter Driver Ver. 1.30 for IBM OS/2 2.x * * * ******************************************************************* BusLogic's SCSI Adapter Driver BTSCSI.ADD Ver 1.20 runs under both IBM OS/2 2.0 and IBM OS/2 2.1. Hereafter these two versions of OS/2 will be referred to as OS/2 2.x. Before installing the BusLogic OS/2 2.x SCSI Adapter Driver, you must fully install OS/2 2.x. You are able to do this out of the box because IBM ships a generic "Int 13" driver that will get you through the installation. Once OS/2 is installed and you have rebooted OS/2 from the hard disk following the installation, you can install the BusLogic driver using one of the two following methods: Method A - Automatic Method --------------------------- 1) Insert the BusLogic diskette in Drive A:. Either: a) Choose the System Setup icon from the OS/2 Desktop, then choose the Device Driver Install icon from the System Setup icon view screen or .. b) Type DDINSTAL at the system prompt (This will invoke the same icon as above). 2) Click on the Change button of the Source directory. 3) Select the OS22X directory and click on the Set button. 4) Click on the Install button, select the BusLogic driver, and then click on OK. The installation and modification to CONFIG.SYS will be performed automatically. Method B - Manual Method ------------------------ 1) Copy the BusLogic files \OS22X\BTSCSI.ADD over to the \OS2 directory on the C: boot drive. 2) Edit C:\CONFIG.SYS you can invoke E - the IBM OS/2 editor that is automatically installed and after invoking the IBM OS/2 editor, add the following line: BASEDEV = BTSCSI.ADD The system will find the driver in the \OS2 directory. If you plan on using CDROM.SYS or OPTICAL.SYS from IBM, you must also add the following line to C:\CONFIG.SYS: BASEDEV = OS2SCSI.DMD Once you have completed either method of driver installation, you must reboot for changes to take effect. BusLogic's OS/2 2.x Adapter Device Driver supports the following command line switches: /V - Verbose switch. This switch enables driver verbosity at initialization time. /A:x - Adapter identification switch. x is between 0 and 5 and identifies the adapter being referenced. This switch is followed by one of the switches below describing the enabling/disabling of tagged queuing support. /DM:xx - DASD Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied DASD Manager (OS2DASD.DMD). /SM:xx - SCSI Manager Support switch. As defined by IBM, this switch enables/disables support for this unit by the IBM-supplied SCSI Manager (OS2SCSI.DMD). /BON:xx & /BOFF:xx - Bus On / Bus Off switches. x is between 2 and 15 and specifies the desired bus on/bus off time in microseconds. Tagged queuing is an advanced SCSI-II feature that allows overlapped commands to a SCSI device, this results in enhanced performance. While BusLogic provides support for this important SCSI-II feature, not all SCSI devices support tagged queuing. Both the host adapter and the SCSI device must support tagged queuing to take advantage of this feature. BusLogic's OS/2 2.x SCSI Adapter Driver defaults to tagged queuing DISABLED on all devices. For devices that support tagged queuing, the following command line switches are provided to manage tagged queuing support: /TQ - Enable tagged queuing support on ALL targets on the specified host adapter (specified by the receding /A: switch) that supports tagged queuing. If this switch is specified and the specified host adapter supports tagged queuing (revision 3.30 firmware and above), then tagged queuing is enabled. /TQ: x,y,z,... - Enable tagged queuing support on a specified list of SCSI targets. x,y,and z is a list of embedded SCSI targets separated by commas. The Logical Unit Number (LUN) is presumed to be 0. /TQ: (a,b), (c,d), ... - Enable tagged queuing support on a specified list of pairs of SCSI targets/LUNs in parenthesies. Each parenthesied pair is separated by commas. Examples: 1) BASEDEV = BTSCSI.ADD /A:0 /TQ This example enables tagged queuing on host adapter 0 on all targets that support it. Targets attached to host adapter 0 that do not support tagged queuing are not affected. 2) BASEDEV = BTSCSI.ADD /A:0 /TQ /A:1 /TQ This example enables tagged queuing on all targets on host adapters 0 and 1 that support it. Targets attached to host adapters 0 and 1 that do not support tagged queuing are not affected. 3) BASEDEV = BTSCSI.ADD /A:0 /TQ: 0,2,3 /A:2 /TQ: 0,1 This example enables tagged queuing on targets 0,2, and 3 on host adapter 0 and on targets 0 and 1 on host adapter 2. If any of the specified targets are not attached or do not support tagged queuing, specification of those particular devices is ignored. 4) BASEDEV = BTSCSI.ADD /A:0 /TQ: (0,0),(2,1) This example enables tagged queuing on target 0 LUN 0 and target 2 LUN 1 on host adapter 0. If any of the specified target/LUN combinations are not attached or do not support tagged queuing, specification of those particular devices is ignored. ******************************************************************* * * * BusLogic LADDR Support for IBM and MS OS/2 1.3 Ver. 1.20 * * * ******************************************************************* This installation note outlines the steps needed to install BusLogic's OS/2 1.3 LADDR device driver under IBM OS/2 version 1.3. The installation procedure will "ladderize" the IBM OS/2 system. Ladderizing replaces the original IO subsystem on your OS/2 Install diskette or OS/2 installed system with a LADDR IO subsystem. The first section discusses installing the BusLogic driver at the time of initial OS/2 1.3 installation. The following sections discuss adding the BusLogic driver (and host adapter(s)) to an existing OS/2 1.3 system. In this case, (called a secondary installation) remember to: *** Make a complete backup of your boot volume *** before attempting to ladderize. 1) BusLogic SCSI Host Adapter as Intended Boot Adapter This set of instructions assumes NO existing OS/2 1.3 system. It assumes you are doing an initial installation of OS/2 1.3 onto a disk supported by a BusLogic SCSI host adapter. o Backup (Diskcopy) the OS/2 installation disk - it will be modified during this procedure. o Boot the backup copy installation disk. o At the first full screen when asked: "Enter to continue Or Escape to Exit" hit Escape. o After the A:\ prompt appears, remove the installation disk. o Insert the BusLogic SW-190 installation disk. o Type: A: CD \OS213\IBM o Determine the location of the ram disk created by the IBM install disk in the following manner: Type: DIR X: where X is a drive letter ,starting with C and continuing with ascending drive letters (i.e., C,D,E,...) UNTIL the following message appears: SYS0015: The system cannot find the drive specified. The ram disk is the drive letter immediately BEFORE the current drive letter value. Examples: If DIR D: is the first drive letter to produce the error message above, then the ram disk is drive C:. If DIR E: is the first drive letter to produce the error message above, then the ram disk is drive D:. o For Microchannel installations, type: GO drive: MCA where drive is the ram disk drive letter identified in the step above. For ISA and EISA installations, type: GO drive: ISA where drive is the ram disk drive letter identified in the step above. o When prompted to, remove the BusLogic SW-190 install disk and insert the OS/2 installation disk. The OS/2 installation disk will now be modified. Use this modified installation diskette for the rest of the installation. o Reboot the machine. o Continue as instructed with the installation. o At the very end of the normal system installation, when the message "Remove the floppy from drive A:" appears, reinsert the modified installation diskette. o Reboot the machine. o At the first full screen when asked: "Enter to continue Or Escape to Exit" o hit Escape. o Type: HARD.cmd This program copies the proper files to the hard disk. Failure to complete this step will result in a TRAP when attempting to boot from the hard disk. o Ladderized Installation is now Complete ! Reboot the machine. 2) BusLogic MCA SCSI host adapter as Secondary (non-boot) Device This set of instructions assume an existing OS/2 1.3 system to which you wish to add one or more BusLogic MicroChannel SCSI host adapters. WARNING!!! Back up the existing system before continuing to the next step! o Under OS/2, create an OS2 command window. o Insert the BusLogic 1.30 driver install disk in drive A: o Type: A: CD \OS213\IBM\IBM_130.MCA SECONDAR o Ladderized Installation is now Complete ! Reboot the machine. 3) BusLogic ISA or EISA SCSI host adapter as Secondary (non-boot) Device This set of instructions assume an existing OS/2 1.3 system to which you wish to add one or more BusLogic ISA or EISA SCSI host adapters. WARNING!!! Back up the existing system before continuing to the next step! o Under OS/2, create an OS2 command window. o Insert the BusLogic 1.30 driver install disk in drive A: o Type: A: CD \OS213\IBM\IBM_130.ISA SECONDAR o Ladderized Installation is now Complete ! Reboot the machine. 4) Adding CDROM support o Install as described above. o Insert the BusLogic SW-190 install disk in drive A: o Type: MD C:\CDROM o Type: A: CD \OS213\IBM\CDROM COPY A:*.* C:\CDROM o Edit config.sys - Insert the following three lines starting at the first line of the file (or second line if the first line is "IFS=C:\OS2\HPFS.IFS /cache:64"): IFS=C:\CDROM\CDFS.IFS DEVICE=C:\CDROM\STDCDROM.VSD DEVICE=C:\CDROM\CDROM.TSD o Exit your editor and type: COPY C:\CDROM\UCDFS.DLL to C:\OS2\DLL ******************************************************************* * * * BusLogic SCSI Host Adapter Configuration Files for * * EISA and Micro Channel * * * ******************************************************************* The configuration files for both the EISA and Micro Channel are under the sub-directory \CONFIG. !BUS4201.CFG EISA configuration file for BusLogic SCSI host adapters BT-74x. model 'B' !BUS4202.CFG EISA configuration file for BusLogic SCSI host adapters BT-74x. model 'C' Copy this configration file into your EISA System Configration/Setup diskette. Refer to the appropriate hardware installation guide to install your BusLogic SCSI host adapter. @0708.ADF Micro Channel configuration file for BusLogic SCSI host adapters BT-64x. Copy this configration file into your Micro Channel System Configration/Setup diskette. Refer to the appropriate hardware installation guide to install your BusLogic SCSI host adapter.