Download Sunix USB Devices Driver

| 29-03-2021
[RAND-1-100] Comments

You can use Android Debug Bridge (ADB) to connect your Fire tablet to your computer for testing and debugging. You connect your computer to your Fire tablet through a micro-USB cable.

Android Debug Bridge (ADB) is a command-line utility for running and managing Android apps on your device or emulator. For more information and instructions on using ADB, see Android Debug Bridge.

If you're looking for instructions on connecting to a Fire TV instead, see Connect to Fire TV Through ADB.

USB Drivers Futronic USB Driver ( v10.0.0.1 (Windows 32 bit & 64 bit)) Supported Devices: Futronic FS80, Futronic FS88. OS: Windows 8, Windows 8.1, Windows 10: Download: Futronic USB Driver ( v4.0.1.5 (Windows 32 bit & 64 bit)) Supported Devices: Futronic FS80, Futronic FS88. OS: Windows XP, Windows 2003, Windows Vista, Windows 2008, Windows.

  • Check for Device Connections Using ADB (Optional)
  • Troubleshooting
  1. LG USB Drivers Ver. 4.5.0 and LG USB Drivers Ver 4.4.2 In this post, you can download and install the latest LG USB Drivers Ver 4.5.0 for your LG Phones or tablets. In order to establish communications between your LG devices and computer, you need to install the latest LG Drivers properly onto your computer.
  2. These miniport drivers allow connection of SCSI devices including disk drives, CD-ROMs, and tape drives for PCI-based machines. To support a new SCSI device, the Windows 95/98 architectures require that a class driver for that type device is present (usually supplied by Microsoft, or possibly by the peripheral manufacturer).

Step 1: Enable Developer Options

  1. Go to Settings > Device Options and look for a Developer Options menu. If it's not there, do the following:

    a. Go to Settings > Device Options > About Fire Tablet.b. Tap your Serial Number seven times.c. Return to Device Options. A new menu appears called 'Developer Options.'

  2. Tap Developer options. (2013 models might call this option 'Security.')
  3. Set Developer options and USB debugging to ON.
  • If you have a Kindle Fire 1st Generation, ADB is enabled by default.

Step 2: Install the Kindle Fire Driver (Windows Only)

  1. If you're using Windows, download this Kindle Fire driver: kindle_fire_usb_driver.zip.
  2. After downloading the file, extract the contents into a new folder and double-click the Fire_Devices ABD drivers file.
  3. Proceed through the installation wizard screens to install the driver.

Step 3: Install Android Studio

ADB is available on your computer when you install Android Studio. If you don't already have Android Studio, download and install Android Studio. If you're not using Android Studio, you need to download and install Android SDK platform tools.

Step 4: Connect Your Fire Device to Your Computer with a USB Cable

  1. Using a USB cable, connect your Fire tablet to a USB port on your computer.

    Note that Fire tablets can treat the USB with different transfer options. After connecting the USB cable, swipe down from the top of your tablet to see the USB option used. You might see various notifications, including the USB connection type that was used when you connected the cable. The relevant notification is highlighted in the screenshot below.

    If you don't see 'Connected as Media Device', press Tap for other USB options. Then select Media device (MTP). Later Fire OS versions have a different interface here. If you're using Fire OS 7, select File Transfer.

    Note: If your USB is connected as a Camera (PTP), Android Studio won't recognize the tablet as a device in Android Studio.

    If you don't see the USB connection type in the above notifications, go to Settings > Device Options > Developer Options > USB computer connection. Set this to Media device (MTP). For Fire OS 7, select File Transfer.

  2. When the Allow USB debugging? dialog appears on your tablet, tap OK.

  3. Open Android Studio and look for the device to appear in devices drop-down menu:

    The device's name will use the android.os.Build.MODEL property for the device. KFSUWI refers to Fire HD 10 (2017) tablet. You can see a list of build model names in the Identifying Fire Tablet Devices.

    If you have not selected the 'Allow USB Debugging' dialog on your tablet, the name 'Unknown device' will appear in the devices drop-down menu in Android Studio until you allow debugging.

  4. With the tablet connected, you can now run your app on your tablet by clicking the Run App button in Android Studio.

Drivers

If you run into issues, see the Troubleshooting section below.

Check for Device Connections Using ADB (Optional)

Instead of looking in the devices menu in Android Studio, you can also use some ADB terminal commands to confirm that your device is connected. ADB is useful for performing many other operations as well, such as entering sandbox mode or installing other assets. Follow these two sections:

If you skip adding ADB to your PATH, you can also Check for Connected Devices If ADB Isn't In Your PATH.

Add ADB to Your PATH

