Thanks for all your work. I'm having a little issue that I was hoping you might lend some advice to. I have downloaded and installed your latest STB Firewire Capture Package. I'm running Windows XP Home SP3 Build 2600. A little background first: I used your Capture Package software on my Motorola STB from Comcast for a few years without a problem. However, I switched to FiOS and now have a Cisco 435HDC. I just can't seem to get it to work. I have the same problem everyone else has:
Error 80070057: Cannot start capture.
I was hoping your latest V4 would work, but no dice.
So I tried using another capture program (Sony Vegas, Microsoft Movie maker), and I get a system error and the PC reboots. It seems like I'm actually going as far as interfacing with the Firewire device, but the system doesn't like the driver. Does that make sense? Any ideas?
Thanks for all your help.
(Wish I still had a Motorola)
Yeah, I've had the same issue with Cisco units. I believe they have a firmware bug that is causing it. When I added the 435 to the driver .inf I was working off of info provided by another forum member (thus I couldn't actually test it...they provided me with the hardware ID seen in Device Manager, and the rest is simply formatting the .inf properly). I don't have access to any Cisco units, but when I visit family (thousands of miles away, so this only happens a few times a year) my parents have a Cisco unit...I have only been able to capture a few frames of television before it crashes with that error. I really think Cisco has horribly broken the FireWire on those units.
You should contact your provider and complain. Twice. Let them know that it is a violation of federal law for them to fail to provide you with working FireWire. The law currently states that cable companies are no longer required to only purchase cable boxes that have FireWire, however, if a customer requests one, the company must provide a unit with working FireWire. What I am uncertain of is if that rule applies equally to both traditional cable companies and FIOS.
The FireWire trade association recommends contacting your provider at least twice before filing a formal complaint with the FCC.
Here's an excerpt from my Win7 Legacy FireWire documentation (part of the .MSI driver package) that talks about the FireWire requirement:
FireWire (also known as IEEE 1394, i.LINK, and Lynx) is required to be available and functional on all cable boxes purchased by cable companies from July 2005 – Nov 2010. As of Nov 2010, cable companies are still required to provide a cable box with a functional FireWire port upon customer request, but they are also free to source cable boxes that do not include a FireWire port. If the FireWire port of your cable box is not functional, visit the following website for specific instructions on how to complain to the FCC. http://www.1394ta.org/consumers/FCC_complaint.html
As of July, 2011, HD cable set-top boxes must include an interface capable of delivering recordable high-definition video and closed captioning data in an industry standard format. As of Dec, 2012, HD cable set-top boxes must comply with an open industry standard that provides for service discovery, video transport, and remote control command pass-through for home networking.
FireWire allows for the transfer of HD (and SD) television to devices such as DVHS VCR’s and computers (either Windows PC’s or Macs…but not Linux or UNIX). While both 32-bit and 64-bit Macs can connect to cable boxes, Windows PC’s are limited to the 32-bit releases; the required Windows drivers that would communicate from the cable box to the PC unfortunately do not (and will not) exist for 64-bit Windows.
With Windows 7, Microsoft made changes to the FireWire driver which make it incompatible with CapDVHS (the utility used to capture television from cable boxes) and the Cable box “FireSTB” drivers (Note: Windows XP, Windows Vista and Windows 8 have better FireWire support that does not require the following workaround.) In order to work around this, you need to have Windows 7 switch to its “Legacy” FireWire driver.
(BTW, It is likely that the cable companies have been granted an extension beyond the December 2012 deadline mentioned above)
Something else I should mention: You should seriously consider reloading your Windows system. All sorts of problems can be caused by filter drivers (ex: Apple iTunes installs a USB filter driver that detects when you plug you iDevice in, VMware Workstation installs a filter driver in order to emulate USB in virtual machines, etc.) I have had frequent situations when a fresh install was able to cure issues related to FireWire capturing. Also: not all Windows FireWire implementations are equal. I currently am looking into an issue where one of my laptops can not perform FireWire captures using Windows Server 2008. That same laptop captures flawlessly with XP SP3, Vista, Windows 7 and Windows 8, therefore I know that the laptop's FireWire port is functioning perfectly fine and my cable box's FireWire port is fine. But I can not get it to capture using Windows Server 2008. I can then take that very same laptop hard drive, hook it to another PC (not a laptop) and after booting up and giving it 5 minutes to figure all of its drivers out (being that it has just been transplanted from an Intel Core 2 laptop to an Intel Pentium 4 PC and there are gobs of hardware differences to account for) it is able to flawlessly capture via FireWire. Both FireWire implementations are Texas Instruments, but I highly doubt that they are the same model. So that proves that Windows Server 2008 is not incapable of FireWire captures...it's just suckier than the other operating systems in my one case; There must be some sort of incompatibility between the FireWire implementation in Windows Server 2008 and my one laptop's FireWire port.
You may want to search the Internet for a vendor-provided FireWire driver instead of relying on Microsoft's built-in FireWire driver (yeah, this idea is a real long shot.)
Also, I want to reiterate that Windows 8 has a much better FireWire driver than Windows 7!
Edited by TNO821 - 11/1/12 at 8:19pm