RADIO FREQUENCY INTERFERENCE STATEMENT
CAUTION: Changes or modifications to the ULTRA 34F not expressly approved by UltraStor Corporation could void the user's authority to operate this equipment.
NOTE: This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy, and, if not installed and used in accordance with the instruction, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult UltraStor Corporation or an experienced radio/TV technician for help.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
Information furnished by ULTRASTOR Corporation is believed to be accurate and reliable. However, no responsibility is assumed by ULTRASTOR Corporation for its use; nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of ULTRASTOR Corporation. ULTRASTOR Corporation reserves the right to change specifications at any time without notice.
IBM, OS/2, PC-DOS, and AT are registered trademarks of International Business Machines Corporation. MS-DOS is a registered trademark of Microsoft Corporation. DR DOS is a registered trademark of Digital Research. Xenix and SCO UNIX are registered trademarks of Santa Cruz Operations. UNIX is a registered trademark of AT&T. ESIX is a registered trademark of Everex Corporation. BMIC and Intel Unix 3.2 are registered trademarks of Intel Corporation. Novell and NetWare are registered trademarks of Novell Inc. QEMM386 is a registered trademark of Quarterdeck Office Systems. 386MAX is a registered trademark of Qualitas.
Copyright 1992, ULTRASTOR Corporation
All Rights Reserved
P/N 691-00011-00A
BIOS 38008-001 F/W 28008-003
ASSY 802-45288-00A
ULTRASTOR CORPORATION
ULTRA 34F
VL-BUS SCSI BUS MASTER CONTROLLER
USER MANUAL
Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2.0 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
3.0 Software Installation Package . . . . . . . . . . . . . . . . 3-1
4.0 Hardware Installation . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 ULTRA 34F Controller Setup . . . . . . . . . . . . . . 4-4
4.1.1 Controller Configuration . . . . . . . . . . . . . 4-6
4.1.2 SCSI Control Options . . . . . . . . . . . . . . . 4-6
4.2 SCSI Device Setup . . . . . . . . . . . . . . . . . . . 4-8
4.3 VESA System Setup . . . . . . . . . . . . . . . . . 4-10
5.0 Software Installation . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 Low Level Format and
ULTRA 34F Onboard BIOS Utility . . . . . . . . . . . 5-1
5.2 ULTRA 34F Software Layer Architecture . . . . . . . 5-3
5.3 DOS Installation . . . . . . . . . . . . . . . . . . . . 5-4
5.4 NetWare 386 V3.1x ASPI Controller Administration Manager . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5 Netware V2.2 SCSI Installation . . . . . . . . . . . . 5-10
5.6 SCO UNIX System V/386 Release 3.2.4 Installation . 5-12
5.7 UNIX System V/386 Release 4.0 . . . . . . . . . . . 5-15
5.8 OS/2 1.x ASPI Manager Installation . . . . . . . . . 5-20
5.9 OS/2 1.3 LADDR Installation . . . . . . . . . . . . . 5-23
5.10 OS/2 2.0 ADD Driver Installation . . . . . . . . . . . 5-24
6.0 Trouble Shooting Guide . . . . . . . . . . . . . . . . . . . 6-1
6.1 Possible Problems . . . . . . . . . . . . . . . . . . . . 6-4
2.0 Features
VESA VL-Bus Master Up To 66MB/Sec Transfers
Highly Reliable Advanced Design
ULTRA SCSI Controller Performance Provided by:
. 32 bit VESA VL-Bus Transfers
. 32 bit Internal Processor to Minimize Firmware Overhead
. 10MB/s FAST SCSI-2 Device Support
. Bus Master (up to 66MB/sec) Data Transfers
. Command Queuing and Sorting
. Low SCSI Command Processing Overhead
. Multi-thread Operation
. Scatter/Gather Support
. FAST Disconnect/Reselect
. Concurrent I/O Execution
Universal SCSI-1 & SCSI-2 Device Support
4 Selectable I/O Register Set (Supports Multiple Controllers to Co-reside)
Virtual Memory Support
32 Bit Memory Addressing (4GB) over the VESA Bus
Support for Up To 7 SCSI Devices (or 56 devices with Bridge Controller)
External High Density SCSI-2 Connector (Female 50 Pin Micro D Connector)
Current Limit Thermister Prevents SCSI Device Drainage from Reverse Connection
Active Terminators are Standard
Power Sequencing to Prevent Power Supply Overload
"NetWare Ready" Support
Extensive Defect Management Functions
Unique Support of Duplexing and Mirroring Under OS/2 LAN Manager
1.0 Introduction
UltraStor's family of disk controllers are designed to break the present system bottleneck. . .its I/O throughput. The ULTRA family of disk controllers provides the ultimate in speed and features ideally suited to meet the needs of the high capacity, high performance market. Its many advanced features are designed to support a broad range of applications, cost effectively and with ease of use.
The ULTRA 34F is a high performance VESA VL-Bus to SCSI controller supporting up to 7 SCSI devices (or up to 56 devices if a SCSI bridge controller is used). This controller is designed to support a variety of SCSI devices such as Hard disk, Tape, CDROM, DAT, WORM, MO rewritable disk, Scanner, Laser printer, etc.. A high speed 32 bit microprocessor provides the local intelligence for controller command processing.
This intelligent controller features Bus Master DMA data transfers up to 66MBytes/sec, low overhead SCSI command processing, command queuing, multi-threaded operation, scatter/gather, and disk defect management.
The ULTRA 34F controller conforms to the industry standard SCSI-1 and SCSI-2 specification. It automatically negotiates for FAST, synchronous and/or asynchronous data transfers without host/user intervention. SCSI features such as disconnect/reselect, command linking, and command queuing are implemented to take full advantage of multitasking environments.
The onboard BIOS allows OS drivers to interface efficiently to the controller and also provides users the ease of installing SCSI drives to the system.
In the enhanced Bus Master mode, a multi-thread, Mail-Box type, Bus Master protocol is implemented to reduce system CPU intervention and data command transaction overhead. Under the Bus Master enhanced mode operation, the controller will operate with a Bus Master data transfer rate up to 66Mbytes per second. Due to its efficient Bus Master command protocol, the system CPU is free most of the time to do other tasks while the controller's local CPU does all the command processing, SCSI device accessing, and data transfer operations. It interrupts the system CPU only when the command is completed or when an error has occurred.
The ULTRA 34F is fully compatible with UltraSCSI, a complete set of peripheral drivers (CD-ROM, Tape, Removable, etc) for MS DOS operating environments. Please contact your retailer for details on this complete package.ULTRASTOR CORPORATION
ULTRA 34F
VL-BUS SCSI BUS MASTER CONTROLLER
USER MANUAL
Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2.0 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
3.0 Software Installation Package . . . . . . . . . . . . . . . . 3-1
4.0 Hardware Installation . . . . . . . . . . . . . . . . . . . . . 4-1
4.1 ULTRA 34F Controller Setup . . . . . . . . . . . . . . 4-4
4.1.1 Controller Configuration . . . . . . . . . . . . . 4-6
4.1.2 SCSI Control Options . . . . . . . . . . . . . . . 4-6
4.2 SCSI Device Setup . . . . . . . . . . . . . . . . . . . 4-8
4.3 VESA System Setup . . . . . . . . . . . . . . . . . 4-10
5.0 Software Installation . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 Low Level Format and
ULTRA 34F Onboard BIOS Utility . . . . . . . . . . . 5-1
5.2 ULTRA 34F Software Layer Architecture . . . . . . . 5-3
5.3 DOS Installation . . . . . . . . . . . . . . . . . . . . 5-4
5.4 NetWare 386 V3.1x ASPI Controller Administration Manager . . . . . . . . . . . . . . . . . . . . . . . . 5-7
5.5 Netware V2.2 SCSI Installation . . . . . . . . . . . . 5-10
5.6 SCO UNIX System V/386 Release 3.2.4 Installation . 5-12
5.7 UNIX System V/386 Release 4.0 . . . . . . . . . . . 5-15
5.8 OS/2 1.x ASPI Manager Installation . . . . . . . . . 5-20
5.9 OS/2 1.3 LADDR Installation . . . . . . . . . . . . . 5-23
5.10 OS/2 2.0 ADD Driver Installation . . . . . . . . . . . 5-24
6.0 Trouble Shooting Guide . . . . . . . . . . . . . . . . . . . 6-1
6.1 Possible Problems . . . . . . . . . . . . . . . . . . . . 6-4
2.0 Features
VESA VL-Bus Master Up To 66MB/Sec Transfers
Highly Reliable Advanced Design
ULTRA SCSI Controller Performance Provided by:
. 32 bit VESA VL-Bus Transfers
. 32 bit Internal Processor to Minimize Firmware Overhead
. 10MB/s FAST SCSI-2 Device Support
. Bus Master (up to 66MB/sec) Data Transfers
. Command Queuing and Sorting
. Low SCSI Command Processing Overhead
. Multi-thread Operation
. Scatter/Gather Support
. FAST Disconnect/Reselect
. Concurrent I/O Execution
Universal SCSI-1 & SCSI-2 Device Support
4 Selectable I/O Register Set (Supports Multiple Controllers to Co-reside)
Virtual Memory Support
32 Bit Memory Addressing (4GB) over the VESA Bus
Support for Up To 7 SCSI Devices (or 56 devices with Bridge Controller)
External High Density SCSI-2 Connector (Female 50 Pin Micro D Connector)
Current Limit Thermister Prevents SCSI Device Drainage from Reverse Connection
Active Terminators are Standard
Power Sequencing to Prevent Power Supply Overload
"NetWare Ready" Support
Extensive Defect Management Functions
Unique Support of Duplexing and Mirroring Under OS/2 LAN Manager
3.0 Software Installation Package
Included in the software package that comes with the ULTRA 34F are:
1. ULTRA 34F SCSI Controller
Utilities & Device Drivers (DOS/NETWARE/OS2)
README : Readme file.
\DOS\USPI14.SYS : DOS device driver for supporting ASPI compatible device module interface used with ULTRA 34F.
\NETWARE\ASPITRAN.DSK : Novell NetWare 386 ASPI controller administration manager.
\NETWARE\U14_31X.DSK : Novell device driver for supporting ASPI compatible SCSI device manager.
\NETWARE\U14_2X.DSK : Novell NetWare 2.2 device driv-
\NETWARE\U14_2X.OBJ ers.
\OS2\DISK01.SYS : OS/2 device driver for supporting ASPI compatible SCSI device manager.
\OS2\ULTRA14.BID : OS/2 device driver for supporting LADDR Bus Interface Driver
2. USL UNIX SVR4 SCSI SDI Device Driver
System V/386 Release 4.0
: Device Driver and install script for System V, release 4 versions of UNIX
3. SCO UNIX MSCSI BTLD Device Driver
System V/386 Release 3.2.4
: Device Driver and install script for Release 3.2.4
4.0 Hardware Installation
SCSI Devices: Async or synchronous single ended SCSI-1 or SCSI-2 devices and manufacturer's instructions for setting jumpers as well as terminating resistors.
Computer: A PC with a VESA VL-Bus Master 32 bit slot. The PCs' power supply must be able to deliver adequate power and if it does not have enough drive power cables, you may need one or more Y-power cables.
Cables: Based on the installation options you have chosen, you will need an internal SCSI cable (50 pin flat ribbon cable) and/or an external SCSI cable (shielded cable with one connector a 50 position SCSI-2( AMP P/N 749621-5), or equivalent, and the other connector compatible with the interface port on your SCSI device).
Mechanical: You will need one or more screwdrivers or nut drivers to open the PC case and install the drives and controller board. A small pair of pliers or tweezers may be useful to change jumper settings.
Software: A bootable MS-DOS diskette that also contains the DEBUG, FDISK, and FORMAT external command files.
The controller exchanges information with the PC through a range of memory addresses and through some "input/output ports." If the ULTRA 34F is going to be the system's only disk controller, the default values for these numbers will probably work fine. If you wish to install it in addition to another controller, you will have to know the memory, port address, and IRQ address that the other controller uses and perhaps those used by other options installed in your PC.
Finally, you will have to know which operating system your PC will be using (PC-DOS or MS-DOS, OS/2, UNIX, or Novell) and which version of that operating system.
The ULTRA family of controllers support many different operating systems and networks. Installation instructions for several of them are included in this document.
There are three steps in the hardware installation prior to installing the operating system:
1. ULTRA 34F Controller Setup
2. SCSI Device Setup
3. VESA System Setup
CAUTION
Please take proper electro-static discharge precaution
when handling the board. Handle the product by
the ends of the board.
Table 1.0
Default Jumper Settings
Jumper Name Default Jumper Description
JP2 1-2 Factory Setting
JP3 7-8 IRQ 14
13-14 C8000 BIOS Starting Address
JP4 9-10 64 Head-32 Sector Mapping
11-12/13-14/15-16 Host SCSI ID of 7
JP10 1-2 Factory Setting
TABLE 2.0
CONNECTOR DEFINITION
J1 50 Pin Single-ended Internal SCSI Connector
J2 High Density SCSI-2 External Connector (50 pin
Female Micro D)
JP5 LED Connector
4.1 ULTRA 34F Controller Setup
TABLE 3.0
ULTRA 34F JUMPER DEFINITION
JP3 Jumper Block 1
1-2 : Motor Spin Up Sequencing
*OUT Automatically Drive Spin Up
IN Motor Spin Up from ID0 to ID7
3-4 : Sync Negotiation
*OUT ULTRA 34F Initiated Negotiation
IN Target Initiated Negotiation
5-6 7-8 : Interrupt Channel
OUT OUT IRQ15
*OUT IN IRQ14
IN OUT IRQ11
IN IN IRQ10
9-10 : SCSI Parity Control
*OUT Parity Enabled
IN Parity Disabled
11-12:13-14:15-16 : BIOS Segment
OUT OUT OUT Disable
OUT OUT IN C4000 - C7FFF
*OUT IN OUT C8000 - CBFFF
OUT IN IN CC000 - CFFFF
IN OUT OUT D0000 - D3FFF
IN OUT IN D4000 - D7FFF
IN IN OUT D8000 - DBFFF
IN IN IN DC000 - DFFFFTABLE 3.0 (Continued)
JUMPER DEFINITION
JP4 Jumper Block 2
1-2 3-4 : MailBox Port I/O Base
*OUT OUT 330H
OUT IN 340H
IN OUT 230H
IN IN 130H
5-6 : BIOS Support for more than 2 hard disk drives
*OUT : Maximum 2 hard disk drives per system
IN : Maximum 7 hard disk drives per controller
7-8 9-10 : Head mapping mode selection
OUT OUT : 16 head 63 sector mapping
*OUT IN : 64 head 32 sector mapping
IN OUT : 64 head 63 sector mapping
IN IN : 64 head 32 sector mapping
11-12:13-14:15-16 : Controller SCSI ID
OUT OUT OUT : (Manufacturer Reserved)
OUT OUT IN : ID 1
OUT IN OUT : ID 2
OUT IN IN : ID 3
IN OUT OUT : ID 4
IN OUT IN : ID 5
IN IN OUT : ID 6
*IN IN IN : ID 7
NOTE: * Indicates default settings. 4.1.1 Controller Configuration
. Bus Master Mailbox Port I/O Address
To select the mailbox port I/O base address according to the jumper definition JP4 pins 1-2 and 3-4.
Options: 330H/340H/230H/130H
. BIOS Address Selection:
For selection of onboard BIOS location by configuring jumper JP3 pins 11-12, 13-14, and 15-16.
Options :
C8000/CC000/D0000/D4000/D8000/DC000/C4000/Disable*
*If the BIOS is disabled, certain features will not function, e.g., support for more than 2 drives under MS DOS 5.0.
. IRQ Selection
Interrupt vector selection can be configured by jumper JP3 pins 5-6 and 7-8. Options IRQ14/IRQ10/IRQ15/IRQ11.
4.1.2 SCSI Control Options
. Motor Spin Up Sequencing
SCSI device motor spin up can be done by the SCSI device or by SCSI 'Start Unit' command issued from ULTRA 34F to the SCSI device. The spin up sequence starts from SCSI ID 0 device with 5 second intervals between each ID. This is to prevent power surge due to the heavy load of multiple SCSI devices. This option is set by jumper JP3 pins 1-2.
Options: Device Auto Spin Up/Sequential Spin Up
Device Auto Spin Up Device auto spin up upon power on.
Sequential Spin Up The controller issues SCSI 'Start Unit' to the SCSI device.
. Sync Negotiation
Synchronous transfer negotiation can be initiated by the target (SCSI device) or the initiator (controller). The negotiation is to determine the synchronous transfer, REQ/ACK offset and transfer period. If negotiation does not occur or fails, the default will be asynchronous transfer mode. Most SCSI devices default to Controller Initiated Negotiation. This option is set by jumper JP3 pins 3-4.
Some SCSI Drives will default to SCSI-1 timing (less than 2.0MB/sec if a "TARGET Initiated" configuration is selected. Be certain to configure for "Host Initiated" for maximum transfers and performance
Options: ULTRA 34F/Target Initiated Negotiation
. SCSI Parity
SCSI Data Bus Parity Check can be disabled or enabled using jumper JP3 pins 9-10.
Options: Enable/Disable
. Drive Mapping Mode
The drive mapping mode is set by jumper JP4 pins 7-8 and 9-10. The mapping mode is provided to support translation from Logical Block Address (LBA) used in SCSI commands to mapped drive geometry numbers used by most operating systems.
Options:
64 HD/32 SCTR Used by most SCSI controllers for compatibility
16 HD/63 SCTR Required if reading a drive used with this mapping on another controller
64 HD/63 SCTR Only required if the drive capacity is >1.2 Gbyte
. Support For More Than 2 Hard Drives
Jumper JP4, pins 5-6 determines the maximum number of hard drives supported, per controller, by the ULTRA 34F's onboard BIOS. Additional drives will be supported through software device drivers with DOS 4.01 or previous versions. Support for up to 7 drives per Controller through onboard BIOS is possible only with DOS 5.0 or later. Up to 3 Controllers can be used per system.
Options: 2 hard drives per adapter/7 hard drives per adapter
. Controller SCSI ID
Since the ULTRA 34F is one of the SCSI devices on the bus, an ID number needs to be assigned to it. Usually the H/A is given to the highest priority ID, i.e. 7. Make sure there is no duplication of the ID with the target devices. This controller ID can be set by jumper JP4, pins 11-12, 13-14 and 15-16.
Options: 7 / 6 / 5 / 4 / 3 / 2 / 1
4.2 SCSI Device Setup
Below are the three steps required to setup a SCSI device on a daisy chained 50 pin single ended SCSI cable.
1. SCSI ID Setup
The H/A controls up to 7 SCSI devices, with each device assigned to a unique ID number. Make sure that every device, including the ULTRA 34F controller, has its own unique SCSI ID. The ULTRA 34F SCSI ID is assigned using jumper JP4 pins 11-12, 13-14, and 15-16. Most of the SCSI devices use dip switches or jumpers to select SCSI ID. Refer to the device vendor for ID setting. The hard disk device with the lowest SCSI ID detected will be assigned as the boot drive (i.e. drive C:).
2. Motor Spin Up Option
If the Motor Spin Up Option in the jumper JP3, pins 1-2, selects the controller to issue SCSI "Start Unit" sequentially for all the SCSI devices attached, the SCSI devices need to be configured not to spin up the motor upon power on. Otherwise, the motor needs to spin up upon power on.
3. SCSI Cable and Terminators
The SCSI cable and terminators are important elements that affect the operation of the SCSI subsystem. The ULTRA 34F supports internal as well as external connections. The internal connector is a 50 pin header, compatible with nonshielded low-density cable connectors as specified in Fig. 4-4 of ANSI document X3.131 - 198X. The external connector is a 50 pin shielded high-density connector, compatible with shielded high-density cable connectors as specified in Fig. 4-6 of ANSI document X3.131 - 198X.
Only the devices that are connected at the ends of the SCSI cable need terminators; all the other devices' terminators must be removed. If both internal and external cables are used, the ULTRA 34F is not considered as either end of the SCSI cable; therefore, the terminators in the card (RP6 and RP7 near the internal connector) MUST be removed (See FIGURE 1.0). If only one cable, either internal or external, is connected to the adapter, the terminator must remain installed since the controller is at one end of the SCSI cable.
NOTE
Make sure that Pin 1 of the cable (usually designated by a colored stripe) is connected to Pin 1 of the SCSI device connector and to Pin 1 of the ULTRA 34F SCSI connector.
4. The ULTRA 34F supports Active Termination. If the SCSI Drive supports Active Termination, make sure it is Enabled; otherwise, performance may be limited when the drives default for slower SCSI timing; e.g. the drive may support FAST SCSI-2 timing only when Active Termination is Enabled.
4.3 VESA System Setup
After the SCSI device has been connected to the ULTRA 34F, turn on the system power to configure CMOS.
The following describes the two system CMOS drive type setup choices:
1. The ULTRA 34F is used as the primary controller. This is the standard configuration and works for most cases. The CMOS drive type needs to be set as "0" (NONE or Not Installed). The boot device is the hard disk device with the lowest SCSI ID.
2. The ULTRA 34F is used as the secondary controller. The primary controller may be an IDE controller, ST506 type controller, or ESDI controller, such as the ULTRA 12F. The ULTRA 34F will co-reside with the primary controller. The system CMOS drive type is set according to the primary controller and has no effect on the ULTRA 34F controller.
5.0 Software Installation
The ULTRA 34F onboard BIOS utility displays the number of attached SCSI devices, including information about device type, manufacturer, model number, logical drive number assigned, capacity and mapped drive geometry.
5.1 Low Level Format and ULTRA 34F Onboard BIOS Utility
After the system CMOS has been set up, the system will go through a boot up process. Upon boot up, the following screen will appear:
FIGURE 3.0
ULTRA 34F BIOS DISPLAY UPON BOOT UP
UltraStor ULTRA 34F SCSI Controller BIOS Version 1.00
COPYRIGHT (C) UltraStor Corporation, 1991
SCSI ID LUN DEVICE MANUFACTURER MODEL DRV# Capacity Cyl / Hd / Sec
4 0 HD MICROP 1528-15MD105 0 1341.8MB 650 64 63
5 0 HD MICROP 1598-15MB105 1 1038.3MB 503 64 63
7 H/A ULTRASTOR ULTRA 34F
Most SCSI hard disk drives are low level formatted and prepared to be defect free when shipped from the manufacturer, so it is not necessary and not recommended to perform any low level drive preparation.
The hard drive preparation utility in the BIOS is provided in case the drive has become unusable due to increased grown defects and a new low level format is necessary.
The ULTRA 34F onboard BIOS utility can be invoked with the following steps:
1. Load DEBUG program by typing
DEBUG after the DOS prompt ">" sign
2. Once in DEBUG program, following the prompt "-" sign, type
g=C800:5 or
whatever BIOS address the board is configured, i.e., if the board is configured to have BIOS address DC000, type
g=DC00:5
3. The "UltraStor SCSI Controller Utility Menu" will appear on the screen (See FIGURE 4.0). User can select the following four functions for any SCSI drive connected, using the "arrow" keys.
Verify Non-destructive surface verification. This routine verifies every logical block in the drive and reports the number of bad blocks found.
Scan Surface scanning of the entire drive. If a bad block is found, a SCSI 'Reassign Block' is issued to the drive to reassign the block to a good block so that a defect free drive can be achieved.
Format Low level format without any option specified. The drive will perform the low level format with all the default options implemented in the drive firmware, which should be the standard manufacturing drive preparation format.
Cformat Low level format with drive certification required (CLIST). After low level format, the drive firmware will run a surface certification process to map out all the defects and make the drive defect free. NOTE: This option is not implemented in all SCSI drives.
FIGURE 4.0
UltraStor SCSI Controller Utility Menu V1.01 (C) USC 1991
SCSI ID LUN Device Manufacturer Model DRV# Capacity Cyl / Hd / Sec
3 0 CD Sony CD-ROM CDU-5
4 0 HD MICROP 1528-15md105 0 1341.8MB 650/ 64 / 63
6 0 TAPE Sony SDT-1000
7 H/A UltraStor ULTRA 34F
Verify Scan Format CFormat
Surface scan with bad block reassigned
Use the "up-down arrow" keys to select drive, the "left and right arrow" keys to select function
Use "ESC" key to exit, "Enter" to execute, "F1" to pause/continue5.2 ULTRA 34F Software Layer Architecture
Prior to the installation of the operating system, it is helpful to understand the Software Layer Architecture used by the ULTRA 34F.
The SCSI interface allows a variety of devices connected to the same bus. In addition to hard disk drives, devices such as Tape, CDROM, and DAT are growing rapidly in popularity. It is very difficult for a single company to provide all the device drivers, utilities, and file systems to support all these devices. Despite the common SCSI interface protocol, each device differs in terms of characteristics. To handle a Tape or CDROM device is quite different from handling a hard disk drive.
The Software Layer Architecture of the SCSI subsystem can be described as:
FIGURE 5.0
Operating System
(DOS/OS2/UNIX/NOVELL . . )
Operating System Interface
Device Disk Tape DAT CD-ROM SCANNER
Specific
Handler
(Module) WORM MODSK PRINTER . . . . . . .
SCSI Software Layer Interface
(ASPI, LADDR, MSCSI, SDI . . .)
Controller
Driver H/A Device Driver
Controller Interface
SCSI ULTRA 34F
Adapter
SCSI BUS
SCSI Disk CD Tape WORM MO ... ...
Device
The ULTRA 34F software layer architecture is designed with the goal to provide a common software interface so that each device handler, whether in the form of device drivers or utility programs, can use the same software interface to communicate with the controller and SCSI devices. With this architecture, different controllers (from the same vendor or from different vendors) can share the same interface. The device handler or device module can be written specific to the device characteristics and not worry about the controller card being used.
The device module software can be supplied from the device vendor or from 3rd party software houses. Tape backup software such as SystosPlus from Sytron and Cheyenne Software, CDROM utilities from Corel, and Micro Design are examples.
UltraStor provides the device drivers for the SCSI software layer interface under various operating systems. Examples are MSCSI interface driver for SCO UNIX, and ASPI managers for DOS, OS/2, and Novell. (See FIGURE 6.0)
In addition to the above sources for device drivers, UltraStor markets a full set of SCSI peripheral drivers called "UltraSCSI". Please contact your reseller for availability and pricing.
5.3 DOS Installation
There is 1 EPROM on the ULTRA 34F for the BIOS code. The onboard BIOS will hook the system disk I/O service routine (INT 13H) to the ULTRA 34F VESA disk I/O service routine after system power on and before booting the operating system. After boot up, the controller is automatically operated under Bus Master DMA mode. There is no need for any software device driver in order to get the controller to operate under Bus Master DMA mode.
The BIOS supports up to two hard disks under DOS 4.01 or prior DOS versions and up to 7 hard disks per Controller under DOS 5.0 or later.
For DOS installation, follow the same procedure as you would for a regular ISA disk controller (such as ULTRA 12F) doing both FDISK and FORMAT.
Since the onboard BIOS services the system hard disk activity, the performance of the disk controller may depend on the speed of the BIOS execution. This not only slows down execution of the command transaction but also introduces more overhead to the Bus Master data transfer over the VESA bus since both BIOS instruction fetch and controller data transfers have to arbitrate for the same VESA bus. One alternate solution is to use the UltraStor DOS device driver USPI14.SYS program, which will replace the BIOS disk service routine and is resident in the system memory.
Please note that the BIOS supports only hard disk service routine. If devices other than disk are needed, such as CDROM, Tape, the software layer device driver USPI14.SYS is needed to provide ASPI (Advanced SCSI Programming Interface) compatible interface.
Although the ULTRA 34F is a true 32 bit controller, in running applications such as MS Windows 286, MS Windows, QEMM386 or 386MAX that use the virtual mode of the 386, the virtual address translation may be needed. Both the ULTRA 34F BIOS and USPI14.SYS support the industry standard "Virtual DMA Service".
UltraStor SCSI
A TOTAL SOLUTION THROUGH STANDARDS
UltraStor provides the complete ISA SCSI solution. UltraStor's standardized software interfaces conform to the SCSI standards that have emerged for each operating system, thereby supporting a wide range of SCSI peripherals. This standard software interface includes direct support for DOS-ASPI, Novell-ASPI, OS/2-ADD, AT&T UNIX-SDI, and SCO UNIX-MSCSI. By conforming to the resident operating system's SCSI support and/or defacto third party utilities, UltraStor provides a total solution for attaching disk, tape, and optical devices.
UTILITY SOFTWARE
The operating system resident or loadable third party utilities that support a wide variety of SCSI peripherals.
SCSI STANDARD LAYER
The standardized SCSI protocol layer that bridges the operating system to the SCSI controller. It is resident in the operating system and/or is a defacto standard provided by third party vendors.
ULTRASTOR SCSI INTERFACE
The UltraStor supplied software which allows the UltraStor SCSI adapter to conform to the operating system's SCSI STANDARD LAYER.If the application supports virtual DMA service, such as QEMM 386 version 5.0 and 386MAX version 4.08 or later, add the following line in the CONFIG.SYS:
device = USPI14.SYS
The USPI14.SYS file is in the DOS directory on the diskette labeled "ULTRA 34F VESA SCSI Host Adapter Utilities & Device Drivers (DOS/NETWARE/OS2)". Copy this file to the hard disk root directory or any other directory. If the USPI14.SYS file is not in the root directory, a path must be specified in front of USPI14.SYS.
Please check the vendor of the application program to see if the "Virtual DMA Service" is supported.
If the application doesn't support the Virtual DMA Service, a virtual buffer should be allocated to overcome the virtual address problem with Bus Mastering data transfers. Include the following line in the CONFIG.SYS to enable the double buffering:
device = USPI14.SYS /b
NOTE
When running Windows 3.0/3.1 enhanced mode, it is required that the "[386enh]" section of the SYSTEM.INI file in Windows contains the following line:
VIRTUALHDIRQ = OFF
Refer to Windows Users' Guide for how to modify the SYSTEM.INI file.
Once the USPI14 device driver is installed, the ASPI interface is available to the SCSI device software module. Refer to the device software vendor's documentation, such as Tape Back Sytos Plus from Sytron, CDROM utility from Corel, etc. for procedures to install device module using the ASPI interface.
5.4 NOVELL NetWare 386 V3.1x ASPI Controller Administration Manager
Installation of NetWare 386 for the ULTRA 34F is done through the use of NLMs (NetWare Loadable Module).
The ULTRA 34F device driver for the NetWare 386 consists of two parts, ASPI compatible SCSI device manager and embedded Hard Disk module. The ASPI compatible SCSI device manager provides a standard software layer interface to various SCSI device modules such as the tape module from Cheyenne, and optical disk module from COREL. The embedded hard disk module can be disabled through a command line switch (/NF). This is required only if the user wants to load his own ASPI compatible hard disk module.
The ULTRA 34F device driver is a re-entrant loadable module and supports up to 4 ULTRA 34F controllers in the same system. The loading sequence of the controllers is dependent on the address of the onboard BIOS, with the lowest address be the first and the highest address be the last. If no BIOS is supported, then the sequence is dependent on the sequence of the I/O Port Address.
The NetWare device driver U14_31X.DSK has been divided into two separate modules, U14_31X.DSK and ASPITRAN.DSK. This is designed to allow different SCSI controllers with an ASPI interface to co-reside in the same system. ASPITRAN.DSK is used for co-residency when using different SCSI controllers and for SCSI device software that looks for "ASPITRAN" to support the ASPI manager, e.g., the SBACKUP module in NetWare 3.11
STEPS:
1. Copy U14_31X.DSK and ASPITRAN.DSK from the diskette labeled "ULTRA 34F VESA SCSI Controller Utilities & Device Drivers (DOS/NETWARE/OS2) under the directory /NETWARE to the NetWare 386 "system" diskette(s) or the DOS partition in the hard disk that has the Netware 386 system files. If another controller provides ASPITRAN.DSK, the ULTRA 34F can co-reside with the adapter and use the other ASPITRAN.DSK.
2. The user only needs to load U14_31X.DSK in the console. The ASPITRAN.DSK will automatically be loaded into the system. The ASPITRAN.DSK needs to be loaded one time only, while the U14_31X.DSK needs to be loaded for every controller card installed in the system.
NOTE
When creating or editing the STARTUP.NCF, load ASPITRAN.DSK before loading U14_31X.DSK.
3. Type "server" to invoke NetWare installation.
4. Enter server name and internal network number in the NOVELL SERVER program. Following the prompt ":" enter the following command to load the device driver for the first ULTRA 34F controller:
:load U14_31X (load ASPI compatible with disk module enabled)
or
:load U14_31X /NF (load ASPI compatible with disk module disabled)
Loading module U14_31X.DSK
ULTRA 14 in port N1 has been loaded.
5. Reload the U14_31X loadable device module for next ULTRA 34F controller (if applicable).
:load U14_31X (load ASPI compatible with disk module enabled)
or
:load U14_31X /NF (load ASPI compatible with disk module disabled)
Loading module U14_31X.DSK
ULTRA 14 in port N2 has been loaded.
6. Repeat step 4 if more ULTRA 34F controllers are in the system. Up to 4 ULTRA 34F's can be installed in a VESA VL-BUS system..
7. If /NF was not used, go to step 8; otherwise with /NF, the disk module for the ASPI compatible layer must be loaded.
e.g. Universal disk module for ASPI from Corel :load UNIV.DSK
8. Load NetWare 386 "INSTALL" module
:load INSTALL
This invokes the system installation options. The drives that are attached to the ULTRA 34F controllers will be shown under the drive options.
Proceed with the NetWare 386 installation procedures to do partitioning, mirroring, volume creation and mounting, and surface testing of the hard disk drives.
NOTE: Please refer to the NOVELL NetWare 386 installation guide.
9. To use NetWare's SBACKUP, load NOVADIBI.NLM first (which provides the link to the ASPI) before invoking the SBACKUP Module.
e.g. :load DIBI\NOVADIBI
:load TSA
:load SBACKUP
In the SBACKUP menu, select device driver - "HP DIBI-2 Tape Driver".
10. For SCSI devices other than hard disk, the specific device loadable module must be loaded for linking to the ASPI layer interface. Please refer to the vendor of the device module for the installation procedure or utility.
For example, following are brief steps for installing the Tape module from Cheyenne ARCServe:
. Load U14_31X from NetWare server console
( /NF option is not required)
. Install ARCserve Manager from workstation
. Install Tape Driver from workstation
(Select ASPI controller software interface)
. Load TAPEDRV from NetWare server console
. Load ARCserve from NetWare server console
Detailed installation procedures can be found in the ARCserve installation procedures from Cheyenne.
5.5 NetWare V2.2 SCSI Installation.
This section describes the setup procedure for running the ULTRA 34F SCSI Controller under Novell NetWare 2.2.
Refer to Section 4.1 of this manual for the controller set up in the system.
The device driver consists of two files:
u14_2x.obj and u14_2x.dsk.
For installing NetWare 2.2 using the ULTRA 34F controller, it is recommended to use "INSTALL -E" to generate the operating configuration, and "INSTALL -L" to install the operating system on a file server.
If the operating system configuration is generated from floppy, use the ULTRA 34F VESA SCSI Controller Utilities & Device Drivers (DOS/NetWare/OS2), during NetWare installation. If the operating system configuration is generated from a hard drive or network, the device driver files need to be copied to a directory, "DSK_DRV_.211", which needs to be created on the hard drive or network drive used to install from. Refer to the DOS manual for creating a directory on a hard drive.
Select "UltraStor ULTRA 14 SCSI Controller" Disk Driver for the disk channels. The configuration options for ULTRA 34F are:
0 : I/O Base = 330h
1 : I/O Base = 340h
3 : I/O Base = 230h
6 : I/O Base = 130h
8 : I/O Base = 330h Verify On
9 : I/O Base = 340h Verify On
11 : I/O Base = 230h Verify On
14 : I/O Base = 130h Verify On
The configuration option should match to the jumper settings on the ULTRA 34F controller (JP4, pins 1-2 and 3-4). The "Verify on" option for NetWare fault tolerance is "Read After Write Verification".
Refer to the NetWare Installation guide for detailed installation instructions.
5.6 SCO UNIX System V/386 Release 3.2.4 Installation
SCO UNIX System V/386 Release 3.2.4 utilizes BTLD drivers (Boot-time loadable drivers), which allow drivers to be loaded during the initial installation, or on an existing UNIX system.
Boot-time loadable drivers are drivers which can be link-edited into the UNIX kernel during the boot process. The link-editing is done by boot after the driver is loaded into memory, but before the kernel is started. A BTLD enables SCO UNIX System V/386 to be installed either onto, or using, new hardware as soon as a driver for the hardware is available. It also allows SCSI connectivity for hard drives, and tapes, as well as CD-ROMs.
The two ways to install the UltraStor BTLD are; to a new UNIX system during installation, and to an existing UNIX system.
Part 1. Loading the UltraStor BTLD at installation time
1. Configuring an UltraStor ULTRA 34F in a computer system.
BIOS Address Selection : C8000 or
CC000/D0000/D4000/
D8000/DC000
IRQ Selection : IRQ14 or
IRQ10/IRQ11
/IRQ15
Drive Mapping Mode : 64 HD/32 SCTR, 2 DRV
(recommended) or
16 HD/63 SCTR, 2 DRV
64 HD/32 SCTR, >2 DRV
64 HD/63 SCTR, >2 DRV
System CMOS type : Type 0 or Not Installed
2. Insert SCO UNIX N1 disk into floppy drive A: and boot the system.
3. Enter link at the "BOOT:" prompt. The screen will display the following message:
What packages do you need linked in the system,
or 'q' to quit?
4. Enter u14pkg after the above message and a series of progress messages have been displayed:
fd(64)unix root=fd(64) swap=ram(0) swaplo=0 nswap=16 ronly mem=/p link="u14pkg" btld=fd(x)
memory found: OK - yyy, 1M - zM
Loading kernel fd(x)unix.text
........................................................................................................................
Loading kernel fd(x)unix.data
........................................................................................................................
Loading kernel fd(x).bss
5. Insert the ULTRA 34 MSCSI BTLD Device Driver into the floppy drive when the following message is displayed:
Please insert the fd(x)u14pkg volume and press <Return>.
A series of loading module messages will be displayed:
u14pkg.u14: Loading module fd(x)/u14pkg/driver/u14/Driver.o.text
u14pkg.u14: Loading module fd(x)/u14pkg/driver/u14/Driver.o.data
u14pkg.u14: Characteristic 'h' not supported; ignored
u14pkg: Driver"u14" successfully loaded.
NOTE: A successful link of the u14pkg BTLD can be verified with the following status lines during Initialization Selection and at boot time:
%disk - - - type=S ha=0 id=0 ht= fts=sdb
%Sdisk - - - cyls=ccc hds=hh secs=ss
6. Continue the installation to partition the disk and make the file system. The following screens will be displayed when the N1 floppy is extracted onto the hard disk:
The BTLD packages will now be extracted.
Please enter the u14pkg volume and press <Return>:
7. Insert ULTRA 34 MSCSI BTLD Device Driver into the floppy drive and continue installation until at least the Link Kit (Extended Utilities) package is installed.
8. After the operating system has successfully been installed, the UltraStor u14pkg BTLD will need to be added to the Link Kit. The following message will be displayed:
The BTLD packages will now be added to the Link Kit.
The following packages are on this disk:
NAME DESCRIPTION
u14pkg ULTRA 14/34 SCSI Controller Device Driver (Vx.xx)
Please enter the names of the packages you wish to install,
or q to quit
(default: u14pkg):
9. Insert the ULTRA 34 MSCSI BTLD Device Driver into floppy drive, then press <Return>. The following messages will display on screen:
Installing u14pkg
Installing device: u14
Installed u14pkg
10. The package has now been added to the Link Kit. The new UNIX kernel will now be rebuilt and the Link Kit will be used to add UltraStor u14pkg BTLD into the new system.
Part 2 Installing UltraStor BTLD to an existing SCO UNIX system.
1. Boot the system as superuser.
2. Insert ULTRA 34 MSCSI BTLD Device Driver into floppy drive and enter installpkg to add the UltraStor u14pkg BTLD to the Link Kit.
3. Enter u14pkg at the prompt:
Please enter the names of the packages you
wish to install, or q to quit:
4. The following messages will be displayed on screen:
Installing u14pkg
Installing device: u14
Installed u14pkg
5. The package has been added to the Link Kit. The new UNIX kernel will need to be rebuilt, by entering the following commands:
cd /etc/conf/cf.d
./link_unix
6. The UltraStor u14pkg BTLD has been built into the new system. The system will need to be shut down and re-booted in order for the new driver to be implemented.
Part 3 Adding Additional SCSI Peripherals to the System.
1. Boot the system as superuser.
2. Type mkdev hd to add a second hard drive, or mkdev tape to add a SCSI tape.
3. Enter u14 as the prefix of the SCSI controller.
4. Enter the appropriate id information, such as controller number, SCSI target ID and LUN number, for the devices attached.
5. Answer y to update SCSI configuration. Rebuilding of new UNIX kernel will take place.
6. Answer y to relink kernel, y to boot by default, and y to rebuild kernel environment.
7. When adding a second hard drive, mkdev hd needs to be invoked twice. After reboot, enter mkdev hd again to initialize the disk.
8. Refer to the SCO UNIX System V/386 Release 3.2.4 installation guide for further instructions.
5.7 UNIX System V/386 Release 4.0.
This section describes the installation procedure for running an ULTRA 34F SCSI controller in a computer system under UNIX System V/386 Rel 4.0 (SVR4). Various UNIX SVR4 offerings from UNIX System Labs, including Intel and Interactive, have been verified using this installation procedure.
There are two ways of installing the ULTRA 34F SDI Device Driver. First, if the UNIX SVR4 operating system has been installed using another vendor's controller, such as AHA 154x, the installation procedure will replace the existing SDI device driver with the ULTRA 34F SDI Device Driver, and then re-boot the system with the ULTRA 34F controller. Second, if installing UNIX SVR4 to a new drive, the installation includes creating an ULTRA 34F boot disk and linking the ULTRA 34F SDI Device Driver in the new kernel.
Part I. Installing UNIX SVR4 Using the ULTRA 34F Controller.
Step 1. Create an ULTRA 34F UNIX SVR4 Boot Floppy.
Locate the "Adaptec SCSI Boot Floppy 1/2" disk that comes with the UNIX SVR4 package, make a working copy of this disk and relabel it as "ULTRA34 Boot Floppy 1/2".
On an existing UNIX operating system, copy the UNIX SVR4 mini-kernel from the "ULTRA 34 SVR4 SDI Device Driver" disk to the new "ULTRA34 Boot Floppy 1/2".
Example:
Insert "ULTRA 34 SVR4 SDI Device Driver" disk in drive A: and type:
#cd /tmp
#tar xvf /dev/rdsk/f0q15d unix (for 5-1/4") or
#tar xvf /dev/rdsk/f03d unix (for 3-1/2")
Remove the disk and insert the "ULTRA 34 Boot Floppy 1/2" disk in drive A: by typing
#mount /dev/dsk/f0 /mnt
#cp /tmp/unix /mnt
#unmount /mnt
The ULTRA 34F UNIX SVR4 boot disk has been created.
Step 2. Installing UNIX SVR4 using the "ULTRA 34F Boot Floppy 1/2"
NOTE: Refer to ULTRA 34F SCSI Controller Reference Manual for configuring the ULTRA 34F. Certain configuration options should be setup as follows for installing UNIX SVR4:
.BIOS Address Selection : C8000 or
CC000/D0000/D4000
D8000/DC000
.IRQ Selection : IRQ14
.Drive Mapping Mode : 64 HD/32 SCTR, 2DRV
Other configuration options are user selectable and should be set based on the system requirements.
The system CMOS drive type needs to be set to "None" (or Not Installed) for drive 0 or drive 1.
After the configuration is complete, connect the hard disk and/or SCSI tape drives. Insert the "ULTRA 34 Boot Floppy 1/2" and power up the system.
The system will boot from the "ULTRA 34 Boot Floppy 1/2" disk. Continue the installation following the standard installation procedure of UNIX SVR4, either installing from floppy or tape cartridge.
At the completion of the installation, a new unix kernel will be generated which doesn't include the ULTRA 34F SDI Device Driver. The mini kernel which includes ULTRA 34F SDI Device Driver is renamed as "unix.old" and placed in the "/stand" directory. Step 3 will link the ULTRA 34F SDI Device Driver to a new kernel.
Step 3. Installing ULTRA 34F SDI Device Driver to the Kernel.
After step 2, the system will shutdown and will require re-booting. Since the ULTRA 34F SDI Device Driver is not yet in the new kernel, the booting process must use the original mini-kernel, which was renamed as "unix.old".
Re-boot the system. During boot time, when the message "Booting the UNIX System. . ." shown, press the space bar to prevent booting from the new kernel. When the message "Enter the name of a kernel to boot:" appears, enter "unix.old" and press <ENTER>. The UNIX SVR4 will boot using the original mini-kernel. After the system boots up:
1. Login as a superuser (root).
2. Change to tmp directory by typing
# cd /tmp
3. Insert the "ULTRA 34 SVR4 SDI Device Driver" disk in drive A: and type
# tar xvf /dev/rdsk/f0q15d Driver.o Install Name Remove System space.c u24.h u14.h
(for 5-1/4")
OR
# tar xvf /dev/rdsk/f03d Driver.o Install Name Remove System space.c u24.h u14.h
(for 3-1/2")
The files "Install", "Driver.o", "Remove", "Name", "System", "space.c", "u24.h", and "u14.h" will be copied to the "/tmp" directory.
4. Install and rebuild the UNIX kernel by typing
# ./Install
5. Select "14" for device driver interrupt.
6. After rebuilding the kernel, shutdown the system by typing
# cd /
# shutdown
7. Re-boot the system. UNIX will boot with the ULTRA 34F SDI device driver installed.
Part II. Replacing an Existing UNIX SVR4 With ULTRA 34F
The following procedure is for replacing the controller driver in a UNIX SVR4 system that was installed with another vendor's controller.
Step 1. Installing the ULTRA 34F SDI Device Driver.
Re-boot the system using the installed controller. After the system boots up:
1. Login as a superuser (root)
2. Change to tmp directory by typing
# cd /tmp
3. Insert the "ULTRA 34 SVR4 SDI Device Driver" disk in drive A: and type
# tar xvf /dev/rdsk/f0q15d Driver.o Install Name Remove System space.c u24.h u14.h
(for 5-1/4")
OR
# tar xvf /dev/rdsk/f03d Driver.o Install Name Remove System space.c u24.h u14.h
(for 3-1/2")
The files "Install", "Driver.o", "Remove", "Name", "System", "space.c", "u24.h", and "u14.h" will be copied to the "/tmp" directory.
4. Install and rebuild the UNIX kernel by typing
# ./Install
5. Select device driver interrupt, IRQ 15, 14, 11, or 10.
6. After rebuilding the kernel, shutdown the system by typing
# cd /
# shutdown
Step 2. Configuring the ULTRA 34F Controller in the System.
After shutting the system down, replace the existing controller with the ULTRA 34F. Refer to the ULTRA 34F SCSI Controller Reference Manual for configuring the ULTRA 34F. Certain configuration options should be setup as follows for installing UNIX SVR4:
.BIOS Address Selection : C8000 or
CC000/D0000/D4000
D8000/DC000
.IRQ Selection : IRQ 15, IRQ 14, IRQ 11, or IRQ 10
.Drive Mapping Mode : 64 HD/32 SCTR, 2DRV
Other configuration options are user selectable and should be set based on the system requirements.
After the configuration is complete, power down the system and connect the hard disk and/or SCSI tape drives to the controller, then power up the system. The system will boot with the ULTRA 34 SDI Device Driver installed.
The installation is complete.
5.8 OS/2 1.X ASPI Manager Installation
The UltraStor VESA SCSI Controller OS/2 device driver, DISK01.SYS, supports IBM OS/2 1.2, 1.3 and standard, and OEM versions of MS-OS/2 1.21. Some OEMs may modify their version of OS/2 and make the following procedures invalid. If problems occur, contact the OEM supplying the OS/2.
The UltraStor device driver for these OS/2 versions supports two controllers, and up to four SCSI hard drives.
Support for LAN MANAGER 2.0 is available only with MS-OS/2 1.21.
Additionally, the device driver supports the ASPI compatible software layer interface. SCSI device manager software, for tape or optical, that interfaces to the OS/2 ASPI interface, can be used with the ULTRA 34F SCSI controller.
The installation of the UltraStor OS/2 device requires replacing the DISK01.SYS device driver on the OS/2 installation disk. This replacement procedure works with IBM OS/2 1.2 or 1.3, and standard, and OEM versions of MS-OS/2 1.21.
OS/2 Installation for MS v1.21 and IBM 1.2
Before installing OS/2, check the size of the available space on the "Installation" disk. If the disk can accommodate the ULTRA 34F VESA SCSI Controller OS/2 device driver "DISK01.SYS", follow STEP 1. If there is not enough space for the driver, follow STEP 2.
IMPORTANT: Back up the original OS/2 "Installation" disk and use the backup copy to do the following. If following STEP 2, a second backup copy of the "Installation" disk will be required.
STEP 1: OS/2 Installation disk can accommodate the UltraStor OS/2 device driver.
1) Copy the file DISK01.SYS from the disk labeled "ULTRA 34F VESA SCSI Controller Utilities & Device Drivers (DOS/NETWARE/OS2), " to the backup copy of the installation disk.
e.g. A>copy a:OS2\DISK01.SYS b:
2) Boot the system with the modified "Installation" disk in drive A: and proceed with the installation, following the OS/2 installation guide.
STEP 2: OS/2 Installation disk cannot accommodate the UltraStor OS/2 driver.
1) Make a second backup copy of the "Installation" disk, delete FDISK.EXE, and copy DISK01.SYS from the "ULTRA 34F VESA SCSI Controller Utilities & Device Drivers (DOS/NETWARE/OS2)," disk. Use the second backup disk when asked to re-insert the "Installation" disk (see step 3).
2) Delete the *.RC@ files from the first backup copy of the installation disk and copy the UltraStor device driver, DISK01.SYS onto the disk.
3) Boot the system with the first backup copy of the installation disk in drive A: and proceed with the installation, UNTIL asked to re-insert the installation disk. When asked to re-insert the "Installation" disk, use the second backup copy of the disk.
OS/2 Installation for IBM OS/2 v1.3
1) Delete the files DISK01.SYS and DISK02.SYS from the "Installation" disk.
2) Copy DISK01.SYS from the "ULTRA 34F VESA SCSI Controller Utilities & Device Drivers (DOS/NETWARE/OS2)" disk to the OS/2 "Installation" disk.
e.g. A>copy a:OS2\DISK01.SYS b:
3) Boot the system with the modified "Installation" disk in drive A: and proceed with the installation, following the OS/2 installation guide.
LAN Manager Version 2.0 Installation
NOTE: LAN Manager works only with OS/2, version 1.21 or later.
OS/2 Installation with Disk Duplexing
Follow the OS/2 installation as described above, unless implementing disk duplexing.
1) If intending to use the disk duplexing function, select "Specify Your Own Partition", in the "Preparing the Fixed Disk" menu.
NOTE: Selecting "Accept pre-defined partition", or using the maximum size for primary partition will not allow setup for disk mirroring. The "Accept pre-defined partition" option will create a single boot partition on the drive 0, and the boot partition cannot be mirrored under LAN Manager, version 2.0.
2) In "Select the File System" menu, select "High Performance File System". Only the HPFS allows the disk duplexing function.
3) Continue the OS/2 installation, following the OS/2 installation guide.
LAN Manager Installation
1) After successfully installing OS/2, re-boot the system.
2) Insert the LAN Manager "OS/2 SETUP" disk in drive A:. Go to full screen and type "A:SETUP", to install LAN Manager.
3) From the "Install LAN Manager" menu, select "Server" option.
4) Refer to the LAN Manager documentation for further information.
Fault Tolerance Setup
1) After installing LAN Manager successfully, open the OS/2 window. Run "FDISKPM" to create a partition, and run "FTSETUP" for Fault Tolerance System Setup.
2) Refer to the LAN Manager documentation for further information.
5.9 OS/2 1.3 LADDR Installation
This describes the setup procedure for running the ULTRA 34 SCSI Controller in an EISA system under the Microsoft OS/2 LADDR implementation.
This device driver conforms to the LADDR architecture, e.g. Microsoft OS/2 version 1.3.
Some OEMs may modify their version of OS/2 and make the following procedures invalid. If problems occur, contact the OEMs supplying the OS/2.
The device driver,ULTRA14.BID, is a Bus InterfaceDriver that provides a communication path between the OS/2 operating system and the ULTRA 34 family of SCSI controllers. Through LADDR support, the device driver is able to provide the connections to various SCSI devices, such as hard disk, tape,CD-ROM, etc.
Follow the ULTRA 34F SCSI Controller Reference Manual to setup the controller in an VESA system.
Before installing the device driver, make sure the SCSI devices and the ULTRA 34 controller are setup in the system and ready for OS/2 instalation. Follow the ULTRA 34F SCSI Controller Reference Manual to setup the controller in the system.
The ULTRA 34F can be used as the primary bootable controller or as a secondary SCSI controller, provided that the system has a primary bootable disk controller, such as an ULTRA 12F. The installation procedure differs for each configuration.
Part I. Installing the ULTRA 34F as the Primary Bootable Controller
Since the ULTRA 14.BID is not in the OS/2 base load list of the LADDR BASEDD, the following steps are required to perform the installation.
Step 1. "IMPORTANT !!!" Back up the original OS/2 "INSTALL A" diskette and use the backup copy of the diskette to do the following.
Step 2. Copy ULTRA14.BID from the UltraStor's distribution diskette onto the OS/2 "INSTALL A" diskette.
Step 3. On the "INSTALL A" diskette, rename the ULTRA14.BID to BOOTBID.BID
e.g. A>ren ultra14.bid bootbid.bid
Step 4. Insert the "INSTALL A' diskette in drive A, re-boot the system to start the OS/2 installation. Refer to the OS/2 installation guide for detailed installation procedures.
Part II. Installing the ULTRA 34F as a Secondary Non-bootable Controller
Since the ULTRA14.BID is not in the OS/2 base load list of the LADDR BASEDD, the spare001.sys file is used to access the ULTRA 34 controller.
Step 1. Boot the system from the boot drive C:
Step 2. Copy the ULTRA14.BID from UltraStor's distribution diskette to the drive C: root directory, and rename it as spare001.sys
e.g. C:\copy a:ultra14.bid spare001.sys
Step 3. Re-boot the system to make spare001.sys in effect. Refer to the OS/2 installation guide for adding devices to the system.
5.11 OS/2 Version 2.0 ADD, Driver Installation
After installing OS/2 with Basic INT 13 services:
1. Copy the ULTRA 14.ADD file from the UltraStor install diskette to the "OS2" directory.
2. Modify the "CONFIG.SYS" file to contain the following statement:
BASEDEV = ULTRA14.ADD
3. Re-boot, and the UltraStor driver will now function in Bus Master 32 bit, protected mode.
6.0 Trouble Shooting Guide
Controller and SCSI Device Error Codes
Error codes may be displayed from the onboard BIOS during system bootup or when running BIOS Utility from DEBUG. The error code consists of 5 bytes in the following format. These bytes are expressed in 2 digit hexadecimal numbers:
HA TA - SK S12 S13
HA Controller error code
TA SCSI device Target Status byte
SK SCSI device Sense Key
S12 SCSI device Additional Sense Code Byte 12
S13 SCSI device Additional Sense Code Byte 13
NOTE
TA, SK, S12, and S13 are SCSI device related and are defined in the SCSI device technical reference menu.
Controller Error Codes
ERROR
CODE DEFINITION POSSIBLE CAUSE
00H No Error
01H Invalid command code
02H Invalid parameters
03H Invalid data list
30H CPU diagnostic error
31H Buffer RAM diagnostic
error
32H Static RAM diagnostic fail
33H Interface diagnostic System or controller related
See 1), 2), 3), 4) Possible
34H Adapter Cache Tag RAM Solutions
diagnostic fail
36H Invalid data in the
configuration register
40H Buffer underrun
41H Buffer overrun
42H Buffer parity error
91H SCSI bus selection SCSI device related See 1), 4), 5),
time out 6), 7), 8), 9) Possible Solutions
92H SCSI bus transfer System, controller OR SCSI
underrun / overrun device related. See 1) through 9)
Possible Solutions
93H Unexpected bus free
94H Invalid SCSI phase change
9BH Auto Request Sense error SCSI device related
9FH Command complete See 1), 4), 5), 6), 7), 8), 9)
message error Possible Solutions
A3H SCSI BUS reset error
NOTE: The above "Possible Causes" given to each individual error code are not the only possibilities for the occurrence of an error. The "Possible Solutions", following, may also assist in relieving the error.
Possible Solutions
1) Ensure that the power supply provides adequate power to the system AND the attached peripherals. The wattage demands of the system AND the peripherals must not exceed the output wattage of the power supply.
2) Check the jumper setting and reconfigure the ULTRA 34F if necessary.
3) Try the ULTRA 34F on a different system.
4) Try another ULTRA 34F on the same system.
5) Check terminators on the SCSI bus (controller, SCSI devices) and make sure they are properly set on BOTH ENDS of the SCSI bus.
6) Check for SCSI ID conflict in the SCSI bus by ensuring that each attached SCSI device has a unique SCSI ID.
7) Check cable connection and ensure that pin 1 of the cable is connected to pin 1 of the SCSI device and pin 1 of the controller SCSI bus connector.
8) Verify cable integrity by changing to a cable known to be working properly, or a new cable.
9) Verify integrity of SCSI device (target) by:
a) Attaching ONLY the SCSI device exhibiting a problem to the controller to isolate any conflict with other attached devices.
b) Attaching the SCSI device to a controller known to be functioning properly to ensure the SCSI device is problem free.
Unusual Occurrences
The following describes an unusual error condition which has been reported in some VESA System motherboards (assuming the ULTRA 34F is the acknowledged controller):
Symptom
During power up, undefined error messages are displayed by the ULTRA 34F BIOS.
NOTE: "Undefined" error message indicates an error code neither defined here nor in the SCSI Device Technical Menu. The "undefined" error code appears to be a random hexadecimal number.
Action
1. Reboot system from floppy. (It may take a few minutes for the system to boot.)
2. Run DEBUG to enter ULTRA 34F BIOS Utility MENU.
3. Check for "undefined" error messages.
If all SCSI device detection and display are successful, without error, see "Explanation" section below.
If "undefined" error messages are still displayed, check the following:
a. Ensure that theVEISA motherboard supports VESA VL-Bus Master mode transfers.
Explanation
Upon power up, the Controller transfers SCSI Pass Through Command/Status which resides in the controller BIOS RAM area using Bus Master Mode transfer. There have been reports that some system motherboards do not transfer into the adapter card BIOS RAM area properly, thus prohibiting the controller from executing the SCSI Pass Through Command correctly.
This problem does not exist under BIOS Utility Menu if the System motherboard does not have a problem performing Bus Master Burst transfer through the system memory area, since under DEBUG, the SCSI Pass Through Command/Status is resident in the system memory, not in the Controller BIOS RAM area.
Contact the system motherboard company if problems continue.
6.1 Possible Problems
System Hang at Boot Time
- Wait for error message.
- By process of elimination, remove the attached SCSI devices one at a time to find the problem source. Reboot the system with the Controller and no attached devices and check for "hang" or error messages.
- See Controller Error Code section.
Attached SCSI Device Not Displayed
- Wait for error message.
- Check cable connections.
- Try a different cable.
- Make sure SCSI device ID numbers do not conflict, especially with the Controller ID in the same BUS.
- Check Hard Disk Motor Spin Up.
- Check Termination on hard disk and Controller.
- See Controller Error Code section.
Debug Hangs
- Try a different BIOS address.
- See Add-on Card Conflict.
Add-On Card Conflict with ULTRA 34F
If a conflict exists with other add-on cards (video cards, network cards, or another hard disk controller/Controller), the symptoms are:
1. System "hangs" upon power up or BIOS Powerup display does not appear.
2. DEBUG cannot access ULTRA 34F BIOS Utility:
- Try to determine which cards have the conflict by the process of elimination. Leave the cards that have the conflict and the video card in the system only.
- Make sure ULTRA 34F BIOS Address does not conflict with other add-on cards.
- Make sure IRQ selection does not conflict with other add-on cards.
- Refer to "Debug Hangs" for solution.
Each Sector is Reported as Bad During Verify
- The drive media may not have been formatted - reformat in BIOS utility.
System BIOS Error Message at Boot Time
- "Shadow RAM Error at 3E00".
Try a different BIOS Address.
Don't Get Full Capacity Under DOS
- See Drive Mapping Options in Section 4.1.2.
Multiple Drives Support Under DOS 5.0 and Earlier DOS Versions
- DOS 4.01 or earlier versions support up to 2 hard disk drives.
- If more than 2 hard drives are attached under DOS 5.0, select the "BIOS support for more than 2 hard disk drives" jumper options.
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.