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.

The current official release of the driver is 6.4.6, released on September 26, 2011 by Christopher R. Baker [email protected] After more than a year of wrestling with the nuances of Microsoft's 64-bit operating systems, and with no small quantity of assistance from a few brave testers (you know who you are!), I am proud to officially release this next version of the CMU 1394 Digital. D This section provides installation information, specific to IEEE 1394 device drivers in Microsoft Windows 2000 and later operating systems. Vendors supplying their own IEEE 1394 device driver should make that driver a member of the Base setup class in the INF Version Section of the driver's INF file.

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:

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:
   

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

Windows 7 includes 1394ohci.sys, a new IEEE 1394 bus driver that supports faster speeds and alternative media as defined in the IEEE-1394b specification. The 1394ohci.sys bus driver is a single (monolithic) device driver, implemented by using the kernel-mode driver framework (KMDF). The legacy 1394 bus driver (available in earlier versions of Windows) includes multiple device drivers that were implemented by using the Windows Driver Model (WDM) in a port/miniport configuration. The 1394ohci.sys bus driver replaces the legacy port driver, 1394bus.sys, and the primary miniport driver, ochi1394.sys.

The new 1394ohci.sys bus driver is fully backward compatible with the legacy bus driver. This topic describes some of the known differences in behavior between the new and the legacy 1394 bus driver.

Note

The 1394ohci.sys driver is a system driver that is included in Windows. It is automatically loaded when you install a 1394 controller. This is not a redistributable driver that you can download separately.

I/O Request Completion

All I/O requests that are sent to the new 1394 bus driver return STATUS_PENDING because the 1394ohci.sys bus driver is implemented by using KMDF instead of WDM. This behavior differs from that of the legacy 1394 bus driver, in which certain I/O requests complete immediately.

A client driver must wait until I/O requests sent to the new 1394 bus driver are complete. You can provide an I/O completion routine that is called after the request is complete. The status of the completed I/O request is in the IRP.

Configuration ROM Retrieval

The new 1394 bus driver tries to use asynchronous block transactions at faster bus speeds to retrieve the contents of a node's configuration ROM. The legacy 1394 bus driver uses asynchronous quadlet reads at S100 speed—or 100 megabits per second (Mbps). The 1394ohci.sys bus driver also uses the values that are specified in generation and max_rom entries of the node's configuration ROM header to improve the retrieval of the remaining content of the configuration ROM. For more information about how the new 1394 bus driver retrieves the contents of a node's configuration ROM, see Retrieving the Contents of a IEEE 1394 Node's Configuration ROM.

IEEE-1394-1995 PHY Support

The 1394ohci.sys bus driver requires a physical layer (PHY) that supports IEEE-1394a or IEEE-1394b. It does not support a PHY that supports IEEE-1394-1995. This requirement is due to the 1394ohci.sys bus driver's exclusive use of short (arbitrated) bus resets.

NODE_DEVICE_EXTENSION Structure Usage

A client driver can reference the device extension in the 1394 bus driver associated with the physical device object (PDO) for the device that the client driver controls. This device extension is described by the NODE_DEVICE_EXTENSION structure. In 1394ohci.sys, this structure remains at the same location as in the legacy 1394 bus driver, but the nonstatic members of the structure might not be valid. When a client driver uses the new 1394 bus driver, they must make sure that the data accessed in NODE_DEVICE_EXTENSION is valid. The static members of NODE_DEVICE_EXTENSION that contain valid data are Tag, DeviceObject, and PortDeviceObject. All other members NODE_DEVICE_EXTENSION are nonstatic, which the client driver must not reference.

Gap Count Optimization

The default behavior of the 1394ohci.sys bus driver is to optimize the gap count when it finds only IEEE 1394a devices on the 1394 bus, excluding the local node. For example, if the system that is running 1394ohci.sys has a host controller that complies with IEEE 1394b but all devices on the bus comply with IEEE 1394a, then the new 1394 bus driver tries to optimize the gap count.

Gap count optimization occurs only if the 1394ohci.sys bus driver determines that the local node is the bus manager.

The 1394ohci.sys bus driver determines whether a device complies with IEEE-1394a by the speed setting in the node's self-id packet. If a node sets both of the bits in the speed (sp) field in the self-id packet, then 1394ohci.sys considers the node to comply with IEEE-1394b. If the speed field contains any other value, then 1394ohci.sys considers the node to comply with IEEE-1394a. The gap count value that is used is based on table E-1 in the IEEE-1394a specification, which provides the gap count as a function of hops. The 1394ohci.sys bus driver does not compute the gap count. You can change the default gap count behavior by using a registry value. For more information, see Modifying the Default Behavior of the IEEE 1394 Bus Driver.

Driver 1394 Windows Xp

Device Driver Interface (DDI) Changes

In Windows 7, the 1394 DDIs were changed to support faster speeds as defined by the 1394b specification and improved to simplify the development of 1394 client drivers. For more information about the general DDI changes that the new 1394 bus driver supports, see Device Driver Interface (DDI) Changes in Windows 7.

How To Install 1394 Legacy Driver Windows 10

Related topics

How To Install 1394 Legacy Driver

The IEEE 1394 Driver Stack
Retrieving the Contents of a IEEE 1394 Node's Configuration ROM