Release: SCO OpenServer ADV Driver 3.3B Last Updated: 04/25/00 Copyright (c) 2000 Initio Corporation The AdvanSys SCO OpenServer ADV Driver supports AdvanSys SCSI Adapters for the SCO Unix 4.2, OpenServer 5.0.0, and OpenServer 5.0.2, 5.0.4 , 5.0.5 Releases. The SCO directory includes the following files. Readme.txt Installation Instructions SCOBTLD.EXE DOS Self-extracting Boot (BTLD) Diskette Image SCOBTLD.Z UNIX Compressed Boot (BTLD) Diskette Image To install the SCO ADV Driver you will need to create a Boot Diskette containing the driver. You may create the diskette using either a DOS or Unix system. Decide which system to use and follow the directions below. After the diskette is created it can be used to add the driver during an SCO OpenServer installation or used to add the driver to an existing SCO OpenServer system. Directions for both of these installation options are listed below. Supported Adapters ================== ABP940/ASB3940 UW Bus Master PCI ( Single Channel) ASB3940 U2W Bus Master PCI ( Single Channel) ABP950/ASB3950 UW Bus Master PCI ( Dual Channel) ABP950/ASB3950 U2W Bus Master PCI ( Dual Channel) ASB3950 U3W Bus Master PCI ( Dual Channel) Instructions for creating the ADV Driver Diskette from DOS ============================================================== The file scobtld.exe is a self-extracting archive which contains an image of an SCO OpenServer EAFS file system. The image can be copied to a 3.5" diskette to make an ADV Driver BTLD diskette. 1. Copy the file scobtld.exe from the AdvanSys DOS diskette containing the directory SCO to a DOS system. > copy a:\sco\scobtld.exe 2. Type the command scobtld.exe. The following two files will be created: btld.dat unixfer.exe 3. Insert a blank formatted diskette in the 3.5" floppy disk drive and create the diskette with the following command. > unixfer btld.dat a: 4. To verify the contents of the diskette unixfer can also be run in reverse. The file btld.dat should exactly match test.dat. > unixfer a: test.dat > fc btld.dat test.dat Instructions for creating the ADV Driver Diskette from SCO OpenServer ================================================================ The file scobtld.Z is a compressed image of an SCO OpenServer EAFS file system. The image can be copied to a 3.5" diskette to make an ADV Driver Diskette. 1. Copy the DOS file SCOBTLD.Z from the AdvanSys DOS diskette containing the directory SCO to an SCO Unix system. $ doscp a:/sco/scobtld.z scobtld.Z 2. Uncompress the file scobtld.Z with the following command. $ uncompress scobtld.Z 3. Insert a blank diskette in the 3.5" floppy disk drive and use "dd" to create the diskette with the following command. $ dd if=scobtld of=/dev/rfd0 bs=64k 4. To verify the contents of the diskette run dd in reverse. The file scobtld should exactly match test.dat. $ dd if=/dev/rfd0 of=test.dat bs=64k $ cmp scobtld test.dat Installing the ADV Driver during SCO OpenServer Installation ============================================================= 1. Create an AdvanSys driver diskette as described above. Label the diskette "AdvanSys SCO BTLD Diskette." Please also record the version of the driver on the diskette. The driver version number should be listed at the beginning of this file. 2. Set-up your devices to have the following SCSI Target IDs: Hard Disk: 0, CD-ROM: 5, and Tape Drive: 2. 3. Boot the system with the SCO installation boot disk. 4. Type "link" at the boot prompt "Boot:". This will cause SCO to dynamically link the AdvanSys driver into the install kernel. The AdvanSys driver is a BTLD (Boot Time Loadable Driver). 5. When the installation asks you what package to link, enter "adv". This is the name of the AdvanSys BTLD driver package. NOTE : When using both "asc" and "adv" drivers, type in "asc" first. "asc" is the SCO-OpenServer driver for AdvanSys Ultra/narrow SCSI adapters. 6. Insert the "AdvanSys SCO BTLD Diskette" into the floppy drive when the system requests it. Note: The diskette should not be inserted after entering "adv". The install procedure will ask for it later. 7. The install procedure may ask for the "AdvanSys SCO BTLD Diskette" more than once. Installing the ADV Driver after SCO OpenServer has already been Installed ================================================================= 1. Create an AdvanSys driver diskette ask described above. Label the diskette "AdvanSys SCO BTLD Diskette." Please also record the version of the driver on the diskette. The driver version number should be listed at the beginning of this file. 2. Type the command "installpkg" from the SCO OpenServer command line. 3. Insert the "AdvanSys SCO BTLD Diskette" into the floppy drive when prompted. 4. After installation, type the following commands to rebuild a new kernel that contains the adv driver. For more information refer to the SCO documentation regarding compiling the kernel. cd /etc/conf/cf.d ./link_unix Installing SCSI Devices under SCO OpenServer ======================================= To create device files to access SCSI devices use the SCO "mkdev" command. "mkdev" is an interactive command that will ask you questions about your SCSI configuration, make kernel configuration changes, and re-build the kernel. Type "mkdev hd" for disks, "mkdev tape" for tape drives, and "mkdev cdrom" for CD-ROM devices. "mkdev" will ask the name of the AdvanSys driver and AdvanSys SCSI adapter number. The driver name is "adv" and adapter numbering begins with 0. If there is one AdvanSys adapter enter "0", a second adapter is number "1", etc. For disk devices "mkdev hd" should be run twice. The second time it is run after the kernel has been re-built and booted so that the disk can be partitioned and file systems can be built. The "mkdev" kernel configuration file is /etc/conf/cf.d/mscsi. It can be viewed with an editor to verify "mkdev" has added the correct parameters to the kernel configuration. Here is a basic list of SCO SCSI device files: Disk Device Files: /dev/[r]dsk/[0-9]s[0-9] Tape Device Files: /dev/[nruh]Stp[0-9] CD-ROM Device Files: /dev/[r]cd[0-9] Installation Problems and Troubleshooting ========================================= Problem 1: ---------- The AdvanSys SCSI Host Adapter controls the boot disk. When the system boots the following warning message is printed and, the SCSI disk is NOT recognized. WARNING: hd: no root disk controller Resolution 1: Make sure that the SCSI Disk is at ID 0. Resolution 2: When there are multiple HBAs installed ( AdvanSys or from other vendors ), the root hard disk is expected to be on the first of these HBAs as detected by the OS. To change this default, enter the following string after "link" at the "Boot:" prompt. ( Step 4 of Installation procedure) defbootstr Sdsk=adv(ha_num, SCSI ID, 0) Example : link defbootstr Sdsk=adv(1,0,0) Note : The ha_num can be found from the line printed by the AdvanSys Driver. %adv 0x6000-0x6040 11 0 AdvanSys U2W/UW SCSI 3.2B ha_num=0 %adv 0x6000-0x6040 13 0 AdvanSys U2W/UW SCSI 3.2B ha_num=1 . . . . %adv 0x6000-0x6040 15 0 AdvanSys U2W/UW SCSI 3.2B ha_num=n Problem 2: ---------- The AdvanSys SCSI Host Adapter controls the boot disk. When the system boots the following warning and panic messages are printed: WARNING: hd: no root disk controller PANIC: srmountfun - Error 19 mounting rootdev (1/40) Resolution 1: These error messages indicate that the AdvanSys driver is not compiled into the SCO OpenServer kernel being booted or on an initial installation the SCSI hard disk is not set to target ID 0. If you are performing a first time installation make sure that your SCSI hard disk target ID is 0. This is an SCO OpenServer requirement. To recover if you have rebuilt the SCO OpenServer kernel and the previous kernel worked with the AdvanSys adapter, then at the boot prompt "Boot:" type "unix.old". This will cause the last kernel to be booted ("unix.old") instead of the currently installed kernel ("unix"). After restarting the system, rebuild the SCO kernel to include the AdvanSys driver. Problem 3: ---------- The CD-ROM drive is not being recognized by the OS and the following error message is displayed : NO RESPONSE : There is no response from the controller for the device that you have selected. Resolution 1 : Make sure that the SCSI ID correct. Resolution 2 : Make sure that the SCSI Adapter type is adv. Resolution 3 : Make sure that the SCSI Host Adapter is correct. When there are multiple AdvanSys HBAs this will take values 0,1,2.... Resolution 4 : Restart the Installation procedure and change the default CDROM settings as follows. To change this default, enter the following string after "link" at the "Boot:" prompt. ( Step 4 of Installation procedure) defbootstr Srom=adv(ha_num, SCSI ID, 0) Example : link defbootstr Srom=adv(1, 5 ,0) Problem 5: ---------- During SCO OpenServer 5.0 installation the keyboard locks up and does not accept any keyboard input. Resolution : This is a known SCO OpenServer 5.0 problem on faster systems with an AMI keyboard BIOS. SCO has a solution for the problem available from their technical support. The problem can be identified as OSS424A. Here is the FTP location of the solution: ftp://ftp.sco.com/SLS/oss424a.ltr.Z ftp://ftp.sco.com/SLS/oss424a.Z Initio Contact Information =========================== Mail: Initio Corporation 2205 Fortune Drive Suite A San Jose, CA 95131 Operator: 1-408-577-1919 FAX: 1-408-577-0640 Tech Support: 1-408-965-5039 Tech Support E-Mail: support@initio.com Web Site: http://www.initio.comDownload Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.