1394 (Firewire) Driver Solved

Page 3 of 4 FirstFirst 1234 LastLast
  1.    28 Aug 2017 #21

    Ed, its not earthshaking if I don't find out. One of those "nice to know" things. Nothing you or others have posted leads to the answer, which apparently is only somewhere deep in Microsoft.

    The current driver works perfectly, at least with my MOTU 896Mk3 Hybrid recording interface, and it led me to wonder if this is actually the legacy driver. I've seen the same question on recording forums.
      My ComputersSystem Spec

  2.    31 Aug 2017 #22

    Fireberd, I saw your post on the Sonar forum. I know exactly what you are talking about.
    I have had the Saffire Pro 14 for some time and originally used the older legacy firewire driver.
    Some time later Focusrite recommended using the standard windows driver, if I recall correctly.
    My memory is fuzzy, but I think I switched from legacy firewire driver to the standard windows driver.
    I wish I could be more exact, but at any rate I use the one that was shown above earlier:
    MD5: AAB860A5E606B9621E130D8C29D3F305
    version: 10.0.15063.0

    This one is NOT the former legacy driver which I think was in Win 7.

    I think...

    Sorry for not really helping.

    In my case, both worked fine. I only switched when Focusrite had an update and mentioned something about the driver. It may have been during the Win7->Win8 upgrade timeframe.
      My ComputerSystem Spec

  3.    31 Aug 2017 #23

    Jim, I used the "new" driver in Win 8 for the Saffire Pro40 I had at the time and worked OK. When I installed Win 8 I forgot to change to legacy driver and it worked OK. According to reference docs earlier in this thread the drivers were reduced to one driver in Win 8.1, but no one knows if it was the legacy driver "renamed" or if it was a different driver.

    BTW, I don't think the guy on the Sonar forum that is trying to make it work through the Thunderbolt adapters is ever going to get it working.

      My ComputersSystem Spec

  4.    01 Sep 2017 #24

    I did a search and I think this may be the original legacy driver.
    You could download it and see if it is.
    I downloaded, but the driver is not easy to extract (like with 7-zip) so I didn't look further:

    1394 OHCI Compliant Host Controller (Legacy) Drivers Download for Windows 10, 8.1, 7, Vista, XP
      My ComputerSystem Spec

  5.    01 Sep 2017 #25

    I wonder where they got those. The "official" Microsoft driver has a 2006 date (V10).
      My ComputersSystem Spec

  6.    01 Sep 2017 #26

    I don't know, but there are lots of those types of sites that accumulate drivers.
    Some of them seem to get them from vendor-supplied software delivered in finished products, like laptops and desktop driver download sites.
    I'd be pretty wary of using them without careful scrutiny, but in some cases I found them useful.
      My ComputerSystem Spec

  7.    01 Sep 2017 #27

    fireberd said: View Post
    I wonder where they got those. The "official" Microsoft driver has a 2006 date (V10).
    By the way, a lot of those dates are artificial - made old so that newer ones always sort first in a list.
      My ComputerSystem Spec

  8.    01 Sep 2017 #28

    Here is the reason for the 2006 date on "official" Microsoft drivers.
    Why are all Windows drivers dated June 21, 2006? Don The Old New Thing
      My ComputersSystem Spec

  9.    02 Sep 2017 #29

    I've been jogging my memory and I think I remember the history, but I could be wrong.
    Firewire was mostly adopted by video enthusiasts and then later by the audio industry.
    There were 2 versions 'a' and 'b' - a = 400 Mbps, b= 800 Mbps.
    The legacy driver had something in it for the 'b' version that later drivers lacked.
    So there was controversy over chipsets - VIA versus TI or whatever - and they may have used different drivers.
    All this is hazy, but I think that eventually Microsoft merged everything together in the Win 7 or 8 driver.
    So now that Firewire is 'dead' all the problems should be resolved.
      My ComputerSystem Spec

  10.    02 Sep 2017 #30

    It developed at same time as USB as they are closely related.
      My ComputersSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast

Related Threads
Hi all, My JMicron JMB35x LUN0 IEEE 1394 SBP2 Device (EOS_DIGITAL CF Card) keeps ejecting. In Computer Management > Device Manager the installed driver is the latest YTD and of course I already assigned a drive letter to it. When trying to...
I have installed in my system drivers for my Gigabyte P45-775-UD3-rev1.0 on-board firewire port dated to 2006. 123735 Any ideas if there is a newer driver around?
Hi good people, So, I'm on here like thousands of others with intermittent wifi issues. I upgraded from 8.1 to 10 yesterday and everything works very well except for losing my wifi connection every 30 minutes to an hour. My wireless adapter...
Firewire (1394) for Windows 10 in Drivers and Hardware
Buongiorno a tutti, Ho un problema , ho appena inserito la scheda Firewire. Ho windows 10. Sulla gestione dispositivi compare OHCI e ho installato il drive OHCI 1394 Legacy e aggiornato. Ma quando collego il cavo dalla telecamera SONY...
Cannot see my Lacie Firewire drive in Drivers and Hardware
I have a fire wire Lacie external fitted, working well with prior versions. Now can't see the drive in Win10 - whether file explorer of for saving files Is a Firewire connection a problem?
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 06:34.
Find Us