Release: ASC.ADD 2.3.6
Last Updated: 2/26/95
Copyright (c) 1995-1996 Advanced System Products, Inc.
The SIIG OS/2 Universal Driver supports all the SIIG SCSI
Adapters listed below for the OS/2 2.1 and OS/2 Warp Releases. The
installation directions below apply to OS/2 Warp.
The OS2 directory includes the following files. The latest versions
of these files are maintained on the SIIG FTP and BBS sites. If
the date listed in this file is more than a few months old, please
check the FTP or BBS site for a newer version of the driver.
OS2.TXT This File
ASC.ADD SIIG Universal SCSI Adapter Device Driver
PRASC.EXE Presence Check Program (Only needed for desktop install)
PRASC.DDP Presence Check Definition File (Only needed for desktop install)
Supported Adapters
==================
The CDB counts below indicate the number of SCSI CDB (Command
Descriptor Block) requests that can be stored in the RISC chip
cache and board LRAM. The driver detect routine will display the
number of CDBs available for each adapter detected. This value
can be lowered in the BIOS by changing the 'Host Queue Size'
adapter setting.
Connectivity Products:
ABP920 - Bus-Master PCI 16 CDB
ABP930 - Bus-Master PCI 16 CDB
ABP5140 - Bus-Master ISA 16 CDB
ABP5150 - Bus-Master ISA 240 CDB *
Single Channel Products:
ABP542 - Bus-Master ISA 240 CDB
ABP742 - Bus-Master EISA 240 CDB
ABP842 - Bus-Master VL 240 CDB
ABP940 - Bus-Master PCI 240 CDB
Dual Channel Products:
ABP950 - Dual Channel Bus-Master PCI 240 CDB Per Channel
ABP852 - Dual Channel Bus-Master VL 240 CDB Per Channel
ABP752 - Dual Channel Bus-Master EISA 240 CDB Per Channel
* This board is shipped by HP with the 4020i CD-R drive. It has
no BIOS so it cannot control a boot device, but it can control
any secondary devices.
SIIG ASC.ADD Device Driver Installation for OS/2 Warp
=========================================================
Directions for installing the driver to a new system:
-----------------------------------------------------
1. Obtain the OS/2 Warp CD-ROM installation kit with the
following items:
a. IBM OS/2 Warp "Installation Diskette for CD-ROM"
b. IBM OS/2 Warp "Diskette for CD-ROM (1)"
c. IBM OS/2 Warp CD-ROM
2. Make a back-up copy of the diskette "Diskette for CD-ROM (1)".
This diskette must be modified to install the ASC driver.
3. The file ASC.ADD must be added to the diskette "Diskette for
CD-ROM (1)". Make space on the diskette by removing at least two
of the following driver files. Don't remove any drivers that you
have Adapter Cards for in your system. These are all drivers for
other SCSI Adapter Cards.
DPT20XX.ADD, BTSCSI.ADD, AHA152X.ADD, AHA154X.ADD, AHA164X.ADD,
AHA174X.ADD, AIC7770.ADD, AIC7870.ADD
4. Use a text editor to add the line "BASEDEV=ASC.ADD" as the last
line of the file CONFIG.SYS on the "Diskette for CD-ROM (1)".
Remove or comment out with REM the BASEDEV lines in CONFIG.SYS
for the driver files that you removed from the diskette.
5. Insert the "Installation Diskette for CD-ROM" into drive A:,
insert the install CD-ROM into the CD-ROM drive, and install
OS/2 by following the IBM OS/2 installation instructions.
6. After the OS/2 Installation has completed, install the driver
from the OS/2 Desktop by following the "Directions for installing
the driver to an existing system", Step A. Alternatively you can
install the driver manually following Step B.
Directions for installing the driver to an existing system:
-----------------------------------------------------------
Follow (A) for installing from the OS/2 Desktop or (B) for installing
from the OS/2 Command Line Desktop. It is recommended that (A) be used
because it is simpler to perform. Use either method of installation,
but don't use both.
A. From the OS/2 desktop:
1. Boot up the existing OS/2 system.
2. Insert the SIIG driver diskette in drive A:.
3. Select "System Setup" in the "OS/2 System" icon. Select
"Device Driver Install" and follow the directions
to install the driver. Specify the OS2 directory on
the diskette as the "Source Directory".
4. If you would like to add options to the ASC.ADD command
line in the CONFIG.SYS file, use a text editor (tedit)
from an OS/2 Window command line to edit the CONFIG.SYS
file. Find the BASEDEV=ASC.ADD line in the file and add
the desired options. Refer to driver options below.
5. Reboot the system by selecting "Shutdown" from the
"Launch Pad" icon.
B. From the OS/2 command line:
1. Boot up the existing OS/2 system.
2. Insert the SIIG driver diskette in drive A:.
3. Copy the file ASC.ADD from the diskette OS2 directory
to the directory C:\. This assumes that C: is the root
drive. Substitute the correct drive letter if your root
drive is different.
4. Use a text editor to add the line "BASEDEV=ASC.ADD" as the
last line of the drive C: or root drive CONFIG.SYS file. Add
any desired options to the line at this time. Refer to
driver options below.
5. Reboot the system.
SIIG Universal SCSI Adapter Device Driver Options
=====================================================
/V Verbose
Display information during OS/2 system initialization.
/A:d Adapter Index
"d" is a decimal number. This option is used to
specify an adapter for options that follow like
/I, /DM, or /SM. The first SIIG adapter in the
system is numbered 0, the second 1, etc.
/I Ignore Adapter
Must be preceded by a /A:d option.
/[!]DM:target
or
/[!]DM:(target,lun),...
DASD Manager Support:
Indicate the unit(s) are to be controlled by
OS2DASD.DMD. "target" and "lun" are decimal numbers
that specify the devices to use. Must be preceded by
a /A:d option. If the '/' is followed by a '!' the
unit will not be controlled by OS2DASD.DMD.
/[!]SM:target
or
/[!]SM:(target,lun),...
SCSI Manager Support:
Indicate the unit(s) are to be controlled by
OS2SCSI.DMD. "target" and "lun" are decimal
numbers that specify the devices to use. Must
be preceded by a /A:d option. If the '/' is
followed by a '!' the unit will not be controlled
by OS2SCSI.DMD.
/L Enable scanning for LUN devices for all targets.
By default no LUN scanning is done.
/I:port Specify an I/O port address where an SIIG ISA
or VL adapter card can be found. Up to four of
these options can be present on the driver
command-line. "port" is a hexadecimal number.
/I- Avoid searching for any ISA or VL adapters.
/[!]TO Enable/disable software timeouts of disk I/O
operations. By default the driver will timeout
a disk I/O after 15 seconds.
ASC Driver CONFIG.SYS Examples
==============================
DEVICE=ASC.ADD /V /I:110
Print adapter and device information during start-up. And only
look for ISA or VL type cards at I/O port 0x110. The /I:XXX
option does not prevent the driver from finding and controlling
EISA and PCI cards.
DEVICE=ASC.ADD /I- /L
Do not look for any ISA and VL type cards. The driver will only
look for and control EISA and PCI cards. For each adapter found
scan each target device for LUN devices.
BASEDEV=ASC.ADD /A:0 /!SM:5 /!DM:5
Prevent the SIIG Adapter 0, Target 5 device from being
controlled by the OS2SCSI.DMD and OS2DASD.DMD Device Manager
Drivers. If OS2ASPI.DMD is loaded in your CONFIG.SYS it will
take control of the device.
Troubleshooting and Recovery Suggestions
========================================
Troubleshooting Tip 1:
If OS/2 hangs while booting it is possible to see
which driver OS/2 is loading when the hang occured.
To see drivers listed as they are being loaded do
the following: Reboot the system; After the boot
manager menu has been exited (if the boot manager is installed)
and while the string "OS2" is displayed to the right of
a white box in the upper, left-hand corner, press ALT-F2.
Each driver that OS/2 loads will be displayed in the lower,
left-hand corner of the screen.
Troubleshooting Tip 2:
To get to an OS/2 prompt of a system that hangs during
start-up press ALT-F1 while the string "OS2" is displayed
in the upper, left-hand corner. The OS/2 logo will be
displayed and then after a few seconds a menu of options will
be presented. Choose the option to enter the command line.
This will allow you to make changes to your CONFIG.SYS file
or install new driver files. The OS/2 editor "tedit" can be
used to edit the CONFIG.SYS file.
If the above procedure fails boot the "Installation Diskette for
CD-ROM" and when prompted insert the "Diskette for CD-ROM (1)".
Before the install procedure begins you will be given the option
of exiting to the command line by pressing F3. Press F3 to enter
the OS/2 command line.
Problem 1:
OS/2 hangs while loading the ASC.ADD driver and an ASC ISA or
VL card is installed and other ISA SCSI cards or network cards
are installed.
Solution 1:
Write down the I/O port address that is printed by the SIIG BIOS
when the system is booted. Re-boot the system to the OS/2 command
line as described above in Troubleshooting Tip 2. Edit the CONFIG.SYS
file and add the /I:port address option to the ASC.ADD line to
explicitly tell the driver which I/O port the SIIG adapter
has been configured at.
Problem 2:
OS/2 panics while loading the ASC.ADD driver with a ASC PCI card
installed. OS/2 2.X is being used. The problem does not occur with
OS/2 Warp.
Solution 2:
OS/2 2.X does not support PCI. You must obtain a patch for OS/2 2.X
either from IBM or SIIG. Contact SIIG Customer Support.
Problem 3:
When installing the ASC driver from the desktop the error message
"A profile control file could not be found" is displayed and the
installation fails.
Solution 3:
The "Source Directory" for the install must be set to the directory
which contains the files PRASC.DDP, PRASC.EXE, and ASC.ADD. Change
the "Source Directory" to this directory. The directory as on the
SIIG Driver diskette is A:\OS2.
Problem 4:
Where is the SIIG ASPI driver?
Solution 4:
The ASPI (Advanced SCSI Programming Interface) Driver for OS/2
is provides by IBM. The OS/2 ASPI driver (OS2ASPI.DMD) works with
any ADD (Adapter Device Driver) including ASC.ADD. Add the line
listed below to your CONFIG.SYS file. Also refer to the Problem
below. You may need to add options to your ASC.ADD BASEDEV line
to ensure that OS2ASPI.DMD controls a particular device.
BASEDEV=OS2ASPI.DMD
Problem 5:
OS2ASPI.DMD does not seem to see a SCSI device I want it to control.
Solution 5:
Each ADD (Adapter Device Driver) target device can only be
controlled/allocated by one DMD (Device Manager Driver). The
OS2SCSI.DMD (SCSI pass-through driver), OS2DASD.DMD (Disk Block
Driver), and OS2CDROM.DMD (CD-ROM Block Driver) Device Managers
control any devices that they find to be unallocated, of a particular
type they may be looking for (e.g. OS2DASD.DMD only looks for
disk devices), and not flagged to not be controlled by them
when they are loaded. The ADD options /SM and /DM can be used to
specify which DMD should control a particular ADD target device.
Refer to the section above entitled "SIIG Universal SCSI
Adapter Device Driver Options" for a description of the /SM and /DM
options.
The OS2ASPI Device Manager works differently. By default it only
allocates devices that it finds to be unallocated. Therefore any
targets you want to be controlled by OS2ASPI.DMD should be flagged
on the ASC.ADD BASEDEV line to indicate that they should not be
controlled by OS2SCSI.DMD, OS2DASD.DMD, or OS2CDROM.DMD. (Note:
there is no way to prevent OS2CDROM.DMD from controlling CD-ROM
devices. If you want OS2ASPI.DMD to control a CD-ROM device don't
include OS2CDROM.DMD in your CONFIG.SYS file.)
As an example if you have a scanner attached to SIIG Adapter 0
at Target 5, try the following to make OS2ASPI.DMD control it. A
/!DM:5 option shouldn't be necessary, because OS2DASD.DMD ignores
non-disk type devices. Even the "/A:0 /!SM:5" options are only
necessary if you include a BASEDEV=OS2SCSI.DMD line in your
CONFIG.SYS file.
BASEDEV=ASC.ADD /V /A:0 /!SM:5
Problem 6:
The ASC.ADD driver does not load at boot time. OS/2 displays a
message about there being an error with the driver. After this
ASC.ADD displays a message about disabling the BIOS SCAM option.
OS/2 may have displayed this message too quickly for it to
be readable.
Solution 6:
If your SIIG BIOS does not have the "SCAM Device Support" option
then ignore this solution. If your SIIG Card BIOS does have the
SCAM (SCSI Configured AutoMatic) option make sure that it is disabled.
The OS/2 operating system does not have support for this feature. If
the ASC.ADD driver detects that the option has been enabled, it will
return an error. To correct this problem or check the setting, enter
the SIIG BIOS by typing Ctl-A during the SIIG BIOS Device
Scan at boot time. Select the "SCSI Configuration" option and then
the "SCAM Device Support" option. If the "SCAM Device Support" option
is enabled then disable it, save the change, and reboot the system.
Problem 7:
The system already had an IDE boot disk and was working fine.
An ASC adapter and driver were installed and now the system
doesn't boot. The OS/2 logo is displayed and then OS/2 prints
a message about not being able to control or find the primary
drive.
Solution 7:
The IBM1S506.ADD (IDE) driver should precede the ASC.ADD driver
in the CONFIG.SYS file if the system boots from an IDE drive.
OS/2 will initially boot from the BIOS (0x80) boot drive.
It will then read the CONFIG.SYS file contained on this boot
drive. OS/2 continues its boot procedure with the first ADD
BASEDEV driver it finds that controls a fixed disk. If this
fixed disk is not the same as the BIOS (0x80) boot disk, OS/2
will actually switch to this different drive to complete booting
the system. For this reason the order of BASEDEV ADD lines in
the CONFIG.SYS file is very important. If you boot from an IDE
drive simply ensure that IBM1S506.ADD is the first BASEDEV line
in the CONFIG.SYS file.
Problem 8:
The system boots very slowly. After the ASC.ADD driver is loaded
the SIIG adapter or boot disk drive light comes on about once
per second. If the /!TO option is used the system hangs after loading
the ASC.ADD driver.
Solution 8:
This problem is probably the result of the ASC.ADD interrupt
handler not being called by OS/2 after the SIIG adapter has
completed an I/O. Instead I/O requests are being completed by
the ASC.ADD timer interrupt handler which is called once per
second. (Note: If the /!TO option is used with the ASC.ADD driver,
the ASC.ADD timer interrupt handler will be disabled and the system
would simply hang after loading the ASC.ADD driver.) Try setting
your SIIG adapter IRQ to a different setting using the SIIG
BIOS. If you have a PCI motherboard and SIIG PCI Adapter, try
setting the IRQ for the SIIG PCI Adapter slot to an different
IRQ using the motherboard BIOS.
Problem 9:
The system does not recognize a MO (Magneto-Optical) drive.
Solution 9:
Add the /V option to the ASC.ADD command line in the CONFIG.SYS
file. This will cause the driver to print a banner and information
about each device that it detects on the SCSI bus. Check to see
if the MO drive is displayed and what device type is listed with.
OS2DASD.DMD will only recognize MO drives when they are set
to be "Disk" type devices (SCSI Device Type 0). If the drive is
listed as an "Optical Memory" device (SCSI Device Type 7), change
its setting to "Disk". This can usually be changed with a jumper
or switch on the MO drive. When OS2DASD.DMD recognizes the MO drive
a removable drive icon will appear in the "Drives" folder.
Problem 10:
A MO (Magneto-Optical) disk formatted under DOS or Windows is not
recognized by OS/2.
Solution 10:
OS/2 has its own format for MO disks. They are treated like large
floppy disks and do not have a partition table. Windows 95 can
read OS/2 formatted MO disks, but OS/2 will not recognize MO
disks formatted under Windows 95. If you want to transfer MO
disks between OS/2 and Windows 95 format the disks under OS/2.
Problem 11:
An OS/2 installation does not work to an MO (Magneto-Optical) disk.
Solution 11:
OS/2 has its own format for MO disks. They are treated like large
floppy disks and do not have a partition table, because of this
OS/2 can not be installed to an MO disk.
SIIG Contact Information
============================
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.