First, add ADB to your PATH so you can more easily run ADB commands. (Your PATH is an environment variable used to specify the location of the program's executable. If you don't add ADB to your PATH, running ADB commands will require you to browse to the <Android SDK>/platform-tools directory to run adb.)

Tip: You can check whether ADB is already added to your PATH by typing adb version from a terminal or command prompt. If you get back version information, then ADB is in your PATH. If the response says adb is an unrecognized command, ADB is not in your PATH.

To add ADB to your PATH on Mac:

  1. Get the path to your Android SDK platform-tools directory:

    1. Open Android Studio and click the SDK Manager button .The location to your Android SDK appears near the top next to Android SDK Location. For example: /Users/<your username>/Library/Android/sdk

      If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.

    2. Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
    3. Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
    4. Copy the full path to your clipboard.

  2. Use the following command to add ADB to your .bash_profile. Replace <your username> with your actual username. Also, make sure the path points to your Android SDK.

    Your .bash_profile file is usually in your user directory, which you can find by typing cd ~ (change to your user directory). Then type ls -a (list all) to show all files, including hidden ones.

    If the file isn't there, simply create one. You can then type open .bash_profile to see the paths listed.

    After you add this PATH to your bash profile, you should see the following in your .bash_profile file:

    (Only instead of johndoe, you will see your own username.)

  3. Fully restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'

To add ADB to your PATH on Windows:

  1. Get the path to your Android SDK platform-tools directory:

    1. Open Android Studio and click the SDK Manager button .

      The location to your Android SDK appears near the top next to Android SDK Location. For example: C:Users<your user name>AppDataLocalAndroidSdk

      If this is your first time opening Android Studio, there isn't an SDK Manager button. Instead, at the Welcome to Android Studio prompt, click Configure > SDK Manager and provide the location to the Android SDK.

    2. Copy the path to the SDK and paste it somewhere convenient, such as a text editor.
    3. Add /platform-tools to the end of the path you copied in the previous step. ('platform-tools' is the directory containing the ADB executable.)
    4. Copy the full path to your clipboard.
  2. Click your computer's search button (next to Start) and type view advanced system settings.
  3. Click View advanced system settings.
  4. When the System Settings dialog opens, click the Environment Variables button.
  5. Under System Variables (the lower pane), select Path and click Edit.

  6. Do one of the following:

    • On Windows 7 or 8, move your cursor to the farthest position on the right, type ; and then press Ctrl+V to insert the path to your SDK that you copied earlier. It may look like this: ;C:Users<your user name>AppDataLocalAndroidSdkplatform-tools. Click OK on each of the three open dialog boxes to close them.
    • On Windows 10, click the New button and add this location.
  7. Restart any terminal sessions, and then type adb. If you successfully added ADB to your path, you will see ADB help info rather than 'command not found.'

Check for Connected Devices

  1. Assuming ADB is added to your PATH, run the following commands:

  2. Confirm that the serial number for your Fire tablet appears in the list of devices. For example:

    On your tablet, your device's serial number is located under Settings > Device Options.

Check for Connected Devices If ADB Isn't In Your PATH

If your terminal doesn't recognize adb as a command (that is, you didn't add ADB to your PATH), you might have to run the commands from the SDK directory that contains ADB.

  1. In Android Studio go to Tools > SDK Manager.
  2. In the SDK Manager dialog box, copy the Android SDK Location.

  3. Browse to this location in your terminal or command prompt. For example:

    Mac

    Windows

    Then go into the platform-tools directory:

    The platform-tools directory contains adb.

  4. Now run the ADB commands as follows:

    Mac:

    Windows:

    The response should list your device's serial number. For example:

    If your Fire tablet is still not detected, you may need to reboot your computer or log out and back in for the changes to take effect.

Troubleshooting

Tablet doesn't appear in list of devices in Android Studio

  1. If you don't see your tablet device in the list of devices in Android Studio, click the devices drop-down menu and select Troubleshoot device connections:

  2. Click Rescan devices.

    If rescanning devices doesn't detect your Fire tablet as a device, your micro-USB cable might be bad, you might have the wrong USB connection type (e.g, camera instead of media device), or you might not have enabled USB debugging. You can also try restarting your computer and the tablet.

Uninstall the non-ADB Driver (Windows)

If you previously connected a Fire tablet without first enabling ADB on the Fire tablet, you might need to remove the existing USB device driver and force re-installation of the driver. To remove the non-ADB driver:

  1. Using a micro-USB cable, connect your Fire tablet to a USB port on your computer.
  2. On your computer (Windows 10), click the search button (next to the Start menu) and type Device Manager in the search. Then select it in the results. (Other Windows versions have different options for accessing the Control Panel.)
  3. In the Device Manager window, expand Portable Devices.
  4. Right-click the Fire device and then click Properties.
  5. In the Properties window, on the Driver tab, click Uninstall, and then Confirm.
  6. Unplug your Fire tablet from your computer.

