SP2 and firewire

I have had this problem since December of 04 and have not found a fix. As soon as I upgraded to SP2, Windows XP no longer detected my Canon ZR65. I gave up on it and just recently built a new computer, with a PCI card for firewire, and thought I would try again. Same problem, XP does not see my minidv, but device mgr reports it as working. I have tried every fix that Google returns. This is my last plea for help before throwing the camera in the river. Does anyone have a ZR65 Canon that is working with XP SP2?

Thanks

hi,
Have you tried MS ?

http://www.softwarepatch.com/windows/winxp-1394.html

jolphil

I've had the same problem as well with my Canon Elura, bought back in 2000. When I tried to upgrade to SP2 when it came out, my camera wasn't detected anymore. Reverting to SP1 solved it, and I've been on SP1 ever since, but I've read that Microsoft support for SP1 will be phased out this fall, so now I'm not sure what I should do.

I am still waiting for Canon to reply. They show they zr65 as windows compatable, so maybe they have something to offer. From what I understand, that not only MS did not adhere too well to the IEEE1394 standard, most camera mfgs did not as well. Supposedly MS tightened up their adherence to the spec with SP2 and from all that I can read, there has been alot of cameras that no longer talked with XP. If you stumble across something, please let me know. I am also in touch with a guy from MS to see if he can offer any help.

Originally Posted by 2Busy

Supposedly MS tightened up their adherence to the spec with SP2 and from all that I can read, there has been alot of cameras that no longer talked with XP.

That's exactly the conclusion my research into the problem led to me at the time. Microsoft improved things so well they don't work anymore.

I haven't found a solution yet, but I imagine there are other people out there with the same problem.

I have heard that some people were using S-Video. However, I would have to dig out my tv capture card and see if works as well with SP2. I was using the component input off it mainly to my tv set, never messed with the S video. Does s video transfer sound as well, or video only?

S-video is video only; if you want audio, you have to use the red and white RCA jacks, too. But I want to transfer my DV footage in its lossless original digital DV-AVI format via firewire, not in an analog format, then recompressed to digital, which would not be a lossless process. It would be nice if Microsoft or Canon or somebody else had a fix for this.

I just got an email back from Canon. Here is a cut and paste of their response.

Thank you for contacting Canon product support. We value you as a Canon
customer and appreciate the opportunity to assist you.

To verify that the camcorder has a solid, unbroken connection to the
computer, check the camcorder screen while you have it powered by the AC
adaptor and connected to the computer through the firewire interface.
If you see the message "DV IN" displayed and it is not blinking in the
camcorders display, then the camcorder recognizes the computer. At that
point, any possible troubleshooting would have to take place in the
computer to verify that the operating system is recognizing the
camcorder, and that the software is properly configured.

You may wish to check the firewire card in your computer to make sure
that it is OHCI Compliant. OHCI Compliance is a requirement for
compatibility with any miniDV camcorder, and should be indicated
somewhere in the literature for your firewire card.

If you do not see "DV IN," or if "DV IN" is blinking, then the camcorder
has a broken connection, or does not recognize any connection at all.
No connection indicates that either the camcorder DV port, the firewire
cable, or the computer's firewire port is faulty. At that point, we
would recommend either trying a different cable or connecting the
camcorder to a different computer to narrow down the possibilities.
Once you determine which piece of equipment is not functioning properly,
further troubleshooting possibilities become available.

If it is determined that the camcorder DV port is not functioning
properly, then unfortunately your camcorder may need to be examined by
an authorized repair facility. There are two (2) Canon Factories that

Well, when I tried this, I did not see dv in. I tried this with 2 different cables just now as well. I doubt that it is my camera, and device mgr says my 1394 card is working properly. However, I have no other means to test it.

Will keep looking............
work on those camcorders

Update: I jumped through the hoops for this convoluted fix (start at Back to SP1?) and it works! I'd been on SP1 all this time since SP2 came out because of this issue, and now I'm finally on SP2, and my Canon Elura camcorder is finally detected via Firewire (IEEE 1394) under SP2. Hope this helps someone.

http://www.rme-audio.com/english/techinfo/fw800sp2.htm

Back to SP1?


So is it necessary to uninstall SP2 to get back the previously achieved performance? No. It is sufficient to install the operating system's old FireWire driver. In fact it is already enough to exchange two files [1]. Here's how to do it:

Go to the the hidden Windows\Inf directory and copy 1394.inf to a new directory, like \1394_fix.
Before updating to SP2:

Go to Windows\system32\drivers and copy ohci1394.sys and 1394bus.sys to \1394_fix. These files have a date around august 2002, and say SP1 in their file properties.
If you already updated to SP2: the old ohci1394.sys and 1394bus.sys are found in Windows\Driver Cache\i386\sp1.cab. Copy the files from this archive into the directory \1394_fix.

If you had not installed SP1: the files are found in driver.cab, but this archive includes older files that we did not test.

Install the SP2 update

Go to Windows\system32\drivers and copy these files to \1394_fix: arp1394.sys, enum1394.sys, nic1394.sys
These files are the ones from SP2. There is no need to reinstall all old FireWire drivers. Some of them haven't changed, others are for network use only.

These files are now also found in the sp2.cab, location see above.

Rename sp2.cab to sp2_dead.cab.
This is necessary, as Windows includes a nice security mechanism, which prevents worst-case-users from accidentally overwriting important driver files with older versions, or even worse, deleting them completely. So if you try to install the mix of driver files in \1394_fix, Windows will automatically install the newer files found in its sp2.cab!

Make sure no other external FireWire device is present.

Go to Device Manager, FireWire controller (OHCI xxx, 1394 or similar), Properties, Driver, Driver Update. Select 'No, only this time', 'Install from a list or specific location (advanced)', click 'Next', select 'Don't search I will choose the driver to install', click 'Next', then 'Have Disk'. Now point to \1394_fix. Then continue.

Windows will now ask for the path to the file ohci1394.sys and 1394bus.sys. It wants to install the newer ones (see above). Again point to \1394_fix.
That's it. You can now go to Driver Details, and verify that all driver files are from SP2 except the ohci1394.sys and 1394bus.sys, which are from SP1.

Finally you can rename sp2_dead.cab back to sp2.cab. Windows will no longer try to copy the newer driver file until you do a reinstall of the FireWire controller driver. So it makes sense to activate the driver cache security mechanism again.

[1] In the first version of this Tech Info, only the file ohci1394.sys had been exchanged. With this, the throughput rises to good S400. But exchanging the 1394bus.sys as well will activate full 800 Mbit/s.