1. NCRSCSI7.EXE Driver
2. OS2.TXT File Contents

OS2.TXT Driver File Contents (NCRSCSI7.EXE)

**********************************************************
			OS2.TXT
**********************************************************



   INSTALLATION GUIDE FOR THE SDMS OS/2 DRIVER V3.03.00



This file describes the features and use of the NCR SDMS 
device driver for the OS/2 operating system environment.
It is divided into the following sections:

Introduction
	Features of the SDMS OS/2 Driver
	Description of the SDMS OS/2 Driver
Installing Your SDMS OS/2 Driver
	Command Line Options
	Troubleshooting




******************** Introduction ***********************


The OS/2 operating systems version 2.X and later provide 
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 microprocessor. Other hardware requirements include 
a minimum of 4 megabytes of RAM (8 megabytes or more is 
recommended) and a minimum hard disk drive size of 40 
megabytes. NCR SDMS provides the necessary SCSI device 
driver for OS/2. We recommend reviewing the OS/2 manual 
prior to proceeding.


* Features of the SDMS OS/2 Driver *

Enhances host bus adapter performance
Supports synchronous negotiation (including fast SCSI)
Supports Wide SCSI (single-ended and differential)
Supports multiple host adapters
Supports Disconnect/Reselect
Supports scatter/gather
Allows tagged command queuing


* Description of the SDMS OS/2 Driver *

Although the NCR SCSI controller's firmware can access 
the SCSI hard disk drives attached to the computer 
independently, the SCSI device driver OS2CAM.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 NCR OS2CAM.ADD device driver is written in compliance 
with the IBM OS/2 ADD (Adapter Device Driver) 
specification, and will work 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 OS2CAM.ADD V3.03.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.


* Installing OS2CAM.ADD (with OS/2 already installed) *

The NCR device driver floppy diskette contains two files, 
the device driver OS2CAM.ADD and a text file, OS2CAM.DDP. 
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.

1) At the OS/2 Desktop, open the System Setup folder, and 
   double-click on the Device Driver Install icon.

2) Insert the floppy disk containing the NCR device driver 
   in the source drive.

3) If installing a 2.X version of OS/2, go to step six.

4) If installing a Warp version of OS/2, click on the change 
   button for the destination directory. Double click on the 
   OS2 directory, double click on the boot directory, and 
   click on the set button.

5) Click the install button.

6) Choose the NCR OS2CAM.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.

7) To make sure that the installation was successful, open 
   the productivity folder on the OS/2 Desktop, then 
   double-click the OS/2 System Editor to start the editor. 
   Open the CONFIG.SYS file and find the line:

	BASEDEV=OS2CAM.ADD /V

   Then check that the file OS2CAM.ADD is in the 
   appropriate directory on the boot drive.


* Installing OS2CAM.ADD and OS/2 
	(from a floppy) to a SCSI Hard Drive *

In this case, since OS/2 will be installed from a floppy 
disk, 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 is complete and the 
   WorkPlace Shell desktop is built, open the system 
   setup folder and double click on the Device Driver 
   Install icon.

2) Insert the floppy disk containing the NCR device 
   driver in the source drive.

3) If installing a 2.X version of OS/2, go to step six.

4) If installing a Warp version of OS/2, click on the 
   change button for the destination directory. Double-
   click on the OS2 directory, double-click on the boot 
   directory, and click on the SET button.

5) Click the install button.

6) Choose the NCR OS2CAM.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.

7) To make sure that the installation was successful, 
   open the productivity folder on the OS/2 Desktop, then 
   double-click the OS/2 System Editor to start the editor. 
   Open the CONFIG.SYS file and find the line:

	BASEDEV=OS2CAM.ADD /V

   Then check that the file OS2CAM.ADD is in the 
   appropriate directory on the boot drive.

8) Continue with the OS/2 installation process as 
   documented in the OS/2 Installation Guide.



* Installing OS2CAM.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 an NCR 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 two floppy disks used for 
   installation that are included with the CD-ROM version 
   of OS/2. These disks are labeled "Installation Diskette" 
   and "Diskette 1".

