Dubaiblog925

1. Hp Device Drivers
2. ASK Port Devices Driver

• Eaton5E driver = blazerusb port = auto Result of $ upsdrvctl start for usbhid-ups driver: Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 No matching HID UPS found Driver failed to start (exit status=1) Result of $ upsdrvctl start for blazerusb driver.
• There might be an issue with the USB port. Try connecting to a different USB port. If the USB device displays in Device Manager after connecting the cable to a different port, then uninstall and reinstall the USB device software driver.

This article describes an issue that occurs when you use a FireWire port-based device in Windows 8.1 or Windows 8. Additional steps of configuration is required to enable this update after the installation.

Virtual COM Port Drivers. Some USB devices use a Virtual COM port (VCP) driver, which causes the USB device to appear as an additional COM port available to the PC (listed in Windows Device Manager, under the Ports (COM & LPT) type, as a “USB Serial Port (COMx)” device. In computing, a device driver is a computer program that operates or controls a particular type of device that is attached to a computer or automaton. A driver provides a software interface to hardware devices, enabling operating systems and other computer programs to access hardware functions without needing to know precise details about the hardware being used. These system class drivers set up IRPMJINTERNALDEVICECONTROL requests for an underlying port driver. Any new keyboard or mouse port driver that interoperates with these system class drivers also must support these public internal device control requests. The system parallel class/port driver model has similar features.

Symptoms

Assume that you have a computer that equips with an IEEE 1394 FireWire controller card. After you upgrade the computer from Windows 7 to Windows 8.1 or Windows 8, devices that connect to the computer by using a FireWire port do not work.

Cause

This issue occurs because the legacy 1394 bus drivers (1394bus.sys and Ochi1394.sys) are removed in Windows 8.1 or Windows 8.

Resolution

Update information

How to obtain this update

Microsoft Download Center

The following files are available for download from the Microsoft Download Center:

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Additional steps of configuration requirement

After you install the 1394 OHCI Legacy Driver.msi file, follow these steps:

Hp Device Drivers

1. Right-click the Legacy1394.inf file under one of the following paths based on the computer's architecture:
   

   • C:Program Files1394 OHCI Compliant Host Controller (Legacy)x86_driver

   • C:Program Files1394 OHCI Compliant Host Controller (Legacy)x64_driver

2. Click Install.

3. Open Device Manager in Control Panel.

4. Expand IEEE 1394 Bus host controllers, and then locate the host controller.

5. Right-click the host controller, and then click Update Driver Software.
   The screen shot of the host controller and the Update Driver Software is listed in the following example:
   

6. Click Browse my computer for driver software.

7. Click Let me pick from a list of device drivers on my computer.

8. Click Generic1394 OHCI compliant host controller (Legacy), and then click the Next button.

9. Click the Close button.

Prerequisites

There are no prerequisites for installing this update.

Registry information

To apply this update, you do not have to make any changes to the registry.

Restart requirement

You have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows 8 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are not listed

For all supported x86-based versions of Windows 8.1 or of Windows 8

For all supported x86-based versions of Windows 8.1 or of Windows 8

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the 'Applies to' section.

More Information

Steps of uninstalling the 1394 OHCI Legacy Driver.msi file

1. Open Control Panel in the Category view.

2. Click Uninstall a program in Control Panel.

3. Right-click 1394 OHCI Compliant Host Controller (Legacy), and then click Uninstall.
   The screen shot of uninstalling the 1394 OHCI Compliant Host Controller (Legacy) is listed in the following example:
   

ASK Port Devices Driver

Additional package information

• This driver is only intended to work with legacy 1394 host controllers. Therefore, you may experience lower transfer data rates than the 1394b driver.

• The driver is intended to resolve compatibility issues for 1394 peripherals on 1394b systems. If you are not experiencing these issues, you should continue to use inbox drivers that are provided in Windows 8.1 or Windows 8.

• You have to reinstall this stand-alone driver package if you upgrade to a newer operating system version in the future.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

The higher-level driver of a class/port pair can sometimes complete IRPs in its DispatchDeviceControl routine. For example a class driver could, during initialization, gather and store information about the features of the underlying device, which might be sought in a subsequent IRP_MJ_DEVICE_CONTROL request, and thus save processing time by satisfying the request without passing it on to the underlying device driver. A class driver might also be designed to check the IRP's parameters and send only requests with valid parameters to the port driver.

Closely coupled class/port drivers also can define a set of driver-specific or device-specific internal I/O control codes that the class driver can use for IRP_MJ_INTERNAL_DEVICE_CONTROL requests to the port driver.

For example, the DispatchCreateClose routines in the system keyboard and mouse class drivers send system-defined internal device control requests to enable or disable keyboard and mouse interrupts to the underlying port drivers. These system class drivers set up IRP_MJ_INTERNAL_DEVICE_CONTROL requests for an underlying port driver. Any new keyboard or mouse port driver that interoperates with these system class drivers also must support these public internal device control requests.

The system parallel class/port driver model has similar features. New parallel class drivers can get support from the system parallel port driver by setting up IRPs for IRP_MJ_INTERNAL_DEVICE_CONTROL requests with public IOCTL_PARALLEL_PORT_XXX control codes. You can replace the system parallel port driver, but any new driver also must support this set of public internal device control requests.

For more information about these public internal device control requests, see device-specific documentation in the Windows Driver Kit (WDK). For information about how to define private I/O control codes, see Using I/O Control Codes.

For a closely coupled pair of port/class drivers, the class driver might handle the processing of certain device control requests without passing them on to the port driver. In a new class/port driver pair, the class driver's DispatchDeviceControl routine can do either of the following:

• Check the validity of the parameters in its own I/O stack location, set the I/O status block if it finds any parameter errors, and call IoCompleteRequest with a PriorityBoost of IO_NO_INCREMENT; otherwise, call IoGetNextIrpStackLocation copy its own I/O stack location into the port driver's, and pass the IRP on with IoCallDriver.

• Or, do nothing more than set up the port driver's I/O stack location in the IRP without checking parameters and pass it on to the port driver for processing.

SCSI class drivers have special requirements for handling device control requests. For more information about these requirements, see Storage Drivers.