Confirm the Fire Driver Is Installed Correctly

You can confirm that the Fire driver is installed correctly by doing the following:

  1. On your computer, click the search button search button (next to the Start menu) and type Device Manager.

  2. In Device Manager, under Fire Devices, verify that that a device appears called Android Composite ADB Interface.

    If your Device Manager shows an Other Devices section with a second Fire device with a yellow alert sign, your computer is listing Amazon's unrecognized ADB module as a separate device. To fix this issue:

    1. Under Other Devices, right-click the Fire device and select Properties.
    2. On the Driver tab of the Properties window, select Update Driver…
    3. Choose to browse for the driver software, then navigate to Let me pick from a list of device drivers on my computer > Show All Devices > Have Disk.
    4. Navigate to the folder where you installed the Amazon driver (typically C:Program Files (x86)Amazon.comFire_DevicesDrivers) and select it.

    5. Ignore the warning regarding installing drivers and proceed.

      You should now correctly see your Fire tablet with the ADB driver installed.

Last updated: Oct 29, 2020

Device Drivers for Windows 95 and Windows 98

Installing the SDMS™ Drivers:
SYMC8XX.MPD, SYM_HI.MPD, and SYM_U3.MPD

This document provides installation instructions and includes these topics:

Windows 95 and Windows 98 are operating systems designed to run on Intel processors using current technology. This file refers to Windows 95 and Windows 98 as Windows 95/98 in many instances throughout this document. LSI Logic uses the same filenames for their drivers for different Windows operating systems. The driver files are packaged either in separate subdirectories based on the Windows operating system or on different diskettes. To determine the driver file for Windows 95/98, note that the filename ends with '.MPD.' For example, SYMC8XX.MPD.

Windows 95/98 provide a graphical user interface environment incorporating many high-level features, which are described in Microsoft Windows 95 and Windows 98 documentation. An I/O manager handles I/O requests in Windows 95/98. To address a SCSI peripheral, the I/O manager goes through the appropriate drivers.

Windows 95/98 provide class drivers for hard disk, floptical, CD-ROM, printer, and scanner peripherals. Various peripheral manufacturers provide other class drivers, which you can add to support new devices.

Microsoft provides the port driver, and LSI Logic provides the miniport drivers, which are called SYMC8XX.MPD, SYM_HI.MPD and SYM_U3.MPD. These drivers complete the path to an LSI Logic controller or processor with an optional SDMS SCSI BIOS.

Note: Current Windows 95/98 drivers can be downloaded from the LSI Logic web site at http://www.lsilogic.com. After you are connected to this web site, place your cursor on the Get Drivers option in the menu bar. Click on the Drivers selection. Choose the Windows 95/98 operating system for SCSI and click on the Go button. Follow the instructions on subsequent screens to download the drivers.

The next sections describe the SDMS miniport drivers and their installation procedures.

The SDMS device drivers for Windows 95/98 support these features:

  • Ultra160 data transfers (for LSI53C1010)
  • Domain Validation (for SYM_U3.MPD driver only)
  • Parallel Protocol Request (for SYM_U3.MPD driver only)
  • Cyclic Redundancy Check (for SYM_U3.MPD driver only)
  • Synchronous negotiation (including Fast SCSI/Ultra SCSI/Ultra2 SCSI)
  • Wide negotiation
  • Auto request sense
  • Multiple host adapters
  • Multiple Logical Unit Numbers (LUNs)
  • Disconnect/Reselect
  • Scatter/Gather
  • Provides differential support
  • SCSI pass-through functionality
  • SCAM support (SCSI Configured AutoMatically)
  • Target-initiated negotiation support
  • NVRAM support (wide/sync parameters, SCSI Host ID, SCAM on/off)

Note: These SDMS miniport drivers also support Windows Me (Millennium Edition). The installation and upgrade procedures are similar to the Windows 98 instructions in this document.

All LSI Logic devices and host adapters have undergone a name change. They have transitioned from a SYM prefix to an LSI prefix. No name changes have occurred for the SDMS Windows 95/98 drivers.

The SYMC8XX.MPD driver supports the following devices and their associated LSI Logic host adapters:

  • LSI53C810, LSI53C810A, LSI53C810AE (LSI8100S, LSI8100ASP)
  • LSI53C815 (LSI815XS, LSI8150SP)
  • LSI53C825, LSI53C825A (LSI8250S, LSI8251S, LSI8251D, LSI8250ASP, LSI8251ASP, LSI8251AD)
  • LSI53C860, LSI53C860AE (LSI8600SP)
  • LSI53C875, LSI53C875E (LSI8750SP, LSI8751SP, LSI8751SPE, LSI8751D)
  • LSI53C876 (LSI22801, LSI22802)
  • LSI53C885
  • LSI53C895 (LSI8951U, LSI8952U)