2) Copy the file OS2CAM.ADD from the NCR distribution disk 
   to the copy of "Diskette 1".

NOTE: OS/2 Warp versions of "Diskette 1" do not contain 
      enough available space to copy OS2CAM.ADD. A file 
      must be deleted in order to copy the driver file 
      onto the diskette. If the target installation system 
      DOES NOT contain a Microchannel system bus, delete 
      the file named "IBM2FLPY.ADD". If the target 
      installation system DOES contain a Microchannel bus, 
      delete the file named "IBM1FLPY.ADD". Alternatively, 
      any unused .ADD driver(s) may also be deleted.

      When any .ADD drivers are deleted from "Diskette 1", 
      make certain to delete or remark out the corresponding 
      BASEDEV= statement in CONFIG.SYS. Otherwise, error 
      messages will show up during installation.

3) Edit the file CONFIG.SYS on the copy of "Diskette 1" 
   by adding the following line at the end of the file:

	BASEDEV=OS2CAM.ADD /v

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 a hard drive attached 
     to an IDE bus, the IDE driver must appear before 
     OS2CAM.ADD in CONFIG.SYS. 

Refer to the OS/2 documentation to fully understand this 
requirement.


* Command Line Options *


The OS2CAM.ADD driver has several embedded functions 
which can be accessed via switches on the command line 
in the CONFIG.SYS file. These options are described 
below.


Using the /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. 
The command line in CONFIG.SYS should look like this:

	BASEDEV=OS2CAM.ADD /V

To disable this feature, remove this switch from the 
command line.


Using the /!SN Option

This option means "no synchronous". Synchronous transfers 
are typically faster than asynchronous, so this option 
should only be used if synchronous transfers cause a 
problem with your system. To disable synchronous 
operations, the command line in CONFIG.SYS should look 
like this:

	BASEDEV=OS2CAM.ADD /!SN


Using the /!Q Option

This option means "no queue tag support". Queue tagging is 
used to allow more than one outstanding command per SCSI 
device. To disable queue tag support, the command line in 
CONFIG.SYS should look like this:

	BASEDEV=OS2CAM.ADD /!Q


Using the /ET Option

This option is used to enable Embedded Targets (LUNs). 
LUNs are used by high end systems, such as disk arrays, 
to address certain portions of a SCSI ID. Most standard 
SCSI devices do not use LUNs, and default to LUN 0. This 
option should be used only for devices that use multiple 
embedded targets with LUNs other than 0. To enable LUN 
support, the command line in CONFIG.SYS should look like 
this:

	BASEDEV=OS2CAM.ADD /ET


Using the /DM Option

This option enables use of the IBM-supplied DASD manager 
(OS2DASD.DMD) for the devices listed. The DASD manager is 
used to support direct access devices such as hard drives. 
To enable DASD manager support, the command line in 
CONFIG.SYS looks like this:

	BASEDEV=OS2CAM.ADD /DM:S|((S,L),[S|(S,L)])

Where:

S represents a SCSI target ID. Do not use a leading zero 
when specifying target IDs. The LUN for the specified ID 
is assumed to be zero.

(S,L) represents a SCSI target/LUN ID pair.

"|" means "or".

For example, the /DM statement:

	BASEDEV=OS2CAM.ADD /DM:3|((2,1),[4|(5,1)])

reads "SCSI ID 3 LUN 0 or SCSI ID 2 LUN 1 and SCSI ID 4 
LUN 0 or SCSI ID 5 LUN 1".

This statement is evaluated as "SCSI ID 4 LUN 0 or SCSI 
ID 5 LUN 1" first. Whichever is true is then combined 
with "SCSI ID 2 LUN 1". This "and" combination is then 
"or"ed with "SCSI ID3 LUN 0". The IBM DASD manager is 
then used with the result.


Using the /!DM Option

This option disables use of the IBM-supplied DASD manager 
(OS2DASD.DMD) for the devices listed. The DASD manager is 
used to support direct access devices such as hard drives. 
To disable DASD manager support, the command line in 
CONFIG.SYS looks like this:

	BASEDEV=OS2CAM.ADD /!DM:S|((S,L),[S|(S,L)])

