Home

DC-390 Series

1. 3 After selecting a device more detailed information is displayed For example selecting the Fujitsu drive brings up a window like so 4 DOS ASPI DRIVERS amp UTILITIES The system has the following SCSI devices Devt HA Peripheral Device Type Removal Media SCSI Revision gt SCSI 1 Vendor Identification FUJITSU Product Identification M2614S Product Revision Level 0607 Command Linking Supported Syncounous Transfer Supported Tagged Command Linking Not Supported Fixed disk ND The following screen provides information on the number of SCSI devices installed and asks if you want to install the drivers Note Only install the ASPI Hard Disk Driver if you have a removable device such as an M O drive or if More than 2 drives support is Disabled Current System Has 2 Disk Drives including Removal and Optical Device 1 CD ROM Devices Do You Want to install ASPI Manager Y N Y Driver Y N Do You Want to install CD ROM can have any name you choose The default path would be C DC390 for DC 390 or CADC390W for DC 390U 390F 390U2B 390U2W For this example we ll use This Installation Program will copy some Device Drivers and Utility to the following directory Press Enter to accept the default directory If you have one or more CD ROMs installed in your system and choose to install the ASPI CD ROM Driver the next screen will require you to specify the path
2. For OS 2 Warp 4 0 Only OS 2 Warp 4 0 may detect the DC 390 as a QL510 SCSI card and load the QL510 ADD driver The system can hang or Trap if this driver is loaded with the Tekram driver at the same time DC 390 Series User s Manual 6 OS 2 DRIVERS If there is a problem check the CONFIG SYS on the hard drive for the line BASEDEV QL510 ADD If this line exists change it as follows BASEDEV QL510 ADD to REM BASEDEV QL510 ADD You may also install the driver manually 1 Copy the file TMSCSIM ADD from the directory OS2DRV on the Tekram driver disk to the directory C OS2 2 Edit C CONFIG SYS At the beginning of the file add the following line BASEDEV TMSCSIM ADD Note1 If OS 2 is booting from an IDE drive the line BASEDEV TMSCSIM ADD must appear after the line that loads the IDE driver e g IBM1S506 ADD in the CONFIG SYS Note2 If your OS 2 is installed to IDE drive from SCSI CD ROM drive TMSCSIM ADD will be located at the first line in C CONFIG SYS after installation Before booting OS 2 from IDE drive modify the file C CONFIG SYS as described in Notel 6 3 Un installing the Driver 1 Edit the C CONFIG SYS file Modify the line BASEDEV TMSCSIM ADD to REM BASEDEV TMSCSIM ADD 2 Re boot the system 48 DC 390 Series User s Manual 6 OS 2 DRIVERS 6 4 Command Line Switches for TMSCSIM ADD BASEDEV TMSCSIM ADD
3. Removable Media as BIOS Device Boot only Default Immediate Return on SEEK Command Disabled Default Scan All LUN For Devices Disabled Default Active Negation cceeeee scene ees Enabled Default Power on RESET SCSI Bus Enabled Default Delay Before BIOS scans device 3 sec Default Max Number of Tagged Commands 32 Default SCAM Support eaeou nie eeri Enabled Default F2 or F6 Function During Bootup Enabled Default Pressing lt F8 gt will reset all the settings to their default values DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD Adapter SCSI ID 0 7 The default ID for the DC 390 series adapter is 7 It is recommended not to change this default value of 7 as it gives the adapter the highest priority on the SCSI bus However if you have two adapters on the same SCSI bus you should give one of them a currently unassigned ID Note For DC 390F 390U2B U2W sixteen SCSI IDs 0 15 are available Jf there is any 8 bit device connected on the SCSI bus avoid setting the adapter SCSI ID to the number 8 or larger otherwise you may run into difficulties Boot Device ID SCSI ID 0 default 7 DC 390 DC 390U or 15 DC 390F 390U2B 390U2W This option allows you to boot from any bootable devices connected To ensure proper operation see the following notes e If a bootable IDE drive is The IDE drive will boot
4. 3 CONFIGURING YOUR SCSI CARD 3 2 5 Since most SCSI drives are already pre formatted when shipped from their manufacturers you can skip this section except in the following situations A disk drive is damaged The disk drive has not been formatted with the 512B block parameter proceed Under normal circumstances it is both unnecessary and inadvisable to perform low level formatting Executing this utility will erase all information on the drive 3 2 6 Verify Disk Utility This utility is used to detect bad blocks on the chosen disk With your confirmation the bad destructive and therefore won t destroy the data on the drive DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES This chapter describes in detail the various ASPI Drivers and Utility programs that are provided with the DC 390 Host Adapter Kit for use under the DOS operating system To get up and running quickly under DOS see Section 4 1 Easy DOS Driver Installation Software for easy installation instructions The major ASPI Drivers and Utilities are e ASPLSYS The ASPI Advanced SCSI Programming Interface driver that provides the basic communication interface for the host adapter and the DOS operating system It supports up to four coexisting host adapters and is compatible with peripheral drivers for Sytos Plus ARCserve Solo tape subsystems fixed disks removable cartridges MO drives Flopticals CD ROMs CD Changers and Scanners
5. C General Troubleshooting Tips 5 A connected device is not recognized by the DC 390 e Ifthe device is a hard drive particularly an older one there may not be a sufficient delay time specified in the DC 390 PCU You can tell if this is the case by simply warm booting the computer after the drive has had plenty of time to spin up If the controller sees the drive then go into the DC 390 BIOS and increase the setting Delay Before BIOS Scans Device Make sure the option Included in BIOS Scan is set to Yes for that device ID If the device is not a hard drive or the above solution does not work first check to see if any device is recognized Try devices one at a time to make sure the cable or card is not bad If there is one device that will not be seen check the SCSI ID and terminators The SCSI ID should not be on 7 If a SCSI device is not seen by the card keep in mind that it is very unlikely a fault with the card itself The card should identify any properly connected SCSI device 6 Possible incompatibility problems when enabling the More Than 2 Drives Support option in the PCU e Due to the condition of occupying the 1KB 639KB 640KB of memory space some software such as anti virus programs may issue false alarms 7 System Hangs very soon after the PCU setup e For some specific drives such as the NEC 384 Seagate ST3283N amp Alps DR312D set the Max Sync Xfer Rate option to 5MB sec instead of 1OMB sec defa
6. DC 390 Series PCI SCSI Host Adapters User s Manual Manual Rev 6 00 Date April 99 Model Protocol Mode SCSI Max Xfer Max Number Width Rate MB S Devices U Ultra SCSI Narrow F Ultra SCSI Wide U2 Wide Ultra2 SCSI The designation DC 390 is used throughout this manual in reference to the common features of all the above models Any discrepancies or special features not supported by the entire DC 390 Series are described using specific model numbers All other product names are trademarks or copyrights of their respective owners DC 390 Series User s Manual FCC Compliance Statement This equipment has been tested and found to comply with limits for a Class B digital device pursuant to Part 15 of the FCC rules These limits are designed to provide reasonable protection against harmful interference in residential installations This equipment generates uses and can radiate radio frequency energy and if not installed and used in accordance with the instructions may cause harmful interface to radio communications However there is no guarantee that interference will not occur in a particular installation If this equipment does cause interference to radio or television equipment reception which can be determined by turning the equipment off and on the user is encouraged to try to correct the interference by one or more of the following measures Reorient or relocate the receiving antenna Move the equipment
7. Universal switch Adapter ID Unit switch Universal switch An option that applies to all adapters MO Do not change MO device type to DASD type when reporting to Device Manager TMSCSIM ADD default Change MO device type to DASD Adapter ID A x where x starts from 0 is the order number of the adapter that was found in the system Unit switch An option that applies to device s unit I Ignore the specified adapter DM Enable DASD manager support default IDM Disable DASD manager support SM Enable SCSI manager support default ISM Disable SCSI manager support Example BASEDEV TMSCSIM ADD MO A 0 DM 1 A 1 SM 2 3 This will prevent OS2DASD DMD from controlling device with SCSI ID 1 and prevent OS2SCSILDMD from accessing device with SCSI ID 2 3 and keep all MO device type from changing to DASD type DC 390 Series User s Manual 149 7 WINDOWS NT DRIVERS This chapter provides driver installation and un installation procedures for Windows NT v3 x 4 x There are two driver directories under the WINNT directory of the driver diskette one is for NT 3 1 3 5 and the other is for NT 3 51 4 x WINNT 3_51 4_x WINNT 3_1 3_5 Device driver for NT 3 51 Trm390 sys Device driver for NT amp 4 x 3 1 amp 3 5 Oemsetup inf Device information file Oemsetup inf Device information file trm390w sys for DC 390U F U2B U2W And two others are under the root dire
8. The option Greater Than 1GB Support in the Tekram BIOS should be enabled if any device has more than 1024 cylinders IF you are using a FAT file system DOS Windows 3 X Windows 95 Some Operating Systems such as OS 2 and Windows NT can use either FAT or HPFS NTFS respectively For these Operating Systems the Greater Than 1GB Support feature only needs to be enabled if FAT is to be used as the file system NTFS and HPFS do not impose a 1024 cylinder limit e Netware and UNIX are two Operating Systems that do not have a 1024 cylinder barrier and therefore do not require that Greater Than 1GB Support be enabled e If your HDD was formatted without Greater Than 1GB Support enabled originally you will have to backup the data and re FDISK the drive in order to use the maximum capacity under DOS or any Operating System using FAT e Enabling the Greater than 1G support option will reassign the parameters to 512Bytes per Sector 63Sectors and 255Heads for SCSI disk drives with a capacity larger than 1 GByte This allows the operation of hard drives with a capacity up to 8GByte with operating systems such as DOS Windows 95 etc e For drives smaller than 1GByte the 64Head 32Sector translation scheme will always be employed regardless of this option being enabled or not More Than 2 Drives Support Enabled Disabled When enabled this option provides support of up to eight devices controlled by BIOS INT 13H such as IDE ESDI ST506 SCSI fix
9. e TRMDISK SYS This driver is for controlling those SCSI devices not supported by BIOS INT 13H See More Than 2 Drives Support and Included in BIOS Scan These devices would primarily be fixed disks removable cartridges re writable optical disks MO and flopticals It allows the creation of valid partitions on these devices for use as logical drives and also recognizes data formats used by other adapter manufacturers e TRMCD SYS The device driver for CD ROM and CD Changer devices This driver is loaded after ASPLSYS in the CONFIG SYS file e TEDISK EXE A DOS compatible disk partitioning utility program for SCSI hard disks removable media and magneto optical drives that are not managed by the BIOS of the DC 390 Those managed by TRMDISK SYS e UTIL EXE Allows configuration of the PCU from DOS as opposed to re booting the system and pressing the lt F2 gt key DOS uses the ASPI manager as a software interface to communicate with SCSI devices The specific peripheral driver then talks to the ASPI interface instead of the host adapter hardware Under this architecture multiple devices can share the host adapter without conflict The ASPI driver is typically installed under the following situations e Multiple adapters coexist up to four e SCSI devices not controlled by BIOS INT 13H are installed CD ROMs e Devices that use removable media are installed e An interface to Tape Drives CD ROMs and other SCSI devices is needed
10. 3 Un installing the Driver rairai aeeoeia eair a i i oeae 6 4 Command Line Switches for TMSCSIM ADD 7 WINDOWS NT DRIVERS wicca jecccccecececededecedececede decade cedecedededeenctenceenteeis 50 7 1 New Windows NT Installation eecscceeesseceeeneeceeeneeeessaeeceeeeeeeesaeeeeeeneeeess 7 2 Adding the Driver to an Existing NT System Zlob FOV NT Versions 3 X GN 3I iresi ST N oE ias aS SEa T22 A FOENT VETOS 4X sce cca tE EOE EENS 52 7 3 Removing the SCSI Host Adapter from the System 7 3 1 For NT Versions 3 x and 3 5x A32 AKONT Versions Ahn nio a E a he Oe 53 8 WINDOWS 3 X DRIVERS isiyi aaa 54 S Driver Installationicccs225 65215 45 255 otek a ase AL E a 54 8 2 Driver Un installation 2 0 0 cece A A eaaa a E E iaaeao 54 9 WINDOWS 95 98 DRIVERS ccccsceesseeeeeeeeeeeeeeeeeeeeeseeeeeeeeesnneeeeeeees 55 9 1 Installing the Windows 95 Driver cet eeeeeeeeeeseeseneeeseeeeseeseseeesneeeseeeeaeeene 55 9 2 Installing the Windows 95 OSR2 Drivet eeceeeceeseceseeeeseeeeseeseeeseneenseeesee 56 9 3 Installing the Windows 98 Driver ceceeeeeeseeeeseeeeneeeseeeeseeseeeesaeeeseeseaeeenes 57 9 4 Adding the Driver to an Existing 95 98 System sseseseeseseseesissreerrssreesresrrrsres 59 9 4 1 For an Existing Windows 95 System ccccccscccsssessesesetenseseneeesaeeesaeeeaes 59 9 4 2 For an Existing Windows 95 OSR2 System sesser 59 9 4 3 For an Existing Windows 98 System sssssseseeeeseeereererr
11. Example You could operate 7 SCSI Hard Disks under MS DOS with no ASPI drivers loaded as long as More Than 2 Drives Support is Enabled If you were to add a CD ROM or tape drive however you would need to install the ASPI drivers DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES Easy DOS Driver Installation Software INSTALL EXE easy driver installation for your SCSI devices Under DOS the driver installation will be necessary if either More than two Hard Drives are installed and is disabled sec or b A SCSI device other than a Hard Drive is installed CD ROM etc This software program provides you with information about the adapter and your SCSI the CONFIG SYS and AUTOEXEC BAT files automatically Further information about drivers and step by step installation procedures can be found in Chapter 3 DOS ASPI The following screens illustrate the DOS driver install procedure 1 To begin this screen displays information about the adapter number HA 0 I O port address Base E400H interrupt level IRQ 11 and SCSI ID ID 7 In this case there select which adapter you want to work with The system has the following Host Adapter s DC 390 HA 0 Base E400H IRQ 11 ID7 This screen provides information regarding the SCSI devices controlled by the chosen The system has the following SCSI devices Dev SCSI ID Vendor ID Revision Level 0 0 FUJITSU 0607 1 1 MAXTOR 2 11 2 3 NEC 1 0
12. F Windows 98 will detect Tekram DC 390U F PCI SCSI Cards and prompt you with Need update driver from Tekram during installation AT this point you need to install the DC 390U F device driver as follows 1 Make sure Windows 98 is up and running properly Insert the Tekram Driver Disk into your floppy drive A 2 Run the patch file located at a win95_98 98patch exe Refer to the notes below 3 Open the Control Panel and double click the System Icon 4 Click the Device Manager Tab and select PCI SCSI Bus Controllers 5 Select Tekram DC 390U F PCI SCSI Adapter and click Properties 6 Click the Driver Tab and choose Update Driver The Update Device Driver Wizard will appear Click Next 7 Select Search for a better driver than the one your device is using now Recommended and click Next 8 Select Specify a location 9 Type inthe path A WIN95_98 10 Click Next 11 Select Tekram DC 390 U F PCI SCSI Adapter and click Finish to install the driver 12 Restart the system Notes Windows 98 PCI VXD will generate a Tekram key to replace the normal VEN_1000 amp DEV_O0OF amp SUBSYS_O00000000 amp DEV_03 in the directory of KEY_LOCAL_MACHINE Enum PCI This will result in a compatibility problem with HCT test Our 93PATCH EXE modifies the PCI VXD program and fix this problem 98Patch exe is only for DC 390U F under Windows 98 For windows 95 and windows 95 OSR2 yo
13. Module Optional HotPlug Support Module Optional Storage adapter IDEATA IDEATA For DC 390U F U2B U2W Device types Driver names Platform Support Module Optional HotPlug Support Module Optional Storage adapter IDEATA IDEATA S YM8XXNW DC 390 Series User s Manual 5 NETWARE DRIVERS Select Modify option and choose Storage adapter then press Enter key For DC 390 installation skip step 4 Delete SYMXXNW HAM Symbios Logic 53C8XX SYMXXNW HAM is the Symbios 53C8XX driver DC 390U F U2B U2W use Symbios 53C8XX Chip Insert the DC390 U F U2B U2W device drivers diskette into drive A or B Press Ins key Use the Ins key to select an unlisted driver If the driver diskette is in drive A press Enter key to continue If the driver diskette is in the B drive press the lt F3 gt key to specify the path B NETWARE and press lt Enter gt key to load this driver You will find DC390XR1 HAM or DC390R1 HAM in the Driver names list Follow the NetWare Installation to complete the procedure 5 1 2 NetWare 4 xx This subsection covers the installation of the driver module DC390XR1 HAM and DC390XR1 DDI for NetWare Versions 4 00 4 01 4 02 4 1x 4 2 4 2SB 1 Begin the file server installation according to the instructions in the file server installation chapter in the Novell NetWare installation manual After seeing a message bl
14. PCI SCSI Driver Ver XXX Tekram DC 390 NT 3 1 amp 3 5 PCI SCSI Driver Ver XXX Select the NT version you want to install and press ENTER After NT scans the hardware and finds the controller it will display Setup has recognized the following Mass Storage devices in your computer Tekram DC 390 PCI SCSI Adapter Ver XXX DC 390 Series User s Manual 7 WINDOWS NT DRIVERS Press ENTER to continue and copy the driver files At this point simply follow the Microsoft Windows NT installation procedure 7 2 Adding the Driver to an Existing NT System 7 2 1 For NT Versions 3 x and 3 5x 1 2 3 From the Main Program group double click the Windows NT Setup icon From the Option pull down menu select Add Remove SCSI Adapters Click the Add button and select Other Requires a disk form a hardware manufacturer NT will prompt you to insert the Manufacturer supplied support disk Insert the DC 390 driver diskette into drive A and type in the path A WINNT 3_1 3_5 For NT versions 3 1 and 3 5 A WINNT 3_51 4_x For NT versions 3 51 and 4 0 Windows NT will show Tekram DC 390 PCI SCSI Adapter Ver XXX Select OK Windows NT will display Adapter Tekram DC 390 PCI SCSI Adapter Ver XXX Select Install At this point if the specified driver has already been installed NT will display The drivers for this adapter are already on the system Select Current if you want to use existing driver or
15. Tekram Technology Co Ltd Supported SLOT Options are 3 2 Select SLOT Option 3 When prompted for a slot number accept the slot numbers displayed This slot number is SLOT and MAINBOARD dependent 7 Write down the slot number for use below and press lt Enter gt to proceed In case where two DC 390U F U2B U2W series adapters are present in the system the driver must be loaded once for each card Further along the console screen will display the message Edit File As Necessary STARTUP NCF Modify the file as follows Load DC390XR1 HAM or DC390R1 HAM SLOT 3 Note use the slot number above Load DC390XR1 HAM or DC390R1 HAM SLOT 2 The HAM driver s are loaded for each DC 390 U F U2B U2W controller SCSI channel from the first LOAD statement to the last LOAD statement 40 DC 390 Series User s Manual 5 NETWARE DRIVERS 5 1 3 NetWare 3 12 SFT III This subsection covers the installation of the driver module DC390XR1 HAM and DC390XR1 DDI for NetWare Versions 3 12 SFT III 1 WwW CO Oy I 10 11 Download those two files NWPA_UP EXE and 312PTD EXE from Novell website at http developer novell com devres sas certinfo htm at Download Upgrade Package for NetWare v3 12 Copy NWPA_UP EXE and 312PTD EXE to C SERVER_312 directory Copy DC390XR1 HAM or DC390R1 HAM or DC390XR1 DDI or DC390R1 DDI to C SSERVER_312 directory Execute NWPA_312 EXE in the same directory Execute 312PTD EXE in the same d
16. automatically scans the parameters from the master boot record of your drives it is possible to install drives previously used with other SCSI adapters without any inconsistency DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES Using the d option you have the ability to reserve up to 9 logical drives for each SCSI device However you must keep the total number of partitions logical drives reserved by the driver to within 16 This option is important for removable media devices If you do not reserve enough logical drives for your removable media some of the logical drives may go unrecognized To install add a line after ASPI driver in the CONFIG SYS DEVICE C ASPNASPLSYS DEVICE C ASPATRMDISK SYS d n1 n2 n3 n8 e nl logical drives are reserved for 1st physical drive n2 logical drives are reserved for 2nd physical drive n8 logical drives are reserved for 8th physical drive The value of nx x 1 8 ranges from 0 to 9 nx 0 DC 390 scans the number of logical drives automatically The order of drives starts from primary partition to secondary and SCSI ID 0 to 7 It is recommended that DOS 4 x or higher be used For DOS 3 x logical drive capacity is limited to 32M bytes e The logical drive scanning sequence of TRMDISK SYS starts with adapter 0 SCSI ID 0 primary partition then moves on to the extended partition Example The following is an example of the scanning sequence with two DC 390s insta
17. away from the receiver e Plug the equipment into an outlet on a circuit different from that to which the receiver is connected e Consult the dealer or an experienced radio television technician for additional suggestions Only equipment certified to comply with Class B should be attached to this equipment and must have shielded interface cables The FCC requires the user to be notified that any change or modifications to the equipment by the user not expressly approved by the grantee or manufacturer could void the user s authority to operate such equipment Each DC 390 is equipped with an FCC compliance label which shows only the FCC Identification number FCC ID KHADC 390 This device complies with Part 15 of the FCC rule Operation is subjected to the following two conditions 1 This device may not cause harmful interference and 2 This device must accept any interference received including interference that may cause undesired operation TekrAm DC 390 Series yy CA No Ki Co ry Tested to Comply with FCC Standards 4 z a C 2 ay For Home or Office Use DC 390 Series User s Manual Award BIOS with built in NCR SCSI BIOS amp DC 390 Controllers Possible Compatibility Problem Why and when the problem occurs The built in SCSI BIOS feature incorporated into some mainboards with Award BIOS is meant to control NCR Symbios Logic based SCSI adapters that have no BIOS of their own Since the DC 390 c
18. s 1 2 Other devices 1 IDE ESDI 2 3 4 Other SCSI device s 1 2 3 4 System Software Configuration please list the version Operating System Application Program 5 Detailed description of error messages and symptoms with information on CONFIG SYS AUTOEXEC BAT and PCU options DC 390 Series User s Manual C General Troubleshooting Tips Most controller errors are traceable to external factors such as conflicts with other installed cards bad or incorrectly configured drives loose cables improper SCSI termination or other installation errors To troubleshoot SCSI problems try simplifying your hardware configuration by removing some devices from the system and then adding them back one at a time For slow external SCSI devices you may also try to set the Sync Negotiation to No i e Async or decrease the transfer rate to a lower speed within DC 390 s PCU Look for the latest information on Tekram SCSI Controllers as well as the newest drivers on the Tekram web site at http www tekram com or ftp ftp tekram com The following are general guidelines for some specific error conditions 1 The error WARNING 64Heads 32 Sectors Parameter is expected pops up after the DC 390 BIOS e The most likely cause of this error message is using the DC 390 with a drive that has been formatted with a different controller Try toggling the setting Gr
19. the normal procedures to install SCO UNIX During the installation process the driver diskette may need to be inserted again as instructed Once the system reboots with the driver successfully installed messages similar to the following will be displayed DC 390 Series User s Manual 10 SCO UNIX DRIVERS device address vector dma comment DC390 Tekram PCI SCSI adapter driver V2 0 adapter 0x9000 0x9100 11 ha 0 id 7 at bus 0 dev 5 func 0 device id 0 lun 0 disk 206MB IBM _ device id 2 lun 0 tape W ANGTEK 10 3 Adding the Driver to an Existing SCO UNIX System with non SCSI boot drive Boot SCO UNIX into administration single user mode 2 It is required to make a backup copy of the working UNIX kernel in case a hazardous condition should arise Use the following command to make the copy diskette first cp unix unix ok 3 Insert the BTLD driver diskette created in 10 1 into the floppy drive and start the installation by typing installpkg 4 The screen will then show the driver package description NAME DESCRIPTION tps Tekram DC390 PCI SCSI Host Adapter V2 0 If you re not using DC 390 under SCO Unix3 2v4 x check the above table for corresponding command 5 Type the following command to install the driver tps A series of messages will be displayed The procedure is completed 7 If any SCSI device is to be added it is NOT necessary to have the hardwa
20. to you choose the default path of C DCSCSI you need to copy MSCDEX EXE from CDOS or the directory where it resides to C DCSCI after the driver installation is DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES Please Key in the PathName where MSCDEX EXE Resides ENTER Accept the Pathname ESC Abort Install MSCDEX EXE You would then assign the first drive letter to be reserved for the CD ROM drive s In Please keyin the first drive letter reserved for CD ROM drive s used by MSCDEX Drive F D2 Specify the drive letter ENTER Accept the drive letter and Install MSCDEX ESC Abort install MSCDEX 8 After confirmation the installation program will modify both the CONFIG SYS and AUTOEXEC BAT files This installation program will modify system CONFIG SYS by adding the following lines DEVICE C DCSCSIASPLSYS DEVICE C DCSCSITRMDISK SYS DEVICE C DCSCSI TRMCD EXE D CDROMO Installation also modifies AUTOEXEC BAT by adding the following lines C DCSCSI MSCDEX D CDROMO L F M 12 Press ENTER to make change to CONFIG SYS and AUTOEXEC BAT and Exit Installation Program Press ESC to Abort Change and Exit Installation Program 9 After this re boot the system The installed drivers will then be loaded DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES 4 2 Installing the ASPI Driver With the ASPI driver ASPLSYS ins
21. 2 v2 x and Warp 3 0 4 0 There are three driver files under the OS2DRV directory on the software diskette e TMSCSIM ADD is the DC 390 s OS 2 Adapter Device Driver that is fully compatible with OS 2 v2 x and Warp 3 0 e TMSCSIM DDP contains installation instructions used by TMSCSIM EXE e TMSCSIM EXE is the program that searches for the DC 390 and determines its configuration 6 1 New OS 2 Installation The following procedures are for a new OS 2 installation or upgrading to a newer version of OS 2 To add a DC 390 to an existing OS 2 system see next section 1 Make a copy of the OS 2 Setup Disk 1 Label this disk DISK 1A The original DISK 1 will not be used again in these procedures 2 Copy the file TMSCSIM ADD from the directory OS2DRV on the Tekram driver disk to the root directory of DISK 1A made in step 1 3 Edit the CONFIG SYS of DISK 1A At the end of the file add the following line BASEDEV TMSCSIM ADD Kor OS 2 Warp 4 0 Only Edit the CONFIG SYS of DISK 1A and change the line BASEDEV 0L510 ADD to REM BASEDEV QL510 ADD e OS 2 Warp 4 0 may detect the DC 390 as a QL510 SCSI card and load the QL510 ADD driver The system can hang if this driver is loaded with the Tekram driver at the same time The above step disables the QL510 driver 46 DC 390 Series User s Manual 6 OS 2 DRIVERS Then add one more line at the end of the CONFIG SYS SET
22. 6 bit devices are connected to the Wide SCSI connector either Internal or External arrange the devices so that a Wide device with termination enabled is at the end of the bus A Narrow device at the end of the bus can have termination problems in this case since the Wide bus is 16 bit and the terminator on the Narrow device is only effective for the lower 8 bit not the whole 16 bit Note2 DC 390U2B W only Since the termination of internal Ultra2 devices are set to disabled at the factory and cannot be changed special Ultra2 internal SCSI ribbon cables with a terminator installed at the end are specified for the operation with Ultra2 SCSI devices Note3 There are two types of termination available on SCSI devices active and passive Active termination is strongly recommended to ensure system integrity particularly when devices with high transfer rates are being used A SCSI CD ROM drive usually comes with a passive terminator For proper termination it is recommended that you keep this terminator disabled i e avoid connect the CD ROM drive at the end of the SCSI bus DC 390 Series User s Manual 2 HARDWARE SETUP 2 5 Cable Connection Internal DC 390 CN1 50 pin 8 bit Female DC 390U CN1 50 pin 8 bit Female CN2 50 pin 8 bit Male CN2 50 pin 8 bit Male CN2 68 pin 16 bit wide Female CN3 50 pin 8 bit Male DC 390F CN1 68 pin 16 bit wide Female DC 390U2B J1 68 pin 16 bit wide
23. 94 Procedures for correcting this problem 1 Set Parity Checking for all IDs to No in Set Devices Options setup menu recommended Or 2 Set Allow Disconnection for the ID corresponding to RO 1420C to No in the Set Devices Options setup menu This method may affect the overall SCSI bus performance The following controllers do not exhibit this problem when combined with the RO 1420C since their associated SCSI cores IGNORE any SCSI parity error during the SCSI reselection phase e AHA 2940 Adaptec PCI SCSI controller e DC 390U F PCI Ultra Wide SCSI controller by TEKRAM based on 53C875 12 Linux FreeBSD Unix based drivers They are available under Driver amp AP section of each model under Storage section on FTP site ftp ftp tekram com tw 13 Overclocking policy The difference between SCSI chip and CPU is that CPU will pack 100MHz if it can run 100MHz and 66MHz if can run 66MHz during production It is a natural phenomena that some chips can run higher speed and others can t do so in production process There is a yield rate problem for the same batch of chips The trivial in manufacturing process will make a difference in working frequency for different chips Even a different location on the same wafer in the middle or on the side of chips will cause a different yield rate and working frequency The production and packing process of SCSI chips doesn t have operating frequency testing p
24. 9X gt Enter RaWrite 1 2 Write disk file to raw floppy diskette Enter source file name OS5_39X_ gt Enter Enter destination drive A gt Enter Please insert a formatted diskette into drive A and press ENTER Number of sectors per track for this disk is 18 Writing image to drive A Press C to abort Track 79 Head 1 Sector 16 Done DC 390 Series User s Manual 10 SCO UNIX DRIVERS The SCO Unix OpenServer driver diskette is now made Proceed to the following instruction for installation procedures 10 2 New SCO UNIX Installation with DC 390 as the primary SCSI adapter 1 Insert the system diskette N1 and boot up 2 When the boot prompt is shown Boot Type the following command to proceed link 3 When you are prompted What package do you need linked in the system or a to quit Type the following package name to proceed ams If you install DC 390 U F U2B U2W with Openserver 5 0 skip step 4 4 When you are prompted Table io_init contains at27 another routine named amsinit please enter which routine 0 40 to replace To list a to add amsinit at the end default n to do nothing Or q to quit Type the following option to proceed 27 io_init value 5 The system will keep booting from floppy N1 then request to have the driver diskette inserted Insert the SCO driver diskette created in 10 1 After the driver is successfully loaded follow
25. COPYFROMFLOPPY 1 Remove DISK 1A and insert the OS 2 Installation diskette Boot from this disk to begin the OS 2 installation A blue screen will prompt for the OS 2 DISK 1 Insert DISK 1A instead and proceed with the installation The driver for the DC 390 will be loaded automatically Kor OS 2 Warp 4 0 Only When Remove the diskette and press Enter to restart the workstation and continue the installation appears press F3 to activate the command prompt use TEDIT to open CONFIG SYS and modify the line BASEDEV 0L510 ADD to REM BASEDEV QL510 ADD Then exit the command prompt and continue as instructed When the system configuration screen comes up click the SCSI icon at left side of SCSI Adapter Support In the Select SCSI adapter list deselect the QLogic QLA510 adapter and leave as None unless you have another SCSI adapter installed in your system 6 2 Adding the Driver to an Existing OS 2 System 1 Double click the Device Driver Install Icon This icon is located in the System Setup folder under OS 2 2 X 3 X Under OS 2 4 X this icon resides in the System Setup gt Install Remove folder Insert the DC 390 Driver diskette in the floppy drive Change the SOURCE directory to A OS2DRV and click SET Change the DESTINATION directory to OS2 BOOT or OS2 for OS 2 version 2 x only and click SET Select Install and then Exit to complete the driver installation
26. DC 390U Included In BIOS Scan Yes default No When set to Yes the DC 390 s BIOS will scan and display the device s information during system bootup HDD scanned by the BIOS will be controlled by BIOS INT 13H See More Than 2 Drives Support When set to No the DC 390 will not scan the device and device drivers will be needed to control it You may set this option to No for SCSI ID s without device s connected to speed up the device scanning during boot But beware that any connected device will not be scanned and recognized by the BIOS when this option is set to No So if any connected devices are not presented in DC 390 s BIOS display message during bootup check this option first DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD 3 2 4 Show SCSI Devices This sub menu provides general information for all devices on the SCSI bus Select A Device For Display Device Information SCSI Device Information Vender ID EAEE EEE T T ST32171N Product Revision level ds iabea EE EAEE E E EER a hea Fixed disk SCSI Version EEEN Supported Linked Command aae aaan Supported SCAM Protocol PO EEEE ES 8 Bits Disk Capacity RE E ADA PT 512 You can then move on to other drives to view their information R E ANNEN FUJITSU Product ID E AET 1000 Device Type AEEA SAAT DTRNEA iR SCSL II TEE T ATAA Not Supported ET EE A T Not Supported E A EEE 604 MB Bytes Per Sector DC 390 Series User s Manual
27. DC 390U2W e For DC 390F up to fifteen 16 bit and or 8 bit SCSI single ended SE devices can be connected Up to seven of these can be 8 bit And only two of the three SCSI connectors either Internal or External can be used to connect SCSI devices at any given time e For DC 390U2B mixing Fast Ultra devices with Ultra2 devices brings the entire SCSI bus to Ultra SCSI speed and cable requirements e For DC 390U2W it is recommended that you keep your Ultra2 devices separate from your non Ultra2 devices Mixing Ultra2 devices with non Ultra2 devices will bring the Ultra2 devices to Ultra SCSI performance level Correct termination and cable connections are also necessary for SCSI adapters to function properly Section 2 4 and 2 5 e DC 390 Series User s Manual 2 HARDWARE SETUP 2 1 Board Layout The following figures illustrate the jumper and connector locations for the DC 390 Series PCI SCSI Host Adapters Fast SCSI 2 adapter 50 pin 8 bit internal SCSI connector 50 pin 8 bit external SCSI connector CLOSESROM ENABLE OPEN ROM DISABLE DC 390U Ulira SCSI 3 adapter 50 pin 8 bit internal SCSI connector 50 pin 8 bit external SCSI connector DC 390 Series User s Manual 2 HARDWARE SETUP DC 390F Ulira Wide SCSI 3 adapter 68 pin 16 bit Ultra WIDE internal SCSI connector 50 pin 8 bit internal SCSI connector SCSI connector DC 390F Ultra SCSI 68 pin 16 bit Ultra WIDE external up to
28. M BIOS is mapped at TEKRAM DC 310 PCI SCSI Controller BIOS v3 04 Date 1999 2 11 Installed at IOPORT E400h IRQ 9 Level triggered BIOS ROM mapped at C800h lt lt Press F2 or F6 to enter configuration Menu gt gt TEKRAM DC 390U PCI SCSI Controller BIOS v3 04 Date 1999 2 11 Installed at IOPORT E800h IRQ 10 Level triggered BIOS ROM mapped at C800h lt lt Press F2 or F6 to enter configuration Menu gt gt Upon pressing the lt F2 gt or lt F6 gt key the following screen will pop up Select An Adapter To Setup DC 310 gt gt gt gt BUSOO Dev0OA Fun0 IO E400h IRQ 09 DC 390 gt gt gt gt BUSOO DevOB Fun0 IO E800h IRQ 05 Note It is normal when it appears No BIOS Disk Found SCSI BIOS Not Installed or NO SCSI boot device found gt BIOS not installed during system boot It represents that there was no bootable SCSI device such as SCSI HDD found after SCSI BIOS detected peripheral devices Thus above messages are shown and they will not affect system operation DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD 3 2 Running the PCU PCI Configuration Utility Since the DC 390 series is PCI compliant with Plug amp Play PnP readiness the system should allocate the proper Interrupt Level Adapter BIOS Address and other settings automatically Still entering the PCU allows you to view more information and set additional options for both the DC 390 series adap
29. MAINBOARD dependent 12 Write down the slot number for use below and press lt Enter gt to proceed In case where two DC 390U W F U2B U2W series adapters are present in the system the driver must be loaded once for each card Further along the console screen will display the message Edit File As Necessary STARTUP NCF Modify the file as follows Load DC390XR1 HAM port E800 int A Modify to Load C SERVER 312 312PTD NATIVE START NPAPATCH Load C SERCER 312 MMATTRFX Load C SERVER 312 NBI31X Load DC390XR1 HAM SLOT 3 Note use the slot number above Load DC390XR1 HAM SLOT 2 DC 390 Series User s Manual 5 NETWARE DRIVERS 5 2 Driver Options The following options are supported by EEPROM Setting Set these n options by using DOS UTIL EXE or during POST by pressing F2 F6 to enter set up utility n Supported options are n n Parity check n Synchronous negotiation n Synchronous transfer rate n Disconnection n Wide negotiation n Tagged command queuing n Depth of tagged command queuing n Using Queue Tag Option Command Line option qtagtype lt option gt Default value ORDERED Valid options ORDERED SIMPLE Function Select the type of queue tag to be used when tagged command queuing is enabled SIMPLE tags are generally more efficient but some devices experience problems under heavy IO As a result ORDERED queue tag is chosen as the default Using Elevator Threshold Optio
30. Negotiation in DC 390F U2W s BIOS to NO for these two non Wide devices to work properly And it would require setting the Allow Disconnection option for Sony 926S to No 17 DC 390 series VIA M B Win98 Have to update the latest VIA driver from M B supplier or VIA and the OnChip USB option in the mainboard BIOS must be set to Enabled to ensure DC 390x s proper driver installation 18 TIMEOUT Reset SCSI Bus SCSI Bus Reset Detected under NetWare Try to set Tagged Command Queuing which is in Set Devices Options of SCSI BIOS menu for the Hard drive s to No and see if there is any difference 19 Warning 64 heads 32 sectors is expected for Linux FreeBSD or other Unix O S Most of the manuals would suggest you to install a small MS DOS partition at the beginning of the disk and install the O S after that This would ensure the machine gets the correct geometry So try to create a small DOS partition first in order to infer the correct HD geometry and then create the desired partition And if you don t need that DOS partition you can still select the ENTIRE disk for your O S in PARTITIONING process during the Operating System installation 20 Cannot see SCSI device after installing Win98 driver Make sure DC 390x s driver is properly installed and try to add lastdrive z in CONFIG SYS to see if there is any difference 21 Assign IRQ for the DC 390 series Lik
31. Ultra2 J1 68 pin 16 bit DC 390U2W Female wide Ultra2 Female Only two of the three connectors can be used to connect SCSI devices at the same time J2 68 pin 16 bit wide Ultra2 Female External SCSI connector This high density D type SCSI connector is for connecting external SCSI devices wide Ultra2 Female CN1 50 pin 8 bit Male CN2 68 pin 16 bit wide Female Internal SCSI connector The internal flat cable should connect to the internal SCSI connector with its colored stripe normally red aligned with Pin 1 of the connector Maximum length of the SCSI bus is determined by the number of devices and the data transfer rate The following table summarizes the maximum allowable cable lengths for the DC 390 series Model SCSI Type Data Xfer Max of Max Cable Length Rate Devices 8 DC 390 SCSI 2 10 MB Sec 3 meters 9 8 feet DC 390U F Ultra SCSI 20 40 MB Sec 3meters 9 8 feet DC 390U F Ultra SCSI 20 40 MB Sec 8_ _ _1 5 meters 4 9 feet Wide Ultra2 80 MB Sec 390U2B U2W SCSI e If there are internal devices connected the internal cable length must be included in the measurement of SCSI bus length For DC 390U2B mixing Fast Ultra devices with Ultra2 devices brings the entire SCSI bus to Ultra SCSI speed and cable requirements 16 12 5 meters 41 feet e For DC 390U2W it is recommended that you keep your Ultra2 devices on connectors J1 and J2 non Ultra2 devic
32. Ultra2 performance The DC 390 series supports ASPI Advanced SCSI Programming Interface managers for the following operating systems to assure operation with popular third party applications e MS DOS e Windows 3 x 95 98 NT OS 2 2 0 WARP 3 0 4 0 NetWare 3 x 4 x Device drivers are also supported for the following major operating systems for compatibility with a full range of SCSI peripherals including CD ROMs Photo CDs tape backups scanners removable media and SCSI hard drives e MS DOS e Windows 3 x amp WFWG 3 x e Windows NT 3 x 4 0 e Windows 95 98 e OS 2 2 0 WARP 3 0 4 0 o NetWare 3 x 4 x e SCO Unix 3 2v4 x amp OpenServer 5 0 e UnixWare 1 1 SVR4 2 version1 UnixWare Slackware RedHat Linux and FreeBSD drivers can be accessed via www tekram com or ftp tekram com scsi Most SCSI Adapters require device drivers to support more than 2 hard drives under DOS The DC 390 series however provides special support to handle up to eight devices including fixed disks and removable media under MS DOS 5 0 6 x without the need for device drivers More than 2 drives support The on board menu driven setup and jumperless design of the DC 390 series allow you to configure the host adapter SCSI devices and BIOS related parameters without opening your computer The DC 390 series also provides a utility program that supports low level formatting And with the help of the DOS driver installation software INSTALL EXE the drivers ar
33. as C or D However if your mainboard BIOS has multiple boot options such as boot from SCSI device this will allow the system to boot from any bootable SCSI device connected to the DC 390 series controller Since the mainboard BIOS will automatically shadow the PCI adapter s BIOS there is no need to set the shadow option between C800 and DFFF This option is for ISA adapter ROM only The I O Base Address and IRQ ROM shadow addresses are also assigned by the mainboard BIOS automatically You do not need to worry about it Just Plug amp Play and enjoy it Right after exiting the system BIOS CMOS setup the following message will pop up and prompt you to enter the PCI Configuration Utility to configure the card TEKRAM DC 390 PCI SCSI Controller BIOS v3 00 Date 1998 4 20 Installed at IOPORT 6800h IRQ 10 Level triggered BIOS ROM mapped at C800h lt lt Press F2 or F6 to enter configuration Menu gt gt ID LUN 6 0 MICROP 2217 15MZ1001905HQ30 Fixed disk 1678MB gt C 80h C H S 21 4 253 63 Xfer Rate 10 0MB Sec Sync Offset 15Bytes ID LUN 3 0 SONY CD R CDU924S 1 1d CD ROM Xfer Rate 4 0MB Sec Sync Offset 15Bytes SCSI BIOS installed DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD After powering up the system the DC 390U F U2B U2W BIOS will show a message with two screen indicating its BIOS version with a date code and information about the IOPORT address IRQ number and address that the RO
34. by default before any SCSI installed in the system devices This is a function of the mainboard s BIOS To boot from a SCSI device in this case a setting in the mainboard BIOS such as Boot From SCSI must be available Booting from a removable The above applies Also the setting Removable media as SCSI device BIOS device see page 22 should be set to Boot drive only e Booting from a SCSI CD The setting Boot From CD ROM see below must be ROM Enabled for CD Changer Boot Device LUN may need additional configuration This setting takes precedence over the boot device setting in the mainboard s BIOS Since removable media with 2048 Byte sector is not supported by the system BIOS this type of media won t be accepted as a Bootable device by the system Boot Device LUN LUN 0 default 7 If the SCSI device you wish to boot from has a LUN number other than 0 this option must be set for the specific LUN number in addition to setting the Boot Device ID for the SCSI ID number Boot From CD ROM Disabled Enabled When enabled the option will be given to boot from CD ROMs detected by the controller as bootable This setting takes precedence over any settings in the mainboard BIOS such as boot from IDE The Boot Device ID and Boot Device LUN if LUN is not 0 settings can be adjusted to ensure proper operation If these options are left on the default the bootable CD ROM with the lowest SCSI ID LUN nu
35. city 0 SEAGATE ST31230W Fixed disk 1010M 1 FUJITSU M2513A Optical disk 604 M 2 SONY CD R CDU924S CD ROM 121M 3 NEC CD ROM DRIVE 462 CD ROM 4 IOMEGA ZIP 100 Removable disk 95 M 5 6 WANGTEK 5525ES SCSI M74H Tape drive 7 For DC 390F 390U2B 390U2W Press lt Tab gt to see the next screen for SCSI ID 8 15 if available For DC 390U Wide Negotiation is always set to No and cannot be changed Parity Checking Yes No This option defaults to enabled i e Yes If set to No the DC 390 won t perform parity checking For devices that do not implement the parity function you should disable this option Allow Disconnection Yes No Yes is the default option and allows a SCSI device to go off line thereby freeing the SCSI bus when performing multi tasking operations In this way the DC 390 can simultaneously process multiple operations on the SCSI bus and thus improve efficiency in a multiple device environment Send START UNIT Command Yes No default Some specific drives require additional spin up commands to start their motors during system initialization These devices would require that this setting be set to Yes However most drives will spin up their motors automatically during power up and would not require the START UNIT Command Some drives have a jumper to enable disable this option Note Enabling this feature would reduce the load on your computer s power supply by allowing the DC 390 to turn on SCSI de
36. ctory e TXTSETUP OEM Text Setup File e DCSCI Text Setup Tag File 7 1 New Windows NT Installation You can boot Microsoft Windows NT from Setup Diskette NT 3 1 3 5 3 51 4 X or CD ROMU NT 3 51 4 X The following is the procedure for installing the Tekram adapter driver while installing Windows NT Boot from Diskette DC 390 U F U2B U2W 1 Insert the Microsoft Windows NT Setup Diskette for CD ROM installation into drive A and boot from this disk Note If you do not have the Windows NT Setup diskettes you can create them from the Windows NT CD ROM a First prepare three blank formatted 3 5 floppy diskettes Boot your system in DOS b Change to the CD ROM drive c Then change to the i386 directory d Type WINNT OX This will generate three setup diskettes for Windows NT 2 The first screen of the NT setup program will show Welcome to Setup Press ENTER to continue 3 The next screen will show Windows NT provides two Setup methods Press C to run the custom setup DC 390 Series User s Manual 7 WINDOWS NT DRIVERS Press S to skip mass storage device detection The next screen will show Setup has recognized the following SCSI Adapters in your computer none Choose to configure an additional SCSI adapter by pressing S and continue with the following steps On the next screen NT will show various drivers Choose Other Required disk provided by a hardware manufacture
37. d automatically every time the cartridge is changed 4 4 Disk Partition Utility TFDISK EXE is a disk partitioning program for modifying or creating partition tables under DOS Valid DOS partitions can be created by DOS FDISK only for drives controlled by BIOS INT 13H Drives controlled by TRMDISK SYS must use TFDISK EXE After you partition a disk device with TFDISK you must also run the DOS FORMAT command on the device before you can use it To run this program you have to install the ASPI drivers first then add a line after ASPI driver i e add two lines to the CONFIG SYS file DEVICE C ASPNASPLSYS DEVICE C ASPATRMDISK SYS To partition a disk simply type TFDISK EXE at the DOS prompt NOT the MS DOS Prompt under Windows Two translation methods are available depending on the disk space lt 1GB or gt 1GB Heads 64 Sectors 32 Cylinders XXX Depends on drive s capacity e lt 1GB Translation Method e gt 1GB Translation Two methods available Method e Using default disk parameters This method reads and uses the parameters from the master boot record of drives used previously with other adapters If no previous settings are available the 64Head 32 Sector parameter scheme is used Heads 64 Sectors 32 DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES Cylinders XXX Depends on drive s capacity e Using 255 heads 63 sectors parameters Heads 255 Sectors 63 Cylin
38. ders XXX Depends on drive s capacity After partitioning the disk you must also choose Create Logical Drive to assign a DOS drive letter to the partition Then exit and re boot the system 4 5 Installing the CD ROM Driver TRMCD SYS is the driver for CD ROM and CD Changer devices To enable a CD ROM under DOS you will also need MSCDEX EXE which is supplied with MS DOS 6 0 or higher This program can be acquired from Microsoft separately 1 Add a line after the ASPI driver DEVICE C ASPI ASPLSYS DEVICE C ASPATRMCD SYS d cdrom0 Note 1 For Trantor s Music Box you have to add one more option as follows DEVICE C ASPINTRMCD SYS d cdrom0 mb Note 2 If your CD ROM is compatible with another manufacturer and not recognized you have to add one more option t XXX XXX Short for compatible manufacturer name For example If your DEC CD ROM CDU 541 is compatible with the SONY CDU 541 and not recognized by the previous command you can try to add the following option DEVICE C ASPIATRMCD SYS d cdrom0 t SON 2 Add a line in the AUTOEXEC BAT file C A DOS MSCDEX EXE d cdrom0 m 12 Note In the above example CADOS is the directory containing the file MSCDEX EXE DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES 4 6 Installing Tape Streamer DAT After installing the ASPLSYS driver the DC 390 can support the following tape backup subsystems under DOS e SYTOS PLUS Tape backup progra
39. e Active Negation on REQ ACK and data outputs e Target Command Set Support e Single Ended 48mA outputs to drive the SCSI bus directly e Supports Low Voltage Differential LVD signaling DC 390U2B U2W only Overall Features e Supports Flash BIOS except DC 390 e Level Triggering support allows multiple adapters to share a single interrupt e Coexists with other SCSI ESDI or IDE adapters e Supports up to eight drives in DOS 5 0 6 x without the need for device drivers e Complete software driver support for all major PC operating systems e User friendly utility for quick and easy adapter installation and system configuration e Fully static design for low frequency and low power operation e State of the art submicron CMOS process technology 64 DC 390 Series User s Manual B Product Support Form The following information may be required by your supplier in order to obtain technical support assistance 1 Have you tried the General Troubleshooting Tips in Appendix C without success Yes No DC 390 Information Serial Purchase Date Firmware Version BIOS Version Driver Installed System Hardware Configuration please list the manufacturer model chip and SCSI ID of each device Motherboard Speed MB DRAM SRAM Video card Hard disk Floppy card 1 2 Network card Hard disk drive s SCSI 1 Z i 4 Floppy drive
40. e all other PCI PnP cards the IRQs for the DC 390 series SCSI adapters are auto assigned by mainboard BIOS So to re shuffle your PCI cards would actually invoke the mainboard BIOS to re assign the IRQ for each PCI card And if to manually change the IRQ is necessary may try the following two methods DC 390 Series User s Manual 169 C General Troubleshooting Tips 1 If mainboard BIOS is O K to let you manually assign the IRQ take Award BIOS for example and now want to manually assign the DC 390x which is seated in PCI slot 2 to IRQ10 The mainboard BIOS may have Slot n Use IRQ NO option n 1 4 or 5 in the PNP PCI Configuration entry a Press lt Del gt key during system s power up to enter BIOS setup menu b Select PNP PCI Configuration entry c Set Slot 2 Use IRQ NO IRQ10 2 If the mainboard BIOS only supports Resources Controlled By option in the PNP PCI Configuration entry a Press lt Del gt key during system s power up to enter BIOS setup menu b Select PNP PCI Configuration entry c Set Resources Controlled By to Manual d Assign all IRQs to legacy ISA except IRQ 10 to PCI ISA PnP DC 390 Series User s Manual D Flash BIOS Programming Utility Flash BIOS is featured on DC 390 series with the exception of DC 390 The word FLASH on the adapter s BIOS chip indicates flash support Updating the DC 390U F U2B U2W BIOS Code is made
41. e easily installed and the CONFIG SYS and AUTOEXEC BAT files are automatically updated The fully intelligent solution provided by the DC 390 PCI to SCSI Host Kit is ideal for multitasking environments such as OS 2 NetWare Unix Microsoft Windows 95 and Windows NT as well as next generation operating systems such as Microsoft Windows 98 DC 390 Series User s Manual 2 HARDWARE SETUP Static Precautions Static electricity can be a serious danger to the electronic components on this board To avoid damage caused by electrostatic discharge observe the following precautions vV Don t remove the board from its anti static packaging until you are ready to install it into a computer case Also handle add in cards and modules by the edges or mounting bracket v Before you handle the board in any way touch a grounded anti static surface such as an unpainted portion of the system chassis for a few seconds to discharge any built up static electricity Before plugging the DC 390 series adapter into your system make sure all jumpers on the card are correctly set according to the instructions outlined in section 2 2 Also take care that the SCSI ID number 0 6 for DC 390 390U 0 15 for DC 390F 390U2B 390U2W of each SCSI device is set properly for the host adapter Section 2 3 The maximum devices that can be installed on each model are show below Model Max Devices Number DC 390 DC 390U DC 390F DC 390U2B
42. e the driver DC 390 Series User s Manual 8 WINDOWS 3 X DRIVERS This chapter provides installation and un install procedures for the DC 390 Windows 3 x driver Note This driver is for use with all versions of Windows 3 0 or higher as well as Windows for WorkGroups 3 11 or higher The primary purpose of this driver is to enable the option of 32 Bit Disk Access under the above mentioned environments Both Windows AND the Tekram ASPI Drivers must be installed FIRST before beginning this procedure Run DOSINST to install the Tekram ASPI Drivers 8 1 Driver Installation 1 Make sure that Windows 3 x is up and running properly Insert the driver disk into your floppy drive Enter Main Group go to File Manager then run A WINDRV INSTALL EXE if the driver disk is in a Reboot to load the driver 8 2 Driver Un installation 1 The original SYSTEML INI file which is under the Windows directory will be renamed to SYSTEM 001 during the Driver Installation To un install the driver rename the SYSTEMLINI file to another name such as SYSTEM TEK then rename SYSTEM 001 back to SYSTEM INI Restart Windows for the changes to take effect DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS This chapter provides installation procedures for the DC 390 series Windows 95 98 drivers Windows 95 98 must first be installed before beginning this procedure There are two driver files under the WIN95_98 di
43. easy with the TRMFLASH EXE Utility which can be found in the lt BIOS gt directory of the driver disk Since the DC 390U F board versions 1 1 2 2 and later and DC 390U2B U2W feature FLASH BIOS it is not necessary to change the actual BIOS chip in order to upgrade the SCSI BIOS The user can simply re program the old BIOS using the TRMFLASH EXE Utility as follows 1 First boot the system with DOS or to Safe Mode under Windows 95 If you are booting DOS from a hard drive or floppy disk press F5 when the message Starting MS DOS appears on the screen If you are booting Windows 95 press the F8 key and select the Safe mode command prompt option This will assure that the system is running in real mode with no device drivers loaded This is the only correct way to run the TRMFLASH Utility program 2 There are 2 important files needed to re program the BIOS The first is TRMFLASH EXE which is the FLASH BIOS Programming Utility The second file needed is the updated BIN file which contains the actual BIOS code This file will have the extension bin such as INT13 BIN Make sure these files are on the diskette or hard drive in the same directory 3 Start the TRMFLASH Utility by changing to the directory where the two required files exist and typing TRMFLASH and pressing ENTER 4 The TRMFLASH Utility Screen appears You will be asked for the file name to program Type in the name of the
44. eater Than 1G Support in the PCU e Ifthe above solution does not work you must boot from a floppy and run FDISK EXE to delete the partitions Then re Fdisk and Format the drive to make it compatible with the DC 390 2 The BIOS Message of the DC 390 never appears on the screen e Check if you have any other cards in the system that could be using BIOS addresses C800 DCOO If you do one of these cards may be conflicting with the BIOS of the DC 390 Take out the suspect cards and see if the BIOS for the DC 390 comes up If it does change the address on the conflicting card 3 The lt lt lt Press F2 or F6 gt gt gt BIOS Message is missing after BIOS upgrade e After BIOS upgrade there will be no lt lt lt Press F2 gt gt gt message shown along with DC 390 s BIOS message during next bootup since the setting for F2 or F6 Function During Bootup is set to Disabled To enable this display you need to execute DOS UTIL EXE from the DOS NetWare driver diskette and set the F2 or F6 Function During Bootup in Set Adapter Options to Enabled 4 When the system attempts to boot the error Missing Operating System pops up e If you are using a drive that has been formatted with a different controller try changing the Greater Than 1G Support option in the DC 390 BIOS If you still get the error you must re Fdisk and Format the drive to get it to boot normally 66 DC 390 Series User s Manual
45. ed disks removable cartridges and re writable optical disks MO without the need for device drivers under DOS 5 0 or above This setting may be disabled under other operating systems than DOS Under DOS environments the devices connected to the DC 390 can be controlled through BIOS INT 13H or device drivers When the option Included in BIOS Scan is set to Yes that device is controlled by BIOS INT 13H If this option is set DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD to No that device must be controlled through device drivers The two options for More Than 2 Drive Support are as follows e Enabled default Under DOS 5 0 or above the ability to control up to eight devices controlled by BIOS INT 13H is provided Devices controlled could be IDE ESDI ST506 SCSI fixed disks removable cartridges and re writable optical disks MO e Disabled When this option is disabled only the number of drives in your mainboard CMOS setup are supported without drivers All other devices such as fixed disks over two removable cartridges re writable optical disks MO tape streamers DATs and CD ROMs would require device drivers When devices are under the control of BIOS INT 13H IDE drives always have higher priorities over SCSI drives The following is an example describing all the combinations Device Case0 Case1 Case2 IDE HDD 0 none Drive C Drive C SCSI Device 0 Drive C Drive D Numb
46. eerrrreres 60 10 SCO UNIX DRIVERS aia ee ee 61 10 1 Preparing a Driver Diskette eee eesceceseeceneeeeeeceseeseecesneseseeeeseessaeessaes 61 10 2 New SCO UNIX Installation ccccccccccccccececeeeeeeceeeeeeeeeceeeeeeeeeeeeeeeeeeeeees 62 DC 390 Series User s Manual 10 3 Adding the Driver to an Existing SCO UNIX System 0 eee eeeeeeeeeereeeeees 63 APPENDIX ono E fice te E E at Bi Seti ac ade Si Sedat dada Sa dec ducade deh 64 As Specifications nenn ana eee Ran ie eee 64 B Product Support Form ics e icecs seiescdsseacdeencedeuese ces suede sod EER EN EE E NRA 65 C General Troubleshooting Tips eeeseeseeesessresrserersresressresressresstesressresrresressres 66 D Flash BIOS Programming Utility sseeseeeseeeeeeseeressessreeressresressreeressreerresressres 71 DC 390 Series User s Manual 1 INTRODUCTION The DC 390 series is a SCSI Small Computer System Interface bus to PCI bus host adapter which complies to the PCI 2 1 specification with Plug amp Play PnP readiness By using the Disconnect Reconnect technique performance degradation during multitasking operations is prevented Other enhanced SCSI 2 features such as scatter gather and command tag queuing are supported The DC 390U2B W is a 16 bit Low Voltage Differential LVD Single Ended SE Ultra2 SCSI solution DC 390U2W can support both the legacy Fast SCSI and Ultra SCSI as well as the newest LVD Ultra2 SCSI without down grading the
47. elect Yes Recommended Click Next and Insert the Tekram Driver diskette in drive A Click Other Locations and specify the path as A Win95_98 Update Device Driver Wizard dialog box shows Windows found The following update driver for the device Tekram DC 395U UW or DC 315 U PCI SCSI Adapter Click Finish DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS 10 A Copying Files screen dialog box appears Specify path as A Win95_98 and click OK A System Settings Change dialog box appears Remove the driver disk from the drive and click on Yes to restart the computer 9 4 3 For an Existing Windows 98 System 10 11 12 13 14 Open the Control Panel and double click the System Icon Click the Device Manager Tab Double click on SCSI controllers Select Tekram DC 395U UW or DC 315 U PCI SCSI Adapter entry and click Properties Click the Driver Tab and choose Update Driver The Update Device Driver Wizard appears Click Next Choose Search for a better driver than the one your device is using now Recommended and click Next Select Specify a location and insert the Tekram Driver Disk into your floppy drive Specify path as A WIN95_98 Select Install one of the other drivers and click on the View List button Highlight the driver of choice and click OK Click Next The summary window displays the driver of choice and the path to be installed fr
48. er 11 Select Tekram DC 390 U F U2B U2W PCI SCSI and click Finish 12 Click OK to complete the installation DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS 9 3 Installing the Windows 98 Driver For DC 390 U2B U2W Windows 98 will detect the DC 390 series PCI SCSI Adapter as an AMD or Symbios PCI SCSI Controller DC 390U2B U2W and install its built in driver during Windows 98 Setup To replace the driver with the Tekram driver follow these steps 1 Open the Control Panel and double click the System Icon 2 Click the Device Manager Tab and select PCI SCSI Bus Controllers 3 Select Symbios Logic 895IU PCI SCSI Adapter for DC 390U2B U2W or AMD PCI SCSI Controller for DC 390 and click Properties 4 Click the Driver Tab and choose Update Driver The Update Device Driver Wizard will appear Click Next 5 Select Search for a better driver than the one your device is using now Recommended and click Next Select Specify a location and insert the Tekram Driver Disk into your floppy drive Type in the path A WIN95_98 Click Next Select Tekram DC 390 U2B U2W PCI SCSI Adapter and click Finish to install the driver SOF GO a ON 10 Restart the system Note Detailed installation procedures for Windows 98 amp NT can be found at http www tekram com DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS For DC 390U
49. er of drives supported by CMOS 2 has been reached Device driver must be used for this device Case 0 No IDE drives Two SCSI drives can be controlled with BIOS INT 13H Case 1 One IDE drive is installed as drive C One SCSI drive can be controlled through BIOS INT 13H Case 2 Two IDE drives are installed as C and D Since the maximum number of drives supported by the CMOS 2 has been reached no more SCSI device can be controlled by BIOS INT 13H Removable media as BIOS device Disabled Boot drive only All devices A BIOS device here is a device that can be controlled via BIOS INT 13H meaning that it does not need a device driver and can be bootable However when used as a BIOS device the full removability of removable media devices is not preserved The following constraints apply a The Device can only work as a fixed disk i e media change is not allowed b The Media must be inserted before the system boots up c Only media with 512 Bytes sector is supported DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD Disabled If this option is disabled the removable media devices will not be used as BIOS devices Boot drive This setting allows only the removable media installed as Drive C to only default work as a BIOS device thereby allowing it to boot As stated above this device would function as a hard drive not a removable However installing the provided device driver on this bootable drive wo
50. es on CN1 and CN2 Mixing Ultra2 devices with non Ultra2 devices will bring the Ultra2 devices to Ultra SCSI performance level DC 390 Series User s Manual 2 HARDWARE SETUP 2 6 Coexisting with Symbios 53C810 53C860 based Card 1 When you use DC 310 U or other Symbios 53C810 cards having EEPROM built on board with DC 390U F U2B U2W please only use tekram driver 2 If you use DC 310 U only or with other none Symbios chip card you have to use Symbios driver not Tekram driver The latest Symbios driver can get from LSI S web site http www lsi com 3 Other cards with 53C810 chip without EEPROM can not co exist with DC 390U F U2B U2W DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD 3 1 Setting the System BIOS After the DC 390 is inserted in an available PCI BUS slot and the jumpers and cables are properly set first turn on the power to your external SCSI devices and then power on the system When installing a SCSI drive as drive C or D set the CMOS HDD drive type according to the IDE drive installed The CMOS HDD is NOT related to SCSI HDD Note With most mainboards IDE Intelligent Drive Electronics ST506 and ESDI Enhanced Small Device Interface drives always take precedence over SCSI drives That means that if one IDE ST506 ESDI drive has already been installed you cannot install the SCSI drive as drive C If two IDE STS06 ESDI drives already exist no SCSI drives can be installed
51. evice has a capacity of 120MB with SCSI ID 4 ISC stands for PCI SCSI Controller 5 At the NetWare prompt type mount volume_name_as_desired At this point the file system is mounted and the device is locked Any attempt to eject the media while the file system is mounted will have no effect If the volume name of the new media is unknown it can be checked by selecting the item Volume Options after typing load install lt Return gt at the NetWare prompt Dismounting a File System To dismount a file system on removable media type dismount volume_name_as_desired lt Return gt load monitor lt Retum gt Select Disk Information Select the corresponding drive with removable media 3 Move the inverted cursor bar to the item Removable Drive Mount Status and choose dismount to dismount the device 4 Media ejection is now possible 5 5 Duplexing Both Mirroring and Duplexing are referred to as mirroring in the NetWare operating system Duplexing involves two drives on two separate host adapters while Mirroring is associated with two drives on a single host adapter Before enabling the duplexing function be sure to load the driver NV4XXBMP DSK two times for NetWare 4 xx or NV31XBMP DSK for NetWare 3 1x Further information about this subject can be found in the NetWare manual DC 390 Series User s Manual 6 OS 2 DRIVERS This chapter provides driver installation and un installation instructions for IBM OS
52. fifteen 16 bit and or 8 bit single ended SCSI devices amp up to seven of these can be 8 bit devices DC 390U2B Wide Ultra2 SCSI adapter 68 pin 16 bit Wide Ultra2 internal SCSI connector 68 pin 16 bit Wide Ultra2 external SCSI connector up to fifteen 16 bit LVD SE SCSI devices DC 390 Series User s Manual 2 HARDWARE SETUP DC 390U2W Wide Ultra2 SCSI adapter J1 68 pin 16 bit WIDE Ultra2 CN2 68 pin 16 bit Ultra Wide internal SCSI connector internal SCSI connector CN1 50 pin 8 bit internal SCSI connector E X O N es o gt 9 is We ag 5 Z z9 tn o lt g 3 peed up to fifteen 16 bit LVD SE and or 8 bit SE SCSI devices up to seven of these can be 8 bit device For DC 390U2B W When any SE device is connected on the Ultra2 connector s J1 and or J2 all the LVD devices on the connector s will be down graded to SE performance Therefore it is recommended that non Ultra2 devices are not to be used on DC 390U2B For DC 390U2W non Ultra2 devices should be kept on connectors CN1 and CN2 There are four connectors in DC 390U2W which can be separated into two independent SCSI buses using 53C141 SCSI Bus Expander http www Isilogic com products sym53c141 htm One is Ultra 2 connector s J1 and J2 and the other is single ended connector s CN1 and CN2 It is not an expander and the total devices are only 15 for this card The Max Cable Length is calculated by each ot
53. g initialization This amount of time is enough for most devices to get ready for proper operation Since some older hard drives may need more time to spin up you may need to extend the delay for those devices Max number of tagged commands 2 4 8 16 32 default The setting of this option depends largely on your application software In general a larger number of tagged commands results in better random disk access performance SCAM Support Disabled default Enabled SCAM SCSI Configured AutoMatically is the new SCSI Plug and Play protocol When enabled the DC 390 will auto assign a SOFT ID for SCAM supported devices thus the user is not required to re arrange the SCSI ID jumpers to resolve conflicts Refer to the device manual or enter Show_SCSI_Devices Sec 2 5 4 in PCU for more SCAM support information DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD F2 or F6 Function During Bootup Disabled Enabled default This setting determines whether or not the user can access the DC 390 s BIOS via the F2 or F6 keys during system boot When disabled the option to enter the PCU will not be displayed in which case the only way to configure the DC 390 s settings will be to run the UTIL EXE program in the DOS directory on the driver diskette You may want to disable this setting to prevent users from using potentially damaging functions such as the low level format 3 2 3 Set Devices Options This sub menu allows you
54. gn SCSI IDs to theses peripherals See page 23 to enable SCAM support DC 390 Series User s Manual 2 HARDWARE SETUP 2 4 Checking the Terminators on the SCSI Bus In order to stabilize the SCSI bus only two sets of terminators can be installed one at each end of the SCSI bus The DC 390 series is equipped with Active Terminators that automatically switch from Enabled to Disabled or vice versa by scanning the devices connected on the SCSI bus So manual termination adjustment is not required The following explains the terminator configuration of other devices on the SCSI bus 1 When only internal devices are connected to the DC 390 series adapter Leave the terminator mounted on the last device only with the SCSI card being the first SCSI device Remove terminators on all other devices connected in between When only external devices are connected to the DC 390 series adapter Leave the terminators mounted on the last device only Since external SCSI devices are daisy chained this would be the device without another SCSI cable plugged into it Remove terminators on all other devices connected in between When both internal and external devices are connected to the DC 390 series adapter Leave only the terminators mounted on the last internal device and the last external device As in the above case remove the terminators from all other devices connected in between Notel For DC 390F only When both Narrow 8 bit and Wide 1
55. her The terminator is set as two SCSI cards DC 390 Series User s Manual 2 HARDWARE SETUP 2 2 Setting the Jumpers DC 390 JP1 LED JP2 ROM DC 390U 390F 390U2B 390U2W SCSI Device Activity LED Indicator JP1 JP1 is used to indicate activity of the SCSI devices controlled by the DC 390 series adapter and should be connected to the cable leading to the Hard Drive LED on the front panel of your computer case ROM BIOS jumper JP2 DC 390 only You can install a maximum of 4 DC 390s in the same system However early mainboard BIOS cannot initialize adapter PCI ROM when multiple DC 390s are installed Newer mainboard BIOS should not have this problem When this occurs set JP2 to Enabled for the first adapter and Disabled for all additional DC 390s The BIOS of the first DC 390 will control all others installed 2 3 Setting the SCSI IDs Each SCSI device attached to the SCSI card as well as the card itself must be assigned a unique SCSI ID number SCSI ID 7 is preset to the SCSI card giving it the highest priority on the SCSI bus The SCSI IDs of your peripheral devices are usually set with jumpers or with a switch on the peripheral Refer to the peripheral manufacturer s manual to determine the ID of each device and how to change it Any SCSI device with SCAM SCSI Configured AutoMatically can assign its own SCSI ID dynamically and resolves SCSI ID conflicts automatically You do not need to manually assi
56. hows Tekram DC 390 DC 390U F U2B U2W PCI SCSI Adapter Click OK 9 A PCI SCSI Bus Controller Properties dialog box shows driver Files directory Windows S YSTEM IOSBUS YS TRM390 MPD or TRM390W MPD Click OK 10 A System Settings Change dialog box appears Remove the driver disk from the drive and click on Yes to restart the computer 9 2 Installing the Windows 95 OSR2 Driver The driver installation procedures are slightly different for the new Windows 95 B OSR2 You can check your Windows 95 version under Control Panel System 1 Open the Control Panel and double click the Add New Hardware Icon The Add New Hardware Wizard will appear Choose No for Do you want Windows to search for your new hardware Select SCSI Controllers for Hardware Types Click Have Disk and insert the DC 390 Driver Disk Type in the path A WIN95_98 and click OK ONT E es a a After the driver is installed open the Control Panel and double click the System Icon again 7 Click the Device Manager Tab and double click SCSI Controllers DC 390 or Other Devices DC 390F U U2B U2W 8 Select AMD PCI SCSI DC 390 or SCSI Controller DC 390F U U2B U2W and click Properties 9 Click the Driver Tab and choose Update Driver The Update Device Driver Wizard will appear 10 Choose No for Do you want Windows to search for your new driv
57. in detailed descriptions of the above options DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD 3 2 1 Show Adapter Information This screen displays detailed information about the SCSI chip ROM BIOS address I O port address IRQ PCI interrupt line etc The information about the SCSI Chip IRQ Trigger Type and Data Xfer Type is provided by the DC 390 series adapter itself The rest of the information in this table is provided by the mainboard s BIOS which should support the PCI PnP specification This information cannot be modified Adapter Information SCSI Chip cccce cece eeee AM53C974A Bus LY Pe Pinior A vetanves PCI Bus BUSH tives EEE i 00h Devicett edro einer cove OCh Function c eee 00h BIOS ROM mapped at CC00h IO Address 00 0 008 96000h PCI Interrupt Line INTA TROP oer mionario enana seen 11 IRQ Trigger Type Level triggered Data Xfer Type 065 PCI Bus Master 3 2 2 Set Adapter Options Set Adapter Options Adapter SCSI ID n a i E r ea SCSI ID 7 Default Boot Device IDencsrieoa i d en i SCSI ID 0 Default Boot Device LUN necirecciiinrareriscsess LUN 0 Default Boot From CD ROM ee Disabled Default INT13 Extension be sae Enabled Default Greater Than 1G Support sea Enabled Default More Than 2 Drives Support Enabled Default
58. irectory Create the directory C SERVER_312 CDSAVE Copy CDROM NLM to C SERVER_312 CDSAVE Change directory to the C SERVER_312 312PTD NATIVE LOADER Iswap loader exe C SERVER_312 SERVER EXE CD SERVER_312 Enter install at DOS command line Proceed through the installation of NetWare v3 12 as usual until the installation program ends with the cursor at the server console command line At the server console enter the following commands Load C SERVER_312 312PTD NATIVE START NPAPATCH Load C SSERCER_312 MMATTRFX Load C SERVER_312 NBI31X Load C SERVER_312 DC390XR1 HAM or DC390R1 HAM The install program will then require you to install additional server drivers You may see a message stating that the driver did not load in the time allowed Following that you should see a message like that below Load C NWSERVER DC390XR1 HAM Loading module DC390XR1 HAM DC 395U W F U2 or DC 310 U PCI SCSI Adapter Driver For NetWare V3 12 V4 XX 5 XX Version 3 03 March 1 1999 DC 390 Series User s Manual 5 NETWARE DRIVERS Tekram Technology Co Ltd Auto loading module NWPA NLM NetWare 3 12 4 x NetWare Peripheral Architecture NLM NBI Aware Version 2 33a July 31 1998 Copyright 1991 1998 Novell Inc All rights reserved HAM Auto Scan is enabled CDM Auto Loader is enabled Supported SLOT Options are 3 2 Select SLOT Option 3 When prompted for a slot number accept the slot numbers displayed This slot number is SLOT and
59. lled The first one adapter 0 controls two floppy drives two BIOS INT 13H controlled SCSI HDDs one MO device with three logical partitions drives and one SCSI HDD The second adapter 1 controls one SCSI HDD with one primary partition that is seen as logical partition G The CONFIG SYS would look like this DEVICE C ASPNASPLSYS DEVICE C ASPI TRMDISK SYS d300 Adapter 0 SCSI ID 0 BIOS INT13h controlled HD Drive D Adapter 0 SCSI ID 1 BIOS INT13h controlled HD Adapter 0 SCSI ID 4 Primary DOS MO i 5 DC 390 Series User s Manual 4 DOS ASPI DRIVERS amp UTILITIES Note With the More Than 2 Drives Support option enabled in the PCU you will be able to install up to eight drives without installing device drivers Of course your DOS version must be 5 0 or higher LOCK UNLOCK functions are crucial for data integrity of removable devices and need to be supported by drivers To prevent the data from being destroyed by improper operation of your devices it is recommended to use the DOS 4 x or higher SHARE utility for automatic LOCK UNLOCK support This can be done by adding SHARE EXE to your AUTOEXEC BAT file After loading share exe the system will LOCK your media when opening a file and UNLOCK it when closing the file This means that removable media can be ejected and changed at any time as long as no file is opened This change is transparent to the user and DOS logical drive information will be update
60. m from SYTRON CORP e SYTOS V3 xTape backup program from SYTRON CORP e ARCserve SoloTape backup program from Cheyenne CORP Note that the ASPI driver only provides the interface for tape systems You must purchase the desired tape backup software program separately DC 390 Series User s Manual 5 NETWARE DRIVERS The DC 390 U F U2B U2W supports drivers for NetWare V3 12 SFT III 4 00 4 01 4 02 4 1x 4 2 4 2SB 5 0 These are located under same directory on the software diskette This document explains how to install and use the Tekram NWPA SCSI Host Adapter Module HAM driver for NetWare This directory contains the following drivers e DC390R1 HAM DC390XR1 HAM support SCSI devices such as Fixed Disks Removable Cartridges and Re writable Optical Disks MO e DC390XR1 DDI DC390X DDI are the driver definition information file that provides setup information to NetWare during installation 5 1 ASPI Drivers for NetWare 5 1 1 NetWare 5 0 This subsection covers the installation of the driver module DC390R1 HAM DC390R1 DDI for DC 390 and DC 390XR1 HAM DC390XR1 DDI for DC 390U F U2B U2W for NetWare Versions 5 0 1 Begin the file server installation according to the instructions in the file server installation chapter in the Novell NetWare installation manual 2 After seeing the following dialog box appear in NetWare Installation Screen For DC 390 Device types Driver names Platform Support
61. mber will boot if there is more than one bootable CD ROM Note Don t confuse these settings with the Boot From CD ROM option in the mainboard s BIOS setup which is relevant only to ATAPI CD ROMs DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD INT13 Extension Enabled default Disabled When enabled the DC 390 will support more than 1024 cylinders for use with operating systems supporting the INT13 Extension The conventional INT 13H disk interface supports a maximum of only 1024 cylinders For operating systems such as Win95 OSR2 or later supporting INT13 Extension the DC 390 will support gt 1024 cylinders by using the Command Packet Mechanism instead of the cylinder head sector mechanism and thus work with SCSI disks greater than 8GB e For operating systems not supporting the INT13 Extension this option will be ignored e This setting is not to be confused with Greater Than 1GB Support which simply remaps the device s parameters to compensate for the 1024 cylinder limit Greater Than 1GB Support can handle drives up to 8GB in size due to fact that the maximum cylinders heads sectors is 1024 255 63 8GB INT13 Extension supports drives beyond 8GB in supported operating systems by using the Command Packet Mechanism Greater Than 1G Support Enabled Disabled FAT File Allocation Table file system Operating Systems such as DOS have traditionally imposed a barrier on the number of cylinders supported 1024
62. n Command Line option elev lt option gt Default value 4 Valid options 0 32 0 disable Function The threshold specifies the maximum number of request the HAM driver should queue up before NWPA to filter and organize scatter gather request DC 390 Series User s Manual 5 NETWARE DRIVERS 5 3 Server based Backup Restore Support The server based backup restore utility Sbackup comes with the NetWare OS The DC 390 s ASPI drivers provide an interface between this utility and the tape subsystem To run Sbackup at the NetWare prompt type load tsa410 lt Return gt load sbackup lt Return gt The Sbackup screen will appear Input the user name as requested and select the device driver Be sure to select the item HP DIBI 2 Tape Driver regardless of which type of tape drive you are using Different versions of NetWare may have slight differences in their procedures for running Sbackup For example under NetWare 3 12 you may have to execute the following procedures instead load tapedai load tsa312 load sbackup key in username and then select DIBI 2 DAI Tape Drive So refer to the NetWare manual regarding Server Backup for detailed backup restore procedures 5 4 Removable Media Support Removable media devices including Magneto Optical MO Disks differ from Fixed Disks in that the media can be dynamically changed ejecting and inserting disks while the system is running Due to the caching capability and file struc
63. new BIOS bin file and hit ENTER 5 The program will then ask if you want to backup the old BIOS This is recommended in case there are any problems with the new bin file Enter the name of the new backup file such as backup bin and press ENTER 6 At this time the system will prompt you for final confirmation before beginning programming The Utility can be aborted at this time by hitting n To begin programming hit y When the Flash programming starts a bar indicator will show the progress of the programming operation After successful completion hit the reset button or power off the computer After BIOS upgrade there will be no lt lt lt Press F2 gt gt gt message shown along with DC 390 s BIOS message during next bootup To enable this display you need to execute DOS UTIL EXE from the DOS NetWare driver diskette and set the F2 or F6 Function During Bootup in Set Adapter Options to Enabled DC 390 Series User s Manual
64. ock showing Choose the server Drivers Disk Driver during the installation insert the DC 390U F U2B U2W device driver diskette into drive A or B Then use the Ins key to select an unlisted driver A dialog box will appear If the driver diskette is in drive A press Enter key to continue If the driver diskette is in the B drive press the lt F3 gt key to specify the path B NETWARE The DC 390XR1 HAM driver will appear as a selection and press lt Enter gt key to load this driver For DC 390 installation skip step 4 DC 390XR1 will in the Driver Names further along the following procedure to delete the Symbios driver SYMXXNW in the Driver Names Choose Select additional modify selected Disk LAN driver Choose SYM8XXNW DC390XR1 Press Enter Choose Deselect a selected driver Delete SYM8XXNW Load a separate instance of the driver for every Host adapter present in the system DC 390 Series User s Manual 5 NETWARE DRIVERS 6 The install program will then require you to install additional server drivers You may see a message stating that the driver did not load in the time allowed Following that you should see a message like that below LOAD C NWSERVER DC390XR1 HAM or DC390R1 HAM for DC 390 Loading module DC390XR1 HAM or DC390R1 HAM for DC 390 DC 390U W F U2 or DC 310 U PCI SCSI Adapter Driver For NetWare V3 12 V4 XX 5 XX Version 3 0 3 March 1 1999
65. om is brought up Click Next Click Finish A System Settings Change dialog box appears Remove the Driver disk from the drive and click on Yes to restart the computer 60 DC 390 Series User s Manual 10 SCO UNIX DRIVERS This chapter explains how to install the SCO UNIX Boot Time Loadable Driver BTLD for Tekram PCI SCSI adapter DC 390 Two different installation procedures will be described separately Use the one that fits your environment e SCO UNIX has been installed on a non SCSI boot drive e SCO UNIX is to be installed from scratch on a SCSI drive attached to a DC 390 host adapter The example used throughout this chapter is for DC 390 under SCO Unix 3 2v4 x The following is the table for mapping different driver names used for DC 390 series under either SCO Unix 3 2v4 x or SCO OpenServer 5 0 DC 390 DC 390U F U2B U2W SCO Unix 3 2v4x ps E SCO OpenServer50 ams O sha 10 1 Preparing a Driver Diskette In order to install the Unix OpenServer driver a 1 44M driver diskette must be made first Download the SCO39X ZIP file from our Website at http www tekram com SCO39X ZIP is a compressed file of the SCO Unix OpenServer driver diskette which contains three files 1 RAWRITE EXE 2 OS5_39X and 3 SCO TXT In order to install the Unix OpenServer driver a 1 44M diskette must be made first from this file Follow the steps below C unzipped SCO gt RA WRITE OS5_3
66. ontrollers use Symbios SCSI chips some mainboards with built in NCR or Symbios Logic SCSI BIOS may detect these cards and load their own BIOS to control them This happens because Award BIOS checks only the Vendor ID NCR Symbios and Class Code SCSI device to determine if a suitable adapter exists to enable the built in SCSI BIOS This situation can arise with mainboards equipped with either of the following e Earlier versions of Award BIOS with NCR SCSI BIOS support e NCR Symbios V3 0 SCSI BIOS built in supports only 53C810 20 chips How to verify if you have this problem This problem can be verified by observing which BIOS banner is displayed upon bootup If an NCR or Symbios Logic BIOS banner is displayed the problem exists If only the Tekram BIOS banner is displayed there should be no problem If the NCR or Symbios Logic banner is observed take out the DC 390 and make sure that the banner goes away This will verify that the built in SCSI BIOS is being loaded to control the Tekram card If this is the case try the following solutions Solutions 1 See if there is a way to set the built in or on board SCSI BIOS to Disabled instead of Enabled or Auto in the mainboard s BIOS Setup This is the easiest solution if such an option is available If not see if a BIOS upgrade for the mainboard is available with this option 2 Remove the built in SCSI BIOS from the mainboard s Award BIOS using PROG ZIP a
67. r and press ENTER NT will prompt for the Manufacturer supplied support disk Insert the DC 390 driver diskette in drive A and press ENTER NT will check the floppy and show Tekram DC 390 NT 3 51 amp 4 x PCI SCSI Driver Ver XXX Tekram DC 390 NT 3 1 amp 3 5 PCI SCSI Driver Ver XXX Select the NT version you want to install and press ENTER After NT scans the hardware and finds the controller it will display Setup has recognized the following SCSI Adapters in your computer Tekram DC 390 PCI SCSI Adapter Ver XXX Press ENTER to continue and copy the driver files Boot from CD ROM DC 390 U2B U2W You can boot from CD ROM when you set the CD ROM as a boot device from Main Board BIOS for ATAPI CD ROM or DC 390 U2B U2W boot up screen for SCSI CD ROM 1 Press F6 key when the screen shows Setup is inspecting your Computer s hardware Configuration The next screen will show Setup could not determine the type of one or more mass storage device installed in your system Choose to configure an specify additional SCSI adapter by pressing S On the next screen NT will show various drivers Choose Other Required disk provided by a hardware manufacturer and press ENTER NT will prompt for the Manufacturer supplied hardware support disk into drive A Insert the DC 390 serier driver diskette in drive A and press ENTER NT will check the floppy and show Tekram DC 390 NT 3 51 amp 4 x
68. re actually connected now is the time to do it Refer to the SCO UNIX administrator s manual for how to add SCSI devices to the system Note It is important that when you are asked to input the driver prefix enter tps in response and proceed as normal Or you can manually edit the SCSI device configuration file etc conf cf d mscsi 8 After the devices are added rebuild the kernel as instructed If you do not plan to add any devices in order to rebuild the kernel type the following commands cd etc conf cf d link_unix 9 Reboot the system for the changes to take effect DC 390 Series User s Manual APPENDIX A Specifications PCI Features e PCI Specification Revision 2 1 compliant with full PnP support by host adapter s BIOS e High speed 32 bit PCI bus master DMA transfers of up to 132 Mbyte sec in burst mode e Direct glueless interface to 33MHz 32 bit PCI bus e Support for Scatter Gather DMA data transfers e Multiple byte DMA FIFO for low bus latency SCSI Features SCSI Protocol Max sync Max Model No SCSI I SCSI SCSI 3 Ultra2 data Xfer rate Devices DC 390 v s 10 7 DC 390U s s s 20 7 DC 390F v s v 40 15 DC 390U2B s v s v 80 15 DC 390U2W s v s v 80 15 e Boot ROM support e On chip state machine to control the SCSI sequences in hardware e Patented programmable GLITCH EATER Circuitry on REQ and ACK inputs DC 390 only e Programmabl
69. rectory on the driver diskette e TRM390 MPD Windows 95 98 driver file TRM390W MPD for DC 390U F U2B U2W e SCSLINF Information file 9 1 Installing the Windows 95 Driver For DC 390 Since the DC 390 PCI SCSI Adapter uses the AMD SCSI Chip Windows 95 will detect the card as an AMD PCI SCSI Controller and install that driver during Windows 95 Setup To replace the AMD driver with the Tekram driver follow these steps 1 Open the Control Panel and double click the System Icon Click the Device Manager Tab and double click SCSI Controllers Select AMD PCI SCSI and click Properties Click the Driver Tab and choose Change Driver Click Have Disk and insert the DC 390 Driver Disk Type in the path A WIN95_98 and click OK So OV as SB n EBS Select Tekram DC 390 PCI SCSI and click OK to install the driver For DC 390F U U2B U2W 1 Open the Control Panel and double click the System Icon Click the Device Manager Tab and double click Other Devices Select the PCI SCSI Bus Controller entry Click the Properties button Click the Driver Tab and choose Change Driver A Select Hardware Type dialog box appears Double click SCSI Controllers Click Have Disk and insert the Tekram Driver diskette in drive A et a a a Specify the path as A Win95_98 Click OK DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS 8 A Select Device dialog box s
70. ro initia aiaa 28 332 0 Verify Disk Utility i net taiah sek oh eek eke aii oa ee 28 4 DOS ASPI DRIVERS amp UTILITIES 0 0 eteccceeesseeeseeeeeeeeeeeeeeeeseeeeeeeeees 29 4 1 Easy DOS Driver Installation Software INSTALL EXE 42 gt Installing the ASPI Driver srin narse eat sede ccnvcedesecnacte teense sedeascene deaesugnnve 4 3 Installing the TRMDISK SYS Driver 4 4 Disk Partition Utility eee esse eeneeeeeeeee 4 5 Installing the CD ROM Driver eee eeeesceeseeeeeceseeceeeeseeceeeseeeesneeesaeees 4 6 Installing Tape Streamer DAT 0 eee eeecceneeeseeeseeceeeeseeeesnesneeeneeeeaeees 5 NETWARE DRIVERS ccceeeeseseeeseeeeeeeeeeeaneesseeeeeseeeeseeeeseneeeeeeees 38 5 1 ASPI Drivers for NetWare sanan onere et e i iaeaea iaai e Ei 38 SALA Netware 3 0221 sect eola tarna taa a ee a 38 Del 2 NetWare ANK reveni deian EREE EERE aa EE a Bedishesstenss hatte cissh 39 JLI NetWare 3 1 2 S R T a A RO E 41 DC 390 Series User s Manual 3 2 Driver Opuons eier rr EEE Eien E EEE EEV ETE E KEETE ES EEAS EESE EEA AE aE 43 5 3 Server based Backup Restore Support ssseeseesrssreesrssrrssresrrssreerresersreesressres 44 5 4 Removable Media Support ees eeseeseeceseecenecesseceseeeseessseeesseessaeesseeene 44 55 Duplexing iee h chee eiie a a eeeee Gee ie ote ee ARAA 45 6 OS 2 DRIVERS iiinn 46 6 1 New OS 2 Installations rnn erien rir irs a aE R E ER ia 6 2 Adding the Driver to an Existing OS 2 System 6
71. rocedures as CPUs to filter SCSI chip They pass test only if they can run 33MHz or above and are packed That s why some SCSI chips can be overclocked and others can t It can t be differentiated from the package The 33MHz PCI clock is transmitted from motherboard to PCI slot and then to SCSI chip of PCI card So the PCI interface related circuit inside SCSI chip is relevant to PCI clock As to 40MHz OSC on SCSI card it is used for SCSI Core Logics only inside SCSI chip PCI Interface related circuit would not use this 40MHz The circuit of SCSI Core Logics only uses 40MHz provided by OSC It is irrelevant to PCI clock 68 DC 390 Series User s Manual C General Troubleshooting Tips 1 WinASPI solution Windows 95 98 default supports WINASPI WNASPI32 DLL 32 bit User Mode WinASPI DLL 16 bit User Mode APIX VXD kernel Mode We do not need to provide those drivers Windows NT does not support WINASPI Customer install WINASPI to the NT when the Application needs this interface We provide Symbios WINASPI for our DC 390U F U2B U2W You can download from Symbios web site http www symbios com techsupport pci_sw htm agree A gree 15 SCAM support A general suggestion from Microsoft while doing PC98 test shows that user is not recommended to use the SCAM feature since some devices may not fully comply with the SCAM spec and may cause some problems accordingly 16 CD R Yamaha 4416S amp Panasonic 7502 need to set Wide
72. select New if you want to replace or upgrade the current driver Select OK to return to the Windows NT Setup program Shut Down and restart the system 7 2 2 For NT Versions 4 x e In Control Panel double click the SCSI Adapters icon Click on the Drivers Tab Click the ADD button Select Have Disk Insert the DC 390 Driver Disk in drive A and type in the path WINNT 3_51 4_x DC 390 Series User s Manual 7 WINDOWS NT DRIVERS Windows NT will show Tekram DC 390 PCI SCSI Adapter Ver XXX Select OK At this point if the specified driver has already been installed NT will display the following message The drivers for this adapter are already on the system Select Current if you want to use existing driver or select New if you want to replace or upgrade the current driver then enter in the path to the driver files A WINNT 3_51 4_x Restart the system 7 3 Removing the SCSI Host Adapter from the System 7 3 1 For NT Versions 3 x and 3 5x 1 2 3 4 From the Main Program group double click the Windows NT Setup icon From the Option pull down menu select Add Remove SCSI Adapters Select the specific SCSI adapter you want to remove Click the Remove button to delete the adapter 7 3 2 For NT Versions 4 x Be oe In Control Panel double click the SCSI Adapters Icon Click on the Drivers Tab Select the driver you wish to remove and click Remove Select Yes to remov
73. talled you are able to run or install the following utilities and drivers e TFDISK EXE Disk partitioning utility on the DC 390 series driver diskette e TRMDISK SYS Disk driver on the DC 390 series driver diskette e AFDISK EXE Disk partitioning utility from Adaptec e ASPIDISK SYS Disk driver from Adaptec e TRMCD SYS CD ROM and CD Changer driver on the DC 390 driver diskette e SYTOS PLUS Tape backup program from SYTRON CORP e SYTOS V3 x Tape backup program from SYTRON CORP e ARCserve Solo Tape backup program from Cheyenne CORP Other utilities drivers that conform to the ASPI standard may also be used Installation Procedure 1 Turn on the system and boot into DOS 2 Insert the DC 390 Driver Disk1 into your floppy drive 3 Copy the drivers and utilities into a properly named directory e g C ASPI 4 Add a line in the CONFIG SYS DEVICE C ASPI ASPLSYS 4 3 Installing the TRMDISK SYS Driver TRMDISK SYS is used to create valid DOS partitions and logical drives with those disks not controlled by BIOS INT 13H Generally this driver is needed only for Removable devices Remember by default Hard Drives are controlled by BIOS INT 13H More Than 2 Drives Support Enabled whereas removable devices are not controlled by BIOS INT 13H Removable Media as BIOS Device Disabled TRMDISK SYS controls up to eight SCSI devices such as fixed disks removable cartridges re writable optical disks and Flopticals Since TRMDISK SYS
74. ter and the SCSI Devices Utilities for verifying bad blocks and low level formatting are also included Another alternative is to run the provided DOS utility program UTIL EXE which performs the same functions as the PCU does Note UTIL EXE may be the only way to change options in the configuration of DC 390 series adapter in the event that either a The DC 390 s BIOS is disabled OR b The option F2 or F6 Function During Bootup is disabled It also allows you to modify your settings without rebooting to enter the PCU When running UTIL EXE it s best to boot clean from a DOS floppy disk After powering up the system the DC 390 s BIOS will show a message indicating its BIOS version with a date code and information about the IOPORT address IRQ number and address that the ROM BIOS is mapped at Upon pressing the lt F2 gt or lt F6 gt key the following screen will pop up Select An Adapter To Setup DC 390 gt gt gt gt BUS 00 DEV 0C IOPORT 9600h IRQ 11 If two or more adapters are installed choose the desired adapter to proceed with the configuration After pressing lt Enter gt the SCSI bus will be reset and the SCSI IDs for all devices installed on the SCSI bus will be scanned A selection table for further operations will be shown as follows Function Selection Show Adapter Information Set Adapter Options Set Devices Options Show SCSI Devices Low Level Format Verify Disk The sections that follow conta
75. to change options for each device on the SCSI bus Device information related to each SCSI ID is displayed in the lower portion of the screen DC 390 SCSIID 0 1 2 3 4 5 6 7 Parity Checking Yes Yes Yes Yes Yes Yes Yes Yes Allow Disconnection No Yes Yes Yes Yes Yes Yes Yes Send START UNIT Command No No No No No No No No Tagged Command Queuing Yes Yes Yes Yes Yes Yes Yes Yes Synchronous Negotiation Yes Yes Yes Yes Yes Yes Yes Yes Max Sync Xfer Rate 10 0 10 0 10 0 10 0 10 0 10 0 10 0 10 0 Included in BIOS Scan Yes Yes Yes Yes Yes Yes Yes Yes SCSI ID Model Device Type Capacity 0 DEC DSP3107LS Fixed disk 1021 M 1 FUJITSU M2513A Optical disk 604 M 2 SONY CD R CDU924S CD ROM 121M 3 NEC CD ROM DRIVE 462 CD ROM 4 IOMEGA ZIP 100 Removable disk 95 M 5 6 WANGTEK 5525ES SCSI M74H Tape drive 7 DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD DC 390F 390U 390U2B 390U2W MaxSyncXferRate replaced with MaxSyncXfers Wide Negotiation added SCSI ID 0 1 2 3 4 5 6 7 Parity Checking Yes Yes Yes Yes Yes Yes Yes Yes Allow Disconnection No Yes Yes Yes Yes Yes Yes Yes Send START UNIT Command No No No No No No No No Tagged Command Queuing Yes Yes Yes Yes Yes Yes Yes Yes Wide Negotiation Yes Yes Yes Yes Yes Yes Yes Yes Synchronous Negotiation Yes Yes Yes Yes Yes Yes Yes Yes Max Sync Xfers 20 0 20 0 20 0 20 0 20 0 20 0 20 0 20 0 Included in BIOS Scan Yes Yes Yes Yes Yes Yes Yes Yes SCSI ID Model Device Type Capa
76. ture of the NetWare operating system it is hazardous to change a file system disk in operation without the operating system being notified Should this happen the file system would probably be corrupted Another problem arises when a new disk file system is inserted The operating system needs to be informed of the change and the new disk geometry passed on in order for the new file system to be recognized In NetWare terms these problems deal with the mounting and dismounting of file systems on removable devices The following procedures illustrate how these problems can be overcome Mounting a File System To mount a file system on removable media insert the cartridge and wait for the disk to spin up At the NetWare prompt type load monitor lt Return gt Select Disk Information 2 Select the corresponding drive with removable media 3 Move the inverted cursor bar to the item Removable Drive Mount Status and press lt Return gt to mount the device 44 DC 390 Series User s Manual 5 NETWARE DRIVERS Note If the status is mounted already then dismount and mount it again by pressing 4 consecutive lt Return gt to make sure the operating system gets the correct disk geometry Exit monitor 4 The message shown on the console informing you of the new media geometry looks like this HA E800h ID LUN 4 0 Removable media cyls 120 hds 64 sec 32 This indicates that your DC 390 is installed with I O port E800H and your d
77. u don t need to run 98patch exe to fix PCI VXD DC 390 Series User s Manual 9 WINDOWS 95 98 DRIVERS 9 4 Adding the Driver to an Existing 95 98 System 9 4 1 For an Existing Windows 95 System 1 2 W PO Me E Open the Control Panel and double click on the System icon Click on the Device Manager tab and double click on the SCSI controllers entry Select the Tekram DC 395U UW or DC 315 U PCI SCSI Host Adapter entry Click the Properties button Click the Driver tab and click the Change Driver button Click Have Disk and Insert the Tekram Driver diskette in drive A Specify the path as A Win95_98 Click OK A Select Device dialog box shows Tekram DC 395U UW or DC 315 U PCI SCSI Adapter Click OK A Tekram DC 395U UW or DC 315 U PCI SCSI Host Adapter dialog box shows driver Files directory Windows SYSTEM IOSBUSYS Trm3X5 mpd Click OK A System Settings Change dialog box appears Remove the driver disk from the drive and click on Yes to restart the computer 9 4 2 For an Existing Windows 95 OSR2 System 1 2 3 CON Se ie Open the Control Panel and double click on the System icon Click on the Device Manager tab and double click on the SCSI controllers entry Select the Tekram DC 395U UW or DC 315 U PCI SCSI Host Adapter entry Click the Properties button Click the Driver tab and click the Update Driver button The Update Device Driver Wizard appears S
78. uld enable full removability for other removable media devices installed All Disks Enables all removable disk drives to work as BIOS devices Enable More than 2 drives support if necessary Notel Generally unless a Removable device is to be used as a boot drive this setting should be kept at its default and the driver TRMDISK SYS should be used to control removable devices Note2 For a removable media device to boot properly you ll have to use DOS FDISK partitioning utility and FORMAT it under DOS with the S switch Win95 s FORMAT will treat the removable media as a Super Floppy i e with no partition table and thus the disk will not be bootable Immediate return on SEEK command Disabled default Enabled Enable this option to bypass the BIOS SEEK command Scan all LUN for devices Disabled default Enabled Each SCSI ID can have up to eight Logic Unit Numbers LUN 0 7 With this option enabled all the LUNs for all SCSI IDs on the SCSI bus will be scanned and recognized as BIOS Devices If Disabled only LUNO of each SCSI ID will be scanned and recognized as a BIOS device Active Negation Enabled default Disabled Enable this option to enhance the noise immunity on the SCSI bus Power on RESET SCSI Bus Enabled default Disabled When enabled the SCSI BIOS is reset upon initialization Delay before BIOS scans Device 3 120 seconds The default is a 3 second delay before the BIOS starts to scan for SCSI devices durin
79. ult 8 The Message No BIOS Disk Found SCSI BIOS Not Installed is displayed by the DC 390 BIOS e This message is normal when only a CD ROM device is installed Since this type of device uses device drivers the DC 390 s BIOS is not installed 9 No Valid SCSI Device Found is displayed during boot up e If this message is generated by the driver TRMDISK SYS you probably do not need it in CONFIG SYS Remember this driver is only for Removable Devices and HDs if More Than 2 Drives Support is Disabled 10 SCSI device is not presented in the DC 390 s BIOS message during bootup e Check that the Included In BIOS Scan option in Set Device Options is set to Yes or not Setting this option to Yes will enable the DC 390 s BIOS to re scan this device during the next bootup 11 DC 390 with RICOH CD R RO 1420C DC 390U F are O K The RO 1420C may wrongly generate a SCSI parity error during its reselection phase SCSI adapters based on the NCR 53CF94 SCSI core can hang up if this condition occurs since the 53CF94 DOES check SCSI parity during the reselection phase The following SCSI controllers have been tested to confirm the above observation DC 390 Series User s Manual C General Troubleshooting Tips e DC 390 PCI SCSI controller based on AMD 53C974A SCSI core is 53CF94 e DC 300B ISA SCSI controller based on NCR 53CF94 e IN 9100 PCI SCSI controller by INITIO based on PCI bus master controller and 53CF
80. vailable at http www tekram com or ftp ftp tekram com This file contains the following files PROG BAT Batch file used to remove built in NCR SCSI BIOS or restore original mainboard BIOS This is written by Tekram AWDFLASH EXE Utility to retrieve or program mainboard BIOS CBROM EXE Utility to remove built in NCR SCSI BIOS from mainboard BIOS s binary file DC 390 Series User s Manual TABLE OF CONTENTS Ty INTRODUCTION shes eel Aaa taal eet va dna ndeas iradiasi daadaa 7 2 HARDWARE SETUP niinn fetes tein tecedt edt sattcn teed aa 8 2L Board Way Out c3225 425 325 025 0350c aA sek cats N Samed E se POSE Ta Ruse 9 2 2 Setting ithe Jumpers r esi naana eed hese se Mass RS aE NE ede ee SS 12 2 37 Settna the SCSI TDs rran eases oe R R a see es 12 2 4 Checking the Terminators on the SCSI Bus 0 0 ees ceeceeeceeeseeesseeeeeeeeseeeeeeenee 2 5 Cable Connection aknan a 2 6 Coexisting with Symbios 53C810 53C860 based Card 3 CONFIGURING YOUR SCSI CARD sasssssssssnnnnnnennnnnnnnnnnnnnnnnnnnnnna 3 1 Setting th System BIOS sss neve n edie eee eA A eae ns 3 2 Running the PCU PCI Configuration Utility 3 2 1 Show Adapter Information ccccscccccceeseceseceseeeeseeeseeseneessaeeeseeenseesaes 3 2 2 Set Adapter Opuons i e eee si oh wh oa aia enna nanan 19 3 2 3 Set Devices Options oann ronn RE ANE E E RA 24 324 SHOW SCSEDEVICES reaa Ste Aa AE R A R a e AUER 27 3 2 5 Low Level Format Utility srei ara
81. vices one at a time during system initialization starting from the lowest SCSI ID However each device would be required to support this option DC 390 Series User s Manual 3 CONFIGURING YOUR SCSI CARD Tagged Command Queuing Yes No default The Yes option is useful for enhancing overall system performance under multi tasking operating systems such as OS 2 Windows NT and Unix Wide Negotiation Yes No This option is ignored when the DC 390U a non Wide SCSI adapter is installed It is suggested that you enable this option i e Yes for 16 bit Wide SCSI devices in order to gain the best performance and that you disable it for 8 bit devices for less compatibility problems Synchronous Negotiation Yes No Yes default is for Active Synchronous Negotiation In this mode the DC 390 series adapter will initiate SCSI synchronous negotiation when the system boots up NO Asynchronous Negotiation mode is normally at a lower rate and not related to timing MAX Sync Xfer Rate for DC 390 10 0 2 00 MB sec The DC 390 supports 10 00 MB sec as the highest data transfer rate for compatibility with SCSI devices complying with the Fast SCSI II protocol The DC 390 will negotiate an optimum speed depending on the transfer rate of each device under the chosen option MAX Sync Xfers for DC 390U 390F 390U2B 390U2W Model SCSI Byte Xfer Max Sync Xfer Max Sync Xfer Rate width MXfer sec MB sec DC 390U2B DC 390U2W i 2 w DC 390F

DC-390 Series

Contents

Download Pdf Manuals

Related Search

Related Contents