Firewire 1394 autodetect not working

[Dan]

Hi,
I hope someone can help with this. I recently did a fresh
install of WinXP Pro (w/ all service packs/fixes as of
7/24/03) And when I plug in a firewire device (Sony TRV-17
DV cam) I don't get any response from WinXP. I've tried 3
different cables and 3 different ports on my mobo (Abit
IS7). The camcorder showed up a few days ago so I think
the firewire controller is ok (Texas Instr.) but now I
can't get WinXP to recognize that a 1394 device is plugged
in. I've tried turning the cam on/off and plugging/un-
plugging the port several times and it's of no help. On
my old WinXP machine I would have to turn on the camcorder
and then plug/un-plug the cable to get WinXP to recognize
it. Which is what makes me believe this is a windows
issue.

One of the main reasons I built a new PC was for faster
video-editing.. so this is something I really need to get
working.

Thanks,
Dan

 

[Edward W. Thompson]

I have found that detection of a firewire drive is somewhat "flaky" and it
often takes multiple attempts before WINXP or the machine recognizes that
the drive has been connected. It maybe a connector "problem" I suppose but
plugging in and unplugging until the drive is recognized eventually works
for me. It seems as if you may have a similar problem.

 

[Marilyn M]

Dan -
I am having a similar problem with my Sony TRV900. Mine
will occassionaly be recognized, but as soon as I try to
capture anything from it, the device disappears. Most of
the time it isn't even recognized, no matter how many
times I reboot, unplug/plug in, or turn camera off/on.

Have you had any luck fixing the problem yet?

I'm working with MS Support - they seem to feel it is one
of 3 things:
- unsupported firewire card: this is not the problem,
I've already proven that it is.
- bad drivers: either for the firewire card or the
camera - Sony doesn't have anything, I'm relying on what
MS has as a driver
- conflicts with other devices: I've tried repositioning
the firewire card into another PCI slot, but it didn't fix
the problem.

I am continuing to pursue with MS Support, but it will be
a long drawn out process of elimination. If you find out
anything, please let me know, and I'll do the same.

Regards,
Marilyn