Ultra160 Family Manager Set for Windows NT®, Windows® 95/98, Windows 2000, Novell NetWare, SCO UNIX, and UnixWare User’s Guide RR
Copyright © 2000 Adaptec, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior written consent of Adaptec, Inc., 691 South Milpitas Blvd., Milpitas, CA 95035. Trademarks Adaptec, the Adaptec logo, AHA, AIC, EZ-SCSI, and SCSISelect are trademarks of Adaptec, Inc. which may be registered in some jurisdictions.
Adaptec Software License Agreement PLEASE READ CAREFULLY: THE USE OF THIS SOFTWARE IS SUBJECT TO THE SOFTWARE LICENSE TERMS OF ADAPTEC, INC. AND OTHER LICENSORS WHOSE SOFTWARE MAY BE BUNDLED WITH THIS PRODUCT. BY YOUR USE OF THE SOFTWARE INCLUDED WITH THIS PRODUCT YOU AGREE TO THE LICENSE TERMS REQUIRED BY THE LICENSOR OF THAT SOFTWARE, AS SET FORTH DURING THE INSTALLATION PROCESS.
3. Ownership of Software. As Licensee, you own the media upon which the software is recorded or fixed, but Adaptec and its licensors retain title and ownership of the Software recorded on the original media and all subsequent copies of the Software, regardless of the form or media in which or on which the original and other copies may exist. This license is not a sale of the Software or any copy. 4. Confidentiality.
9. Limitation of Liability. IN NO EVENT WILL ADAPTEC OR ITS LICENSORS BE LIABLE TO YOU FOR ANY INCIDENTAL, CONSEQUENTIAL OR INDIRECT DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, OR LOSS OF DATA, EVEN IF ADAPTEC OR A LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, OR FOR ANY CLAIM BY ANY OTHER PARTY. Some states do not allow the exclusion or limitation of special, incidental, or consequential damages, so the above limitation or exclusion may not apply to you. 10. Export.
Contents 1 Introduction Device Drivers 1-2 Adaptec Ultra160 Family Host Adapters 1-2 Requirements 1-3 2 Microsoft Windows NT Installation Installing the Driver When Installing Windows NT 2-2 Completing a Fresh Windows NT 4.0 Installation From Floppy Disk 2-2 Completing a Fresh Windows NT 4.0 Installation From CD-ROM 2-3 Installing the Driver When Windows NT is Already Installed 2-4 Updating Windows NT 4.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing Windows 95/98 3-4 Installing the Driver When Installing Windows 95 3-4 Installing the Driver When Installing Windows 98 3-5 Installing the Driver When Windows 95/98 is Already Installed 3-6 Updating the Driver for Windows 95 3-8 Troubleshooting 3-9 Problems and Solutions 3-9 4 Microsoft Windows 2000 Installation Installing the Driver When Installing Windows 2000 4-2 To Update the Driver When Windows 2000 is Already Installed 4
Contents Using the Load Command Line Options 5-9 adpt160m.ham Command Line Options 5-9 Bit Mask Options 5-11 Sample Load Commands 5-11 Using NetWare and the Host Adapter 5-12 Using Removable Media 5-12 Using the NetWare Tape Backup 5-13 Using a CD-ROM with NetWare 5-14 Optimizing Performance 5-15 Troubleshooting 5-16 Error Messages 5-16 6 SCO UNIX Installation Installing the Driver When Installing SCO UNIX 6-2 Installing SCO OpenServer 5.0.
Ultra160 Family Manager Set User’s Guide Modify the New System File 7-5 Rebuild the UnixWare Kernel 7-6 Boot the New Kernel 7-6 Using UnixWare and the Host Adapter 7-7 Using Tunable Parameters 7-7 Using Multiple Host Adapters 7-7 Removing the Driver 7-8 Troubleshooting 7-9 Problems and Solutions 7-9 Error Messages 7-10 Index x
1 Introduction The Adaptec® Ultra160 Family Manager Set is a set of software drivers and other files that enable your Adaptec Ultra160 Family host adapter to communicate with your computer.
Ultra160 Family Manager Set User’s Guide Device Drivers The Ultra160 Family Manager Set has one or more drivers file for each operating system. Use the table below to determine the correct driver for your operating system. Operating System Ultra160 Driver Windows NT adpu160m.sys Windows 95/98 adpu160m.mpd Windows 2000 adf6u160m.sys (Ultra160 19160) adpu160m.sys (all other Ultra160 cards) NetWare adpt160m.ham SCO UnixWare adst21 (UnixWare 2.1x) adst70 (UnixWare 7.01/7.
Introduction Requirements The following are the minimum and recommended requirements needed to install the Adaptec Ultra160 Family Manager Set: ■ A PCI computer, with an installed and configured Adaptec Ultra160 Family host adapter(s). ■ An installed primary (boot) floppy disk drive. The drive must be able to read your operating system disks. A 3.5-inch (1.44 MB) floppy disk drive is required. ■ The driver disks included with your Adaptec Ultra160 Family Manager Set.
2 Microsoft Windows NT Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set driver adpu160m.sys for Windows NT. The adpu160m.sys driver supports all Adaptec Ultra160 Family host adapters. Refer to the list on page 1-2. If you are performing a first time Windows NT installation, see Installing the Driver When Installing Windows NT on page 2-2. If Windows NT is already installed in your system, see Installing the Driver When Windows NT is Already Installed on page 2-4.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing Windows NT The adpu160m.sys driver is not embedded on the Windows NT 4.0 installation disks (or CD-ROM) and must be added during Windows NT installation. Completing a Fresh Windows NT 4.0 Installation From Floppy Disk 1 Create the Windows NT driver disk. For more information, refer to the Creating Family Set Driver Disks section of the Family Manager Set QuickStart Guide.
Microsoft Windows NT Installation Completing a Fresh Windows NT 4.0 Installation From CD-ROM 1 2 Insert the Windows NT 4.0 CD into the CD-ROM drive. Start your system. Press the F6 key when you see the following message: Setup is inspecting your computer’s hardware configuration... If you do not see this message, your system may not be setup to boot from a CD-ROM. You will need to install from floppy disks. See Completing a Fresh Windows NT 4.0 Installation From Floppy Disk on page 2-2.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Windows NT is Already Installed To update or install the adpu160m.sys driver if Windows NT is already installed, follow the instructions below for the version of Windows NT you are installing. Updating Windows NT 4.0 1 2 Start Windows NT. 3 4 5 6 7 Click the Control Panel. 8 From the Copy Manufacturer’s File From text box, type d:\fmsimage\fms111\windows\nt4_0\nt4, and click OK.
Microsoft Windows NT Installation Using Advanced Configuration Parameters Advanced users may use software parameters to alter the configuration of the Windows NT device drivers supplied by Adaptec. All Windows NT configuration information is stored in a data structure called the Registry. You can edit this information through a tool called the Registry Editor. ! Caution: Do not edit your registry unless it is absolutely necessary.
Ultra160 Family Manager Set User’s Guide ■ Maximum SGList — Specifies the maximum number of Scatter/Gather elements. Valid values are 17-255. The data type for this value is REG_DWORD. To enter Windows NT parameters, follow these steps: 1 2 3 Select Run from the Start button. Type regedt32 and press Enter.
Microsoft Windows NT Installation Using Driver-specific Parameters To use the Registry Editor to enter adpu160m.sys driver-specific parameters that affect the configuration information for Adaptec SCSI PCI device drivers, follow the instructions below. A list of valid parameters follows: Note: The following parameters are case-sensitive and must be entered exactly as shown. When entering multiple parameters, each parameter must be separated by a space.
Ultra160 Family Manager Set User’s Guide 4 5 Click on the adpu160m key. 6 7 Click on the Parameters key. Select Add Key from the Edit menu; type Parameters in the Key Name edit box. Leave the Class edit box blank. Select Add Key from the Edit menu; type Device in the Key Name edit box. Leave the Class edit box blank. To specify a certain host adapter, append Device with the number of the host adapter. For example, type Device0 for the first host adapter, Device1 for the second, etc.
Microsoft Windows NT Installation Follow the instructions below to enable Hot-Plug PCI support in the driver: 1 Insert the Family Manager Set CD-ROM for Windows into drive D. 2 3 Select Run from the Start menu. 4 5 Click OK. Type d:\fmsimage\fms111\windows\nt4_0\nt4\hotp160m.reg and press Enter. Reboot the system. Note: The file hotp160m.reg adds Hot-Plug related entries into the NT Registry, including the driver-specific registry value /HOTPLUG. Running hotp160m.
Ultra160 Family Manager Set User’s Guide Using Windows NT and the Host Adapter This section contains useful information on using Windows NT and your host adapter. Removing a Host Adapter Removing a host adapter can be as simple as physically removing it from the slot when your computer is shut down. Windows NT boots and functions properly in this configuration, but a Warning message is generated every time you boot Windows NT.
Microsoft Windows NT Installation Swapping a Host Adapter Swapping an Ultra160 Family host adapter for a non-Ultra160 Family host adapter is similar to the procedure for adding a host adapter. The important distinction is that you make all software configuration changes while Windows NT is running and before you make the hardware changes. Note: If you do not install the driver that comes with the new host adapter, it may result in a Windows NT boot failure.
Ultra160 Family Manager Set User’s Guide Troubleshooting Problems and Solutions I made changes to the host adapter configuration and Windows NT no longer boots! The boot manager for Windows NT contains recovery logic to allow you to return to the last known good configuration. If you have changed your host adapter configuration and Windows NT no longer boots, follow these steps to recover: 1 Undo any hardware changes you have made to the computer since it was last operational. 2 Reboot the computer.
Microsoft Windows NT Installation Error Messages Error messages generated by the adpu160m.sys driver can be viewed by opening the Windows NT Event Viewer error logs. To view events generated by the driver, follow these steps: 1 Double-click the Event Viewer icon in the Administrative Tools program group. Error messages generated by the driver show up as Event ID 11. Error messages generated by the SCSI port show up as Event ID 9. 2 To view event details, select System from the Log menu.
Ultra160 Family Manager Set User’s Guide adpu160m.sys Error Messages The following error messages are listed sequentially according to the last three digits of the error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc. Note: When reporting problems to Customer Support, be sure to include the complete error message in your problem description.
Microsoft Windows NT Installation [xxxxx023] Target device parity error The driver has detected a parity error by the target device. [xxxxx024] Data overrun or underrun The adapter was given more or less data than the expected amount of data. [xxxxx031] Target device queue full The target device internal buffer is full. [xxxxx032] Target device busy The target device reports a Busy status. Another program may already be using this device.
Ultra160 Family Manager Set User’s Guide [xxxxx097] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system. Verify that your system has at least the minimum amount of memory required by your operating system. [xxxxx0af] Unable to de-allocate memory that was allocated for a target device Normally, this is not a serious problem, unless you get this message frequently over a short period of time.
3 Microsoft Windows 95/98 Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set driver adpu160m.mpd for Windows 95/98. The adpu160m.mpd driver supports all Adaptec Ultra160 Family host adapters. Refer to the list on page 1-2. If you are performing a first time Windows 95/98 installation, see Installing the Driver When Installing Windows 95/98 on page 3-4.
Ultra160 Family Manager Set User’s Guide DOS Drivers for CD-ROM Access The CD-ROM drivers need to be installed only if DOS access to a CD-ROM drive attached to a SCSI host adapter is required. If Windows 95, Windows 98, or NetWare is already installed, or if the CD-ROM drive is not connected to a SCSI adapter, these drivers do not need to be copied or installed. However, you may choose to install these drivers if you are having trouble accessing your CD-ROM from NetWare or Windows 95/98.
Microsoft Windows 95/98 Installation Note: This will assign the CD-ROM to the next available drive letter, typically D if there is only one DOS drive. If you are using MS-DOS 5.0 and do not already have mscdex.exe, you will need to either upgrade to MS-DOS 6.0 or above. 4 Reboot your system. You are now able to access your CD-ROM drive from the command line and from Windows.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing Windows 95/98 Installing the Driver When Installing Windows 95 Note: Follow the Windows 95 Installation Guide to install Windows 95. If your Windows 95 CD came with a Windows 95 Boot disk, you will need to update the Windows 95 Boot disk. Copy the file aspi8u2.sys and aspicd.sys from the DOS directory of the Ultra160 Family Manager Set disk for Windows to the Windows 95 Boot disk.
Microsoft Windows 95/98 Installation Installing the Driver When Installing Windows 98 You will need to update the Windows 98 Boot disk that came with your Windows 98 CD. You need to do this on a system that has DOS, Windows 95, or Windows 98 already installed. Follow the instructions in DOS Drivers for CD-ROM Access on page 3-2. 1 Insert the Windows 98 boot disk into the floppy disk drive. Power on the system, insert the Windows 98 CD into the CD-ROM drive, and wait for the system to boot up.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Windows 95/98 is Already Installed To update or install the adpu160m.mpd driver if Windows 95/98 is already installed, follow these instructions: Note: All Adaptec Ultra160 Family host adapters use the adpu160m.mpd driver. Once the correct driver is updated, it is not necessary to update it again for each Ultra160 Family host adapter installed in your system. 1 2 Start Windows 95/98. 3 4 Click Properties.
Microsoft Windows 95/98 Installation 8 Click Change Driver. If you are prompted to select the hardware type, select SCSI Controller. 9 Click the Have Disk button and type: d:\fmsimage\fms111\windows\win9x as the path. 10 11 12 13 Click OK. Select the Ultra160 Family host adapter, and click OK. Click OK. The driver is copied and scanned. You must restart your computer for the changes to take effect. Click Yes to restart your computer. Click No to return to the System Properties window.
Ultra160 Family Manager Set User’s Guide Updating the Driver for Windows 95 This section covers the remaining steps for updating the driver on Windows 95, OSR 2. 1 Follow Steps 1 through 7 in the previous section, Installing the Driver When Windows 95/98 is Already Installed. 2 3 Click Update Driver. 4 Under Location type d:\fmsimage\fms111\windows\win9x, then click OK. 5 6 Click Finish. In the Update Device Driver Wizard, select Yes, then click Next.
Microsoft Windows 95/98 Installation Troubleshooting Problems and Solutions What is a miniport driver, and how do I make sure that the miniport driver for my host adapter is installed correctly? Miniport drivers are 32-bit Protected Mode device drivers used by Windows 95/98 to control host adapters and devices. Windows 95/98 includes a set of miniport drivers for various SCSI host adapters.
Ultra160 Family Manager Set User’s Guide 7 You must restart your computer for the changes to take effect. What if a yellow exclamation mark or a red X appears in Device Manager in front of my host adapter? This means there is some kind of resource problem. First, see if the names of any host adapters appear that are not actually installed in your computer. If so, select the name and click Remove.
Microsoft Windows 95/98 Installation If I am running under Windows 95/98, do I need lines for the Adaptec Real Mode ASPI drivers and mscdex.exe in my config.sys and autoexec.bat files? Usually, you do not need to use these Real Mode ASPI drivers, because the new Windows miniport drivers support most SCSI host adapters and SCSI devices. However, you need to load the drivers (including mscdex.
4 Microsoft Windows 2000 Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set driver for Windows 2000. The driver supports all Adaptec Ultra160 Family host adapters and ASICs. Refer to the list on page 1-2. If you are performing a first-time Windows 2000 installation, see Installing the Driver When Installing Windows 2000. If Windows 2000 is already installed in your system, see To Update the Driver When Windows 2000 is Already Installed on page 4-3.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing Windows 2000 1 Create the Windows 2000 driver disk. Refer to the Family Manager Set QuickStart Guide section, Creating Family Manager Set Driver Disks. Note: Windows 2000 will not install driver from CD. 2 Start your system with the Windows 2000 CD-ROM in the CD-ROM drive.
Microsoft Windows 2000 Installation a SCSI adapter other than an Adaptec SCSI Card 19160. Follow the steps in To Update the Driver When Windows 2000 is Already Installed to ensure all desired drivers are installed. To Update the Driver When Windows 2000 is Already Installed To update or install the driver if Windows 2000 is already installed, follow these instructions: 1 Start Windows 2000. 2 Click the Start button on the Windows 2000 task bar, and then point to Settings. 3 Click the Control Panel.
Ultra160 Family Manager Set User’s Guide 13 You may be asked to enter the path for the driver. See Driver Pathnames on page 4-4 for a list of pathname choices. 14 Click Finish. You may be required to reboot your system. Note: If your SCSI card is a dual-channel adapter (such as the Adaptec SCSI Card 39160), be sure to update both references in the Device Manager before rebooting.
Microsoft Windows 2000 Installation data structure supplied by Windows 2000, called the Registry. You can edit this information through a tool called the Registry Editor. ! Caution: Do not edit your registry unless it is absolutely necessary. If there is an error in your registry, your computer may become nonfunctional.
Ultra160 Family Manager Set User’s Guide To enter Windows 2000 parameters, follow these steps: 1 2 3 Select Run from the Start button. Type regedt32 and press Enter. Open the registry list to the following location: \HKEY_LOCAL_MACHINE\System\CurrentControlSet\ Services\adpu160m\Parameters\Device If the Parameters\Device keys already exist, skip to Step 8 below to begin entering values. If the keys do not yet exist, you need to create them by continuing with Step 4. 4 5 Click on the adpu160m key.
Microsoft Windows 2000 Installation the modified key are affected by the values you enter here. A list of valid parameters follows: Note: The following parameters are case-sensitive and must be entered exactly as shown. When entering multiple parameters, each parameter must be separated by a space. ■ /MAXTAGS=nnn—specifies the tagged command queue depth. If a number is not specified, the tagged queue depth defaults to 128. Valid values are 1-255. The data type for this value is REG_SZ.
Ultra160 Family Manager Set User’s Guide To specify a certain host adapter, append Device with the number of the host adapter. For example, type Device0 for the first host adapter, Device1 for the second, etc. If you omit the host adapter number, the configuration information applies to all Ultra160 Family host adapters. 8 9 Click on the Device key. Select Add Value from the Edit menu; type DriverParameters in the Value Name edit box. Enter REG_SZ as the data type and press Enter.
Microsoft Windows 2000 Installation Installing a New Host Adapter after Windows 2000 Is Already Installed To install a new host adapter after Windows 2000 is already installed, follow these steps: 1 2 Install the new host adapter. 3 Insert the Adaptec Family Manager Set CD-ROM into the CD-ROM reader and click OK. 4 5 The path will be displayed in the Copy Files from: box. Start Windows 2000. When the hardware wizard detects the card, click Yes to continue the installation.
Ultra160 Family Manager Set User’s Guide Removing a Host Adapter Removing a host adapter can be as simple as physically removing it from the slot when your computer is shut down. See the documentation for your host adapter for more information. Windows 2000 boots and functions properly in this configuration.
Microsoft Windows 2000 Installation 5 6 Reboot if prompted to. 7 Remove the old SCSI adapter and move all desired devices to the new adapter. See Removing a Host Adapter on page 4-10, for more information. 8 All attached devices should be recognized. Once the new SCSI adapter is functioning properly, power down your computer. Troubleshooting Most problems can be resolved by following the recommendations in Problems and Solutions.
Ultra160 Family Manager Set User’s Guide Error Messages Error messages generated by the Windows 2000 drivers can be viewed by opening the Windows 2000 Event Viewer error logs. To view events generated by the driver, follow these steps: 1 Double-click the Event Viewer icon in the Administrative Tools program group. Error messages generated by the driver show up as Event ID 11. Error messages generated by the SCSI port show up as Event ID 9.
Microsoft Windows 2000 Installation Driver Error Messages The following error messages are listed sequentially according to the last three digits of the error message. For example, [xxxxx010], [xxxxx011], [xxxxx012], etc. Note: When reporting problems to Customer Support, be sure to include the complete error message in your problem description.
Ultra160 Family Manager Set User’s Guide [xxxxx023] Target device parity error The driver has detected a parity error by the target device. [xxxxx024] Data overrun or underrun The adapter was given more or less data than the expected amount of data. [xxxxx031] Target device queue full The target device internal buffer is full. [xxxxx032] Target device busy The target device reports a Busy status. Another program may already be using this device.
Microsoft Windows 2000 Installation [xxxxx097] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system. Verify that your system has at least the minimum amount of memory required by your operating system. [xxxxx0af] Unable to de-allocate memory that was allocated for a target device Normally, this is not a serious problem, unless you get this message frequently over a short period of time. The memory can be reclaimed by rebooting the system.
5 Novell NetWare Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set driver adpt160m.ham for Novell NetWare— NetWare 3.2, 4.2, and 5.0. With the exception of SCSI Card 19160, the adpt160m.ham driver supports all other Ultra160 host adapters. Refer to the list on page 1-2. If you are performing a first time NetWare installation, see Installing the Driver When Installing NetWare on page 5-2.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing NetWare To install the adpt160m.ham driver when you install NetWare, follow the instructions below for the version of NetWare you are installing. NetWare 3.2 Follow these instructions only if you are installing NetWare 3.2 for the first time: 1 To complete NetWare 3.2 installation, go to the Novell Web site at: http://developer.novell.
Novell NetWare Installation 8 9 10 11 12 Copy the adpt160m.ham and adpt160m.ddi from the \fmsimage\fms111\nw3-4 directory of the Family Manager Set CD-ROM to the c:\server.312 directory. Run 312ptd.exe. Create the directory c:\server.312\cdsave. Copy cdrom.nlm to c:\server.312\cdsave Execute the following command lines to swap the server’s loader: cd 312ptd\native\loader lswap loader.exe \server.312\server.exe cd \server.312 13 Create the startup.ncf file in the c:\server.
Ultra160 Family Manager Set User’s Guide 17 Create the autoexec.ncf file. Add the following lines and then save the file. load after311 load c:\server.312\nwpaload search add 1 c:\server.312\cdsave load cdrom Note: Omit the search add 1 c:\server.312\cdsave and the load cdrom lines if the CD-ROM is attached to an Adaptec Ultra160 Family host adapter. 18 Load, from the console prompt, the following command: load c:\server.312\312ptd\patch312 19 Install the patches from the c:\server.312\312ptd directory.
Novell NetWare Installation NetWare 4.2 Follow these instructions only if you are installing NetWare 4.2 for the first time: 1 Begin installation of NetWare 4.2 on your server as instructed in your NetWare documentation. 2 When a screen appears that asks you to select a disk driver, press Insert. 3 Insert the Adaptec Family Manager Set CD-ROM into your CD-ROM drive. 4 Press F3 and type d:\fmsimage\fms111\netware\nw3-4 as the path to the adpt160m.ham driver for NetWare. 5 6 Select adpt160m.
Ultra160 Family Manager Set User’s Guide NetWare 5.0 Follow these instructions only if you are installing NetWare 5.0 for the first time: 1 Begin installation of NetWare 5.0 on your server as instructed in your NetWare documentation. 2 When a screen appears that asks you to add device drivers, select Modify and press Enter. 3 4 5 6 Select Storage adapters, and press Enter. 7 Press F3 and type d:\fmsimage\fms111\netware\v5_xx as the path to the adpt160m.ham driver for NetWare.
Novell NetWare Installation Installing the Driver When NetWare is Already Installed To update or install the adpt160m.ham driver when NetWare is already installed, follow the instructions in this section. The procedures are similar for all versions of NetWare. Procedures that are specific to a NetWare version are noted when necessary. 1 Make a backup copy of the old driver (if it exists) before installing the new driver. 2 Copy the adpt160m.
Ultra160 Family Manager Set User’s Guide Loading the Driver at Server Bootup To automatically load the adpt160m.ham at server bootup, the startup.ncf file (usually located in your server’s startup directory) must contain a load command line that specifies the location of the driver and any appropriate command line options (see Using the Load Command Line Options on page 5-9). For additional information on the startup.ncf file, refer to your NetWare documentation.
Novell NetWare Installation Using the Load Command Line Options You can specify several command line options when the driver is loaded. The available options are described in the table below. This table describes command line options for the adpt160m.ham driver for Ultra160 products. adpt160m.ham Command Line Options Option Values Default Description auto_disable_tagq= on, off off Enables/disables auto disable Tagged Queuing algorithm.
Ultra160 Family Manager Set User’s Guide Option Values Default Description lun_enable=1 0-FF 01 A bit mask to enable scanning for specific LUNs on all targets. The default value of 01 causes the driver to scan LUN 0 only. This enable bit mask is entered in hex (see Bit Mask Options on page 5-11.) max_tags= 1-128 16 Specifies maximum number of tagged commands per device. multlun_targets= 0-FFFF FFFF A bit mask to enable LUNs on selected targets. By default, LUNs on all targets are enabled.
Novell NetWare Installation Bit Mask Options Use the example below as an aid for calculating Bit Mask option hex values. Each SCSI device is enabled by a 1 in its corresponding bit position. The table that follows the figure, lists the binary-to-hex conversions. Using this example, if you want to enable scanning for LUNs 0, 2, and 6 on all targets, then use the command line option of lun_enable=0045.
Ultra160 Family Manager Set User’s Guide Using NetWare and the Host Adapter This section contains useful information on using NetWare and your host adapter. Using Removable Media The adpt160m.ham driver module fully supports removable-media disk drives, including magneto-optical drives. Removable media is treated as a standard SCSI hard disk, with some exceptions: ■ The driver only recognizes and registers media with 512 bytes/sector.
Novell NetWare Installation Mount Status Mounting causes a drive to come online as a NetWare storage device. Dismounted drives are inactive and cannot be accessed. Before you eject your current media, you should first Dismount it (menu choice 5). When the media status is Dismounted, you can eject the media. However, NetWare does not allow you to dismount it if the media is locked. To insert your new media, wait for the drive to spin-up, and then select the Drive Mount option.
Ultra160 Family Manager Set User’s Guide 2 When sbackup is loaded, it asks for a login name. Enter the appropriate name. 3 If sbackup asks you to select the device driver, select the HP DIBI-2 Tape Driver, regardless of the type of SCSI tape drive being attached (for example, even if the tape drive is manufactured by Wangtek, do not select the Wangtek driver). Note: Novell also includes a driver called adaptec.nlm. This driver is not needed and should not be loaded.
Novell NetWare Installation 3 Enter the following line at the prompt and then note the number and name of the CD: :cd device list 4 Enter the number or volume name of the CD at the command line: :cd mount [x] [name] 5 Edit the startup.ncf file to include the load commands in Step 1 and 2 above, if auto-mounting devices. 6 Edit the driver load command in the startup.ncf file to include the slot number (for example, load c:\server.312\adpt160m slot=2).
Ultra160 Family Manager Set User’s Guide Troubleshooting Error Messages The error messages listed below are the messages associated with the adpt160m.ham driver. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx080], [xxxxx081], [xxxxx082], etc. Note: When reporting problems to Customer Support, be sure to include the complete error code in your problem description.
Novell NetWare Installation [xxxxx085] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system. Verify that your system has at least the minimum amount of memory required by your operating system. [xxxxx087] Internal driver error An error has occurred while the driver was setting up its internal data structures. Try installing the most up-to-date version of the driver available from the Adaptec Web site.
Ultra160 Family Manager Set User’s Guide [xxxxx0ac] Driver already loaded for all host bus adapters The driver is already loaded for all the supported adapters in this system. [xxxxx0a4] SCSI bus reset by third-party hardware Hardware such as an array enclosure may have reset the SCSI bus. This is a normal condition unless you receive additional errors.
6 SCO UNIX Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set driver ad160 for SCO OpenServer 5.0.x. The ad160 driver supports Adaptec Ultra160 SCSI products. If you are performing a first time SCO UNIX installation, see Installing the Driver When Installing SCO UNIX on page 6-2, below, to begin driver installation. If SCO UNIX is already installed in your system, see Installing the Driver When SCO UNIX is Already Installed on page 6-3.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing SCO UNIX To install the ad160 driver at the same time you install SCO UNIX, follow the instructions below. Installing SCO OpenServer 5.0.x Follow these instructions only if you are installing SCO OpenServer 5.0.x for the first time. Note: Remember that UNIX commands are case sensitive. Enter the commands exactly as shown in the instructions. 1 Insert the SCO OpenServer 5.0.
SCO UNIX Installation Installing the Driver When SCO UNIX is Already Installed To update or install the ad160 driver if SCO UNIX is already installed, follow the instructions in this section. The procedures are similar for all versions of SCO UNIX. Procedures that are specific to a SCO version are noted when necessary. ! Caution: Improper or corrupt driver updates might destroy your existing UNIX file system. Back up all important files before proceeding.
Ultra160 Family Manager Set User’s Guide b To back up the current kernel configuration, type the following and press Enter after each line: umount /stand mount /dev/boot /stand cp /stand/unix /stand/unix.orig Note: If you ever need to boot up from the pre-update kernel, load the unix.orig backup kernel at the UNIX boot: prompt. To do this, type unix.orig and press Enter. c This step is optional. For extra security, you may back up the mdevice file and the sdevice.d directory.
SCO UNIX Installation c At this point, type ad160 and press Enter.
Ultra160 Family Manager Set User’s Guide – If you are not booting from an Ultra160 Family host adapter, make sure the host adapter prefix for the host adapter number 0 is the appropriate prefix for each device on your primary Adaptec host adapter. See the table above. e Save the file and exit the text editor. 4 Rebuild the UNIX kernel by following these steps: a Type the following at the # prompt and press Enter after each line: cd /etc/conf/cf.d ./link_unix Status messages appear on-screen.
SCO UNIX Installation Using SCO UNIX and the Host Adapter This section contains useful information on using SCO UNIX and your host adapter. Using Multiple Host Adapters If you are adding an additional Ultra160 Family host adapter to a system with an Ultra160 Family host adapter already installed, follow the instructions in the SCO UNIX documentation for adding devices using the mkdev command. When the system asks for the host adapter prefix, type ad160 and press Enter.
Ultra160 Family Manager Set User’s Guide Setting Parameters If the space.c file has not been modified, all the parameters are set according to the values specified by your SCSISelect utility for your Ultra160 Family host adapter. However, you can override the parameters by modifying the space.c file. The information you need to change the parameters is included in the space.c file. Examples are provided in the following sections.
SCO UNIX Installation Enabling Scatter/Gather and Tagged Queuing The ad160 driver supports Scatter/Gather and Tagged Queuing; however, the Sdsk (SCSI disk module) driver controls whether these features are enabled or disabled. Look for the Sdsk driver controls in the space.c file located at: /etc/conf/pack.d/Sdsk/space.c Troubleshooting My computer does not recognize my SCSI devices.
Ultra160 Family Manager Set User’s Guide computer for information about configuring IRQs and other parameters in the system CMOS setup. ■ The boot host adapters should be installed into the lowest PCI device number. The device number is determined by the slot number on the PCI bus. To find out the device number of your Ultra160 Family host adapter(s): a Run the SCSISelect utility (by pressing a key combination displayed on-screen at boot time).
SCO UNIX Installation ■ Ensure the Extended BIOS Translation feature in the SCSISelect utility is Disabled. The OS automatically selects the correct translation method as needed. ■ Examine the SCO UNIX mscsi file to make sure the correct host adapter and device are specified as the boot entry. The boot entry is the first Sdsk entry in the mscsi file (see Step 3 on page 6-5 for additional information). For SCO OpenServer 5.0.
Ultra160 Family Manager Set User’s Guide ■ Bus: Identifies the SCSI bus that the SCSI device is attached to. For most Adaptec host adapters, the bus number is 0. If you need to edit the mscsi file, use the vi editor. You must build a new kernel in order for any changes to take effect (see Step 4 on page 6-6). If you are booting from an Ultra160 Family host adapter and are using ISA/EISA-based host adapters as secondary devices, you must disable the BIOS on all ISA/EISA-based host adapters.
SCO UNIX Installation 5 6 7 8 9 10 After increasing the maximum size of configuration information, type q to quit. Type Y to update the system configuration files. Type ./link_unix and press Enter to relink the kernel. Type Y to boot from the new kernel by default. Type Y to rebuild the kernel environment. Reboot the system. Error Messages The error messages listed below are the messages associated with the ad160 driver.
Ultra160 Family Manager Set User’s Guide [xxxxx09D] Unexpected interrupt The Adaptec driver received an interrupt from the system that does not correspond to any adapter supported by the driver. This could be caused by another host adapter from a different vendor, such as a video card or a network card. The problem can also be caused by malfunctioning hardware. [xxxxx0a3] Adapter diagnostic failure - possible resource conflict The driver failed the internal software or hardware diagnostic.
7 UnixWare Installation This chapter explains how to install the Adaptec Ultra160 Family Manager Set drivers adst21 and adst70 for UnixWare—UnixWare 2.1x and UnixWare 7.01/7.1. The adst21 driver (or package) is used with UnixWare 2.1x. The adst70 driver (or package) is used with UnixWare 7.01/7.1. The adst21 and adst70 drivers support Ultra160 SCSI ASICs and host adapters. Refer to the Adaptec Ultra160 Family host adapters on page 1-2.
Ultra160 Family Manager Set User’s Guide Installing the Driver When Installing UnixWare To install either the adst21 or adst70 driver at the same time you install UnixWare, follow the instructions below. The procedures are the same for UnixWare 2.1x and 7.01/7.1. 1 Insert the Install disk of the UnixWare package into the boot floppy disk drive. Reboot your computer. Wait for the first UnixWare installation screen and prompt to appear, then follow the on-screen instructions.
UnixWare Installation Installing the Driver When UnixWare is Already Installed To update or install the adst21 driver or adst70 driver on a system where UnixWare is already installed, follow the instructions in this section. The procedures are similar for UnixWare 2.1x and 7.1. Procedures that are specific to a UnixWare version are noted when necessary. ! Caution: Improper or corrupt driver updates might destroy your existing UnixWare file system. Back up all important files before proceeding.
Ultra160 Family Manager Set User’s Guide Back Up the Computer If you have not already done so, back up all important files on the computer. See your UnixWare documentation for proper UnixWare file system backup procedures. 1 2 Log in as root at the UnixWare # system prompt. To back up the old UnixWare kernel, type the following and press Enter: cp /stand/unix /stand/unix.
UnixWare Installation 5 6 Type pkginfo -l adstxx and press Enter. Verify that the adst21 or adst70 driver is now listed. If the adst21 or adst70 driver does not appear in the pkginfo listing, turn to Troubleshooting on page 7-9. The listing should be similar to PKGINST: adst21 NAME: Ultra160 Driver for UnixWare 2.1x or PKGINST: adst70 NAME: Ultra160 Driver for UnixWare 7.1 Modify the New System File 1 Display the contents of the adst21 file by typing the following and pressing Enter: For UnixWare 2.
Ultra160 Family Manager Set User’s Guide Rebuild the UnixWare Kernel To rebuild the UnixWare kernel with the new changes, follow these steps: 1 Type the following at the # prompt and press Enter after each line: cd /etc/conf/bin ./idbuild -B Status messages appear. 2 When the kernel has been built, type the following and press Enter after each line (0 in -g0 is zero, not the letter O): cd /etc/conf/cf.
UnixWare Installation Using UnixWare and the Host Adapter This section contains useful information on using UnixWare and your host adapter. Using Tunable Parameters For UnixWare, some parameters are defined in the following files: /etc/conf/pack.d/adst21/space.c or /etc/conf/pack.d/adst70/space.c These parameters can be tuned for either the adst21 driver or the adst70 driver. Please refer to the comments in the appropriate space.c file for a description of these parameters. After modifying the space.
Ultra160 Family Manager Set User’s Guide Removing the Driver If you no longer need the adst21 or adst70 driver, you can use the following procedure to remove it completely: 1 2 Back up all important computer files. At the UnixWare root prompt, type the following: For UnixWare 2.1x: /etc/conf/bin/idinstall -d adst21 The following files will be deleted: /etc/conf/mdevice.d/adst21 /etc/conf/pack.d/adst21/Driver.o /etc/conf/pack.d/adst21/space.c /etc/conf/pack.d/adst21/disk.cfg /etc/conf/sdevice.
UnixWare Installation Troubleshooting Problems and Solutions My computer crashes or displays panic messages during the bootup procedure! You may have to boot from the backup kernel created earlier, and then perform the driver update procedure again. To boot from the old kernel, follow these steps: 1 2 Reboot the computer. At the Booting UNIX System… prompt or loading UnixWare graphics, press the Spacebar. 3 For UnixWare 2.
Ultra160 Family Manager Set User’s Guide Error Messages The error messages listed below are the messages associated with the drivers. Messages are listed sequentially according to the last three digits of the error code. For example, [xxxxx020], [xxxxx021], [xxxxx022], etc. Note: When reporting problems to Customer Support, be sure to include the complete error code in your problem description.
UnixWare Installation [xxxxx015] Error issuing command An error has occurred with the driver. Try installing the most up-todate version of the driver available from the Adaptec Web site. [xxxxx020] Adapter or target device not responding or not connected The target device did not respond to the adapter. If the device is present, refer to your host adapter’s user’s guide for troubleshooting information. If the device is no longer connected to the system, ignore this error.
Ultra160 Family Manager Set User’s Guide [xxxxx041] Command aborted [xxxxx042] Command aborted [xxxxx043] Command aborted [xxxxx044] Command aborted [xxxxx045] Command aborted An internal condition caused the driver to abort the command. In most cases, the command is retried and is recovered, and normal operation continues. [xxxxx046] Target device did not respond to abort sequence The target device did not abort the command requested by the driver. Some devices do not support the abort command properly.
UnixWare Installation [xxxxx096] Adapter hardware initialization failure - possible resource conflict The driver has attempted to initialize the adapter hardware but failed. This might suggest that the adapter resources (for example, IRQ) conflict with another board installed in your system. [xxxxx097] Unable to allocate memory This indicates that there may be a problem with the amount of memory installed in your system.
Index A Ultra160 Family 1-1, 1-2 ad160 driver 6-1, 6-5 updating 6-3 Adaptec Web site 4-13, 4-15 AHA-3960D 1-2 AIC-7892 1-2 AIC-7899 1-2 ASPI application 4-15 aspi8u2.sys 3-2 aspicd.sys 3-2 autoexec.bat 3-2 E B host adapters Ultra160 Family 1-2 hot-plug PCI 2-8 backup 5-13 bit mask options 5-9, 5-11 booting from UnixWare 7-5 C CD-ROM 3-2, 3-11, 5-2, 5-14, 6-1 CMOS setup 6-10 command line options 5-7, 5-8, 5-9 command syntax 7-3 config.
Ultra160 Family Manager Set User’s Guide Link Kit 6-5 Load command 5-7, 5-8, 5-11 lock status 5-13 LUN 2-5, 4-5, 5-10 maximum number in UNIX 6-8 O M parameters UnixWare 7-7 Windows NT 2-5, 2-6, 2-7, 4-6 parity checking in UNIX 6-8 pkgadd 6-1, 7-1, 7-2, 7-4 pkginfo 7-5 max_tag 5-15 mdevice file 6-4 miniport driver 3-9 mkdev command 6-7 mount status 5-13 mscdex.exe 3-2 mscsi file 6-11 mscsi file, modifying 6-5 multiple host adapters 7-7 N NetWare adaptec.nlm 5-14 adpt160m.
Index T tagged commands 5-10 tagged queuing 2-5, 4-5, 5-10, 6-9 tape backup 5-13 tape drive 6-1 troubleshooting NetWare 5-16–5-17 UnixWare 7-9–7-13 Windows 95/98 3-9–3-11 Windows NT 2-12, 2-16, 4-15 tunable parameters 7-7 U Ultra160 Family drivers 1-1, 1-2 host adapters 1-2 manager set 1-1 UNIX See SCO UNIX single-user mode 6-3 UNIX commands 6-2 UNIX kernel backing up 6-3 booting 6-6 UNIX Kernel, rebuilding 6-6 UnixWare adst21 1-2 adst70 1-2 booting 7-5 command syntax 7-3 DCU 7-2 device configuration util
R Adaptec, Inc. 691 South Milpitas Boulevard Milpitas, CA 95035 © 2000 Adaptec, Inc. All rights reserved. Adaptec and the Adaptec logo are trademarks of Adaptec, Inc. which may be registered in some jurisdictions. STOCK NUMBER: 512570-00, Ver.