The SYM_HI.MPD driver supports the following devices and their associated LSI Logic host adapters:

  • LSI53C896 (LSI22910, LSI21002, LSI22902)
  • LSI53C895A (LSI8953U)

The SYM_U3.MPD driver supports the following device and its associated LSI Logic host adapters: LSI53C1010 (LSI8955U, LSI22915, LSI21040, LSI22903).

The SYMC8XX.MPD, SYM_HI.MPD, and SYM_U3.MPD drivers meet the Microsoft specification for miniport drivers. These miniport drivers allow connection of SCSI devices including disk drives, CD-ROMs, and tape drives for PCI-based machines. To support a new SCSI device, the Windows 95/98 architectures require that a class driver for that type device is present (usually supplied by Microsoft, or possibly by the peripheral manufacturer). No changes to SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD are required. Windows 95 and Windows 98 only support these SDMS miniport drivers.

A Windows application passes SCSI commands directly to the SCSI devices by using the SCSI pass-through facility (refer to Microsoft Windows 95 or Windows 98 documentation for details). This facility allows applications to directly control and access SCSI devices by filling in a data structure and calling into the port driver.

The SYMC8XX.MPDandSYM_HI.MPDdrivers support Ultra SCSI protocol, providing twice the raw data transfer rate of Fast SCSI for disk drives and LSI Logic host adapters that support Ultra SCSI. These drivers also support Ultra2 SCSI protocol, providing quadruple the raw data transfer rate of Fast SCSI. The SYM_U3.MPD driver supports Ultra160 SCSI protocol providing 80 Mbytes/s of data transfer and up to 160 Mbytes/s data transfer for double transition.

Caution: Ultra SCSI requires a more stringent SCSI bus cabling setup than Fast SCSI. Ultra2 SCSI and Ultra160 SCSI require Low Voltage Differential (LVD) termination.

Installing Your SYMC8XX.MPD/SYM_HI.MPD/SYM_U3.MPD Driver

You can install the SDMS drivers from the SDMS Software Device Drivers and Utilities CD-ROM, or you can make a driver diskette if your system does not have access to a CD-ROM.

If you are not using Internet Explorer, copy the files from the appropriate location to the root directory of a clean diskette, and use this SDMS driver diskette during installation.

For the SYMC8XX.MPD driver, locate the files in this directory:

{CD-ROM Drive Letter}:DRIVERS8XX-1010WIN9X8XX9X

SYMC8XX.MPD

SYMC8XX.INF

For the SYM_HI.MPD driver, locate the files in this directory:

{CD-ROM Drive Letter}:DRIVERS8XX-1010WIN9XWIN9XHI

SYM_HI.MPD

SYM_HI.INF

For the SYM_U3.MPD driver, locate the files in this directory:

{CD-ROM Drive Letter}:DRIVERS8XX-1010WIN9X9XULTRA3

SYM_U3.MPD

SYM_U3.INF

or

If you are using Internet Explorer, use one of the following methods:

Build a driver diskette containing all three Windows 95/98 drivers directly from Windows 95/98.

or

Perform the Guided Installation Using this CD-ROM.

This procedure installs theSYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver onto a Windows 95/98 system. Follow these instructions when initially upgrading to Windows 95 or Windows 98. Windows automatically adds the driver(s) to the registry and copies the driver(s) to the appropriate directories.

Note: A driver bundled in Windows 95 and Windows 98 supports some LSI Logic PCI to SCSI host adapters. For these adapters, the bundled driver is automatically installed during Windows Setup. To change to the newer SYMC8XX.MPD, SYM_HI.MPD, and/or SYM_U3.MPD drivers, follow the instructions under Existing System Installation after the Windows 95 or Windows 98 installation has completed.

  1. Start the Windows 95 or Windows 98 Setup according to the Microsoft instructions.
  1. Setup enters the hardware detection phase after a system reboot. The Setting up Hardware message box appears.

If the message Symbios PCI SCSI Host Adapter appears, then the host adapter supports the bundled driver, and it installs automatically. After the Windows installation has completed, you can install the SYMC8XX.MPD, SYM_HI.MPD, and/or SYM_U3.MPD drivers according to the Existing System Installation instructions.

  1. If the bundled driver does not support the host adapter, Setup displays a New Hardware Found - PCI SCSI Bus Controller dialog box. Select Driver from disk provided by hardware manufacturer and click OK.

    Note: If ASPI8XX.SYS (the SDMS 4.0 DOS ASPI driver) is loaded when beginning the Windows installation, no messages about PCI SCSI Bus Controllers will appear. The installation completes, but real-mode disk drivers are used. See Verifying Correct Driver Installation. To install the SYMC8XX.MPD,SYM_HI.MPD, or SYM_U3.MPD drivers, (which disable loading of the ASPI8XX.SYS driver under Windows 95 and Windows 98) see Existing System Using ASPI8XX.SYS DOS ASPI Driver.

  1. Insert the SDMS driver diskette into drive A: (or B:) (the one prepared in 'Preparing an SDMS Driver Diskette') and click OK. If using drive B:, you must select it from the pick list.
