abacab
The Win10 device driver for FireWire is already included [Texas Instruments 1394 OHCI Compliant Host Controller] with Windows 10.
 
I remember having to install that driver separately when using Win7.  But Win10 found and installed my PCIe FireWire card automagically.
 
You will also need a driver (audio device driver) for your audio interface from the manufacturer [Focusrite]. 
 
My suggestion would be to see if Focusrite has a Win7 or 8 driver for that interface and try it.  As with my M-Audio experience, using a Win7 driver can be good under Win10. 

Thanks. The FW card works fine (as far as I can tell. Windows says it's enabled and working, but I have nothing to connect to it except the Saffire, and it ain't talking), it's the Saffire drivers that don't work.
Tonight, I tried something else; when installing the driver from the disk there is supposed to be a pop-up during the installation to "Continue anyway" when a Windows notice about unsigned software pops up. I get neither the Windows message nor the "Continue anyway" message, and the driver doesn't load.
So I thought maybe there was something in the Win 10 security overzealousness which was preventing the pop-up from... popping up. I disconnected from the internet and turned off all the UACs I could find, including virus scan, and that didn't work, either.
Went to the Focusrite sire and downloaded the 2.7 driver, again, same result. I must be crazy, if you go by the definition of insanity, "doing the same thing over again and expecting different results", but I sure would like to continue using the same interface on each of my machines.
I guess I'll have to do that with a new FW device.  

I should add that I ran it (many times) as administrator, and tried all of the compatibility modes, ran the comp. troubleshooter with recommended settings, too.

One other quick comment about that card above, there is a power supply connection (4-pin from the computer P/S) on the end of the card to provide power to units which get power from the FW cable itself (i.e., no wall wart). Initially, I had installled the card without that, and although the unit ran, it had EMI noise from the GPU. I did the Win8.1 driver install from the above post (it does seem a newer build), but the EMI didn't go away until it had an active P/S connection.
 
I wanted to throw that out just to make sure you have that P/S connection made if your Saffire is powered from the FW cable itself (it may not come on otherwise). Be sure to power off the computer at the plug if you are making/breaking that P/S or FW connection though so you do not send a voltage spike to the unit.

FWIW, The 4-pin Molex power connection on the Syba Firewire controller is there to provide bus-power for using bus-powered Firewire devices. 
 
For audio interfaces, I'm not a fan of bus-power... as it often compromises fidelity on the mic preamps.
If you're not using bus-powered Firewire peripherals, there's no need to connect power.
 

Thanks, Jim. The Saffire came with a wall wart; it's still in the box, unwrapped after all these years.
The computer I use it with came with a FW card already installed (VIA, works great), so when I plugged it in when I first got it, everything worked fine so I never saw a reason to use the power supply.
I did connect the power connector when I installed this Syba card, despite you mentioning years ago to me in another thread that it wasn't necessary. But that's the only thing that works with this Saffire. The lights are on but nobody's home.
I'm looking at getting a MOTU Express, which has both FW and USB, but they seem to indicate that when using FW, you must use bus power.

I am a little hesitant to mention, but I have a Saffire too, but instead of relying on a FW card, I went the TH (thunderbolt) route and have been loving it ever since.  All I needed was a FW to TH adapter and all is fine in Win10.  If your PC is compatible with TH, I would ditch the FW.
 
Kind regards,
 
tecknot

deleted

If the audio interface doesn't have a 64Bit driver, there are *zero* workarounds.
 
Switching from a PCIe Firewire controller to Thunderbolt>Firewire adapter will have no benefit.
Even if the audio interface HAD a 64Bit driver, there would be zero advantage to using Thunderbolt>Firewire verses a PCIe TI chipset Firewire controller.
 
Thunderbolt provides access to the PCIe bus.
By very definition, it can not out-perform PCIe.
Another facet: Some audio interfaces will not be compatible with some Thunderbolt>Firewire adapters.

Jim Roseberry
If the audio interface doesn't have a 64Bit driver, there are *zero* workarounds.
 
Switching from a PCIe Firewire controller to Thunderbolt>Firewire adapter will have no benefit.
Even if the audio interface HAD a 64Bit driver, there would be zero advantage to using Thunderbolt>Firewire verses a PCIe TI chipset Firewire controller.
 
Thunderbolt provides access to the PCIe bus.
By very definition, it can not out-perform PCIe.
Another facet: Some audio interfaces will not be compatible with some Thunderbolt>Firewire adapters.

Hi Jim.  I'm not trying to pick a fight, but some of the points you made above are inaccurate (knowing you have much more experience on computers than I do).  First, a 64bit driver wouldn't make a difference, a 32bit driver would work just as well in Windows 10. Next, switching from a FW PCIe card to a TB one would be beneficial because it eliminates the conflict of TI vs DICE etc. controllers.  Further, the adapter I was referring to was one that you would use to connect a FW device to a TB port.  There was no suggestion that an adapter would "out-perform" in any fashion.  It's all about the connection, that's all.  Although some interfaces may not be compatible in this scenario, I am talking about a Saffire interface which is compatible as verified by Focusrite and by myself as this is the way I have my Saffire interface working with my PC (via the TB card).  So, I just want to clarify that.
 
Kind regards,
 
tecknot

tecknot
 
a 64bit driver wouldn't make a difference, a 32bit driver would work just as well in Windows 10

It matters.  If you run a 64-bit Windows, you must run 64-bit drivers.