Quick Reference
PCSCSI Software
Installation Guide
VERSION 3.0
October 1995
1. Quick Reference
1.1 Driver and Utility Overview
OS/2 2.x and 3.0:
AMSIO2.ADD: OS/2 Adapter Device Driver
AMSIO2.DDP: Setup Profile Driver
AMSIO2.EXE: Hardware Detection Program Driver
1.2 Driver and Utility Features
Brief descriptions of AMD's driver and utility features are
highlighted below.
1.2.1IBM OS/2
a) AMSIO2.EXE: Hardware Detection Program
Determines the existence of a PCSCSI or PCnet-SCSI
controller
b) AMSIO2.DDP: Setup Profile Driver
Identifies the Adapter Device Driver (ADD), the hardware
detection program, and the configuration SCSI device
driver
c) AMSIO2.ADD: Adapter Device Driver
Supports SCSI peripherals via third party drivers
Is certified via OS/2 2.x and 3.0 Test Kit
Complies with IBM OS/2 2.x and 3.0 OEM DASD and SCSI
Device Driver
Supports the suspend and resume commands of the APM spec
1.3 Boot Time Options
At boot time, the end user will have the option to reassign
SCSI IDs for SCSI Configure Auto-Matically (SCAM)
peripherals. Options are chosen by pressing <Alt-A> after
the information banner is displayed at boot time and by
selecting the following menu items:
[-_] Device Select device (SCAM only)
[+-] New SCSI ID Select SCSI IDs (SCAM only)
[F10] Save/Boot Save permanently and boot
[Esc] Boot/No Save Save temporarily and boot
2. Installation and Usage of Drivers and Utilities
2.1 OS/2 2.x and 3.0
There are three drivers required for OS/2 SCSI driver
installation: AMSIOS2.ADD, AMSIO2.DDP, and AMSIO2.EXE.
2.1.1 OS/2 New Installation
If this is a new OS/2 2.x and 3.0 and 3.0 installation and
you are installing on a system using only SCSI (no IDE
peripherals), follow the steps outlined below:
1.Copy AMSIOS2.ADD and AMSIO2.DDP from the AMD Driver
Disk to the OS/2 diskette labeled "Diskette #1."
2.In the "CONFIG.SYS" file found on the OS/2 diskette
labeled "Diskette #1", add the following entry:
BASEDEV=AMSIO2.ADD after the line:
BASEDEV=IMB1S506.ADD.
3.Install OS/2 as normal.
2.1.2 OS/2 Existing Installation
Note: If this is an existing OS/2 2.x and 3.0 installation,
you must replace the existing CONFIG.SYS file with a
new one. During the installation process, the OS/ 2
installation utility will detect the existing
CONFIG.SYS file and will ask if you want to replace it
with the new one. Select `Replace' and continue with
the installation.
In the OS/2 desktop, follow the steps below:
1.Select and open the OS/2 "System" folder.
2.Select and open the "System Setup" folder.
3.Select and open the "Device Driver Install" folder and
follow the instructions for installing a device driver.
Install the floppy diskette containing AMSIO2.ADD when
prompted. The CONFIG.SYS file will be automatically
updated for you.
Note: If shared interrupt support is required, the proper
replacement driver (OS2LDR) can be obtained from IBM.
The OS/2 toll free support number is 1-800-992-4777.
The problem reference numbers that you will need to
refer to are the following: APARPJ 14230 and APARPJ
14710.
3. Driver Switch Definitions
The following table describes which switch options are
supported by the SCSI drivers. Note: Switches may be entered
in any sequence and are not case sensitive.
Table 2. SCSI Software V2.0 Switch Support Matrix
Driver OS
/
DOS CD-ROM Disk SCO OS/2 NetWare Window
s
Switch ASPI Driver Driver UNIX NT
/AN Yes No No No Yes No No
/APM- No n/a n/a n/a Yes n/a n/a
/DI- Yes No No No Yes No No
/Hx Yes No No No No No No
/L Yes No No No Yes No No
/PAR- Yes n/a n/a Yes Yes Yes Yes
/PAUSE Yes No No No No No No
/PCI1 Yes n/a n/a Yes Yes Yes No
/PCI2 Yes n/a n/a Yes Yes Yes No
/RST Yes No No No No No No
/S- Yes n/a n/a Yes Yes Yes Yes
Yes n/a n/a n/a Yes Yes n/a
/SCAM-
/TQ No n/a n/a Yes Yes Yes No
/TQ- n/a n/a n/a n/a n/a Yes Yes
/V Yes n/a n/a Yes Yes Yes No
Table 3. Switch Definitions
Switch Definition
/AN Enable active negation.
/APM- Disable APM (Advanced Power Management) support.
/DI- Disable disconnect privilege.
/Hx Host adapter SCSI ID setting where x is a value
from 0 to 7 (default is 7).
/L Enables support for SCSI logical units other than
0 (if drive supports more than one LUN).
/PAR- Disable device parity.
/PAUSE Pause upon driver load to allow user to read
screen. Press any key to resume booting process.
/PCI1 Force mechanism 1 scan of PCI bus.
/PCI2 Force mechanism 2 scan of PCI bus.
/RST SCSI bus reset upon driver load.
/S- Disable synchronous data transfers.
/SCAM- Disable SCAM (SCSI Configure Auto-Matically)
support.
/TQ En/able tag queuing. (Windows NT enables tag
queuing by default)
/TQ- Disable tag queuing.
/V Verbose mode used to display information about
the host adapter and attached SCSI devices when
booting.
APPENDIX A Error Messages
A.1 SCSI BIOS Error Messages
MessageERROR: Error accessing PCI configuration space.
MeaningUnable to determine PCI configuration space access
method. Either there is no PCI bus in the system or
the PCI arbiter is malfunctioning.
ActionContact your system manufacturer.
MessageERROR: Invalid PCI parameters.
MeaningThe device does not have its resources allocated. The
system BIOS has not initialized the SCSI
controller.
ActionContact your card manufacturer.
MessageERROR: Device diagnostic failure.
MeaningDevice has failed diagnostics.
ActionContact your card manufacturer.
MessageERROR: No int13 supportable devices.
MeaningNo SCSI devices were found to be supported under
Interrupt 13h control.
ActionNo bootable devices will be supported with the BIOS.
A.2 DOS ASPI Manager Error Messages
MessageERROR: PCSCSI PCI Adapter not Responding or not
Present.
MeaningIt can be either PCSCSI device not present or problem
with hardware.
ActionCheck the hardware setup.
MessageERROR: no SCSI Devices Found During Scan.
MeaningNo SCSI device was detected during bus scan.
ActionCheck to make sure all SCSI peripherals are powered on
and connected
properly.
MessageERROR: Invalid Command Line Option Specified.
MeaningThe switch option specified in the DOS ASPI command
line in the CONFIG.SYS file is incorrect.
ActionCheck the DOS ASPI command line in the CONFIG.SYS file
against the options specified in the PCSCSI
Software Driver Installation Manual.
A.3 CD-ROM Driver Error Messages
MessageERROR: DOS ASPI Manager not Present. Driver not
Loaded!
MeaningThe PCSCSI DOS ASPI manager is not loaded.
ActionLoad the DOS ASPI manager prior to loading the CD-ROM
Driver.
MessageERROR: No CD-ROM Devices Detected. Driver not
Loaded!
MeaningNo CD-ROM peripheral detected on the SCSI bus.
ActionCheck the cable connection and make sure that the CD-
ROM is powered-up and is SCSI-2 compatible.
MessageERROR: Error In Command Line. Driver not Loaded.
MeaningError found in the command line for the CD-ROM driver
in the CONFIG.SYS file.
ActionCheck the CD-ROM driver command line in the CONFIG.SYS
file to make sure that the line is correct.
MessageERROR: Error initializing CD-ROM device. Driver not
loaded!
MeaningError found during CD-ROM initialization.
ActionEnsure that the CD-ROM driver is loaded.
A.4 Hard Disk and Removable Media Driver Error Messages
MessageERROR: DOS ASPI Manager not Present. Driver not
Loaded.
MeaningThe PCSCSI DOS ASPI manager is not loaded.
ActionLoad the DOS ASPI manager prior to loading the CD-ROM
driver.
MessageERROR: No Devices Detected. Driver not Loaded.
MeaningNo devices found on SCSI bus or the driver is not
loaded.
ActionCheck the hardware connection on the removable media
device. Check the CONFIG.SYS file to make sure the
correct command line is included to load the
removable media driver.
MessageERROR: No Drive Letters Available. Driver not Loaded.
Meaning The drive letter assigned for the device is not
valid.
Action Check the CONFIG.SYS file to modify the "last drive
= .." line to include the drive letter specified.
MessageERROR: Invalid command line option specified.
Meaning You have selected an invalid command line option.
Action Ensure that the command line settings are entered
correctly. Note: The current version of the driver
does not support any options.
A.5 Windows Show SCSI Utility Error Messages
Message(AMSISS-WIN-001): No Valid ASPI Manager found!
Meaning ASPI manager is incompatible with AMSISS.exe.
Action Check if the ASPI Manager is loaded and present.
Message(AMSISS-WIN-002): No SCSI Drivers found !
Meaning Necessary drivers not loaded: DOS ASPI Manager or
WINASPI.DLL.
Action Check if the ASPI Manager is loaded and present.
Message(AMSISS-WIN-003): ASPI manager incompatible with
Windows !
MeaningOld ASPI Manager.
ActionGet the latest version of the ASPI Manager.
Message(AMSISS-WIN-004): ASPI for Windows failed
initialization !
MeaningWINASPI.DLL failed to initialize.
Action Check if windows is running in enhanced and standard
mode.
Message(AMSISS-WIN-005): Unable to eject Media !
Meaning Unable to eject the removable media.
Action Either the SCSI device does no support the eject
command or the SCSI device is locked.
Message(AMSISS-WIN-006): Unable to lock Media !
Meaning Unable to lock the removable media.
Action The SCSI device does not support the lock command.
Message(AMSISS-WIN-007): Unable to Unlock Media !
Meaning The SCSI device does not support the Unlock command
or a SCSI error has occurred.
Action The SCSI device does not support the unlock command.
Message(AMSISS-WIN-008): Failed ASPI inquiry command !
Meaning Failed to perform an inquiry command.
Action Check the version of the DOS ASPI Manager,
WINASPI.DLL.
A.6 NetASPI Driver Error Messages
Message(AMSIN3-NW-3): Fail Initialization.
Meaning The Controller Initialization failed.
Action Check the hardware to make sure that it is working
(i.e., make sure the
hardware is function/al under other OS environment using the
same platform.
Message(AMSIN3-NW-4): Memory Allocation Failed.
Meaning Failed Allocating configuration information.
Action Increase the system RAM size or remove one or more
applications on the server.
Message(AMSIN3-NW-5): Memory Allocation Failed.
Meaning Dynamic memory allocation has failed.
Action Increase the system RAM size or remove one or more
applications on the server.
Message(AMSIN3-NW-6): PCSCSI not found.
Meaning The Controller could not be found for the supplied
configuration information.
Action Check the hardware to make sure it is functional
under other OS environments
using the same platform.
Message(AMSIN3-NW-8): PCSCSI found but error in config.
Meaning The Controller was found but the controller
configuration information was incorrect.
ActionRelease the conflicting resource on the system (i.e.,
IRQ or Port Number).
Message(AMSIN3-NW-9): Config info invalid.
Meaning The Controller configuration information was
invalid.
Action Check the hardware to make sure that it is
functional.
Message(AMSIN3-NW-12): PCSCSI Initialization Error.
Meaning This Header comes up when ever an error occurred.
Action Check the Error message follow this message for
details of the error.
Message(AMSIN3-NW-14): Too many Cards being installed.
Meaning More than four controllers are being installed in
the system. The maximum
number of controllers supported is four.
Action Remove the excess controllers.
Message(AMSIN3-NW-15): This Driver is already loaded.
Cannot be loaded again.
Meaning This version of the driver can be loaded only once.
Action Do not try to load the driver more than once.
Message(AMSIN3-NW-16): ParseDriverParameters or
RegisterHardwareOptions failed.
Meaning The IRQ or I/O port number or both selected are
conflicting with other devices.
Action Select non conflicting hardware options of the system
for the controller.
Message(AMSIN3-NW-17): Driver Init Complete returned error
(possible hardware).
Meaning Driver could not register the controller with the
OS.
Action Release the conflicting resource on the system (i.e.,
IRQ or Port Number).
Message(AMSIN3-NW-20): A PCSCSI was not found at the
specified location.
Meaning The IRQ or I/O port number or both selected are
conflicting with other devices.
Action Select non conflicting hardware options of the system
for the controller.
Message(AMSIN3-NW-21): No AES Timers.
Meaning The IRQ level of the controller could not be
registered with the OS.
Action This driver supports shared interrupts in systems
which support the same. It may be the case that
another driver that does not support shared
interrupts is using the same IRQ. Select a non
conflicting IRQ for this controller.
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.