Windows automatically copies the appropriate driver files and rebuilds its driver database.

A System Settings Change dialog box appears.

  1. Remove the diskette from the drive and click Yes to restart the computer.

At this point, Windows Setup has completed, and the new driver is operational. To verify this, see the section Verifying Correct Driver Installation.

Note: These instructions for Windows 98 are similar to the installation instructions for Windows Me. Although some differences exist with a new system installation for Windows Me, an experienced user should be able to follow the prompts as they appear. LSI Logic recommends that you also refer to the Microsoft documentation that is included with the Windows Me operating system.

This procedure installs the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver onto an existing Windows 95/98 system. These instructions indicate where specific information applies to Windows 95 or Windows 98. Unless noted, the instructions apply to both operating systems. Please review the steps below before beginning the installation.

  1. Boot Windows 95 or Windows 98.
  1. Click Start. Select Settings-->Control Panel.
  1. Double click on the System icon.
  1. Click on the Device Manager tab.

    Note: If the SCSI controller's entry, or the PCI LSI Logic C8XX SCSI Host Adapter entry do not exist, the system is probably using the ASPI8XX.SYS DOS ASPI driver. See the Existing System Using ASPI8XX.SYS DOS ASPI Driver section.

  1. Either double click on the SCSI controller's entry, or click once on the plus sign to the left of it.
  1. Select the PCI LSI Logic C8XX SCSI Host Adapter entry. Click on the Properties button.
  1. Click on the Driver button. In Windows 95, the version of the active driver should display in the File Details section. In Windows 98, press the Driver File Details button to get this information to appear.

    Note: In certain versions of Windows 95, the version of the active driver is displayed as not available due to an operating system issue. This problem has been corrected in later versions of Windows 95. To verify the version of the driver, click on the Properties field of the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD file under the Version tab.
    The     MPD driver is generally found in the WINDOWSSYSTEMIOSUBSYS directory.

  1. Click on the Change Driver... button.

For Windows 95

  1. Even though you may have previously installed the SYMC8XX.MPD, SYM_HI.MPD or SYM_U3.MPD drivers, proceed to click on the Have Disk... button to install a newer version.
  1. Insert the SDMS driver diskette in drive A: (or B:) (the one prepared in 'Preparing an SDMS Driver Diskette') and click OK. If using drive B:, you must select it from the pick list.
The Select Device dialog box should display Symbios 8xx PCI SCSI Host Adapter, where 8XX matches the installed adapter.
  1. Click OK.
The Driver tab is updated to display the new driver files.
  1. Click OK to install these driver files. (Do not click the Change Driver... button.) The driver files are copied, and a new driver database is built.

For Windows 98

The Update Device Driver Wizard starts and provides several windows with choices. Follow the steps below to correctly install the device driver for Windows 98.

  1. After the Intro window appears, click on the NEXT button.
The Wizard provides a choice between having the Wizard search for a better driver than the one in use or displays a list of drivers from a specific location.
  1. Choose search... and click on the NEXT button.
The next window allows you to specify which device(s) will be searched, such as a diskette, CD-ROM, or specify a precise path.
  1. Select Floppy disk drive and click on the NEXT button.
The next window queries the user about utilizing the currently installed driver.
  1. Select Install one of the other drivers and click on the View List button.
Next, a list of drivers appears from the specified search devices and the currently installed driver.
  1. Highlight the driver of choice and click OK.
The previous window (in step 12) appears with the selected driver displayed as the driver to be installed.
  1. Click on the NEXT button.
The next window will display the chosen driver along with reference to the designated path to install it in.
  1. Click on the NEXT button.

The Wizard summary window appears.

  1. Click on the Finish button.

When the installation has completed, the System Settings Change dialog box appears.

  1. Remove the diskette from the drive and click Yes to restart the computer.

At this point, the new driver is operational. To verify this, see the section Verifying Correct Driver Installation.

Note: These instructions for Windows 98 are similar to the installation instructions for upgrading your SDMS drivers onto an existing Windows Me system. Although some differences exist when upgrading your drivers on Windows Me, an experienced user should be able to follow the prompts as they appear. LSI Logic recommends that you also refer to the Microsoft documentation that is included with the Windows Me operating system.

