Hello ALAN!
Saturday April 11 1998 18:31, ALAN LO wrote to All:
> hi!
> i have a problem... My scsi card (Fire Port 40 by Diamond with Sym
ios
> Logic 53c875) is not reconized. Now can someone help me please? Thanks
n
> adv.
=== Cut ===
*****************************************************************************
OS2.TXT
*****************************************************************************
INSTALLATION GUIDE FOR THE SDMS 8XX OS/2 DRIVER V4.06.00
This file describes the features and use of the Symbios SDMS device
driver for the OS/2 operating system environment. It is divided into the
following sections:
Introduction
Features
Description
Installing Your SDMS OS/2 Driver
Installing SYM8XX.ADD with OS/2 Already Installed
Installing SYM8XX.ADD and OS/2 from a Floppy to a SCSI Hard Drive
Installing SYM8XX.ADD and OS/2 from a SCSI CD-ROM to a SCSI Hard Drive
Driver Order in the CONFIG.SYS File
Command Line Options
Troubleshooting
******************************* Introduction ********************************
The OS/2 operating system version 3.0 and later provides an integrated
platform featuring a graphical windowing interface, called Presentation
Manager, that allows multiple applications to be viewed at the same time.
Multitasking is also supported, enabling several different programs to run at
the same time in different windows. Presentation Manager allows the user to
switch between programs, start other programs, and maintain files and
directories. These versions of OS/2 require an 80386 or higher
icroprocessor.
Other hardware requirements include a minimum of 8 megabytes of RAM and a
minimum hard disk drive size of 90 megabytes. Symbios SDMS 4.0 provides
the necessary SCSI device driver for OS/2. We recommend reviewing the OS/2
manual prior to proceeding.
* * * * * * * * * * * Features * * * * * * * * * * * * *
o Supports synchronous negotiation (including Ultra-2 SCSI)
o Supports Wide SCSI (single-ended and differential)
o Supports multiple host adapters
o Supports Disconnect/Reselect
o Supports Scatter/Gather
o Allows tagged command queuing
* * * * * * * * * * * Description * * * * * * * * * * *
Although the Symbios SCSI controller's firmware can access the SCSI
hard disk drives attached to the computer independently, the SCSI device
driver SYM8XX.ADD acts as an enhanced interface between the computer system
and the SCSI BIOS firmware. Use of the device driver increases the abilities
of the SCSI controller firmware and fully utilizes the advancements and
improvements of 80386 and higher microprocessors.
The device driver is also necessary to support the use of SCSI tape drives
and CD-ROM drives with an OS/2 system. The Symbios SYM8XX.ADD device
driver is written in compliance with the IBM OS/2 ADD (Adapter Device Driver)
specification, and the device driver works with third party applications that
comply with the same specification.
********************** Installing Your SDMS OS/2 Driver *********************
These installation instructions are specific and accurate for the SDMS OS/2
driver SYM8XX.ADD V4.06.00. You may have a more recent version of this
driver. You should refer to the text file OS2.TXT located on the SDMS
diskette for a version of these instructions guaranteed to match your driver.
Note: If you previously installed OS2CAM.ADD (the previous version of this
driver), delete OS2CAM.ADD and delete the corresponding
BASEDEV= statement in CONFIG.SYS after you complete installation
procedures. If you previously installed SYM8XX.ADD in a directory other
than \OS2\BOOT, move SYM8XX.ADD to \OS2\BOOT, where the new version of
SYM8XX.ADD can replace the old version. The system will continue to
boot using the previous driver until these steps are taken.
* * * * * Installing SYM8XX.ADD with OS/2 Already Installed * * * *
The Symbios device driver floppy diskette contains three files: the
device driver SYM8XX.ADD, the text file SYM8XX.DDP, and the executable file,
SYM8XXPC.EXE. When the device driver installation utility under OS/2 is
activated, it looks for a file with the DDP extension. The DDP file contains
the necessary information to install the SCSI device driver. The EXE file
contains a utility that verifies that an appropriate adapter is present.
1) At the OS/2 Desktop, open the System Setup folder located within the OS/2
System folder. For Warp 3.0, double-click on the Device Driver Install
icon.
For Warp 4.0, open the Install/Remove folder and then double-click on the
Device Driver Install icon.
2) Insert the floppy diskette containing the Symbios device driver in
the source drive.
3) Choose the Symbios SYM8XX.ADD driver from the list provided by
clicking on it once. The choice will be highlighted. Then click the OK
button, then the EXIT button.
4) To make sure that the installation was successful, in Warp 3.0 open the
Productivity folder on the OS/2 Desktop. In Warp 4.0, open the Utilities
folder located within the Programs folder on the OS/2 Desktop. Then
double-click on the OS/2 System Editor to start the editor. Open the
CONFIG.SYS file in the root directory and find the line:
BASEDEV=SYM8XX.ADD /V
Then check that the file SYM8XX.ADD is in the \OS2\BOOT directory on the
boot drive.
* * Installing SYM8XX.ADD and OS/2 from a Floppy to a SCSI Hard Drive * *
In this case, since OS/2 will be installed from a floppy diskette, it is not
required that the driver be present to install the operating system (as is
the case when installing from a CD-ROM).
1) After the installation of OS/2 completes and the WorkPlace Shell desktop
builds, open the System Setup folder located in the OS/2 System folder.
or
Warp 3.0, double-click on the Device Driver Install icon. For Warp 4.0,
open the Install/Remove folder and then double-click on the Device Driver
Install icon.
2) Insert the floppy diskette containing the Symbios device driver in
the source drive.
3) Choose the Symbios SYM8XX.ADD driver from the list provided by
clicking on it once. The choice will be highlighted. Then click the OK
button, then the EXIT button.
4) To make sure that the installation was successful, in Warp 3.0, open the
Productivity folder on the OS/2 Desktop. In Warp 4.0, open the Utilities
folder located within the Programs folder on the OS/2 Desktop. Then
double-click on the OS/2 System Editor to start the editor. Open the
CONFIG.SYS file in the root directory and find the line:
BASEDEV=SYM8XX.ADD /V
Then check that the file SYM8XX.ADD is in the \OS2\BOOT directory on the
boot drive.
5) Continue with the OS/2 installation process as documented in the OS/2
Installation Guide.
* * Installing SYM8XX.ADD and OS/2 from a SCSI CD-ROM to a SCSI Hard Drive *
*
To install OS/2 from a SCSI CD-ROM attached to a Symbios host adapter,
the SCSI driver must be present in order to access the CD-ROM. The following
steps allow installation of OS/2 from a SCSI CD-ROM.
1) Make copies of the floppy diskettes used for installation that are
included with the CD-ROM version of OS/2.
2) To copy the file SYM8XX.ADD from the Symbios distribution diskette to
the copy of Diskette 1, you must delete files on Diskette 1 to provide
space. If you are installing a version of OS/2 other than Warp 4.0, any
unused .ADD driver(s) may be deleted. If you are installing Warp 4.0,
consult the README.1ST file on the Device Driver Pak Volume 1.0 CD. It
contains a list of files that may not be deleted. Follow the instructions
provided in the README.1st file. Once space is made available on Diskette
1,
copy the file SYM8XX.ADD onto this diskette.
When .ADD drivers are deleted from Diskette 1, make certain to delete or
remark out the corresponding BASEDEV= statement in the CONFIG.SYS file.
Otherwise, error messages will show up during installation.
3) Edit the CONFIG.SYS file on the copy of Diskette 1 by adding the following
line at the end of the file:
BASEDEV=SYM8XX.ADD /V
If you are installing OS/2 Warp 4.0, follow the directions in the
README.1ST file for adding the following line to CONFIG.SYS:
SET COPYFROMFLOPPY=1
This allows SYM8XX.ADD to be copied from the installation diskette to
the system's boot drive.
4) Place the copy of Installation Diskette in the A: drive and reboot the
computer.
5) Proceed with the OS/2 installation process as documented in the OS/2
Installation Guide.
* * * * * * * Driver Order in the CONFIG.SYS File * * * * * * *
Because of the way OS/2 assigns drive letters, the order in which drivers
appear in the CONFIG.SYS file is important. The drivers must appear in the
order in which the drive letters are to be assigned. In particular:
- OS/2 Warp will install the BASEDEV= line at the beginning of the target
system's CONFIG.SYS file regardless of where the line is located in that
file on Diskette 1. You may need to rearrange the order in which drivers
appear in the CONFIG.SYS file for the target system.
- If the system is to boot from an IDE hard drive, the IDE driver must
appear
before SYM8XX.ADD in CONFIG.SYS.
Refer to the OS/2 documentation to fully understand this requirement.
* * * * * * * * * * Command Line Options * * * * * * * * *
Your host adapter has a default configuration that consists of optimal values
for operation. You may decide to alter these default values if there is a
conflict between device settings or if you need to optimize system
performance.
Some values may be changed using the SCSI Configuration Utility provided with
some members of the 8XX family of host adapters. Refer to your host adapter's
user guide for information on the availability and use of the SCSI
Configuration
Utility. In addition,the SYM8XX.ADD driver has several embedded functions
hat
can be accessed via switches on the command line in the CONFIG.SYS file.
Note: Values are applied in the following order:
o Manufacturer's settings
o SCSI Configuration Utility changes
o Command line options
At any point during this process, subsequent changes in synchronous
nd
wide negotiations may only decrease speed or reduce width. Any changes
that attempt to increase speed or width will be ignored.
The options available using command line switches are described below.
* * * Using the /VERBOSE (or /V) Option * * *
This option appears on the command line by default. It enables display of
a banner, version number, and SCSI bus information during start up of the
system.
Usage:
/VERBOSE
For example, if you wish to see more detailed information displayed when
you boot, the line in CONFIG.SYS that loads SYM8XX.ADD should look like
this:
BASEDEV=SYM8XX.ADD /VERBOSE
or
BASEDEV=SYM8XX.ADD /V
To disable this feature, remove this switch from the command line.
* * * Using the /!DM Option * * *
This option disables use of the IBM-supplied DASD manager (OS2DASD.DMD)
for the devices listed. The DASD manager supports direct access devices
such as hard drives.
Usage:
/!DM[,]*
Where:
path represents the position of a host adapter as indicated
by its numbering displayed by the Verbose option. This is
NOT the SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, if you want to disable OS2DASD.DMD for devices on host
adapter 0 at target IDs 3 and 5, the line in CONFIG.SYS that loads
SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /!DM,
* * * Using the /!SM Option * * *
This option disables use of the IBM-supplied SCSI manager (OS2SCSI.DMD)
for the devices listed. The SCSI manager supports SCSI tape drives.
Usage:
/!SM[,]*
Where:
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, if you want to disable OS2SCSI.DMD for devices on host
adapter 0 at target IDs 3 and 5, the line in CONFIG.SYS that loads
SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /!SM,
* * * Using the /SYNCH_RATE (or /SR) Option * * *
This sets the maximum synchronous transfer rate (in megabyte transfers per
second) to negotiate with a particular device. The allowable values for
this setting are 0, 5, 10, 20, and 40 mega transfers per second, if the
adapter is capable of the specified speed. All host adapters in the 8XX
family support at least 10 megabyte transfers per second; some support 20 or
40 megabyte transfers per second. To turn off synchronous transfers for a
particular device, specify 0 (zero). The value set by this option only
defines the maximum transfer rate negotiated. The actual rate also
depends on what the device can do. The default value is the fastest
transfer rate that is supported by a particular host adapter.
Usage:
/SYNCH_RATE = n[,n]*
Where:
n = 0, 5, 10, 20 or 40.
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, if you want to turn off synchronous transfers to ID 3 on
host adapter 0, the line in CONFIG.SYS that loads SYM8XX.ADD should look
like this:
BASEDEV=SYM8XX.ADD /SYNCH_RATE=0
As another example, if you want to set synchronous transfers to 10
megabyte
transfers per second on all devices on adapter 1, the line in CONFIG.SYS
that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /SR=10
* * * Using the /SYNCH_OFFSET (or /SO) Option * * *
This sets the maximum synchronous offset to negotiate with a particular
device. The allowable values for this setting are 0 to the maximum
synchronous offset supported by the specified path. The 53C8XX
controller chips support offsets up to 31. If 0 (zero) is specified for
the synchronous offset value, then synchronous transfers are turned off
for any specified device. The value set by this option only defines the
maximum offset that is negotiated. The resulting rate also depends on the
device capability. The default value is the maximum offset that is
supported by a particular host adapter.
Usage:
/SYNCH_OFFSET = n[,n]*
Where:
n = 0..maximum synchronous offset for the adapter.
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, if you want to change the synchronous offset to 6 for ID 3,
the line in CONFIG.SYS that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /SYNCH_OFFSET=6
* * * Using the /TIMEOUT (or /T) Option * * *
The SYM8XX.ADD device driver uses a time-out mechanism to detect certain
errors.
When SYM8XX.ADD issues a command to a SCSI device, a timer is started. If the
timer expires before the command completes, SYM8XX.ADD assumes that something
has gone wrong with the device, and takes steps to recover. The default value
for this is 10 seconds. If you set the value to be less than the system has
allocated for a particular device, your value will be ignored.
Usage:
/TIMEOUT = n[,n]*
Where:
n = time-out value in seconds for device, n=(0..65535), 0=infinite.
path represents the position of a host adapter as indicated by its
numbering displayed by the Verbose option. This is NOT the SCSI ID
of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, if you have a particularly slow device on ID 3 and you wish
to extend the time out on this device to 60 seconds, then the line in
CONFIG.SYS that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /TIMEOUT=60
* * * Using the /DISCONNECT (or /DC) Option * * *
SCSI devices have the ability to disconnect from the bus during an I/O
transfer. This option is used to allow (or not allow) a device to
disconnect during an I/O. If a particular adapter has parity checking
disabled, then you must use this option to disable disconnects for all
devices on that adapter that do not generate parity. This is because the
/PARITY option does not change the disconnect state for any device on
that adapter. See the /PARITY option for more information.
Usage:
/DISCONNECT = n[,n]*
Where:
n = ON or OFF.
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
Valid options are "ON" (allow disconnects) and "OFF" (do not allow
disconnects). The default for all devices is "ON".
For example, if you want to disable disconnects on the device at ID 2,
then the line in CONFIG.SYS that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /DISCONNECT=OFF
* * * Using the /PARITY (or /P) Option * * *
The 53C8XX chips are capable of enabling or disabling the SCSI bus
data integrity checking feature known as "parity". Some non-SCSI compliant
devices sold as SCSI devices do not generate parity. You can use this
option to disable parity checking. The 53C8XX chips always generate
parity (for outputs), but may optionally check the parity (for inputs).
Usage:
/PARITY = n[,n]*
Where:
n = ON or OFF.
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
Valid options are "ON" (check parity) and "OFF" (do not check parity).
The default for all devices is "ON", which enables parity checking for
all devices.
Note: When disabling parity checking, it is necessary to disable
disconnects for any device that does not generate parity, as the
53C8XX chips cannot disable parity checking for that device
during the reselection phase. Please refer to using the /DISCONNECT
option for more information on how to disable disconnects for a
device. If a device does not generate parity and it disconnects,
the I/O never completes as the reselection never completes.
For example, to turn off parity checking on host adapter number 0, the
line in CONFIG.SYS that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /PARITY=OFF
* * * Using the /QTAG (or /QT) Option * * *
Queue tagging allows more than one outstanding command per SCSI
device. Some non-SCSI compliant devices sold as SCSI devices do not allow
queue tags, in which case queue tagging needs to be disabled. The value
given in the command line will be the depth of the queue for queue tags
for the device(s) indicated. To disable queue tag support, a value of 0
or 1 should be given.
Usage:
/QTAG = n[,n]*
Where:
n = the number of queue tags allowed for a device (0..256).
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, to turn off queue tagging for ID 3 on host adapter number 0,
the line in CONFIG.SYS that loads SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /QTAG=0
As another example, if you want to set the queue depth to 5 for all
devices on host adapter number 2, the line in CONFIG.SYS that loads
SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /QT=5
* * * Using the /WIDTH (or /W) Option * * *
Devices attached to a SCSI bus are narrow or wide devices. Narrow devices
transfer data one byte (or 8 bits) at a time. Wide devices transfer two
bytes (or 16 bits) at a time. The value given in the command line option
will determine the size of data transfers.
Usage:
/WIDTH = n[,n]*
Where:
n = 8 or 16.
path represents the position of a host adapter as indicated by
its numbering displayed by the Verbose option. This is NOT the
SCSI ID of the host adapter.
id represents a SCSI target ID on the indicated path.
[ ]'s indicate optional information.
* indicates the pattern enclosed in the [ ]'s may be repeated.
For example, to have the device at ID 3 on host adapter number 0 treated
as a narrow device, the line in CONFIG.SYS that loads SYM8XX.ADD should
look like this:
BASEDEV=SYM8XX.ADD /WIDTH=8
As another example, if you want to have all devices on host adapter
number 2 treated as 8-bit devices, the line in CONFIG.SYS that loads
SYM8XX.ADD should look like this:
BASEDEV=SYM8XX.ADD /W=8
* * * * * * * * * * * Troubleshooting * * * * * * * * * *
The following are some potential problems and their suggested solutions:
1. Problem: You cannot access the SCSI device(s).
Solution:
a. Make sure the SCSI device driver is installed properly.
b. Make sure each device has power.
c. Verify that a BASEDEV = SYM8XX.ADD /V line exists in the CONFIG.SYS
file.
d. Verify that SYM8XX.ADD is in the appropriate directory (\OS2\BOOT).
e. Check the cable connections and the host adapter installation.
2. Problem: The computer hangs or locks up when booting and the SCSI devices
attached are not seen by the computer system.
Solution:
a. Make sure that all the SCSI devices are configured at different ID
numbers.
If booting the system from a device on the SCSI bus, the boot drive
must
have the lowest ID or the highest ID, depending on the scan order
option
selected in the configuration utility. For more information, consult
the
BOOTROM.TXT file or the documentation provided with your host adapter
board.
b. Make sure both, but only, the ends of the SCSI bus are terminated.
c. Make sure the device dri
T BAT
'
.
t.bat
t.bat
c:\fd\t.bat
P
P
P
`
`P
P
Quitting c:\fd\mail.bat
3
---------------
FIDO MESSAGE AREA==> TOPIC: 260 OS/2 HARDWARE Ref: F5G00018 Date: 04/18/98
From: TOM PERRETT Time: 02:19pm
\/To: ALL (Read 4 times)
Subj: HP LaserJet 5P & WinOS2
My default OS/2 printer is the HP 5P.
I want to use this for WinOS2 printing too.
Using the HP supplied Windows drivers I get
as far in the installation to where it wants
to talk to the printer.
Bombs out with the advise that it can't establish
2way communicatin with the printer.
The port I selected was LPT1:OS2.
Any one got a HP 5P to work as such
under WinOS2.
It works quite happily as HP 111
Cheers,
Tom tomp@st.net.au
--- Blue Wave/OS2 v2.30
---------------
* Origin: Soft-Tech, Qld, Australia +61-7-3869-2666 (3:640/201)
|