1394 IEEE was working

[brainstewn]

I'm using a Grass Valley ADVC 110 capture device with Windows XP SP3 on a
custom built ASUS M2N-SLI Deluxe motherboard.

A month ago when I plug in the ADVC I would hear the ping and it was
recognized by Adobe Premiere Pro as "online"

Today no ping sound and the device isn't recognized. I take the ADVC and
the same cable to my laptop running home edition XP and the laptop recognizes
the ADVC and I can capture video fine.

Unibrain software indicates that the 1394 is working, control panel has no
errors or caution icons, I'm stumped.

How do uninstall the windows drivers and reinstall?

 

[smlunatick]

I'm using a Grass Valley ADVC 110 capture device with Windows XP SP3 on a
custom built ASUS M2N-SLI Deluxe motherboard.

A month ago when I plug in the ADVC I would hear the ping and it was
recognized by Adobe Premiere Pro as "online"

Today no ping sound and the device isn't recognized.  I take the ADVC and
the same cable to my laptop running home edition XP and the laptop recognizes
the ADVC and I can capture video fine.

Unibrain software indicates that the 1394 is working, control panel has no
errors or caution icons, I'm stumped.  

How do uninstall the windows drivers and reinstall?

To re-install the Windows drivers, you need to complete uninstall the
"devices" in Device Manager.

Copy the following to a "batch" file:

 

[brainstewn]

I created the batch on my desktop, uninstalled the TI IEEE controller,
restarted, scanned for hardware changes it reinstalled but still no firewire
hardware is recognized, something is duplicated or corrupt. With so many
people having this problem where is the utility, debugging tool etc?

Thanks for your time and any other support you might give.

Ciao
Darrell

 

[Patrick Keenan]

I created the batch on my desktop, uninstalled the TI IEEE controller,
restarted, scanned for hardware changes it reinstalled but still no
firewire
hardware is recognized, something is duplicated or corrupt. With so many
people having this problem where is the utility, debugging tool etc?

Thanks for your time and any other support you might give.

Were you hot-plugging this firewire device?

If so, you should be aware that there is a defect in many 1394 chips that,
in the context of hot-plugging, can destroy the port on either or both the
PC and the other device.

Yes, I know that hot-plugging is part of the spec. The problem is that it
sometimes doesn't work, and does so in a very bad way.

It's not necessarily an easy replacement, I've had to return for factory
service a $1000 audio interface because the port blew on the Mac and on the
interface; other 1394 devices plugged into the port on the Mac were
instantly damaged requring factory replacement (we were in a Mac focused
Audio gear store, and so it was the staff who plugged in a new $600
replacement interface, heard the gentle "bang" and puff of smoke, said
"whoops" and put it back in the box and marked it defective). *Every* hard
disk case I have purchased with 1394 ports failed. I never buy them now.

If you look at the M-Audio site, you will find that they caution against
ever hot-pluggng firewire devices. Their advice is to power everything
off, turn the peripherals on, then the PC.

There is a white paper on the net that describes the actual defect in the
chip.

HTH
-pk

 

[brainstewn]

Thanks Patrick:

Almost 6 hours later I determined that it's a bugging Texas Instruments Host
Controller. Grass Valley (Canopus) recommended a third party card and look
for NEC controllers on future motherboards. I will head your advice on
hot-plugging as I did blow a port on a 250g hard drive years ago; you
explained why that happened.

Ciao
Darrell

: