How To Use Driver Pack Autorun

Printable version
  1. Driver Pack Autorun Download
  2. How To Run Autoruns
  3. How To Autorun Dvd

How to Create an AutoRun File for a USB Flash Drive USB AutoRun is the term used when specific, predetermined digital content is automatically launched from your flash drive as soon as it is plugged into a memory port. I am using Windows XP Service Pack 3 and would like to setup a autorun om my computer. The thing is, I have a mobile harddrive, which I want to copy to my compyter, every time it is connected.

How to start autorun manually

Red Hat Enterprise Linux 7.5 Supplement Bundle for Service Pack for ProLiant

By downloading, you agree to the terms and conditions of the Hewlett Packard Enterprise Software License Agreement.
Note: Some software requires a valid warranty, current Hewlett Packard Enterprise support contract, or a license fee.

Type:Application - System Management
Version:2018.03.0(22 May 2018)
Operating System(s): Red Hat Enterprise Linux 7 Server
Multi-part download
File name:manifest.zip (236 KB)
File name:supspp-2018.03.rhel7.5.en.tar.gz (93 MB)
This supplement contains updated drivers to support Red Hat Enterprise Linux 7.5 Supplement for Service Pack for ProLiant. Before beginning installation, the supplement should be copied directly to a separate folder on a test platform.

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.

Prerequisites:

IMPORTANT: Before deploying software updates on a target system, be sure that a recent backup of the target system is available in the event the deployment procedure fails.

To successfully deploy HP SUM on remote target systems based on a Linux operating system, the following must be available:

  • libcrypt.so
  • libcrypt.so.1
  • /usr/lib/libqlsdm.so
  • /usr/lib64/libqlsdm-x86_64.so
  • /lib/cim/libqlsdm.so
  • /usr/lib/libemsdm.so
  • /usr/lib64/libemsdm.so
  • /lib/cim/libemsdm.so
  • /usr/lib/bfahbaapi.so
  • /usr/lib64/bfahbaapi.so
  • /lib/cim/bfahbaapi.so
  • linux-vdso.so.1
  • /lib64/libcrypt.so.1
  • /lib64/libpthread.so.0
  • /lib64/libz.so.1
  • /lib64/libdl.so.2
  • /lib64/librt.so.1
  • /usr/lib64/libstdc++.so.6
  • /lib64/libm.so.6
  • /lib64/libgcc_s.so.1
  • /lib64/libc.so.6
  • /lib64/ld-linux-x86-64.so.2

To ensure the integrity of your download, HPE recommends verifying your results with the following SHA-256 Checksum values:

8ced9ca682571f4e8a3545dc7cf55e871048006fbfac92bbc4d777c8bb943f91supspp-2018.03.rhel7.5.en.tar.gz
7c3cf35df288a709f58d8b4044d093c7cb4c89d6aa65d9de09d97a08b1812cb6manifest.zip

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

Installation:

Installation of the Supplement for Service Pack for ProLiant Using Autorun: supplements may be installed via autorun if autorun is configured on the target Linux server.

Several autorun utilities are available for download from various Internet sites. These distributions will typically mount the CD-ROM on /media/cdrom.

For the purposes of these instructions, the CD-ROM is assumed to have been mounted on /mnt/mnt. The actual mount point should replace /mnt/mnt when executing these instructions.

Manual Installation of the Supplement for Service Pack for ProLiant :

  • For the remainder of this discussion, the CD mount directory will be considered to be /mnt/mnt. The actual mount point should replace /mnt/mnt when executing these instructions. If the CD-ROM mount point is not defined in /etc/fstab, a complete mount command will be required.
  • Download the latest supplemental as applicable. It will be in zipped format.
  • Login on the console as root
  • Copy the supplement on your local server. The supplement will be in zipped format.
  • Unzip/ Untar the supplement.
  • Go to the supplement folder either through GUI and run hpsum file or in command prompt give ./hpsum. Make sure to give read write permission to this file.

Or

  • If the Operating is of x64bit architecture, go to x64bit folder in supplement, and run ./hpsum_bin_x64. This will launch HPSUM in the browser automatically.
  • If the Operating system is of x86bit architecture, go to x86 folder in supplement, and run ./hpsum_bin_x86. This will launch HPSUM in the browser automatically.
  • Note: Make sure to have the supported browser installed on your system.

The installer will open an interactive session which will allow you to install the Linux Service Pack for ProLiant supplement.

NOTE: Be sure to include the version of the compatibility libraries that is appropriate for your architecture. In some cases, there are separate 32-bit and 64-bit compatibility libraries for a given distribution.

For a current list of supported Linux distributions and versions (and their associated errata kernels), see the operating system support matrixes . The supplements are designed for use after you install the operating system so that you can update drivers, install utilities (such as Health and iLO drivers), and install agents (Server, NIC, and Storage).

End User License Agreements:
HPE Software License Agreement v1
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

Important:

When using SUM to create custom iso with 2018.03.0 SPP and this RHEL7.5 supplement bundle, installation of the smartpqi driver may display the following error during the rewrite of smartpqi firmware component:

Deploy error. Deploy skipped as one of the installable has failed dependency and OmitHost is set.

If using SUM, please add the RHEL7.5 as an additional baseline as a work around for this issue. Another alternative is to use the ISO for 2018.03.0 SPP and RHEL 7.5 supplement bundle from the Custom Download site.

When using SUM to create custom iso with 2018.03.0 SPP and this RHEL7.5 supplement bundle, installation of the smartpqi driver may display the following error during the rewrite of smartpqi firmware component:

Deploy error. Deploy skipped as one of the installable has failed dependency and OmitHost is set.

If using SUM, please add the RHEL7.5 as an additional baseline as a work around for this issue. Another alternative is to use the ISO for 2018.03.0 SPP and RHEL 7.5 supplement bundle from the Custom Download site.

Version:2018.11.0 (17 Dec 2018)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

Support for Red Hat Enterprise Linux 7.6.

The release notes for this version of the supplement are available at: https://www.hpe.com/servers/spp/download Click on the documentation tab.


Version:2018.03.0 (22 May 2018)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.


Version:2016.10.0 (8 Dec 2016)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.


Type:Application - System Management
Version:2018.03.0(22 May 2018)
Operating System(s):
Red Hat Enterprise Linux 7 Server

Description

This supplement contains updated drivers to support Red Hat Enterprise Linux 7.5 Supplement for Service Pack for ProLiant. Before beginning installation, the supplement should be copied directly to a separate folder on a test platform.

Enhancements

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.

Installation Instructions

Prerequisites:

IMPORTANT: Before deploying software updates on a target system, be sure that a recent backup of the target system is available in the event the deployment procedure fails.

To successfully deploy HP SUM on remote target systems based on a Linux operating system, the following must be available:

  • libcrypt.so
  • libcrypt.so.1
  • /usr/lib/libqlsdm.so
  • /usr/lib64/libqlsdm-x86_64.so
  • /lib/cim/libqlsdm.so
  • /usr/lib/libemsdm.so
  • /usr/lib64/libemsdm.so
  • /lib/cim/libemsdm.so
  • /usr/lib/bfahbaapi.so
  • /usr/lib64/bfahbaapi.so
  • /lib/cim/bfahbaapi.so
  • linux-vdso.so.1
  • /lib64/libcrypt.so.1
  • /lib64/libpthread.so.0
  • /lib64/libz.so.1
  • /lib64/libdl.so.2
  • /lib64/librt.so.1
  • /usr/lib64/libstdc++.so.6
  • /lib64/libm.so.6
  • /lib64/libgcc_s.so.1
  • /lib64/libc.so.6
  • /lib64/ld-linux-x86-64.so.2

To ensure the integrity of your download, HPE recommends verifying your results with the following SHA-256 Checksum values:

