XP No Longer Recognizes Mini-DV via Firewire [Fix-Long]

Tech-Archive recommends: Fix windows errors by optimizing your registry



I ran into this problem the other day and thought I'd post the (my)
resolution here in case anybody else comes up against the same thing in the
future;

I needed to capture some footage I'd recently shot with my Canon Mini-DV
Camcorder. So, like I'd done hundreds of times before, I connected it via
firewire to my PC and turned the camera on.

I was immediately met with XP's "Found New Hardware Wizard" informing me it
had "discovered" my Camcorder and asking me if I'd like to install it.

Obviously this camera wasn't "new" to XP, but Windows being Windows, I
played along and told it to go ahead with the "install" anyway.

Of course, the "automatic install" failed, and I was then asked to insert
the "installation disk that came with the hardware".

Well, this particular camera didn't come with an "installation disk" because
it doesn't need one. All it needs to connect to the PC, is for the PC to
have a functioning IEE1394 (Firewire) port. I knew this to be true, because
this cam worked the very first time I ever connected it to the machine.

Ding! Ding! There's the clue. Something MUST be up with my Firewire
situation.

I immediately discarded the cable that connects the cam to the PC as being
the problem. I reasoned that if XP could "sense" there was "New Hardware"
to install, the cam and the PC MUST be communicating, and therefore the
cable is OK.

Next logical step is to poke around in Device Manager.

Sure enough, There's a dreaded yellow (!) next to "Unknown Devices".

Expanding "Unknown Devices" reveals an entry called "Unibrain 1394PC" that
is not functioning properly.

Never heard of it, so I Google a little and didn't learn much. But since it
said 1394 (which is Firewire) I knew it probably had something to do with my
problem. I confirmed the association to Firewire by looking at the entry
called IEE1394 Bus Host Controller (still in Device Manager) and seeing the
following: "OHCI Compliant IEE1394 Host Controller\Unibrain 1394PC".

OK. Disconnected the camera and first tried uninstalling "Unibrain" from
"unknown devices" in Device manager and rebooting. But all that
accomplished was to have the "Found New Hardware" wizard pop up and tell me
it found "Unibrain" but could not install it.

I'll spare you all the rest of the details of my trials and errors, and cut
right to the fix (for me) from here:

While In Device Manager, I uninstalled BOTH the "Unibrain" reference in
"Unknown Devices" *AND* the reference to it under IEE1394 Bus Host
Controller - AT THE SAME TIME.

Rebooted, and watched the 'wizard' pop up again and reinstall the controller
on it's own.

Oddly enough? My Firewire connection worked properly again and I was able
to import the footage via WMM, even though all references to "Unibrain" have
disappeared from Device manager.

Like I said. I really don't understand what "Unibrain" is/was. All I can
figure is that maybe it's some part of Windows XP that's supposed to be
contained WITHIN the IEE1394 Bus Host Controller, but somehow got seperated
from it on my machine?






.



Relevant Pages

  • Re: WMDC Just doesnt work at all for me. Can anyone help me?
    ... It may just be an XML parsing error... ... Originally when I installed the WMDC RTM I did it by following the ... It originally said theat it couldn't install the ... Device Manager it showed 2 devices. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Stop Error 0x0000008E
    ... To reinstall drivers for this device click Reinstall Driver. ... I did this using the Install Automatically The wizard ... Everything else under Device Manager looks ok. ... Faulty RAM. ...
    (microsoft.public.windowsxp.basics)
  • Re: External Floppy Drive simply quit
    ... If you have the Windows XP install CDs, you can try running sfc /scannow in ... Floppy Drive using USB. ... alternate driver mahy be providing this functionality (Code 320" Have ... Device Manager, does no good. ...
    (microsoft.public.windows.mediacenter)
  • Re: No auto turnoff after XP SP2 upgrade
    ... Second, download, install and run Ad Aware: ... If you do not have an XP CD, you can download this application ... Another possibility would be an IRQ issue. ... >> If you see no such tab, go to Start and right click My Computer, select>> Properties, go to the Hardware tab and click the Device Manager button> under>> Device Manager. ...
    (microsoft.public.windowsxp.basics)
  • Re: Empty Device Manager after SP2 Upgrade from SP1
    ... create a new user account, that sounds like a brilliant good idea for 25-30 ... >> managers after the SP2 upgrade. ... >> the install file, not windows update. ... >> - The device manager only shows the computer name at the top of the ...
    (microsoft.public.windowsxp.general)