I have upgraded my system to Win7 Ultimate 64bit. I have a JVC GR-D820EK cam with a fire wire connection for down load. The 1394 card is installed and the current driver is: windows system32 drivers 1394 ohci.sys The device manager tells me all is well. The cam recorder shows up in devices and current drivers are: windows system32 drivers ksthunk.sys windows system32 drivers msdu.sys Again listed in devices and printers status OK My software does not pickup the JVC cam, I am using Corel VideoStudio Pro X4 which picks up my desktop cam which is in the same list. It worked fine in win7 32bit Since posting I down loaded some more software, it picked the jvc up but would not play it or record, so I am convinced it is drivers. Similar help and support threads Thread Forum I have some problem with my firewire driver. It is not recognized (see the picture in the attachment).
- Via 1394 Ohci Windows 7 64 Bit Drivers For Mac
- Via 1394 Ohci Windows 7 64 Bit Drivers For Mac Windows 10
I tried to add the 1394 OHCI Compliant Host Controller (Legacy), but with no success. Does this mean that my firewire hardware is not compatible with Win 7?
Drivers Hello everyone I have several firewire devices I use with a Mac but when I connect them to Windows 7 I can only find them in my Control Panel is there any way to use the drive or do I have to use a mac:( Hardware & Devices Hello, New PC has a 1394 Port. Familiar with the USB Ports of course, but have never used a 1394 Port. What and where is it used? What devices should utilize it? Network & Sharing I am having issues with External Hard Drive.
Maxtor III 500gb. When connected by firewire the drive is not seen. Works fine on USB. Worked fine on both Firewire and USB on Vista. Suggestions on how to fix the firewire issue?
Hardware & Devices 1394 MS drivers in Windows 7 x64 work fine with Sony DV camcorders - unlike Vista x64. I'm very very happy. Drivers Our Sites Site Links About Us Find Us.
Hi, For those who are running Windows 8 and want to use their RME Fireface 400/800 cards (and other brands of FW cards should apply) and need to use the legacy firewire driver please try these steps. DO THIS AT YOUR OWN RISK, BACKUP FIRST, DO NOT TAKE ADVICE FROM STRANGERS ON THE INTERNET AS GOSPEL. HUG A KITTEN.
Get yourself access to a Windows 7 computer, if you are running Win8 32bit then you need Win 7 32bit, if you are running Win8 x64 you need files from a Win7 x64 computer. Locate these files from a Windows 7 machine: c: windows inf 1394.inf c: windows inf 1394.pnf c: windows system32 drivers 1394bus.sys c: windows system32 drivers 1394ohci.sys c: windows system32 drivers ohci1394.sys Copy all these files into a folder of your choice on your Windows 8 computer. Then follow this guide on how to reboot without driver signing enabled: Once you have rebooted with driver signing disabled you can proceed.
You can then go into Device Manager: 1. Expand IEEE 1394 Host Controllers 2. Right click on your firewire controller and choose Update Driver Software 3. Click 'Browse My Computer for Driver Software' 4. Click 'Let me pick from a list of device drivers on my computer' 5.
Click Have Disk 6. Click Browse 7. Browse to the folder where you placed the Win7 FW drivers and click Open. You can then install the 1394 OHCI (Legacy) driver. Windows will warn you about unsigned drivers, just accept and continue the install. You will need to reboot, most certainly using the unsigned driver / advanced boot method from the link above.
NOTE: The only problem I'm having is that I have to repeat the bootup process every time I reboot to have audio. The RME Fireface 400 drivers don't seem to play well if I use any other firewire driver. The legacy works - so far, perfectly for me. So far this driver is working flawlessly.
RME mods/devs - is it possible for you to use your position with Microsoft as developers to try get this driver back into Windows 8 or offer us a solution? I had similar problems in Windows 7 and only the Legacy FW driver resolved the issues for me. I hope this helps someone. Sorry forgot to ask, MC, do you know what the difference is with the legacy driver? Ie: What is different about it compared to the standard firewire drivers? If you Google for something like: Windows 7 legacy firewire driver you will find countless posts from people with video camcorders, audio interfaces and other devices that required this driver to be changed to the legacy one in Win 7.
I'm just curious what's special / different about it. I also had this problem with my FF400 in Win 7x64 and the legacy driver fixed it. I've already set bcdedit -set loadoptions DISABLEINTEGRITYCHECKS prviously but still have to reboot into advanced boot mode etc Out of irritation and reading so many people with the VIA 6315N firewire controller having problems using the standard driver (not legacy) I ordered an SIIG controller with the TI chip. That should work perfectly. Not willing to part with my lovely FF400 for a USB soundcard, this thing will die with me. Well until I have money for another RME perhaps The standard driver has never worked for me in Win7 x64 or Win8 RTM x64 so I guess it's partly this crappy controller.
I'll report back with results when I get the card, hopefully in the next week or two as it's an import, can't find these cards in South Africa, and horribly overpriced (double the US price). Well my SIIG controller with a Texas Instruments card arrived.
No joy No matter if I use ASIO or if I play back music in my mp3 player or whatever, after about 30 seconds -3mins or so I get the looping 1ms buffer sound.' Eeeeeeee' (it sounds like 1ms of sample buffer looping) This is the.exact. symptom I had in Windows 7 x64 and it only seems resolved if I use the 'legacy' driver. So my expensive imported FW controller card was a waste.sigh. Is there any hope? I don't really like Windows 8 but I.NEED. it because of the acessibility features, I really struggle with my eyes, some of the new features in Win8 are really helpful but I don't wanna part with my RME.
Hopefully m$ or RME can fix this eventually. I've read that Win8 Consumer Preview of Dev Preview had the legacy drivers. Trying to find copies of the discs to see if I can obtain them from there. Thanks for the quick response! Already set to High Performance and I've disabled the Speedstep/cpu scaling options in my BIOS. Also tried resetting all my TotalMix/Fireface control panel stuff and starting from scratch, no joy.
Tried different outputs 'Speakers' which is analogue 1+2 or analogue 7+8 etc; no change. Summary is: I've been on 3 different FW controllers (two VIAs and not my TI) Two OS's (Win7/8 x64) I can safely say it's not the controller chips but it does seem to be the firewire driver or the interaction between RME's drivers and the FW driver, my RME, once using the 'legacy' driver will run perfectly for days on end without a single hitch. As you can conclude from the above user the problem seems to lie in the motherboard, either its basic design (where is the FW chip and how connected to) or the BIOS implementation. Has been the same for several years. A critical design like that then reacts on all kinds of changes - different FW driver, different audio interface driver.
But we have never seen differences between the FF 800 and FF 400 in such a case. They do not use the same controller (obviously, FireWire 800 is more expensive), but are both TI and therefore similar for sure. MC wrote: As you can conclude from the above user the problem seems to lie in the motherboard, either its basic design (where is the FW chip and how connected to) or the BIOS implementation. Has been the same for several years. A critical design like that then reacts on all kinds of changes - different FW driver, different audio interface driver. Hey M.C Seems a little more involved than anything at the motherboard level actually, he is also using SIIG FW controller card which has been my go to as the current motherboards have culled TI onboard, so its worth looking into further. I'll setup a SIIG on the older X58 dev system instead of using the TI onboard under Win8 and check my reference FF800 when I get some clear air this week, and also try and get in front of one of the X Series units to see how they behave.
This will effect all of my current systems if its a problem.:-( So far Win 8 = Vista II for me. LOL Heres hoping M.S have the sense to continue to offer Win7 OEM for a very long time. Edit: RME FF400 driver: v3.069 Firmware: 1.70 edit2: Saw I was on firmware 1.70, updated to 1.71, powered off the RME, confirmed the flash OK - still the same problem.
Things I've tried since. Power Manager: Set to High Performance (I always do this anyway) - BIOS: Disabled all CPU throttling/scaling etc; - BIOS: Spread Spectrum enabled/disabled makes no difference - BIOS: Onboard soundcard is disabled - Onboard VIA VIA 6315N / TI card no difference - Works.perfectly. using Legacy driver (from post #1) on.both. my onboard VIA fw controller / TI card. Disabled the onboard VIA controller while I'm using the TI card. MC/RME - would this be of any use to try? It describes various registry settings that effect the new firewire driver but I'm not a developer guy so these strings don't make a lot of sense to me.
Google doesn't show anything useful. More info: TAFKAT, thanks for the assist.
Btw can you elaborate on Win8 having the legacy fw driver in previous builds? I looked at the Consumer Preview and Dev Preview ISOs and the files for the legacy driver are not there. Funkyspacecadet wrote: edit:TAFKAT, thanks for the assist. Btw can you elaborate on Win8 having the legacy fw driver in previous builds? I looked at the Consumer Preview and Dev Preview ISOs and the files for the legacy driver are not there. I was actually going on your info that the Developer/Consumer builds may have had it. I have a friend who is a dev at M.S, I might call in a favour and get him to help us with sorting the signing of the earlier legacy FW driver.
No promises but worth a shot. Timur Born wrote: One thing to mention is that the non legacy FW driver in Windows 8 seems to be better (less CPU load) than the one in Windows 7.
Of course that doesn't help those people who cannot get their hardware to work with it. My LSI/Agere based FW ports work fine with any of these drivers. With a FF400? It's a bit of a gamble and I'd probably have to import another FW controller card to test it myself. All I do know is that I've always had to use the legacy FW driver with my current and old PC (VIA onboard and SIIG card with TI chip). Albeit I have access to a dozen PCs, none of these offer a combination of FW + Windows 8 (most don't offer FW even). But in the past I used a FF400 connected to a TI based FW400 onboard port under Vista without having to use legacy drivers.
The question is, what exactly do you want me to test on another machine? I had several generations of Macbook Pro and the LSI/Agere FW ports always worked without having to use legacy drivers. On Windows 7 the non legacy drivers produce more CPU load, though, which may have an impact on desktop systems. On my laptop it doesn't matter in practice, because under high load the CPU has to throttle its maximum Turbo Boost multiplier down (due to Intel's average wattage limits, not necessarily temps). This leads to equal performance with both FW drivers after running performance tests for a few minutes. On Windows 8 the non legacy drivers uses less CPU (and so does the Audio Endpoint service, which causes other problems).
Again, this might have an impact on desktop systems, not so much on my laptop. Timur Born wrote: Albeit I have access to a dozen PCs, none of these offer a combination of FW + Windows 8 (most don't offer FW even). But in the past I used a FF400 connected to a TI based FW400 onboard port under Vista without having to use legacy drivers. It seems fairly random then. On my current and old machine, the FF400 only worked properly with the legacy driver on Win7/8. Both previous machines had onboard VIA fw chips and I'm currently using a SIIG FW400 card which changed/improved nothing. I guess there's no point in you testing since it seems fairly random.
I'll look for an LSI based card perhaps. Timur Born wrote: All I can tell you is that my LSI/Agere based FW800 ports and a TI based FW800 ExpressCard (Sonnet) work here, both with FF 400 and FF 800 (and combination of both).
Likely all depends on the chipset (revision) and hardware implementation of whatever FW card/port you are using. Any way you can tell me which TI chip is in your FW800 Sonnet? There's a FW800+FW400 combo card I can obtain quite cheaply, it's a Vantec though. I may see if I can exchange my SIIG and try my luck with a FW800 card. Funkyspacecadet wrote: Hi, For those who are running Windows 8 and want to use their RME Fireface 400/800 cards (and other brands of FW cards should apply) and need to use the legacy firewire driver please try these steps. DO THIS AT YOUR OWN RISK, BACKUP FIRST, DO NOT TAKE ADVICE FROM STRANGERS ON THE INTERNET AS GOSPEL.
HUG A KITTEN. Get yourself access to a Windows 7 computer, if you are running Win8 32bit then you need Win 7 32bit, if you are running Win8 x64 you need files from a Win7 x64 computer. Locate these files from a Windows 7 machine: c: windows inf 1394.inf c: windows inf 1394.pnf c: windows system32 drivers 1394bus.sys c: windows system32 drivers 1394ohci.sys c: windows system32 drivers ohci1394.sys Copy all these files into a folder of your choice on your Windows 8 computer. Then follow this guide on how to reboot without driver signing enabled: Once you have rebooted with driver signing disabled you can proceed. You can then go into Device Manager: 1. Expand IEEE 1394 Host Controllers 2. Right click on your firewire controller and choose Update Driver Software 3.
Click 'Browse My Computer for Driver Software' 4. Click 'Let me pick from a list of device drivers on my computer' 5. Click Have Disk 6. Click Browse 7.
Browse to the folder where you placed the Win7 FW drivers and click Open. You can then install the 1394 OHCI (Legacy) driver. Windows will warn you about unsigned drivers, just accept and continue the install.
Via 1394 Ohci Windows 7 64 Bit Drivers For Mac
You will need to reboot, most certainly using the unsigned driver / advanced boot method from the link above. NOTE: The only problem I'm having is that I have to repeat the bootup process every time I reboot to have audio.
The RME Fireface 400 drivers don't seem to play well if I use any other firewire driver. The legacy works - so far, perfectly for me. So far this driver is working flawlessly. RME mods/devs - is it possible for you to use your position with Microsoft as developers to try get this driver back into Windows 8 or offer us a solution? I had similar problems in Windows 7 and only the Legacy FW driver resolved the issues for me. I hope this helps someone. I can fix the signed issue making you reboot into unsigned mode each time.
You can enable test mode in Windows 8 which will remain persistent on reboots, however although test mode will load self signed drivers it will not load unsigned driver. I'll talk you through enabling test mode and self signing the drivers. Follow funkyspacecadets excellent guide to installing the legacy Windows 7 driver. (Thanks for this, this has brought my CPU usage down but I'm still getting glitches) Once you have installed the legacy driver in unsigned mode, reboot, the driver will fail to load and you will have no sound. Open command prompt as Administrator. Run the following two commands, both should say The Operation Completed Successfully (if not you probably didn't run command prompt as Admin) bcdedit -set loadoptions DISABLEINTEGRITYCHECKS bcdedit -set TESTSIGNING ON Download this (if for any reason this link dies then google dseo13b.exe) Run the download and choose to sign a system file. Type in C: Windows System32 DRIVERS 1394bus.sys Click OK and the file will be signed for use in test mode.
Run the program again and choose sign a system file Type in C: Windows System32 DRIVERS ohci1394.sys Reboot and voila, the drivers load and no need to keep rebooting into unsigned mode. This obviously reduces the security of your PC by allowing any self signed driver to install so don't blame me if you get some malware from being careless. Hope this helps people!! Wireshark 1.6.0 (64-bit download for mac windows 10. PS I only tried this on Windows 8 Pro x64 - I assume its the same for 32-bit but haven't tested. Not sure that would be related to be honest, I was still having glitches even after enabling the legacy driver, although a lot more often than you (every minute or so).
Funkyspacecadet pointed me to for the Thesycon IEEE1394 driver. My chipset is Ricoh, and there wasn't a Ricoh driver in this package, but I forced the use of the Texas Instruments driver anyway to try it out and haven't had a single audio glitch since. It has introduced a problem with TotalMix where the level meters keep freezing for a few seconds every 10 seconds or so, and whilst frozen you can't adjust any controls in TotalMix. But I'd rather have glitch free audio and loss of totalmix than a working totalmix and glitchy audio. Funkyspacecadet is not getting the totalmix issue and is using the same Thesycon driver as me, but his chipset is TI rather than Ricoh.
Bloody firewire!!! Benofishal wrote: Not sure that would be related to be honest, I was still having glitches even after enabling the legacy driver, although a lot more often than you (every minute or so). Funkyspacecadet pointed me to for the Thesycon IEEE1394 driver. My chipset is Ricoh, and there wasn't a Ricoh driver in this package, but I forced the use of the Texas Instruments driver anyway to try it out and haven't had a single audio glitch since. It has introduced a problem with TotalMix where the level meters keep freezing for a few seconds every 10 seconds or so, and whilst frozen you can't adjust any controls in TotalMix. But I'd rather have glitch free audio and loss of totalmix than a working totalmix and glitchy audio. Funkyspacecadet is not getting the totalmix issue and is using the same Thesycon driver as me, but his chipset is TI rather than Ricoh.
Bloody firewire!!! You are a life saver!!!! I was having the same problems on my machine.
Installed the Thesycon IEEE1394 driver and it solved all my problems!! Thanks so much for posting this. BTW - I am not sure what the chipset is on my firewire card but out of desperation I tried it and voila Thanks again Steve. Hi funkyspacecadet! Thanks for your whole work on this topic!!!!!!!
Unfortunately I still couldn´t find a 100% solution. I´d like to ask if you could provide me with a 64bit legacy driver. What I´ll do: I ordered a FW Expresscard with the LSI FW 643 chip.
Via 1394 Ohci Windows 7 64 Bit Drivers For Mac Windows 10
Very interesting article that led me to that about fw chips here: I don´t get error free results using my buit in JMicron FW chip, neither with my FW expresscard for Dawicontrol, using TI chip XIO2213A. I also tested another FW expresscard with an different TI chip, even worse. Best configuration yet: unsigned legacy driver (i´m not sure if the one i have is 32bit) with Dawicontrol FW card, but still audio hickups, but fewer than in other cofigs. Also tried the Theysicon drivers, didn´t work. Thanks in advance for any recommendations! HP Elitebook 8750W Windows 8 / 64bit Built In FW port Expresscard Dawicontrol FW 800 (Texas Instruments Chio) RME Fireface 800.