This procedure installs the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD drivers onto an existing Windows 95 or Windows 98 system, which is using the ASPI8XX.SYS DOS ASPI driver. You can check this by using the Verifying Correct Driver Installation instructions below.

Download Sunix Usb Devices Driver Win 7

Note: These SDMS miniport drivers also support Windows Me. This procedure is similar to the installation procedure for an existing Windows Me system that is also using the ASPI8XX.SYS DOS ASPI driver.

  1. Boot Windows.
  1. Click Start. Select Settings-->Control Panel.
  1. Double click on the System icon.
  1. Click on the Device Manager tab.
  1. Either double click on the Other entry, or click once on the plus sign to the left of it.
  1. Select the PCI SCSI Bus Controller entry. Click on the Properties button.
  1. Click on the Driver button. A message should state that no drivers are installed for this device.
  1. Click on the Change Driver... button.
  1. Select SCSI Controllers in the Select Hardware Type dialog box.
  1. Click on the Have Disk button in the Select Device dialog box.
  1. Insert the SDMS driver diskette in drive A: (or B:) (the one prepared in 'Preparing an SDMS Driver Diskette') and click OK. If using drive B:, you must select it from the pick list.
The Select Device dialog box should display Symbios 8XX PCI SCSI Host Adapter, where 8XX matches the installed adapter.
  1. Click OK.
The Driver tab is updated to display the new driver files.
  1. Click OK to install these driver files. (Do not click on the Change Driver... button.) The driver files are copied, and a new driver database is built.
The System Settings Change dialog box appears.
  1. Ignore the message saying to turn off your computer and change hardware settings.
  1. Remove the diskette from the drive and click Yes to shut down the computer.
  1. Press Ctrl-Alt-Del or the system reset button to restart the system.

At this point, the new driver is operational. To verify this, see the section 'Verifying Correct Driver Installation'.

After installing/updating your system with the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD drivers, verify the proper operation of the driver(s).

  1. Check that all devices on the SCSI bus are available by using My Computer. Double click on the My Computer icon. Check that all logical SCSI hard drives and CD-ROM drives are shown.
  1. Click on the Start button. Select Settings-->Control Panel.
  1. Double click on the System icon.
  1. Click on the Device Manager tab. Check that no host adapter appears with a yellow or red symbol under the SCSI controller's entry. If there is, continue with the steps below to help determine the problem.
  1. Either double click on the SCSI controller's entry or click once on the plus sign to the left of it. One entry for each host adapter installed in the system is displayed. Select an entry, then click on the Properties button.

The Device Status message should read:This device is working properly.

If any other messages appear, continue with the steps below to get more information on the problem.

  1. Click on the Driver tab. For Windows 98, select Driver File Details. Two entries should appear: one for the INF file and one for the MPD file. The INF file does not contain embedded version information, so the File Details are all Not Available. Select the MPD file. The file version of the driver appears.
  1. Click Cancel to leave the Host Adapter Properties dialog box. Click on the Performance tab. A list of performance attributes appears. Below the list, you should see the message: Your system is configured for optimal performance.

If any other messages appear, select each message and click on the Details button. This provides more information on why the system is not performing optimally and methods to correct the problem.

If no problems are encountered in the above steps, the new driver is operating properly. Otherwise, consult Troubleshooting for additional information.

Settings in the adapter NVRAM control Ultra SCSI support. Use the SCSI BIOS Configuration Utility to view or change these settings. During system boot, after the LSI Logic PCI BIOS banner displays, the message Press Ctrl-C to start Configuration Utility appears for a few seconds. To start this utility, follow these steps:

  1. Press Ctrl-C to start this utility.
  1. Select one of the adapters displayed, then Device Selections. This shows the Sync Rate for each device and the selected adapter.
  1. To set a device to Ultra, the speed should be set to 20 Mbytes/s (for width of 8) or 40 Mbytes/s (for width of 16). To disable Ultra, the speed should be no higher than 10 Mbytes/s (for width of 8) or 20 Mbytes/s (for width of 16). If the speed of the adapter itself is changed, the speed for all devices will be set no higher than the adapter speed.
Sunix

When you install the SYMC8XX.MPD, SYM_HI.MPD, and/or SYM_U3.MPD drivers, support for auto request sense is enabled. Auto request sense is a feature of the adapter where certain device information is obtained automatically without system control, thereby increasing overall performance. However, some third-party peripheral drivers do not support the use of auto request sense, resulting in perceived device failures. To allow these devices to operate properly, use the Device Manager on a per adapter basis to disable the auto request sense feature.

