This article has been archived. It is offered "as is" and will no longer be updated.
This article lists basic steps for troubleshooting Institute of Electrical and Electronics Engineering (IEEE) 1394 devices and host controllers.
The following symptoms and suggestions can help you troubleshoot most problems that concern IEEE 1394 devices.
Device Is Unsupported
Generally, an unsupported device either does not appear in Device Manager, or it is marked with an exclamation point in a yellow circle. This symptom typically occurs when you use an older driver in Windows XP.
To resolve this issue if the device is a host controller, try using a comparable Windows driver. (Note that trying another driver might cripple Plug and Play or Power Management features on the computer.) Some devices--for example, devices for storage or printing--require additional drivers to function. Verify that you have the drivers available before you install such a device.
Only OpenHCI host controllers are supported by Windows XP and Microsoft Windows 98 Second Edition. Sony CXD1947A VAIO, all Adaptec, and any other non-OpenHCI controllers require additional device drivers, which are supplied by the manufacturer.
Device Disappears from Device Manger After Installation
This symptom usually occurs because of the Power Management features of the device itself, most commonly with camcorders that have been connected to the IEEE 1394 bus. After the device's internal power management cycles the device's power, the device disappears from Device Manager because it has been "removed."
To resolve this issue, alter the power-down settings on the device itself, if settings are available. There is no option to do this in Windows.
System Stops Responding After Device Connection
This symptom is usually caused by a bus-reset "storm." Each time a device is connected or removed, the entire bus is reinitialized and the devices are re-enumerated on the bus. This event can occur because of bad hardware, unsupported hardware, or a "loopback" condition in which the cables have been looped back to the controller.
To resolve this issue, recycle the power. Remove the device, verify that the cables have not looped back to the host controller, and then cycle the power.
Device That Is Bus-Powered Is Not Getting Power
Many host controllers that supply power must be connected to a power source inside the system casing, usually by the same type of power connector that is used for internal drives. NEC controllers are a good example of this.
To resolve this issue, verify that the power has been connected. Also, a 4-pin device cannot draw power from the bus and must be plugged into a separate power source. Always connect a 4-pin device to the end of the device chain. If you place a 4-pin device between the host controller and a device that must use power from the bus, the topology allows no power source for the 4-pin device.
IEEE 1394 Camcorder or Video Camera Is Not Listed in Programs
Support for these devices comes from the Microsoft Streaming Class driver. Because of this, you cannot use the Cameras and Scanners tool in Control Panel to add the device.
To resolve this issue, in your software, select Microsoft DV Camera and VCR if that option is available.
Device Is Slow After Connecting
If you connect a low-speed device (such as a 200 MB/second hub, repeater, or other device) in the chain between the host controller and a high-speed device, the software must fragment the packets to accommodate the configuration.
To resolve this issue, always place low-speed devices at the end of a chain.
Cable Is Too Long
The limit for a FireWire cable is 4.5 meters.The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.