8ced9ca682571f4e8a3545dc7cf55e871048006fbfac92bbc4d777c8bb943f91supspp-2018.03.rhel7.5.en.tar.gz
7c3cf35df288a709f58d8b4044d093c7cb4c89d6aa65d9de09d97a08b1812cb6manifest.zip

Reboot Requirement:
Reboot is not required after installation for updates to take effect and hardware stability to be maintained.

Installation:

Installation of the Supplement for Service Pack for ProLiant Using Autorun: supplements may be installed via autorun if autorun is configured on the target Linux server.

Several autorun utilities are available for download from various Internet sites. These distributions will typically mount the CD-ROM on /media/cdrom.

For the purposes of these instructions, the CD-ROM is assumed to have been mounted on /mnt/mnt. The actual mount point should replace /mnt/mnt when executing these instructions.

Manual Installation of the Supplement for Service Pack for ProLiant :

  • For the remainder of this discussion, the CD mount directory will be considered to be /mnt/mnt. The actual mount point should replace /mnt/mnt when executing these instructions. If the CD-ROM mount point is not defined in /etc/fstab, a complete mount command will be required.
  • Download the latest supplemental as applicable. It will be in zipped format.
  • Login on the console as root
  • Copy the supplement on your local server. The supplement will be in zipped format.
  • Unzip/ Untar the supplement.
  • Go to the supplement folder either through GUI and run hpsum file or in command prompt give ./hpsum. Make sure to give read write permission to this file.

Or

  • If the Operating is of x64bit architecture, go to x64bit folder in supplement, and run ./hpsum_bin_x64. This will launch HPSUM in the browser automatically.
  • If the Operating system is of x86bit architecture, go to x86 folder in supplement, and run ./hpsum_bin_x86. This will launch HPSUM in the browser automatically.
  • Note: Make sure to have the supported browser installed on your system.

The installer will open an interactive session which will allow you to install the Linux Service Pack for ProLiant supplement.

NOTE: Be sure to include the version of the compatibility libraries that is appropriate for your architecture. In some cases, there are separate 32-bit and 64-bit compatibility libraries for a given distribution.

For a current list of supported Linux distributions and versions (and their associated errata kernels), see the operating system support matrixes . The supplements are designed for use after you install the operating system so that you can update drivers, install utilities (such as Health and iLO drivers), and install agents (Server, NIC, and Storage).

Release Notes

End User License Agreements:
HPE Software License Agreement v1
Hewlett-Packard End User License Agreement

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

Important:

When using SUM to create custom iso with 2018.03.0 SPP and this RHEL7.5 supplement bundle, installation of the smartpqi driver may display the following error during the rewrite of smartpqi firmware component:

Deploy error. Deploy skipped as one of the installable has failed dependency and OmitHost is set.

If using SUM, please add the RHEL7.5 as an additional baseline as a work around for this issue. Another alternative is to use the ISO for 2018.03.0 SPP and RHEL 7.5 supplement bundle from the Custom Download site.

Important

When using SUM to create custom iso with 2018.03.0 SPP and this RHEL7.5 supplement bundle, installation of the smartpqi driver may display the following error during the rewrite of smartpqi firmware component:

Deploy error. Deploy skipped as one of the installable has failed dependency and OmitHost is set.

If using SUM, please add the RHEL7.5 as an additional baseline as a work around for this issue. Another alternative is to use the ISO for 2018.03.0 SPP and RHEL 7.5 supplement bundle from the Custom Download site.

Revision History

Version:2018.11.0 (17 Dec 2018)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

Support for Red Hat Enterprise Linux 7.6.

The release notes for this version of the supplement are available at: https://www.hpe.com/servers/spp/download Click on the documentation tab.


Version:2018.03.0 (22 May 2018)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.


Version:2016.10.0 (8 Dec 2016)

Upgrade Requirement:
Optional - Users should update to this version if their system is affected by one of the documented fixes or if there is a desire to utilize any of the enhanced functionality provided by this version.

The release notes for this version of the supplement are available at: http://www.hpe.com/servers/spp/download#tab=TAB4.


Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