Use this procedure for disabling auto request sense support:

  1. Click on the Start button. Select Settings-->Control Panel.
  1. Double click on the System icon.
  1. Click on the Device Manager tab.
  1. Either double click on the SCSI controller's entry or click once on the plus sign to the left of it. One entry for each host adapter installed in the system is displayed.
  1. Select the adapter desired, and then click on the Properties button. Click on the Settings tab.
  1. Type in the Adapter settings entry:

DisableAutoReqSense=1;

If there is already an entry displayed, type at the end of the existing entry. Be sure to include the semicolon at the end.

  1. Click OK to exit the Settings tab.
  1. Click OK again.

If the entry was changed, the System Settings Change dialog box appears.

  1. Click Yes to restart the computer.

After the system reboots, auto request sense is disabled for the selected adapter. To re-enable auto request sense, delete the entry that was made above. If other entries exist, be sure to leave them intact.

SCAM (SCSI Configured AutoMatically) is a protocol that allows SCAM-compliant peripherals to assign their SCSI IDs dynamically at boot time, eliminating the need for the user to check and set unique SCSI IDs. This feature is disabled by default in the LSI Logic PCI BIOS and the SYMC8XX.MPD, SYM_HI.MPD, and SYM_U3.MPD drivers. Some legacy (non-SCAM) peripherals have problems with the SCAM protocol, resulting in the device either not being seen by the operating system or not working correctly. However, if usage of the SCAM protocol is desired, there are two methods for enabling SCAM: Method 1 and Method 2.

Use this Method 1 when the adapter has NVRAM.During system boot, after the LSI Logic PCI BIOS banner displays, the message Press Ctrl-C to start Configuration Utility appears for a few seconds. To start this utility, follow these steps:

  1. Press Ctrl-C to start this utility.
  1. Select the desired adapter, then Adapter Setup.
  1. Highlight S-SCAM Support and press Enter on the Adapter Setup menu.
  1. Use the up/down arrows to select the ON setting, and press Enter.
  1. Exit from the menus and save the settings.

This turns SCAM on for both the PCI BIOS and the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver (whichever is controlling the selected adapter). To disable SCAM, repeat the above procedure to change the setting to OFF.

Use this method for adapters that do not have NVRAM to enable SCAM within Windows 95 or Windows 98 by following these steps:

  1. Click on the Start button. Select Settings-->Control Panel.
Sunix
  1. Double click on the System icon.
Usb
  1. Click on the Device Manager tab.

Download Sunix Usb Devices Drivers

  1. Either double click on the SCSI controller's entry or click once on the plus sign to the left of it. One entry for each host adapter installed in the system appears.
  1. Select the adapter desired, and then click on the Properties button.
  1. Click on the Settings tab.
  1. Type in the Adapter settings entry:

do_SCAM=1;

If an entry already appears there, type the above at the end of the existing entry. Be sure to include the semicolon.
  1. Click OK to exit the Settings tab.
  1. Click OK again. If the entry was changed, the System Settings Change dialog box appears.
  1. Click Yes to restart the computer.

After the system reboots, SCAM is enabled for the selected adapter. To disable SCAM, delete the entry that was made above. If other entries exist, be sure to leave them intact.

When the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver is installed, support for domain validation is enabled. Domain validation is a feature of the adapter where the data transfer speed between the adapter and each target is tested at system boot. If the test fails, the data transfer speed is reduced and the test repeated until a supported data transfer speed is found.

However, some older SCSI devices do not properly support the standard SCSI commands used during this testing, resulting in the system not booting or a device being not available. Therefore, to allow these devices to operate properly, the domain validation
feature can be disabled using the Device Manager for all adapters controlled by the respective driver, or in the SCSI BIOS Configuration Utility on a per device basis.
Use this procedure for disabling domain validation support for all adapters controlled by the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver:

  1. Click on the Start button. Select Settings-->Control Panel.

  2. Double click on the System icon.

  3. Click on the Device Manager tab.

  4. Either double click on the SCSI controller's entry or click once on the
    plus sign to the left of it. One entry for each host adapter installed in
    the system appears.

  5. Select any adapter controlled by the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver, then click on the Properties button.

  6. Click on the Settings tab.

  7. Type in the Adapter settings entry:

DisableDomainValidation=1;

If there is already an entry displayed, type the above at the end of the existing entry. Be sure to include the semicolon.

  1. Click OK to exit from the Settings tab.

  2. Click OK again.

If the entry was changed, the System Settings Change dialog box appears.

  1. Click Yes to restart the computer.

After the system reboots, domain validation is disabled for adapters controlled by the .MPD drivers. To re-enable domain validation, delete the entry that was made above. If other entries exist, be sure to leave them intact.

