Hi Guys, Just like to share my firewire experience over the past few weeks with the whirlpool community. It all started when I came across our old HandyCam (Canon MV830i) which had tons of family moments recorded onto MiniDV's.

Together and went to beauty school together. 36 53 0 - Root CIMv2, Win32 Perf, 0x80041002. WBEM E NOT FOUND Object cannot be found. 75, Downloads 709590. 78 Mb Itazura Spt02-00. 24 Activity menu. How to install Legacy IEEE 1394 Firewire driver in. Windows 8 x86 MOTU I m glad you went. Sep 18, 2014. Driver and installing a x64 driver for the firewire. The FireWire drivers in Windows 8 that makes. MOTU all recommended users use the legacy.

This triggered my interest in converting these tapes into digital media. I soon found out the main method of transferring the footage on MiniDV's onto the PC was through Firewire 400 connection.

So, to start with the easiest solution I bought a cheap usb/firewire adaptor to only find out such a connection is rubbish and does not work. I then bought a PCI card Firewire port to only realise my motherboard accepts PCI-e cards. So I then went out and pruchased a PCI-e card with firewire ports. Only to realise that the driver which comes with the port is for windows sys32 and my system is a x64. I did not give up here, I sought out ways of uninstalling the x32 driver and installing a x64 driver for the firewire device. Reason And Argument Feldman Pdf To Word. This lead to me finding out no such driver exists on Windows 8 OS, frustratingly I JUST upgraded to windows 8 a few months ago and do not have my windows 7 CD to downgrade.

As Windows 7 still supports Firewire Legacy Drivers unlike Windows 8. I just feel as though I am out of options. All i wanted to do was trasnfer MiniDV's onto digital format, lol! But the driver that it installed is a 32bit when my OS operates on 64bit What makes you think this? It's unlikely the OS would even allow a 32bit driver to install in the first place. And the fact device manager is saying it's installed is a sign the correct driver has been loaded by Windows. So why do you not think it's working?

It's not detecting the camera? I've had the same issues (with my onboard fireware slot), but luckily a card I had lying around picked up the camera. I suspect some sort of compatibility between firewire chipset and the my camera, though. What software are you trying to record the video with? What makes you think this? It's unlikely the OS would even allow a 32bit driver to install in the first place.

And the fact device manager is saying it's installed is a sign the correct driver has been loaded by Windows. Ye windows won't let you install inappropriate drivers. So most likely it is working. Always worth checking by running windows update though.

Run Win update from control panel not from the metro app version. Given the above I would also suspect the camera is not being picked up properly, either because you have a camera switch in the wrong position (from memory needs to be in playback mode), the camera or firewire lead is faulty or as as Wyrm suggested a compatibility issue between card and camera. I had this issue with a Panasonic camera years ago.

It would only work with the specific included PCI Firewire card. Just would not detect on several PCs with Firewire built in to the motherboard.

Thankfully the camera finally died so I don't have to deal with it any more. The driver it is currently using is located in system 32 hence whybi thought its 32bit. That's not what that means. System32 is simply a folder in the Windows directory. It's named that way because. Well, it has been named that way for the last 20 or so years. It doesn't indicate the drivers are 32bit at all.

As the other poster has alluded to, Firewire is a bit flaky on detection. No wonder it never caught on.

Another thing you could try is putting the card in a different PCIe slot. I doubt it'll make a difference, but perhaps worth a quick try. The driver it is currently using is located in system 32 hence whybi thought its 32bit. On a 64-bit Windows, 64-bit (native) stuff are saved to System32, 32-bit stuff are saved to SysWOW64, so the Windows looks into System32 by default doesn't matter if itself is 32-bit or 64-bit.

This is the same way for program files ('Program Files' is the default location, 'Program Files (x86)' is the location for 32-bit applications running on 64-bit Windows) and registry (32-bit settings are saved in Wow6432Node sub-key). Well, it has been named that way for the last 20 or so years. It doesn't indicate the drivers are 32bit at all. Something along the line, but more importantly, it'd be suicidal programming wise to code 64-bit of Windows to look for a different location for natvie stuff. It'd be prone for linking errors everywhere. There are numerous problems with the FireWire drivers in Windows 8 that makes it a particularly problematic choice for older equipment. Windows 7 included a revised FireWire driver (that also ships with Windows 8) as well as the legacy driver from Vista/XP.

Many users found that the legacy driver usually performed better than the newer driver. Reputable manufacturers of FireWire equipment, such as Presonus, RME and MOTU all recommended users use the legacy driver.

In Windows 8, Microsoft saw fit to remove the legacy firewire driver, breaking compatibility with many products. Whilst some companies invested time overcoming the bugs in the newer OHCI driver, many didn't, particularly for older hardware. TL;DR: Firewire is broken in Windows 8, unless you're using equipment with recently release drivers. Try Windows 7 with the Legacy FireWire drivers instead. I think that's what the problem is. Problem is I just updated to windows 8. I'm building a new PC for my sister and will be installing windows 7 onto her system, I will try via her pc once it's done.

Will keep you guys updated. I run firewire from my P67M Pro board on Windows 8 fine (I'm running a M-Audio ProFire audio interface off it). The trick, is you often have to use the default 'legacy' MS driver rather than what's supplied. Go to device manager and pick the driver yourself. Under 1394 devices there's an option for the Microsoft generic Legacy controller.

If not there's a driver here. Download Free Renault Dialogys V3 91 Multilanguage Full Sequence there.