Windows 10: 1394 (Firewire) Driver

In the Device Manager Properties of the 1394 Host Controller, under the Driver tab, under the date, should the Driver version. If not, go to the Details tab, take the drop down arrow under Property and choose Driver Version.
The latest version with Windows 10 will be 10.0.15063.0

 

Spunk, my original post shows a screenshot of my Device Manager, 1394 driver.
No one has grasped what I'm asking. What version of 1394 driver is it. Is it the "legacy" driver or is it a different version?

 

It is not a legacy, it is a Microsoft driver. Please read my post #7.

The legacy drivers were removed and replaced with a MS driver in Windows 8.

Jim *Cool

 

Forget it. Sorry I asked.

 

Did you try this?

 

In the past, there were 3 1394 drivers available, one was labeled "legacy". My point was, is the current version driver actually the "legacy" driver, but not called the "legacy" driver or is it one of the others. No one has addressed what the current Microsoft provided driver is. I see the documentation about now only having one driver and the 2006 date thing, but neither of those addresses what the currently provided driver is.

 

Wish I knew Fireberd. As you've observed, the only way to know for sure is to get all three drivers, figure out which is which, then compare with what you've got installed to see which one it matches. Perhaps you can find older versions online somewhere? I simply don't know, and apologize for my lack of further insight.
Hope you find the information you need, then tell us about it, too.
Thanks,
--Ed--

 

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.

 

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.

 

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.

Jack

 

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

 

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

 

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.

 

By the way, a lot of those dates are artificial - made old so that newer ones always sort first in a list.

 

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