Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI
ABOUT SSL CERTIFICATES
|Model:||USB 2.0 + IEEE 1394 FireWire Combo Card, PCI|
|Compatibility:||Windows XP, Vista, 7, 8, 10|
|Download Size:||3.4 MB|
|Available Using DriverDoc:||Download Now|
This page contains information about installing the latest Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI driver downloads using the Hama Driver Update Tool.
Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI drivers are tiny programs that enable your Firewire hardware to communicate with your operating system software. Maintaining updated Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI software prevents crashes and maximizes hardware and system performance. Using outdated or corrupt Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI drivers can cause system errors, crashes, and cause your computer or hardware to fail. Furthermore, installing the wrong Hama drivers can make these problems even worse.
Recommendation: If you are inexperienced with updating Hama device drivers manually, we highly recommend downloading the Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI Driver Utility. This tool will download and update the correct Hama USB 2.0 + IEEE 1394 FireWire Combo Card, PCI driver versions automatically, protecting you against installing the wrong USB 2.0 + IEEE 1394 FireWire Combo Card, PCI drivers.
The following diagram illustrates the IEEE 1394 driver stack with the new 1394 bus driver and the Microsoft-supported 1394 client drivers.
A client driver for a device that connects to the IEEE 1394 bus driver sits on top of the IEEE 1394 driver stack. The bus driver provides a hardware-independent interface to the IEEE 1394 bus. The device driver communicates with the device by sending IRPs, which are processed by the IEEE 1394 bus driver. Before Windows 7, the bus driver was a combination of a port driver (1394bus.sys) and a primary miniport driver for the motherboard's host controller (ochi1394.sys). In Windows 7 and later versions, the legacy port/miniport bus drivers are replaced by 1394ohci.sys, a monolithic IEEE 1394 bus driver that is implemented by using the kernel-mode driver framework (KMDF). The 1394ohci.sys bus driver is fully backward compatible with the legacy 1394 bus drivers. For more information about some known differences in behavior between the new bus driver and the legacy 1394 bus drivers, see IEEE 1394 Bus Driver in Windows 7.
The following illustration shows the relationship between the legacy and the new 1394 bus drivers.
To issue commands to devices connected to the bus, drivers issue the IRP_MJ_DEVICE_CONTROL IRP, with control code IOCTL_1394_CLASS. The driver packages the parameters in an IEEE 1394 I/O request block (IRB), and passes a pointer to it in the Parameters.Others.Argument1 member of the IRP. The FunctionNumber member of the IRB determines the type of operation, and the u member describes the operation. The bus driver uses the IOCTL_1394_CLASS IRP to present an interface to both the bus and the host controller.
The IRB structure contains parameters that apply to each bus request and request-specific parameters. The u member of the IRB contains the request-specific parameters, in a union of data structures, one per request type.
During normal operation, drivers receive ordinary I/O requests (such as IRP_MJ_READ), convert them to the appropriate IEEE 1394 operation, and dispatch that operation to the device through IOCTL_1394_CLASS.
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.
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. Mistral windglider manual.
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
Ieee 1394 Interface
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.
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.
The IEEE 1394 Driver Stack
Retrieving the Contents of a IEEE 1394 Node's Configuration ROM
- Restart the computer if Windows 7 has stopped responding. If the Plug and play window for IEEE 1394 opens, cancel the installation.
- Click Start, and type device manager into the search field.
- The Device Manager window opens.
- Select the 1394 Controller, LSI 1394 OHCI Compliant Host Controller (in this example), and select Update Driver Software.
- Select Search automatically for updated driver software. What happens?
- Windows Update finds and installs a driver. Use the FireWire port to see if the problem continues. If problems continue, see the next step.
- Windows 7 stops responding when installing the driver. Restart the computer and see next step.
- Windows Update does not find a more recent driver (problems continue). See next step.
- The hardware on your computer is not compatible with a version of the IEEE 1394 driver for Windows 7. Repeat these steps to open Device Manager and Update Driver Software. Instead of selecting 'Search Automatically..', select Browse my computer for driver software.
- Select Let me pick from a list of device drivers on my computer.
- Select 1394 OHCI Compliant Host Controller (Legacy), and click Next.Figure : Update Driver Software: Legacy Host Controller
- Windows 7 automatically installs the legacy version of the 1394 host controller and restarts the computer.
note:The legacy driver may not perform as well as an updated driver. If problems occur with the most recent IEEE 1394 update from Device Manager, the legacy driver may be your only option. In the future, you can repeat these steps to attempt to install an updated version of IEEE 1394 that might address the compatibility problems affecting your computer.
Windows 7 includes 1394ohci.sys, a new IEEE 1394 bus driver that is implemented by using the kernel-mode driver framework (KMDF). The 1394ohci.sys bus driver replaces the legacy IEEE bus driver in port/miniport configuration-- 1394bus.sys and ochi1394.sys.
In some situations you might want to override the default behavior of 1394ohci.sys,. You can do this by setting certain registry values that it supports.
Registry Value Locations
You can set the 1394-related registry values either globally for all 1394 controllers in the system or individually for each 1394 controller. The 1394ohci.sys, bus driver first queries the global 1394 registry values and then queries the individual 1394 controller registry values.
The following registry location contains the global 1394 registry values:
The following registry location contains the individual 1394 controller registry values: Autocad 2008 serial number and activation code free download.
Ieee 1394 Drivers Xp
<NNNN> represents the instance identification number for each 1394 controller.
The following table describes the registry values that the new 1394 bus driver supports. You can specify all registry values either globally or for a particular 1394 controller. Any registry values that are specified for a particular 1394 controller override any corresponding globally specified registry values.
|DisableGenerationCountCompare||DWORD||0 or 1||0||The 1394ohci.sys bus driver compares the generation count value in the self_id register of the 1394 controller with the generation count value that is received in the asynchronous receive DMA request context buffer when it processes received asynchronous requests. Setting this value to 0 enables generation count comparison. Setting this value to 1 disables generation count comparison.|
|UseQuadletReadsForEnumeration||DWORD||0 or 1||0||Setting this value to 0 enables the default method for retrieving the contents of the configuration ROM. Setting this value to 1 causes the new 1394 bus driver to use asynchronous quadlet read transactions to retrieve the contents of the configuration ROM.|
|EnumerateIP1394||DWORD||0 or 1||0||Setting this value to 0 disables enumeration of IP1394 devices on the 1394 bus. Setting this value to 1 enables enumeration of IP1394 devices on the 1394 bus.|
|EnableGapCountOptimization||DWORD||0 or 1||Optimize for 1394a topology only||Setting this value to 0 disables gap count optimization. Setting this value to 1 enables gap count optimization.|
Note Enabling gap count optimization improves the gap count for all 1394 bus topologies, including 1394b. The gap count value that is used is based on the table method, as specified in the IEEE-1394a specification. End-users must make sure that the gap count that is used is valid for their 1394 bus topology.
|EnablePersistentCycleStarts||DWORD||0 or 1||0||Setting this value to 0 disables cycle start packets if no isochronous-capable nodes are found on the 1394 bus. Setting this value to 1 enables cycle start packets regardless of whether isochronous-capable nodes are found on the 1394 bus.|
Note The 1394ohci.sys bus driver disables and enables cycle start packets only if the local node is the bus manager.
The IEEE 1394 Driver Stack
IEEE 1394 Bus Driver in Windows 7