Via 1394 Ohci Compliant Host Controller Windows 7 Driver 12
Millaray Ball
Although much of this information has already been posted, it's scattered among several camera-specific threads, so I thought I'd create a more search-friendly thread with a more general title. Most here have read the excellent studio1productions.com article on the subject here. I've gone through the studio1 steps as carefully as I could, yet still encountered a number of issues on a new Windows 10 Pro 64-bit system with all current updates (full system-specs are in my signature):
I first bought a $59 StarTech IEEE1394 low-profile PCIe interface card from B+H. Note that this card has the TI-chipset, which the studio1 article doesn't recommend. I downloaded and installed the Windows 64-bit legacy driver linked on the site. Though the installation only resulted in "successful" dialog boxes from Windows after each step, the card never appears in device manager (note: I never attempted to connect a powered-on FireWIre device to the StarTech card):
Next, I bought a generic-branded FireWire PCIe card ("Godshark") from Amazon for $16.99. I made sure this one had the VIA-chipset as the studio1 article recommends. Again, after following the studio1 instructions, Windows' device manager failed to recognize the legacy driver. Every time I boot the computer, the VIA driver is already installed. So I again attempt to uninstall the VIA driver. However, when I attempt to manually install the Windows' 64-bit legacy driver (even though the initial "installation" prompted no error messages), the VIA driver continues to re-appear in device manager and the already "installed" Legacy1394.inf driver never appears.
Even the motherboard's BIOS got confused (which I never altered) and booted in an odd resolution (which a single re-boot "fixed"). I tried every troubleshooting task I could think of (e.g., removing devices, uninstalling drivers/reinstalling drivers, etc.). Prior to starting this whole process, I had no error messages in device manager and a clean-install of Windows 10 Pro 64-bit with only Vegas Movie Studio, FXhome Intensity, and Blackmagic Media Express installed.
Lastly, I pulled the Blackmagic Intensity Pro 4K HDMI capture card from the system. Neither of Vegas' two capture tools see the device. I have downloaded and run the WinDV free capture utility and no device is found. The only other board remaining in the system is the display adapter which shipped with the computer.
Note that according to Windows' device manager, under "IEEE 1394 host controllers," the "VIA 1394 OHCI Compliant Host Controller" general dialogue box continues to indicate, "This device is working properly," which it always says when the VIA driver is installed. When attempting to manually install the 64-bit legacy driver, Windows overrides my installation and re-installs the VIA driver, saying "Windows has determined this driver to be the best." There are no '!' marks or error messages under IEEE 1394 host controllers and I am unable to permanently remove the VIA host controller driver which simply reappears after every re-boot.
I know the next step is to go back to ground-zero and start all over again (i.e., pull every board, and uninstall every piece of software and driver). However, I cannot eliminate the ominous-sounding "Poisoned TLP on slot X" POST-error. This happens no matter which slot I install the VIA card into, so it's as if the VIA hardware itself is causing some kind of basic POST-issue.
Windows had also alerted me to a "PCI-to-PCI bridge" error at some point (I don't recall exactly where), which I can only guess is related to the POST-error. I'm assuming that until I resolve this, nothing else is going to move forward.
Now, this VIA card is exactly like the one pictured in the studio1 article, and when installed, device manager shows no errors whatsoever (i.e.,"this device is working properly"). Yet the POST-error only occurs when the card is in the machine, and no other Windows apps (other than device manager) is able to see the card. Perhaps try another VIA card?
Holy crap! I can't believe I got it to work. When I attempted to install the VIA card again today, my PC lost all internet connectivity (I have it hard-wired to an Ethernet switch). After about a dozen re-boots, BIOS downloads, and system patches, everything finally worked again. Doesn't capture correctly in WinDV, and not at all in VEGAS Capture, but it works in Vegas' "capture video" applet (located under Vegas' project menu). Here's the highlights:
I was super-surprised that everything worked even after getting the "poisoned TLP slot" error again. But it did. Now, I'm crossing my fingers that my Blackmagic Intensity Pro 4K card will work once I reinstall it.
Also, the ghosting appears to be a pulldown-error. At a 1/48th shutter-speed, some motion-blur is to be expected, but the motion appears slightly artifacted (i.e., unnatural), which may suggest an incompatible 3:2-pulldown algorithm somewhere in the chain.
And now . . . it doesn't work. I captured one clip using Vegas' "capture video" applet directly into Vegas and it worked. One re-boot later, and the darned VIA 1394 driver re-appeared in device manager. Again, I "searched for drivers on my PC" and re-installed the Windows' 64-bit legacy driver. Reboot. Now Vegas' ingest tool shows only a black screen while tape is playing back in my DVCAM VTR. It senses the VTR's position, and its counter "knows" when I'm playing, rewinding, etc. (though, no device-control), but NO VIDEO!
1. Re-installed the legacy driver in device manager.
2. PC immediately re-boots on its own (as it did before).
3. PC boots into a POST-error: "Poisoned TLP slot."
4. Vegas' "capture video" tool sees the device, but no image.
5. Uninstalled the legacy driver.
6. Reboot into POST-error.
7. Windows automatically replaces the legacy driver in device manager.
8. Still no video in capture window.
While I was typing this, I turned to the screen and I see video in Vegas' capture video display! As I hot-swapped the FireWIre cable in and out of the VIA-card's two inputs, Vegas continually "found" the "Sony camcorder/VTR" device, but the screen remained black and captured zero frames. Odd. But it's working now (at least for the moment).
I remember problems similar to what you described when either the fire cable or the connectors on the camera were bad. Try another cable. If the connectors on the camera are going bad, not sure what you can do.
As for the PCIEx4 full slot FireWire card, there are several options available in the market. For example, the StarTech.com PEX1394A2V2 2 Port PCI Express FireWire Card is a good option. It supports FireWire 400, uses the Texas Instruments TSB82AA2 chipset, and is compatible with both Windows and Mac. You can find this card on various online marketplaces.
Here is what happened. I upgraded primary syste hardware and MB. It did not have the PCIe4 slot so my firewire card would not mount. I procured an firewire card and when I tried it, Windows said not recognized. In researching the issue, several users of the adapter said it did not work and could corrupt the USB. I reconfigured my secondary Windis 11 system that had a PCIE4 slot for the firewire card. It mounted and installed correctly. When I plugged in the camera with the firewire cable, it would not start. I recharged the battery with the same no power on. It looks like the bad adapter fried the camera.
Click to expand the IEEE 1394 host controllers. : even after installing correct firewire drivers for the card from maker, and windows saying it has installed the drivers, there is no, Click to expand the IEEE 1394 host controllers; anywhere i have tried this over 20 + times and windows 11 always hides IEEE 1394 host controllers, and blanks the driver page to install said drivers, that's windows for you in general, no wonder so many people are moving to other operating systems.
We just got two new computers. They have Windows 7 Professional 64bit installed on them so we're stuck using that (I was going to install labview in XP Mode but there is no support for firewire...so that won't work either). After finally getting labview installed (had to run the setup.exe from Distributions\LabVIEW-ENG\LabVIEW861\ rather than doing the autorun) we can't get this camera to work. It works fine with the PixeLINK driver (and the Capture OEM program that comes with it).
3) Start up MAX. It detects the camera and shows it under NI-IMAQdx Devices. Upon clicking on the camera, it informs me that the device selected is not currently associated with either the Legacy NI-IMAQ for IEEE driver or the NI-IMAQdx driver. This is all fine, it's supposed to do that.
5) It then disappears from MAX (no NI-IMAQdx Devices folder anymore). If I goto windows Device Manager, it shows up under National Instruments IMAQ Interfaces as NI-IMAQdx IIDC Digital Camera, so the driver did get switched properly, it just doesn't show up in MAX anymore...
So, any ideas? Could this be a firewire interface problem rather than the camera? I'm using the onboard firewire port on my computer. It shows up as Texas Instruments 1394 OHCI Compliant Host Controller in Device Manager.
Hello Folks, I am having an identical problem with a later version of LabVIEW. I am using Labview 19.5, Windows 10 64 bit Enterprise. Like the above example I am using an allied vision technologies Stingray F145B camera.
The other option is to install one of the Microsoft IEEE 1394 OHCI Complient Host controller. drivers. Here The vinba software can no longer see the camera but The camera then appears under the national instruments IMAQ interfaces. It also does not appear in NI MAX. See microsoft.png.
If I change the NI-IMAQdx IIDC Digital camera driver to a generic 1394 Desktop Camera (See NI IMAQdx options.png) the device moves up into the Imaging devices folder and appears in NI-MAX as shown in Generic state.png but the camera will not run as it requests that you right click and install the NI IMAQdx driver see IMAQdx error.png. Id I then right click and install either of the IMAQdx drivers (15 or 19.5 are installed) the camera dissapears and everything goes back to how it looked in Microsoft.png.
7fc3f7cf58