-->

When the Shell detects the insertion of new media or the attachment of a hot-plug device, the contents of the device or media are determined. AutoPlay, depending on its current settings, does one of the following.

  • Plays the content automatically.
  • Displays a dialog box prompting the user to choose a default handler for a single content type.
  • Presents, in the case of mixed content, a list of available handler applications to launch. The chosen handler then automatically plays its associated content type.
  • Displays a standard folder view of the files.
  • Does nothing if, earlier, the user had chosen Take no action for that content type as well as specified Always do the selected action.

If the contents do not meet the criteria for AutoPlay, the event is then passed to Windows Image Acquisition (WIA).

The following topics discuss the setup and use of AutoPlay.

  • Preparing Hardware and Software for Use with AutoPlay
  • How AutoPlay Searches Media
  • Defining Single and Mixed Content Types
  • Sample Scenarios
    • AutoPlay for Storage Devices with Picture Media
    • AutoPlay for Music File Playback Devices and Storage Devices Containing Music Media
    • AutoPlay for Video Playback on First Presentation
  • Assigning Default Handler Applications
  • Handling Media Containing Mixed Content Types
  • AutoPlay User Interfaces
    • Single Content Type Dialog Box
    • Mixed Media Dialog Box
    • Property Page

Preparing Hardware and Software for Use with AutoPlay

Several pieces of information need to appear in the registry for AutoPlay to function. These pieces of information interact and reference each other to form the full AutoPlay environment. This document presents the setup of each of these pieces of information as an individual stand-alone procedure.

See the following topics for additional instructions.

How AutoPlay Searches Media

How to run autorun file

AutoPlay searches for media four directory levels below the root directory to find known file types. It uses the PerceivedType value associated with a file name extension in the registry to determine the file category, whether it is an image, an audio file, or a video file. With this information, AutoPlay launches the appropriate handler for that device and file type. For more information, see Perceived Types and Application Registration.

Defining Single and Mixed Content Types

AutoPlay defines three main content categories.

  • Pictures
  • Music
  • Video

A medium is considered to contain a single content type if all of the files on the medium fall into only one of these three categories. Note that this does not mean that the files must be of the same file type; .jpg, .gif, and .bmp are different file types, but one content type (pictures).

If supported content types are present on the medium, but no single content type can account for 100 percent of the total, then the medium is considered to contain mixed content type and is handled accordingly. For more information, see Handling Media Containing Mixed Content Types.

Sample Scenarios

The following scenarios provide a basic understanding of what to expect from AutoPlay.

AutoPlay for Storage Devices with Picture Media

How to autorun a file
  1. The user attaches a USB SanDisk CompactFlash reader device that already has media inserted containing 100 percent picture content type in the form of .jpg files.
  2. Notification displays Found New Hardware - SanDisk ImageMate.
  3. AutoPlay launches the appropriate image application.

Similarly, when the user inserts that same CompactFlash media into the reader when the reader is already attached to the system, the media insert event also causes AutoPlay to launch the image slide show application. The user has the option of going to the Properties page of the SanDisk media device to change the default to another registered AutoPlay application, such as the Scanner and Camera Wizard or Picture It!.

AutoPlay for Music File Playback Devices and Storage Devices Containing Music Media

  1. The user attaches a USB Diamond Rio MP3 Player.
  2. Notification displays Found New Hardware - Diamond Rio MP3 Player.
  3. AutoPlay plays the files using its registered default handler—for instance, Windows Media Player.

Similarly, if the user inserts any media containing .mp3 files (for example, CompactFlash, SmartMedia, Memory Stick, or CD-ROM) that account for 100 percent of the total supported content into a storage device, the media insert event would also cause AutoPlay to play the files using the Windows Media Player. The user can access the property sheet of the storage device and change the default action to another registered AutoPlay application, such as WinAmp or Real Player.