Where:

S represents a SCSI target ID. Do not use a leading zero 
when specifying target IDs. The LUN for the specified ID 
is assumed to be zero.

(S,L) represents a SCSI target/LUN ID pair.

"|" means "or".

For example, the /!DM statement:

	BASEDEV=OS2CAM.ADD /!DM:3,5

disables OS2DASD.DMD on devices at target IDs 3 and 5 
(both at LUN 0).


Using the /SM Option

This option enables use of the IBM-supplied SCSI manager 
(OS2SCSI.DMD) for the devices listed. To enable SCSI manager 
support, the command line in CONFIG.SYS looks like this:

	BASEDEV=OS2CAM.ADD /SM:S|((S,L),[S|(S,L)])

Where:

S represents a SCSI target ID. Do not use a leading zero 
when specifying target IDs. The LUN for the specified ID 
is assumed to be zero.

(S,L) represents a SCSI target/LUN ID pair.

"|" means "or".


Using the /!SM Option

This option disables use of the IBM-supplied SCSI manager 
(OS2SCSI.DMD) for the devices listed. To disable SCSI 
manager support, the command line in CONFIG.SYS looks 
like this:

	BASEDEV=OS2CAM.ADD /!SM:S|((S,L),[S|(S,L)])

Where:

S represents a SCSI target ID. Do not use a leading zero 
when specifying target IDs. The LUN for the specified ID 
is assumed to be zero.

(S,L) represents a SCSI target/LUN ID pair.

"|" means "or".



* Troubleshooting *


YOU CANNOT ACCESS THE SCSI DEVICE(S).

Make sure the SCSI device driver is installed properly.

Make sure each hard drive has power.

Verify that a BASEDEV = OS2CAM.ADD /V line exists in the 
CONFIG.SYS file. 

Verify that OS2CAM.ADD has been placed in the appropriate 
directory for your version of OS/2.

Check the cable connections and the host bus adapter 
installation.


THE COMPUTER HANGS OR LOCKS UP WHEN BOOTING AND THE SCSI 
DEVICES ATTACHED ARE NOT SEEN BY THE COMPUTER SYSTEM.

Make sure that all the SCSI devices are configured at 
different ID numbers (the boot drive should have the 
lowest ID).

Make sure both, but only, the ends of the SCSI bus are 
terminated.

Make sure the device driver is listed in CONFIG.SYS (and 
loaded when booting).

THE DEVICE DRIVER DOES NOT SEE ONE OF THE SCSI DEVICES.

Reboot the computer.

Make sure the SCSI devices have different ID numbers (the 
boot drive should have the lowest ID).

Make sure both, but only, the ends of the SCSI bus are 
terminated.

Check the cable and power connections.

OS/2 INSTALLS TO AN IDE DRIVE IN THE SYSTEM INSTEAD OF 
INSTALLING TO THE SCSI DRIVE.

The IDE drive must be physically disconnected and disabled 
in the CMOS setup before attempting to install to a SCSI 
drive.

NCR ADD ERROR: ONE OR MORE OF YOUR HOST ADAPTERS IS 
MALFUNCTIONING.

This is typically an interrupt problem. The system BIOS 
may not be assigning interrupts properly. Since some 
mainboard vendors require specific jumper settings to enable 
the IRQ set by the CMOS, check your manufacturer's 
documentation for proper jumper configurations. Then check 
that the PCI slot setup in the CMOS is assigned and not in 
conflict. If it is not assigned, it will show as NA. Assign 
it a value. The only way to verify that it is in conflict 
is to change the interrupt assigned to the slot in which the 
NCR adapter is placed. If you no longer get the error, the 
conflict is verified and you have successfully fixed the 
problem.

THE COMPUTER HANGS OR LOCKS UP DURING INSTALLATION, HAS 
SLOW INSTALLATION (7 hours), OR SLOW BOOT (35 minutes).

Some peripheral devices do not properly support the queue 
tag feature for SCSI. This can cause failure of the 
installation process. Add the /!Q option in CONFIG.SYS as 
follows:

		BASEDEV=OS2CAM.ADD /V /!Q