IN-2000 INSTALLATION GUIDE __________________________ Supports BIOS VCN: 887-01 ______________________________________________________________________________ ______________________________________________________________________________ CONTENTS ________ Introduction New Features Chapter 1, IN-2000 Installation Preparation Installing in the Motherboard Configuring the Switches BIOS Segment Address I/O Port Address Interrupt Channel (IRQ) DOS Multiple Drive Support Floppy Controller Installing Multiple IN-2000 Adapters DOS Novell NetWare OS/2 SCO UNIX WindowsNT Installing Floppy Drives Running Diagnostics Diagnostics Hot Key DEBUG Initiated Diagnostics Information About This Installation The Adapter Test BIOS Checksum Failure SCSI Logic Failure Data Buffer Failure Interrupt Logic Failure If Adapter Test Passes Chapter 2, Installing SCSI Peripherals SCSI Cables and Termination Internal External Termination Attaching SCSI Devices SCSI ID Hierarchy Configuring the System CMOS for SCSI Devices Running Diagnostics Option #1, "Show devices on SCSI bus" Option #4, "Hard Disk self-test" Low Level Formatting Hard Disks Option #8 "Low level format SCSI disk" Chapter 3, DOS Installations Compatibility Hardware Software ASPI or Native Support? Native (EPROM) Driver ASPI Driver SCSI Hard Drives Partition Priority Other SCSI Devices The IN-2000 CD-ROM Driver PLAYING AUDIO CDs Chapter 4, ASPI Manager for DOS ASPI Overview ASPI Manager Installation Chapter 5, Novell NetWare NetWare 4.x Installing The Driver Updating Existing Servers NetWare 4.x ASPI Manager Installing the Drivers Hard Disk and CD-ROM Support NetWare 3.x Installing the Driver NetWare 3.x ASPI Manager Installing the Drivers Hard Disk Support Chapter 6, SCO UNIX Installing the IN-2000 as the Primary Adapter Adding the IN-2000 as a Secondary Adapter Chapter 7, IBM OS/2 2.x Installing OS/2 Updating a Previous Installation Chapter 8, WindowsNT Installing NT Updating Existing Drivers Appendix A, Trouble Shooting Problems and Their Solutions Questions and Answers If All Else Fails ______________________________________________________________________________ INTRODUCTION ____________ The IN-2000 is one of the easiest SCSI host adapters to install and configure and offers exceptional performance. It comes complete with software support for many major operating systems and devices. This document provides comprehensive instructions for installing the IN-2000 host adapter, SCSI devices, device drivers, utilities and companion software packages. If this is a first-time installation, it's highly recommended that you read all Chapters, in sequential order, pertaining to your installation to avoid loss of data, or damage to your equipment. If you are already familiar with IN-2000 installations, this document will be a useful reference tool. ---NEW FEATURES--- This version of the BIOS (VCN: 887-01) has several new features: - Support for more than two hard drives under DOS is now automatically enabled by the SCSI BIOS (no more confusing switch changes). - Supports hard drives up to 8 GBytes formatted capacity (9.6 GB unformatted). - Supports most popular translations used by other SCSI manufacturers, so you can replace other SCSI adapters with the IN-2000 without having to re-format the SCSI hard drives. - BIOS now lists all attached SCSI devices by model and firmware versions during boot-up. - hot key option at BIOS post time that jumps you directly into the IN-2000 diagnostics. After exiting diagnostics, system continues booting normally. - SCSI hard drives are not required to be set for consecutive SCSI IDs, starting with ID 0. Example: three hard drives at IDs 2,3 and 5. You will be able to boot to the drive at ID 2 and access all three drives. You may then remove the drive at ID 2 and then boot to ID 3! (providing the drive at ID 3 is a bootable drive) The following bugs from the VCN: 1-03 BIOS have been fixed: - The "disk block size invalid" error comming from SCSI tape or CD-ROM. - The lack of support for the hard disk spin-up command during BIOS post. You must use ASPI manager versions of VCN: 461-13.14 or greater with this BIOS version. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 1, IN-2000 Installation ________________________________ ---PREPARATION--- Before installing the IN-2000 adapter in your system, you should retrieve all documentation and manuals for your system and its components. This will be extremely useful during the switch configuration process of the IN-2000 and throughout the installation. You should also have on hand a bootable DOS diskette with DOS DEBUG, FDISK and FORMAT installed on it. ---INSTALLING IN THE MOTHERBOARD--- Turn power off and disconnect all power cords before opening the computer case to access the components in the system. Be sure to "ground" yourself before handling the IN-2000 adapter or other components in the system. Remove the IN-2000 adapter from its packaging and insert into any available 16-bit AT or EISA type slot. The IN-2000 adapter will not function in an 8-bit slot. Make sure the IN-2000 bracket is connected firmly to the computer case with the bracket screw, assuring a good ground connection. ---CONFIGURING THE SWITCHES--- The IN-2000 adapter is completely configurable using one easily accessible 10 position DIP switch (see fig. 1). Most installations don't require any configurations other than the default setting at which the IN-2000 ships. To find out if that is true in your installation, you may need to consult the documentation for all other adapter boards in your system, such as: Video boards I/O boards Memory expansion boards Network adapters, etc. Refer to Figure 2 in the Quick Installation Guide for a listing of switch settings for the IN-2000. The IN-2000 adapter must be configured so that none of its addresses are the same nor overlap the addresses of your other adapters. For example, "sound cards" commonly use I/O port address 220h which is the same as the IN-2000 adapter's default I/O port address. The BIOS segment address, I/O port address and interrupt channel (IRQ) on the IN-2000 must be different than those settings on any other adapter in the system. ---BIOS Segment Address The IN-2000 can be set for three different segment addresses. It can also be disabled for some installations and for diagnostics (see Running Diagnostics later this Chapter). When running memory management programs, such as QEMM, you should exclude the IN-2000 BIOS address. Refer to your memory manager documentation for details on "exclusions". ---I/O Port Address The IN-2000 has four selectable I/O port addresses. I/O address conflicts are among the most common installation problems. Some of the known I/O conflicts with the IN-2000 come from audio cards and OS/2. If you have any audio cards in your system, they are probably using I/O port address 220h. It's best if you do not change the I/O address on the sound card, since that would require most of your audio software to be re-configured. It's recommended that you set the IN-2000 to an I/O address as far away as possible from the audio card's I/O address, because some audio software will access several I/O addresses in the region of the audio card. If the audio software accesses the I/O address that the IN-2000 is using, the system will probably lock-up. If you are using OS/2, you must not set the IN-2000 for I/O address 100h. OS/2 uses that address, and setting the IN-2000 there will cause the system to perform poorly or simply lock-up. ---Interrupt Channel (IRQ) There are four interrupt channels available on the IN-2000. The interrupt channel can be disabled for operation in some operating system environments or for diagnostic purposes. If you are installing the IN-2000 into a system that has a non-SCSI disk controller already installed, you should not use IRQ 14, since most other disk controllers default to IRQ 14. (In IBM PS/2 installations use IRQ 10) ---DOS Multiple Drive Support The multiple drive support for DOS is now automatically enabled in the BIOS. There are no drivers, jumpers or switches to configure anymore. ---Floppy Controller The floppy controller on the IN-2000 must be enabled if you wish to run floppy disk drives from it. The IN-2000 can control two floppy drives and supports 360K, 720K, 1.2MB and 1.44MB floppy drives. If there is more than one floppy controller installed in the system, only one controller should be enabled. ---INSTALLING MULTIPLE IN-2000 ADAPTERS--- When installing more than one IN-2000 adapter in the same system, you must select a separate BIOS address, I/O port address and interrupt channel. You must also be sure that only one floppy controller is enabled. There are limitations with some operating systems regarding how many adapters and what devices can be run on the adapters. The following paragraphs list currently known limitations. If any of these interfere with your installation, call Always Technology for possible solutions. ---DOS Up to four IN-2000 adapters can be installed, but only the IN-2000 at the lowest BIOS address (e.g., C800h-CBFFh) can control hard disk drives. ---Novell NetWare Up to four IN-2000 adapters can be installed. ---OS/2 Only one IN-2000 adapter can be installed at this time. Call Always Technology if you need additional support. ---SCO UNIX Only one IN-2000 adapter can be installed at this time. Call Always Technology if you need additional support. ---WindowsNT Up to four IN-2000 adapters can be installed. ---INSTALLING FLOPPY DRIVES--- Installing floppy disk drives on the IN-2000 is just like installing floppy drives on most other controllers. 1. On DIP-switch SW1, turn on switch 9 to enable the floppy controller. 2. Connect the floppy cable to the IN-2000. Make sure that pin-1 on the cable connects to pin-1 on the IN-2000. 3. Run your systems CMOS setup program to configure your A and B floppy settings to match the floppy drives installed on the IN-2000. If you are running floppy drives on another controller, be sure that the IN-2000 floppy controller is disabled (SW1-9 off). ---RUNNING DIAGNOSTICS--- Before attaching any devices, you should run diagnostics to verify the integrity of the IN-2000 installation. The IN-2000 comes with a diagnostic utility built in to it's BIOS. ---Diagnostics Hot Key The IN-2000 BIOS now has a hot key for initiating our built in BIOS diagnostics. When you power up the system, there will be a message "" imediately following our BIOS sign-on message. This message only lasts for two seconds, so you need to be quick! If you hit in time, the diagnostics menu will appear. You should then skip the next section "---Debug Initiated Diagnostics", and continue with "---Information About This Installation". If you are not able to bring up the diagnostics by hitting , continue with the following section. ---DEBUG Initiated Diagnostics The first thing you need to do is to make sure the address where you are loading the IN-2000 BIOS is unused. Use the following steps: 1. Disable the IN-2000 BIOS by turning switches 1 and 2 (on SW1) to the on position. 2. Turn on the system and boot from a bootable DOS floppy. 3. Run DOS's DEBUG.EXE program. 4. From the DEBUG '-' prompt, type either: D C800:0 or D D000:0 or D D800:0 to dump the selected memory address. Example: (see fig. 3) The "FF" in every position shows that the C800h address is unused. If the dump had shown any other Hex numbers, then you will need to try a different address. Once you determine which address is clear, then you need to: 1. Exit DEBUG by typing the letter Q and then press ENTER. 2. Enable the BIOS at the appropriate address (in the example, switches 1 and 2 turned off for C800h). 3. Run DEBUG again. 4. Dump the address, as you did in the previous step 4, to see if the IN-2000 BIOS loaded properly. Example: (see fig. 4) If you see the IN-2000 BIOS code (shown above), type: G=C800:8 for this example (type either: G=D000:8 or G=D800:8 if configuring for either of those addresses). This should bring up a menu of diagnostic options. Options 1, 4 and 8 will be discussed later in Chapter 2. ---Information About This Installation (Option 2) When option #2 from the "functions" menu is selected, it will display information about the IN-2000's current configuration. ---The Adapter Test (Option 3) Select option #3 from the menu. If the diagnostics pass, you will see the following: (see fig. 5) ---BIOS Checksum Failure The BIOS checksum of C600 is for the VCN: 887-01 version of the IN-2000 BIOS. If you have a different BIOS version, you will also have a different checksum number. If the adapter test reports a BIOS checksum failure, the BIOS on your adapter may be faulty. You may wish to return the board to the place of purchase. ---SCSI Logic Failure If the adapter test reports a SCSI logic failure, try the IN-2000 in a different slot or even a different system. If the test still reports a logic failure, the board should be returned to the place of purchase. ---Data Buffer Failure There are two failure modes for the RAM data buffer. The first is a "RAM buffer failure", and usually means the adapter is bad. However, in some few cases, it can be remedied by following the trouble shooting steps listed below. The second is a "RAM buffer data error", which can often be corrected with the following steps: - Make sure the IN-2000 is not in an 8-bit slot. - Try a different slot, in the event that the slot it's currently in is bad, or too close to a card that produces high levels of noise. - Sometimes a motherboard or power supply can produce high levels of noise. - Try a different I/O address. I/O port address conflicts with other adapters may cause this failure. - Try a different IRQ. Interrupt channel (IRQ) conflicts can also cause this failure. - Check the bus clock speed of the motherboard (refer to your motherboard manual). The standard bus clock speed is 8 MHz and should not be confused with the CPU clock speed. The IN-2000 will operate flawlessly at higher than standard bus speeds, providing the motherboard runs "clean" at those speeds. ---Interrupt Logic Failure The failure mode "Time out error, no interrupt detected", can usually be corrected with the following steps: - Try a different slot, in the event that the slot it's currently in is bad, or too close to a card that produces high levels of bus noise. Sometimes a motherboard or power supply can produce high levels of noise. - Try a different I/O address. I/O port address conflicts with other adapters may cause this failure. - Try a different IRQ. Interrupt channel (IRQ) conflicts can also cause this failure. - Check the bus clock speed of the motherboard (refer to your motherboard manual). The standard bus clock speed is 8 MHz. The IN-2000 will operate flawlessly at higher than standard bus speeds, providing the motherboard runs "clean" at those speeds. Later, when you have SCSI devices attached, you should run this test again. If it reports "Time out error, no interrupt detected", that indicates one or more of the following: - Bad or incorrect cabling (refer to SCSI Cables and Termination in Chapter 2). - Bad or incorrect termination (refer to SCSI Cables and Termination in Chapter 2). - Bad SCSI device, or SCSI device not powered on. ---If Adapter Test Passes Continue with Chapter 2 - Installing SCSI Peripherals. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 2, Installing SCSI Peripherals _______________________________________ ---SCSI CABLES AND TERMINATION--- The IN-2000 has an internal and an external SCSI connector. Both connectors can be used simultaneously. However, the maximum combined SCSI cable length is 6 meters (approximately 19 feet). ---Internal The internal SCSI cable is a 50-pin flat ribbon cable with two or more connectors. One end must connect to the IN-2000 and the other end to a terminated SCSI device. You may connect additional SCSI devices to the mid connectors (if available on your cable), but termination must be disabled on those devices. Refer to your SCSI device's manual for instructions on disabling termination (not to be confused with 'term power' jumpers). When connecting the cable to the IN-2000, make sure pin-1 on the cable connects to pin-1 on the IN-2000 SCSI connector (see fig. 1). If you wish to install more than two SCSI devices internally (up to seven), see your SCSI device supplier, or an electronics parts store, for cables that support more devices. ---External There are two types of external SCSI cables that can be used with the IN-2000. The first, has a 25-pin connector on one end for connecting to the IN-2000, and a 50-pin Centronics type connector on the other, for connecting to the first external device. The pinout on the 25-pin connector is the same as a Macintosh SCSI cable. The 50-pin connector is a standard SCSI connector. The second, is a "daisy chain" cable that lets you add additional SCSI devices. These "daisy chain" cables have standard 50-pin connectors on both ends. ---Termination Terminator resistors are used to stop signals from reflecting off the cable ends. Therefore, it's very important that termination is always and only installed at the cable ends. Incorrect termination can cause a variety of problems from data corruption to system lock-ups. On external devices, make sure that the manufacturer hasn't accidentally left the termination enabled internally in the device. The correct way to terminate an external device is with a terminator cap plugged into the device's unused (out) SCSI connector. The following is an example of a properly terminated installation of five external and two internal SCSI devices: (see fig. 6) ---ATTACHING SCSI DEVICES--- A total of seven SCSI devices may be attached to the IN-2000. These devices may be attached internally, externally or a combination of both. The devices' positions on the cable chain are unimportant, except in regards to termination. ---SCSI ID Hierarchy There are eight SCSI IDs on the SCSI bus. The IN-2000 is permanently set to SCSI ID 7, so that leaves IDs 0-6 for devices. SCSI hard disk drives may be set to any SCSI ID of 0-6. The drive at the ID will be the primary, the drive at the next lowest ID will be secondary and so on. All other SCSI devices may be set for any other SCSI IDs that are available. Make sure that no two devices have the same SCSI ID. Refer to your SCSI device's documentation for instructions on setting the SCSI ID for the device. ---Configuring the System CMOS for SCSI Devices SCSI devices are either handled by the SCSI adapter's BIOS (hard disk drives), or by drivers (CD-ROM, WORM, tape, etc.). Therefore, the CMOS setup's Fixed Disk settings should be set to "NONE" or "NOT INSTALLED" for SCSI devices. If you have any non-SCSI hard drives, they should be set-up in the CMOS per your non-SCSI hard drive's and controller's instructions. ---RUNNING DIAGNOSTICS--- When all of your SCSI devices are attached (and powered on, with external devices), you should rerun the diagnostics as described in Chapter 1. This time, you should also run option #1, "Show devices on SCSI bus", and option #4, "Hard Disk self-test" (if any SCSI hard disks are installed). ---Option #1, "Show devices on SCSI bus" This will list all eight SCSI IDs and what devices (if any) are using those IDs. If running this option does not display all IDs, 0-7, or if it locks up the system, then you probably have one of the following problems: - Bad or incorrect cabling (refer to SCSI Cables and Termination in Chapter 2). - Bad or incorrect termination (refer to SCSI Cables and Termination in Chapter 2). - Bad SCSI device, or SCSI device not powered on. - Two or more SCSI devices set for the same SCSI ID. ---Option #4, "Hard Disk self-test" This will let you initiate the SCSI hard disk's own built-in self test. If there are any errors reported, you should check your drive's documentation to see if the drive is configured properly, or call the drive manufacturer. The self test is not very "disk intensive", and will sometimes "pass" a hard disk, even if the disk is bad. This test will not destroy any data on the hard drive. ---LOW LEVEL FORMATTING HARD DISKS--- If your SCSI hard disk is new from the manufacturer, it is usually not necessary to low level format the disk. If the drive has been used with a different SCSI adapter, or is not formatted at the 512 byte (standard) sector size, then you should low level format the disk. When using the two following low level formatting programs, choose a "1 to 1" interleave for best performance results. ---Option #8 "Low level format SCSI disk" This option can be selected from the DEBUG diagnostics menu (refer to Chapter 1 - Running Diagnostics, From DEBUG) and will allow you to low level format a SCSI hard disk. However, it will only work if the disk has SCSI code set to the 512 byte (standard) sector size. If you have an "embedded servo" drive, the low level format routine discussed above, will report with "Format complete" within seconds of initiating the low level format. That is completely normal for those types of drives. **** Interrupting a low level format can render the disk unusable! **** ______________________________________________________________________________ ______________________________________________________________________________ Chapter 3, DOS Installations _____________________________ ---COMPATIBILITY--- ---Hardware In DOS installations, the IN-2000 can be installed as the primary or secondary hard disk adapter. When used as a "secondary" adapter, the system will boot from the IDE, ESDI or MFM drive under your motherboard (CMOS) BIOS control. For the IN-2000 to be used as the secondary hard disk adapter, the primary adapter or controller's hard drives must be configured in the system's CMOS setup. It's possible to install up to four IN-2000s in the same system, but only the first IN-2000 (determined by BIOS address) can control hard disk drives. ---Software The IN-2000 uses Advanced Programmed I/O architecture and is fully compatible with DOS and DOS software. There are several "virtual memory" handling programs (Windows, QEMM, 386MAX, etc.) that have special configuration options (e.g., Virtual DMA Systems drivers) for some SCSI adapters. These options are not needed with the IN-2000. When using memory managers, be sure to exclude the IN-2000's BIOS address (e.g., C800h-CBFFh). If the IN-2000 is not excluded, the memory manager might try loading drivers or Terminal Stay Resident programs (T.S.Rs) in the memory location used by the IN-2000 BIOS. ---ASPI OR NATIVE SUPPORT?--- Always Technology now includes Advanced SCSI Programming Interface (ASPI) managers for both DOS and Novell NetWare with both the IN-2000 and IN-2000 Pro adapter kits. Refer to Chapter 4 for more information on ASPI. This means that you now have a choice of two different hard disk drivers. The "Native" mode INT13 hard disk driver is built into the IN-2000's onboard EPROM BIOS. In addition, both the DOS and NetWare ASPI managers have drivers for hard drives. There are advantages to both: ---Native (EPROM) Driver: - Easiest to install. - Does not require any modifications to CONFIG.SYS. - Uses no system memory. ---ASPI Driver - Provides compatibility with popular software. - Supports automatic synchronous negotiation. If you plan to use your IN-2000 only for hard drives or for peripherals supported by non-ASPI compatible software you might want to initially install the Native driver. You can easily change to ASPI later, without the need to remove data from your drive(s). If you wish to run ASPI compatible software such as CorelSCSI!, Sytos Plus, or PC Tools 8.0, then you must run all of your peripherals, including your hard drive(s) under ASPI. Whether or not you intend to install ASPI you should first follow the procedure in this section to partition and format your hard drive(s) and to install DOS. Then if you plan to install ASPI refer to Chapter 4 for ASPI for DOS and Chapter 5 for information on ASPI for NetWare. ---SCSI HARD DRIVES--- Under DOS, the IN-2000 can control up to seven SCSI hard drives. On SCSI hard drives, you must install DOS just like you would with any other hard disk drive type. Install DOS on the drive(s) by following your DOS installation manual. ---Partition Priority When DOS assigns "drive letters" it assigns all primary partitions first, then the extended partitions. Logical DOS drives are contained within extended partitions and will be assigned with the extended partitions. If there are any non-SCSI hard disks installed, the primary non-SCSI partitions have priority over the SCSI primary partitions, and the extended non-SCSI partitions have priority over the SCSI extended partitions. The SCSI primary partitions have priority over the non-SCSI extended partitions. At this point, if you do not wish to add ASPI support, you have completed your hard disk installation. If you wish to support your peripherals (hard disk, tape, CD-ROM, etc.) under ASPI, refer to Chapter 4. ---OTHER SCSI DEVICES--- If you wish to run any SCSI devices, other than hard disk drives, you can do so with the CorelSCSI! software (included in Pro kit models). All IN-2000 kits ship with ASPI compatible CD-ROM and Floptical drivers. ---The IN-2000 CD-ROM Driver The CD-ROM driver is on the IN-2000 Utilities diskette, in the CDROM directory. Copy the file ASPICD.SYS to your boot drive and add the following line to your CONFIG.SYS file: DEVICE=d:\path\ASPICD.SYS where d:\path\ is the drive and directory to which you copied the CD-ROM driver. Re-boot the system for the change to take effect. After the system is re-booted and the CDROM.SYS driver has loaded, you need to run MSCDEX.EXE to gain access to the CD-ROM drive. Type: d:\path\MSCDEX.EXE /D:ASPI_CD where d:\path\ is the drive and directory where MSCDEX.EXE is located. You may also load MSCDEX from your AUTOEXEC.BAT file (recomended). When MSCDEX.EXE loads, it will display the new drive letter assigned to the CD-ROM drive. You should now be able to access all the data on the CD-ROM cartridge. MSCDEX.EXE has additional parameters that may be set for buffering, changing drive letters, etc. Refer to your MSCDEX.EXE documentation for more details. MSCDEX.EXE is available from Microsoft Corporation and included in MS DOS 6.0. ---Playing Audio CDs Some CD-ROM manufacturers include CD audio programs with their drives. Not all of these programs are compatible with the IN-2000 adapter and CD-ROM driver. Many of those programs are written specifically for the adapter that ships with the CD-ROM drive. Most generic CD audio programs, such as Windows 3.1 Media Player, are compatible with the IN-2000 CD-ROM driver. If you have Windows 3.1, and wish to use Media Player for CD audio, you need to add the MCI CD audio driver from the Control Panel, drivers section in Windows 3.1. Refer to your Windows 3.1 manual for more details. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 4, ASPI Manager for DOS ________________________________ ---ASPI OVERVIEW--- SCSI, which became an ANSI standard in 1984, defines the hardware and software interface between the host adapter and peripheral(s). Unfortunately, PCs and DOS were not designed with SCSI in mind. SCSI architecture can support a variety of SCSI devices (hard drives, optical drives, CD-ROMs, etc.) connected to a single SCSI host adapter. In the past, SCSI compatibility has been achieved through the writing of drivers for the operating system, host adapter, device and application software. Previously, there has not been a standard interface specification for writing SCSI drivers. Rapidly gaining in popularity, the Advanced SCSI Programming Interface (ASPI) has become a standard programming interface for writing SCSI drivers. ASPI offers compatibility to all software, devices, host adapters and operating systems that comply to its specifications. ASPI implementation is handled through layers: the manager layer that interfaces with the host adapter, the SCSI device modules and the operating system layer. The manager layer and operating system layer are combined to form the "ASPI manager". A separate ASPI manager is necessary for each operating system and host adapter. The device modules are SCSI device drivers written under the ASPI specification. The CorelSCSI! software (included with Pro kits) has a collection of device modules that support virtually any standard SCSI device. Other device modules are available from the device manufacturer, software manufacturer (i.e., tape backup, removable media, etc.) or the host adapter manufacturer. ---ASPI Manager Installation The ASPI manager is on the IN-2000 Utilities diskette in the DOS_ASPI directory. Copy the file ASPIDRVR.SYS to your boot drive and add the following line to your CONFIG.SYS file: DEVICE=d:\path\ASPIDRVR.SYS where d:\path\ is the drive and directory to which you copied the ASPI manager. ASPIDRVR.SYS should be loaded near the top of your CONFIG.SYS file. If you have any problems with device drivers loading before ASPIDRVR.SYS, try loading them after ASPIDRVR.SYS. Sample CONFIG.SYS FILES = 30 BUFFERS = 30 DEVICE = HIMEM.SYS DEVICE = EMM386.EXE DEVICE = ASPIDRVR.SYS DEVICE = (ASPI DEVICE DRIVER, such as ASPICD.SYS) etc. The ASPI manager must load in CONFIG.SYS before any ASPI device modules are loaded. The ASPI manager will not load successfully if the hardware interrupt (IRQ) on the IN-2000 is disabled (refer to Chapter 1, Configuring the Switches). The IN-2000 BIOS diagnostics, when initiated through DEBUG (Chapter 1), will lock-up the system if run when the ASPI manager is loaded. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 5, Novell NetWare __________________________ The IN-2000 supports all versions of NetWare 3.x and 4.x with your choice of ASPI or dedicated hard disk drivers. Call the Always BBS at 818 597-1400 if you wish to download drivers to support older versions of NetWare. The old drivers may require that you have an older version of the IN-2000 BIOS. If so, the older 1-03 BIOS will also be available on the BBS. The IN-2000 NetWare drivers are certified by Novell and will support all features, such as: - Spanning volumes. - Disk mirroring and duplexing. - Compatibility with greater than 16MB of memory in the server. - Supporting drives greater than a 1000MB formatted capacity. The Novell COMPSURF routine is no longer necessary with current versions of NetWare. ---NETWARE 4.X--- The NetWare 4.x driver for the IN-2000 is included in the Novell NetWare software package. To install this driver, just follow the NetWare installation instructions that ship with your NetWare 4.x package. If for any reason you need to do a manual installation of the NetWare 4.x driver, follow the procedure below. ---Installing the driver One or more IN-2000 SCSI Host Adapters must be installed in the 386 or 486 server prior to installation of NetWare and the Always driver. Please refer to the IN-2000 Installation Guide for instructions on installing the IN-2000(s) and hard drive(s). In particular, pay close attention to the switch settings. Only one floppy disk controller may be enabled in the system, including one, if present, on the motherboard. When using multiple adapters each adapter must have a different setting for I/O Port Address and Interrupt Channel. Multiple disk drives may be daisy chained from one IN-2000 SCSI Host Adapter. Each drive must have a different SCSI ID address setting. The ID addresses are automatically scanned from low to high. Netware 4.x does not need to be reconfigured if a drive is moved or it's address changed. Note that address restrictions may apply to a drive with DOS partitions. If necessary, before beginning Netware the installation, drives may be low level formatted as described in the Installation Guide. The copy the NetWare files from the \NOVELL4X directory to the directory from which the Netware server is loaded. This may be a DOS directory or a floppy. The driver is in 'NLM' format and is activated by a LOAD command from the server console. Normally after the initial installation of Netware, disk driver LOAD commands are stored in the STARTUP.NCF file to be automatically executed when the server is loaded. Port values must be specified which match the switch settings as described in the Preliminary Steps above. If no values are specified the defaults are: I/O Port Address: 200 Hex Interrupt: 15 (0F Hex) Sample load Command is LOAD \NOVEL386\ALWAYS PORT=200 INT=F The IN-2000 SCSI Host Adapter does not use a DMA channel. Therefore no value should be specified. The ALWAYS.DSK driver must be loaded for each IN-2000 adapter. Since it is reentrant, the subsequent load's do not cause the driver to be physically loaded a second time. ---Updating Existing Servers STEPS: 1) "Down" the server. 2) Boot under DOS. 3) Go to the NOVELL sub-directory for the hard drive, where the *.DSK file is located. 4) Copy ALWAYS.DSK from floppy to ALWAYS.DSK on the hard drive. 5) Reboot the server. ---NETWARE 4.X ASPI MANAGER--- Just as with DOS, you may support your SCSI peripherals either using a dedicated driver, or using an ASPI manager for NetWare. The IN-2000 ASPI manager is compatible with popular software that supports a wide range of peripherals on a NetWare server, including tape drives, CD-ROMs and juke boxes. Some better known products running under NLMs include Cheyenne "ARCServe", CorelSCSI! and NovaStor's "NovaNet". When using the ASPI drivers, it is possible to install up to four IN-2000 adapters, with up to seven SCSI devices per adapter. NetWare Ready and non-NetWare Ready drives may be installed on the same IN-2000 adapter without any special configuration procedures. It is important to keep in mind that if you run any peripheral connected to the IN-2000(s) under ASPI, then all peripherals connected to the IN-2000(s), including the hard disks, must run under ASPI. ---Installing the Drivers There are four NetWare files that are in the \NOVELL4X\ASPI directory on the IN-2000 Utility diskette. These drivers should be copied to the directory from which you will be loading NetWare. This directory can be on a hard disk or a floppy. These drivers are in the "NLM" format and are activated with the "LOAD" command from the server console. Normally, after the initial installation of NetWare, the driver load commands are stored in the "STARTUP.NCF" file to be automatically executed when the server is loaded. The first driver to be loaded is the ASPI manager, "IN-2000.DSK". The "IN-2000.DSK" driver will recognize all IN-2000 adapters installed in the server and should only be invoked once. Do not specify any I/O port addresses or interrupt channels when loading this driver. The following is the correct procedure for loading the ASPI manager: LOAD d:\path\IN-2000 where "d" and "path" are the drive and directory path where the "IN-2000.DSK" driver is located. ---Hard Disk and CD-ROM Support If you are using any IN-2000s for controlling hard disks or CD-ROMs, you must also load the ASPI hard disk/CD-ROM driver (ADAASPI.DSK). This driver should only be loaded once, even in multiple IN-2000 installations. The following is the correct procedure for loading the ASPI hard disk driver: LOAD d:\path\ADAASPI where "d" and "path" are the drive and directory path where the "ADAASPI.DSK" driver is located. ---NETWARE 3.X--- You can install up to three (four if using the ASPI manager) IN-2000s in a NetWare 3.x file server. NetWare will boot on the adapter with the lowest BIOS address. All adapters must have their BIOS's enabled (except under ASPI). ---Installing the Driver The NetWare 3.x driver is on the IN-2000 Utilities diskette, in the \NOVELL3X directory and is called ALWAYS.DSK. Copy ALWAYS.DSK to the directory from which the NetWare server will load. This may be a DOS directory on the hard disk or floppy. The driver is in the "NLM" format and is activated by the load command from the server console. Normally, after the initial installation of NetWare, disk driver LOAD commands are stored in the STARTUP.NCF file, to be automatically executed when the server is loaded. The ALWAYS.DSK driver must be loaded for every IN-2000 installed in the file server. When loading the driver more than once, it is loaded re-entrantly and only physically installed the first time. When loading the driver for IN-2000 adapters set for I/O addresses and interrupt channels other than default, you must specify the correct I/O port and interrupt in the load statement. The following is an example of a LOAD statement for the ALWAYS.DSK driver: LOAD ALWAYS PORT=220 INT=F This load statement would be for an IN-2000 set for I/O address 220h-22Fh and interrupt 15. Since the IN-2000 does not use any DMA channels, you should not specify a DMA value in the LOAD statement. ---NETWARE 3.X ASPI MANAGER--- Just as with DOS, you may support your SCSI peripherals either using a dedicated driver, or using an ASPI manager for NetWare. The IN-2000 ASPI manager is compatible with popular software that supports a wide range of peripherals on a NetWare server, including tape drives, CD-ROMs and juke boxes. Some better known products running under NLMs include Cheyenne "ARCServe", CorelSCSI! and NovaStor's "NovaNet". When using the ASPI drivers, it is possible to install up to four IN-2000 adapters, with up to seven SCSI devices per adapter. NetWare Ready and non-NetWare Ready drives may be installed on the same IN-2000 adapter without any special configuration procedures. It is important to keep in mind that if you run any peripheral connected to the IN-2000(s) under ASPI, then all peripherals connected to the IN-2000(s), including the hard disks, must run under ASPI. ---Installing the Drivers There are three files that are in the \NOVELL3X\ASPI directory on the IN-2000 Novell driver diskette. The first, "IN-2000.DSK", is the ASPI manager for NetWare 3.x. The second, "AHDASPI.DSK", is the ASPI hard disk device driver. The third, "ASPITRAN.DSK", is a dummy file required by third party ASPI device drivers. The files "IN-2000.DSK", "AHDASPI.DSK" and "ASPITRAN.DSK" should be copied to the directory from which you will be loading NetWare. This directory can be on a hard disk or a floppy. These drivers are in the "NLM" format and are activated with the "LOAD" command from the server console. Normally, after the initial installation of NetWare, the driver load commands are stored in the "STARTUP.NCF" file to be automatically executed when the server is loaded. The first driver to be loaded is the ASPI manager, "IN-2000.DSK". The "IN-2000.DSK" driver will recognize all IN-2000 adapters installed in the server and should only be invoked once. Do not specify any I/O port addresses or interrupt channels when loading this driver. When the "IN-2000.DSK" driver is loaded, "ASPITRAN.DSK" is automatically loaded along with it and will not need to be loaded manually. The following is the correct procedure for loading the ASPI manager: LOAD d:\path\IN-2000 where "d" and "path" are the drive and directory path where the "IN-2000.DSK" driver is located. ---Hard Disk Support If you are using any IN-2000s for controlling hard disks, you must also load the ASPI hard disk driver (AHDASPI.DSK). This driver should only be loaded once, even in multiple IN-2000 installations. The following is the correct procedure for loading the ASPI hard disk driver: LOAD d:\path\AHDASPI where "d" and "path" are the drive and directory path where the "AHDASPI.DSK" driver is located. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 6, SCO UNIX ____________________ The supplied IN-2000 SCO UNIX Boot Time Loadable Driver software will support SCO UNIX 386 system version 3.2 v 4.x and comparable Open Desktop versions. The IN-2000 can be used as the primary disk adapter or as a secondary adapter. Up to four hard disks may be installed on the IN-2000 under SCO UNIX. ---INSTALLING THE IN-2000 AS THE PRIMARY ADAPTER--- After completing the hardware installation of the IN-2000 and SCSI devices, Insert your SCO N1 boot disk into the A: drive and boot the system. From the "boot:" prompt, type "link" and press ENTER. When prompted for the package name, type "in2000" and press ENTER. When prompted for the driver diskette, insert the IN-2000 BTLD driver diskette into the A: drive and press ENTER. Follow the SCO documentation for the rest of the installation. When the installation is near completion, you will be prompted for the I/O port address and interrupt of the IN-2000. Enter these, and that will complete the IN-2000 related portion of the installation. ***NOTE*** SCO has SCSI tape support set for SCSI ID-2 and CD-ROM support set for ID-5. If you have more than two SCSI hard drives to install on the IN-2000, set the 3rd drive to SCSI ID-3 and the 4th drive to ID-4. Tape drives should ONLY be set to ID-2 and CD-ROMs should ONLY be set to ID-5. ---ADDING THE IN-2000 AS A SECONDARY DRIVER--- After installing the IN-2000 hardware in your SCO UNIX system, boot the system and login as a "single user". Insert the IN-2000 BTLD driver diskette in floppy drive 0 and then from the # prompt, type the following: -mount -r /dev/install /mnt /etc/btldinstall /mnt cd /etc/conf/cf.d ./link_unix haltsys Power down the system and connect your SCSI devices to the IN-2000. If you are installing hard drives, they should be set to SCSI IDs 0,1,3,4; using the lowest ID (0) for the first drive. If you are installing a SCSI tape drive, it must use SCSI ID 2. If you are installing a CD-ROM drive, it must be set to SCSI ID 5. Reboot, login as a single user again and follow SCO's instructions for configuring new devices in the system. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 7, IBM OS/2 2.x ________________________ --- INSTALLING OS/2 --- To install the IN-2000 AL1IN2.ADD OS/2 2.x driver, you will need to copy the AL1IN2.ADD driver file to a copy of the IBM OS/2 diskette labeled "DISK 1". If there is not enough free space on the floppy, you will need to delete some other .ADD driver from the diskette (one that you will not need for this installation). You will then need to modify the CONFIG.SYS on DISK 1 to load the driver. A sample CONFIG.SYS called CONFIG.OS2 in the \OS2 directory on the IN-2000 Utility diskette. You may add support for LUNs by adding the "/et" to the al1in2.add load line in config.sys. - This version of the driver also supports Scatter Gather. - This driver supports SCSI tape and has been tested with NovaStor's NovaBack 2.02b for OS/2 2.x. This driver will not currently allow you to boot to DOS with ASPI loading and then loading OS/2. We will support this feature in the final release. Some SCSI devices can cause system failures when initiating synchronous data transfers. Setting the device to "async" or "sync initiated by host" will usually resolve this problem. ---UPDATING A PREVIOUS INSTALLATION--- In the sample CONFIG.OS2, there are several lines highlited by REM statements. Just add the lines that apply to your installation. All installations will need to load al1in2.add and os2scsi.dmd. If you will be using SCSI hard drives, you also need to load os2dasd.dmd. If you will be using CD-ROM drives, you also need to load os2cdrom.dmd, vcdrom.sys and ifs=cdfs.ifs. NOTE: Do not install this driver with the OS/2 2.1 Service Pack XR06200. If you have this Service Pack, call the Always BBS at 818 597-0275 and download the latest driver that supports the Service Pack (to be released soon). Warning! In OS/2 installations, do not set the IN-2000 for I/O port address 100h - 10Fh. Doing so will cause extremely slow performance or system failures. ______________________________________________________________________________ ______________________________________________________________________________ Chapter 8, WindowsNT _____________________ Up to four IN-2000 adapters may be used in a WindowsNT installation. The priority sequence of the adapters is determined by the I/O port address of the adapter (the lowest I/O address setting is primary). Only the primary IN-2000, with the boot drive attached, needs to have its BIOS enabled. All other IN-2000s may be configured with the BIOS disabled. The IN-2000 adapters will support any SCSI device that is currently supported under WindowsNT. Microsoft WindowsNT ships with built-in support for the IN-2000 adapter. To install our latest WindowsNT drivers, just follow the procedure below. ---INSTALLING NT--- 1) Setup your target system with the desired hardaware configuration. 2) Boot from the NT Setup and Install diskette. 3) Setup will be loaded automatically: The first screen will prompt you to install (Enter), repair (R), or exit (F3). Press enter. The next screen will ask if you wish to run an express or custom(Enter) install (C). To add a third party adapter driver, you must choose custom. Press C. Setup will scan for internally supported adapters. When the scan is done, you will be asked if you wish to add additional SCSI host adapters. Press S. You will be given a list of adapters, with the entry "Other" highlighted. Press enter. You will be prompted for a driver disk. Insert this diskette and press enter. You will be given a choice of AL-7000 and IN-2000 drivers. Highlight IN-2000 and press enter. The IN-2000 driver will be loaded. You will be asked if you wish to load additional drivers (S) or continue installing (Enter). Press Enter. 4) From this point, setup will proceed as documented in the Windows NT installation guide. ---UPDATING EXISTING DRIVERS--- 1) Log in on an Adminitrative account, select the Windows NT Setup icon by double clicking. 2) Setup will determine then display your current configuration. Under options, select Add/Remove SCSI adapter. 3) Highlight the adapter you wish to replace, and select Remove. You will receive a couple messages about removing system drivers, and that the driver you are removing is set to load at boot. You may ignore these messages, by clicking the OK button. 4) Click on Add. You will be given a list of adapters, with the entry "Other" highlighted. Press enter. You will be prompted for a driver disk. Insert this diskette and press enter. You will be given a choice of AL-7000 and IN-2000 drivers. Highlight IN-2000 and press enter. When prompted to install a new driver, or use the existing driver, select New. The IN-2000 driver will be loaded. You will be asked if you wish to load additional drivers (S) or continue installing (Enter). Press Enter. 5) If the adapter you have just updated is your boot adapter, you may wish to update the boot driver as well. When Windows NT boots, it loads a boot time driver, which is later replaced in memory with the run time driver from the system directory. The setup procedure in step 4 was to update the run time driver. From a command prompt, change to the root directory of the boot device (usually C:\). Enter the command: attrib -s -h -r c:\ntbootdd.sys With the Always driver disk in drive A:, enter: copy a:\always.sys c:\ntbootdd.sys attrib +s +h +r c:\ntbootdd.sys 7) The new driver will be loaded the next time you restart the system. NOTES: This driver has been tested with retail version of Microsoft Windows NT 3.1 from the NT SDK and DDK CD-ROMs. All IN-2000s must have their interrupt channels (IRQs) enabled to operate under WindowsNT. ______________________________________________________________________________ ______________________________________________________________________________ Appendix A, Trouble Shooting _____________________________ ---PROBLEMS AND THEIR SOLUTIONS--- PROBLEM: The "Always Technology IN-2000..." BIOS message does not appear during boot-up. SOLUTION: There may be a BIOS address conflict with another adapter. Try changing the BIOS address of the IN-2000. The video BIOS might not be switching to it's 8 bit mode (refer to PC Magazine, September 25, 1990 "Facing the Truth About 16 bit VGA Display Adapters"). Manually jumper the video card to 8 bit BIOS mode and then "shadow" the video BIOS to regain maximum video performance. PROBLEM: The system hangs after "Always Technology IN-2000..." BIOS message. SOLUTION: I/O address, interrupt and BIOS address conflicts with other adapters can cause this. Try changing those settings on the IN-2000 to eliminate the conflict. SOLUTION: Two floppy disk controllers enabled at the same time will also cause this failure. Disable one of the floppy controllers. PROBLEM: The SCSI devices are not found during boot-up, or too many SCSI hard disk drives are found. SOLUTION: Make sure that the SCSI IDs of the hard drives are set correctly. All SCSI devices must have unique ID settings. The IN-2000 uses SCSI ID 7. [Some SCSI drives take a long time to spin-up. In cases like this, you can either warm boot the system after all the drives have spun-up, or set the system for a slower boot-up (enabling the full memory test at boot is a good method for this]. SOLUTION: A defective cable or an external device not powered on could also cause this problem. PROBLEM: The IN-2000 BIOS reports more non-SCSI drives than what is currently installed in the system. SOLUTION: The motherboards CMOS setup is set incorrectly. The CMOS should only show drive type information for non-SCSI drives. If you only have SCSI hard drives installed in the system, the "C" and "D" drives should be set to "Not Installed" in the CMOS setup. PROBLEM: After the IN-2000 BIOS reports how many hard drives are found, the message "Disk block size invalid..." is displayed. SOLUTION: This error message can also be caused by SCSI hard disks that have been formatted for non-IBM PC compatible systems and should be low level formatted. SOLUTION: Sometimes an I/O port address conflict will also cause this error message to appear. Try changing the I/O port address on the IN-2000. PROBLEM: The hard drive will occasionally power down for no apparent reason. SOLUTION: Disconnect the hard drive from the IN-2000 adapter and see if it continues to randomly power down. If it does, return the drive. PROBLEM: The floppy drives will not work properly on the IN-2000. SOLUTION: If switch 9 on DIP-switch SW1 is not in the "on" position, then the IN-2000's floppy controller is still disabled. SOLUTION: Old motherboard BIOS' can cause floppy problems. Update the motherboard BIOS to 1990 or newer. SOLUTION: If the floppy drive displays the directory of the previous floppy, after inserting a new floppy, replace the floppy cable. PROBLEM: The error message "NO ROM BASIC" appears in large characters during boot-up. SOLUTION: If the primary, bootable partition is not set to active, or the hard drive was previously used by a different SCSI adapter, without low level formatting it on the IN-2000, you might see this message if the previous adapter used a SCSI translation that the IN-2000 doesn't recognize. SOLUTION: Run DOS' "FDISK.EXE" and set the primary partition to active (refer to your DOS manual). PROBLEM: The error message "Missing Operating System" appears during boot-up. SOLUTION: If you have partitioned and formatted the SCSI drive under DOS, you must transfer the system files to the "C" partition for it to be bootable (refer to your DOS manual). PROBLEM: The system hangs during "CONFIG.SYS" or "AUTOEXEC.BAT". SOLUTION: Remove lines from "CONFIG.SYS" and "AUTOEXEC.BAT" until the system boots "OK". This should indicate where a conflict might exist. Also experiment with the order in which the drivers and T.S.Rs load. PROBLEM: The IN-2000 diagnostics from "DEBUG.EXE" no longer works properly. SOLUTION: If the IN-2000 ASPI manager ("ASPIDRVR.SYS") has been loaded you cannot run these diagnostics. PROBLEM: Windows locks-up when trying to run in "Enhanced" mode with the IN-2000 ASPI manager loaded. SOLUTION: Do not use interrupt 14 for the IN-2000. If you have another hard disk adapter in the system using interrupt 14, see if it is possible for it to use a different interrupt. If you must use interrupt 14 for the other adapter call Always for possible solutions. ---QUESTIONS AND ANSWERS--- Q. Why is it better to use external terminator modules on the outside of external SCSI devices rather than internal termination? A. External terminator modules properly terminate the end of the SCSI cable. Internal termination (on external devices) leaves the end of the SCSI cable non-terminated and can lead to system failures caused by signal reflection from the non-terminated end of the SCSI cable. Q. Why can't I read the IN-2000 UNIX driver diskette on a DOS system? A. The IN-2000 UNIX driver diskette is only readable on UNIX systems. Q. Why does my hard disk performance test software show low data transfer rates and/or incorrect seek times? A. Many performance test software packages are not made to run on SCSI hard drives. They do not take into account SCSI logical block geometry and will compute the transfer rate based on the wrong data. The incorrect seek times are caused by the BIOS translations and should be ignored. Q. What type of cable is used for attaching external devices to the IN-2000? A. The IN-2000 uses standard Macintosh DB-25 to 50-pin Centronics cables (refer to Appendix B). Q. Why is the hard drive advertised as having a total capacity of one size and after its formatted, the computer reports a much smaller capacity? A. When a drive is formatted, a certain amount of space as lost in every sector due to location information such as head, track and sector. The computer only reports the total user data area. The average loss of space from unformatted to formatted capacity is about 17%. This loss of disk space will occur on any SCSI host adapter. Q. Windows automatically installs Smartdrive double buffering in CONFIG.SYS. Do I need this? A. You do not need "double buffering" with the IN-2000. Remove the Smartdrive device driver from CONFIG.SYS. ---IF ALL ELSE FAILS--- If you cannot get your IN-2000 to function properly after reading all sections of this Installation Guide that apply to your installation, contact your dealer or distributor for assistance. In the event that they are not able to help you, contact Always Technical Support: Phone (818) 597-1400 Fax (818 597-1496 BBS (818) 597-0275 Be prepared to supply the following information: - The serial number of the IN-2000. - The EPROM and serial ROM revisions on the IN-2000. - The make, model and BIOS revision/date of your computer. - The make and model of all SCSI devices attached to the IN-2000. Thank you for reading this Installation Guide!