AutoPlay for Video Playback on First Presentation

  1. The user plugs in a 1394 digital video camera for the first time.
  2. The user is presented with a simple dialog box that asks what application to run. The choices are to run one of the registered AutoPlay applications or to open a folder to view files. The user may set the selected behavior to be saved as the default action for later digital video camera hot-plug events.

Assigning Default Handler Applications

A fresh installation of Windows finds AutoPlay with a set of registered handler applications. Applications registered by default during a Windows installation are as follows.

Media TypeApplications
Pictures
  • Slide Show (default)
  • Camera and Scanner Wizard
  • Printing Wizard
  • Open folder
Music
  • Windows Media Player (default)
  • Open folder
Video
  • Windows Media Player (default)
  • Open folder

In the case of non-supported types, users are asked to assign the default setting for the AutoPlay action associated with each storage device on its first introduction to the system. At that time, the user is prompted to choose an action from a provided list of registered applications or to display a folder view listing the media content. The user also has the option of choosing to be prompted each time the media type is detected rather than saving any particular application as a default.

Driver Pack Autorun Download

Note Device manufacturers have the option of registering and assigning default applications to be used with their particular products. In these cases, the dialog box offering a choice to the user is not displayed.

To be offered as a handler option by AutoPlay, newly installed applications must register themselves in the registry. For details, see Preparing Hardware and Software for Use with AutoPlay.

Users can always change the default AutoPlay handler for any storage device or content type. The AutoPlay property page is accessible for change in the property sheet of the storage device in My Computer.

For examples of user prompts and property pages, see AutoPlay User Interfaces.

Handling Media Containing Mixed Content Types

When AutoPlay is presented with a mixed content medium, it requires user input before it can take action. In this case, the user is presented with a dialog box containing a filtered list of all appropriate registered applications available for the content types present on the media. The user can choose one of these applications to AutoPlay that particular content type, while the rest remain untouched. As the composition of mixed content media varies with each individual disc, there is no option to save this choice as a default.

For examples of user prompts, see AutoPlay User Interfaces.

AutoPlay User Interfaces

There are three possible user interfaces.

  • A dialog box that prompts the user to enter an action for a single content type
  • A dialog box that prompts the user to enter an action for mixed content types
  • A property page

Single Content Type Dialog Box

A dialog box similar to the following is displayed when any supported media not yet assigned a default AutoPlay action is presented to the system.

Users can do one of the following.

How To Run Autoruns

  • Choose an action from the list of registered applications.
  • List the files on the medium in a normal folder view.
  • Take no action.

A user can also save a choice as the default action for this medium by clicking the Always do the selected action box. Once this choice is made, the dialog is not shown again. However, in Windows XP Service Pack 1 (SP1), if a new application that can handle a particular media type is added to the computer, the dialog is once again presented to the user, giving them the opportunity to select the new application as the default AutoPlay action. Applications can also set themselves as the default selection when they are installed.

Windows XP SP1 also adds a feature that retains the user's choice of AutoPlay action if they do not click the Always do the selected action box. If a user chooses an AutoPlay action for a single instance, the next time that dialog is presented for that media type, the same action is the default selection.

For an application to be included in the list of possible actions, it must be registered with AutoPlay. For more information, see Preparing Hardware and Software for Use with AutoPlay.

Mixed Media Dialog Box

The following dialog box is displayed when any medium containing a mix of supported file types is presented to the system. This is essentially the same as the single content medium dialog box but with two significant differences. First, the available action options consist of a filtered list of applications relevant to all content types present on the medium. Second, there is no option to choose a permanent default action because the content types and percentages of mixed content media are too unpredictable.

For an application to be included in the list of possible actions, it must be registered with AutoPlay. For more information, see Preparing Hardware and Software for Use with AutoPlay.

How To Autorun Dvd

Property Page

The following is a sample AutoPlay property page for a DVD/CD-ROM device.

Each device type offers an appropriate subset of content types for AutoPlay configuration. In turn, each content type, when selected, offers an appropriate list of action options in the list box. A different action can be chosen for each content type.