Use this procedure for disabling domain validation support for a selected device, by using the PCI SCSI BIOS Configuration Utility.During system boot, after the LSI Logic PCI BIOS banner, the message Press Ctrl-C to start Configuration Utility appears for a few seconds. At this point, follow these steps:

  1. Press Ctrl-C to start this utility.

  2. Select the desired adapter and press Enter, then choose DeviceSelections, and press Enter. This shows the Sync Rate and Width for each device and the selected adapter.

  3. Set the Sync Rate to 0 and Width to 0 for the specified device to disable domain validation for a selected device. This sets the device to asynchronous/narrow transfers and domain validation functions are not issued to this device.

  4. Exit from the SCSI BIOS Configuration Utility and save changes.

Some potential problems and their suggested solutions are:

Problem: During installation, no SCSI devices are found.

Solution:

Download Sunix USB Devices Driver

  1. Ensure that all devices are powered on and terminated correctly.

  2. Check that no devices have duplicate SCSI IDs.

  3. Make sure INT A is assigned for the PCI slot(s) where your SCSI host adapter(s) is installed.

Problem: Problems with Ultra SCSI devices using Ultra SCSI protocol.

Solution:

If the system is configured with an LSI Logic host adapter that supports Ultra SCSI, an Ultra SCSI device is on the SCSI bus, and Ultra SCSI support by the SYMC8XX.MPD or SYM_HI.MPD driver is enabled, intermittent problems and possible system crashes can occur. It may be that the SCSI bus cable and terminators do not conform to the Ultra SCSI specification.

  1. If the system is bootable, disable Ultra SCSI support using the procedure described above.

  2. If the system is not bootable to Windows, press F8 when the message Starting Windows 95 appears. At the menu, select Safe Mode. For Windows 98 after the BIOS banner appears hold the Ctrl key until the menu appears to select Safe Mode. Once the system is booted, disable Ultra SCSI support using the procedure described above.

  3. If the system operates properly without Ultra SCSI enabled, it is highly likely that the SCSI bus cable and terminators are not configured correctly for Ultra SCSI. See the LSI Logic host adapter hardware manual for information on Ultra SCSI cabling requirements.

  4. Verify that the devices appear with the proper value for speed in the SDMS SCSI BIOS banner at boot time. Please refer to the PCI Storage Device Management System SDMS 4.0 User's Guide for additional details.

Problem: Scanners not operating correctly or cannot be found by the system.

Solution:

If a scanner is not operating properly (either the scanner is not found or a SCSI interface error occurs during scanning), it is possible that the third-party scanner drivers do not support the auto request sense feature of LSI Logic host adapters. Disable the auto request sense feature as described above and try the scanner operation again.

Problem: The system hangs at boot, has a long boot time, or SCSI device is not available.

Some older SCSI devices do not tolerate domain validation operations. At system boot time, domain validation is performed to test the data integrity of the SCSI bus between the host adapter and each target device. With some older SCSI devices, these operations can cause the device to stop responding to SCSI commands.

Solution:

Disable domain validation support as described in Disabling Domain Validation Support above, either for a specific problem SCSI target or all adapters controlled by the SYMC8XX.MPD, SYM_HI.MPD, or SYM_U3.MPD driver.

If you install multiple LSI Logic PCI to SCSI host adapters in your system, special actions are sometimes required to install or change drivers. This is due to the fact that the bundled driver supports some LSI Logic host adapters, and also that one SDMS driver can support multiple LSI Logic host adapters installed in the system.

With multiple LSI Logic adapters, it is possible to have a situation where one adapter is assigned to one driver, and another is assigned to a different version of the same driver. This can cause conflicts that may cause the system to switch to real-mode drivers, affecting performance and access to CD-ROM or tape drives.

Two methods are listed below for ensuring that all LSI Logic host adapters are controlled by only one version of the appropriate driver (when installing additional boards or updating drivers).

  1. Use the Device Manager and change the driver for a particular host adapter to the desired driver.

  2. Click No when asked to reboot the system for the new settings to take effect.

  3. Change drivers for all LSI Logic host adapters in the system supported by that same driver to the new driver, and reply No to rebooting until the final adapter is changed.

Note: If booting from a SCSI device, ensure that the adapter controlling this device is the last one changed.

  1. Determine which driver file is active for all adapters through the Properties tab in Device Manager.

  2. Go to the WINDOWSSYSTEMIOSUBSYS directory and rename the driver file to an extension other than MPD.

  3. Reboot the system.

While booting, the system may ask to load the bundled driver file from the Windows 95/98 disk.

  1. Click OK.

  2. Click Skip File when the system says it cannot find the file.

    Do this for all adapter messages while booting.

  3. Use the Device Manager to change the driver for each adapter to the desired driver after the system is booted. Do not reply Yes to reboot the system until the final adapter has been changed.

WINDOWS IS A REGISTERED TRADEMARK OF MICROSOFT CORPORATION