*****************************************************************
* *
* *
* SCSI Software Drivers/Utility Diskette *
* *
* Copyright (c) 1993 BusLogic Inc. *
* *
* Release 2.00 7/27/1993 *
* *
* *
*****************************************************************
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", 5.25", or both formats.
The diskettes contain the software device drivers and configuration
files for the BusLogic family of SCSI host adapters.
Included are:
DISK #1 Drivers for
- MS-DOS V3.3x and above
- Netware/386 V3.11
- IBM OS/2 V1.30
- IBM OS/2 V2.0 and V2.1
Configuration files for
- EISA
- Micro Channel
DISK #2 (If supplied)
- SCO Unix Release 3.2.4 and ODT Version 2.0 SCSI adapter driver
The following are the list of files on these diskettes
Volume in Drive A is SW-190
README TXT 31335 ; This README file
DOS <DIR> ; Driver/Utility for DOS
NW311 <DIR> ; Driver for NetWare 386 v3.11
OS213 <DIR> ; Driver/Utility for IBM & MS OS/2 1.3
OS220 <DIR> ; Driver for IBM OS/2 2.x
CONFIG <DIR> ; Configuration for MCA & EISA adapter
Sub-directory of \DOS
BTDOSM SYS 15016 7-08-93 3:52p ; BusLogic DOS Device Manager
BTMDISK SYS 8471 7-08-93 3:54p ; BusLogic Extended Hard Disk Driver
BTCDROM SYS 12282 7-08-93 3:56p ; BusLogic SCSI CD-ROM Driver
BTFDISK EXE 36944 5-04-93 4:13p ; BusLogic Extended Hard Disk utility
MSCDEX EXE 25431 2-04-92 2:21a ; Microsoft CD-ROM Extention utility
Sub-directory of \NW311
BT311 DSK 22139 4-26-93 6:54p; Netware/386 SCSI Disk driver
BTASPI DSK 312 7-23-92 3:10p; BusLogic ASPI Support Manager
Sub-directory of \OS220
BTSCSI ADD 15794 5-25-93 8:29p; OS/2 2.x SCSI Adapter Driver
BTSCSI DDP 148 4-22-93 1:28p; Device Driver Profile
Sub-directory of \OS213
IBM <DIR>
MS <DIR>
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 <DIR>
IBM_130 ISA <DIR>
IBM_130 MCA <DIR>
CDROM <DIR>
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 configuration file for BT-74x
@0708 ADF 5861 3-08-93 2:44p; Micro Channel configuration file for BT-64x
*******************************************************************
* *
* BusLogic DOS Manager Version 2.00 *
* *
*******************************************************************
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 v2.00
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 /d rem : first card
DEVICE = C:\BTDOSM.SYS /p334 /d /i rem : second card if installed
DEVICE = C:\BTMDISK.SYS
If you have more than one SCSI host adapter installed in the system,
you need to installed BTDOSM.SYS for each SCSI host adapter with
different I/O port support.
The second card's driver must have the option "/i" added, to avoid conflict.
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 <port address> - 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<bus on time> - Valid bus on time can be between 02 and 15 usecs. The
value is in decimal. Default time is 11 usecs.
/f<bus off time> - 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
(BT40) from the parameter menu. You must HIDE the
CDROM Target-ID.
SCSI tartgets to hide from NetWare
<enter CD-ROM Target-ID>
Continue to complete the standard NetWare installation
2) BTMDISK.SYS V2.00
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 rem : first card
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 v2.00
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 rem : first card
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 v2.00
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/386 V3.11 Disk/ASPI Device Drivers Ver. 2.21 *
* *
*******************************************************************
BusLogic's Netware 3.11 driver - BT311.DSK,version 2.21, includes
support for SCSI-II Tagged Queuing. Two new command line switches are
available to support this feature, detailed below in the Addendum.
BusLogic's Netware v3.11 device driver supports BusLogics' ISA, EISA,
and Microchannel SCSI host adapters. BTASPI.DSK is BusLogics' ASPI Support
Manager.
In addition to standard NetWare disk support, the driver provides
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, and
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 BT311.DSK:
load bt311
To enable BusLogic ASPI support, load BT311.DSK followed by a load of
of the BusLogic ASPI Support Manager BTASPI.DSK:
load bt311
load btaspi
BTASPI.DSK may only be loaded once regardless of how many times you
load bt311.
"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 bt311 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 bt311 Exclude_IDs = 1,2
This would hide SCSI target 1 and target 2 from the operating system.
New SBackup Required
--------------------
NOTE: To run Novell's SBackup, you must download their new 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.
Addendum
--------
This is a special version of the BusLogic Netware 3.11 driver which
includes support for SCSI-II Tagged Queuing. Two new command line
switches are available:
"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 BT311 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 BT311 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 8. 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 BT311 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.
NOTE!!! The value assigned to MaxActive multiplied by the actual number of
devices attached to the Host Adapter (each Target/Lun is considered one
device) should NOT exceed 32 to avoid potential starvation of a device.
Example 1 -
The following 4 devices are attached:
Target 0 (Lun 0)
Target 2 (Lun 0)
Target 4 (Lun 0)
Target 5 (Lun 0)
You may set MaxActive as high as 8 since (4 devices x 8) = 32.
Example 2 -
The following 8 devices are attached:
Target 0 (Lun 0)
Target 2 (Lun 0)
Target 4 (Lun 0)
Target 5 (Lun 0)
Target 3 (Lun 0)
Target 3 (Lun 1)
Target 3 (Lun 2)
Target 3 (Lun 3)
Target 3 (Lun 4)
You may set MaxActive NO HIGHER than 4 since (8 devices x 4) = 32.
"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 BT311 LongTimeout
*******************************************************************
* *
* BusLogic SCSI Adapter Driver Ver. 1.12 for IBM OS/2 2.x *
* *
*******************************************************************
BusLogic's SCSI Adapter Driver BTSCSI.ADD Ver 1.10 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 OS220 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 \OS220\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.
**** New Command Line Switches ****
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:
/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.
/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: <enter>
CD \OS213\IBM <enter>
o Determine the location of the ram disk created
by the IBM install disk in the following manner:
Type:
DIR X: <enter>
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 <enter>
where drive is the ram disk drive letter identified in
the step above.
For ISA and EISA installations, type:
GO drive: ISA <enter>
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 <enter>
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: <enter>
CD \OS213\IBM\IBM_130.MCA <enter>
SECONDAR <enter>
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: <enter>
CD \OS213\IBM\IBM_130.ISA <enter>
SECONDAR <enter>
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 <enter>
o Type:
A:
CD \OS213\IBM\CDROM <enter>
COPY A:*.* C:\CDROM <enter>
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 <enter>
*******************************************************************
* *
* BusLogic SCSI Host Adapter Device Driver Ver. 1.40 *
* for SCO UNIX 3.2.4 & SCO ODT 2.0 *
* *
*******************************************************************
Diskette formatted: SCO UNIX 3.2.4 Boot-Time Loadable (BTLD Format)
The SCO UNIX 3.2.4 SCSI Host Adapter Device Driver diskette contains:
-rw-r--r-- 1 bin bin 159 Aug 10 1992 READ.ME
drwxr-xr-x 4 root other 64 Dec 08 1992 buslogic
drwxr-xr-x 2 root other 48 Dec 08 1992 install
/buslogic:
drwxr-xr-x 3 root other 48 Dec 08 1992 driver
drwxr-xr-x 2 root other 128 Apr 09 15:58 install
/buslogic/driver:
drwxr-xr-x 2 root other 128 Dec 08 1992 btk
/buslogic/driver/btk:
total 52
-rw-rw-rw- 1 bin bin 27 Jul 27 1992 Bootload
-rw-rw-rw- 1 bin bin 18489 Jul 26 11:45 Driver.o
-rw-rw-rw- 1 bin bin 24 Aug 05 1992 Master
-rw-r--r-- 1 root other 1745 Aug 10 1992 Space.c
-rw-r--r-- 1 root other 580 Aug 10 1992 Space.o
-rw-rw-rw- 1 bin bin 26 Apr 16 1992 System
/buslogic/install:
-rw-rw-rw- 1 bin bin 11 Mar 19 1992 bootstring
-rw-rw-rw- 1 bin bin 21 Aug 05 1992 btld
-rw-rw-rw- 1 bin bin 55 Apr 26 14:12 buslogic.name
-rwxrwxrwx 1 bin bin 74 Apr 26 10:13 copyright
-rw-rw-rw- 1 bin bin 21 Aug 05 1992 drivers
-rwxr-xr-x 1 root other 3629 Apr 26 14:04 postinstall
/install:
-rw-r--r-- 1 bin bin 25 Jul 09 1991 INSTALL
The installpkg utility is used to add the BusLogic BTLD package
to an already running SCO Unix System. Use SCO installpkg(ADM).
At the system prompt, type
installpkg <RETURN>
Wait for installpkg to display message
Confirm
Please insert the floppy disk.
....
Insert the BusLogic SCO UNIX BTLD diskette into floppy disk drive
and press <RETURN>
At the end "installpkg" will rebuild the SCO UNIX kernel
with BusLogic SCSI host adapter driver.
*******************************************************************
* *
* 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.
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.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.