*************************************************************************** OS2DRV.TXT *************************************************************************** This file describes the features and use of the NCR SDMS device drivers for the OS/2 operating system environment. It is divided into the following sections: Introduction OS2CAM.ADD Features Description Installation Command Line Options Troubleshooting Important Additional Information High Speed Tape Drive Support *************************************************************************** ******************************* Introduction ****************************** The OS/2 Version 2.X operating system 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. OS/2 Version 2.X requires 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 2.X. We recommend reviewing the OS/2 2.X manual prior to proceeding. ******************************* OS2CAM.ADD ******************************** * Features * 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 * 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 complies with the same specification. * Installation * 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, double-click on System Setup. 2. Double-click on Device Driver Install. 3. Insert the floppy disk containing the NCR device driver in the source drive, then click on the change button for the destination directory. 4. Choose OS2 and click on the set button. 5. Click the install button. 6. Choose the NCR OS/2 2.X 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 OS2 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 select (double click on) the Device Driver Install icon. 2. Insert the floppy disk containing the NCR device driver in the source drive, then click on the change button for the destination directory. 3. Choose OS2 and click on the set button. 4. Click the install button. 5. Choose the NCR OS/2 2.X driver from the list provided by clicking on it once. The choice will be highlighted. Then click the OK button, then the EXIT button. 6. 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 OS2 directory on the boot drive. 7. 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 files OS2CAM.ADD and OS2CAM.DDP from the NCR distribution disks to the copy of "Diskette 1". 3. Edit the file CONFIG.SYS on the copy of "Diskette 1" by adding the following line: 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. 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 by high end systems 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.SYS) for the devices listed. The DASD manager is used to support direct access devices such as hard drives, and should be enabled unless an alternative is being used. To enable DASD manager support, the command line in CONFIG.SYS should look like this: BASEDEV=OS2CAM.ADD /DM: d|((d,d),[d|(d,d)]) Where: d,d,...d represents a SCSI target ID. The LUN for the specified ID is assumed to be 0. (d,d),(d,d),...(d,d) represents a SCSI target/LUN ID pair. "|" means "or". Using the /!DM Option This option disables use of the IBM-supplied DASD manager (OS2DASD.SYS) for the devices listed. The DASD manager is used to support direct access devices such as hard drives, and should be disabled only if an alternative is being used. To disable DASD manager support, the command line in CONFIG.SYS should look like this: BASEDEV=OS2CAM.ADD /!DM: d|((d,d),[d|(d,d)]) Where: d,d,...d represents a SCSI target ID. The LUN for the specified ID is assumed to be 0. (d,d),(d,d),...(d,d) represents a SCSI target/LUN ID pair. "|" means "or". Using the /SM Option This option enables use of the IBM-supplied SCSI manager (OS2SCSI.SYS) for the devices listed. To enable SCSI manager support, the command line in CONFIG.SYS should look like this: BASEDEV=OS2CAM.ADD /SM: d|((d,d),[d|(d,d)]) Where: d,d,...d represents a SCSI target ID. The LUN for the specified ID is assumed to be 0. (d,d),(d,d),...(d,d) represents a SCSI target/LUN ID pair. "|" means "or". Using the /!SM Option This option disables use of the IBM-supplied SCSI manager (OS2SCSI.SYS) for the devices listed. To disable SCSI manager support, the command line in CONFIG.SYS should look like this: BASEDEV=OS2CAM.ADD /SM: d|((d,d),[d|(d,d)]) Where: d,d,...d represents a SCSI target ID. The LUN for the specified ID is assumed to be 0. (d,d),(d,d),...(d,d) 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 line exists in the CONFIG.SYS file. Verify that OS2CAM.ADD has been placed in the OS/2 directory. 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 (boot drive should have 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 (boot drive should have 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 TO THE SCSI DRIVE. The IDE drive must be physically disconnected and disabled in CMOS setup before attempting to install to a SCSI drive. NCR ADD ERROR: ONE OF YOUR HOST ADAPTERS IS MALFUNCTIONING. Typically an interrupt problem. System BIOS may not be assigning interrupt properly. Check CMOS setup for PCI slot setup. Assign or change interrupt assigned to the slot in which the NCR adapter is placed. Reboot computer. ******************* Important Additional Information ********************** * High Speed Tape Drive Support * High-speed tape backup has become essential to computer systems as the capacities of hard disk drives have increased. For example, the NCR OS2CAM.ADD driver provides support for the Sytos Plus Version 1.35 (or above) Tape Backup System, and will function properly with the Sytos Plus software.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.