I've been using the FW1884 (Tascam) for a few years and it has worked flawlessly. I decided to try to upgrade from Win7 to Win8 (both 64bit) and it has been working almost flawlessly as well - but a few times it does not "sync" the firewire. 
I have not been able to use the "legacy" FW driver, as it has been taken out of Win8 (way to go Microsoft...)

Tom has a nice walkthrough on his webiste (which basicly leads to this RME forum writeup), but I'm not able to do that. Even if I disable the "un-signed  driver check at windows startup", I get the error message that this driver can not be used by Windows. 


Anyone have a clue? 
What can I do to override this? 
Or is there any way to get the driver "signed"? 

Kris,
I just re-read the RME posting; I'm confused.
"DISABLE_INTEGRITY_CHECKS" is NOT working for you?

Precisely why I will NOT be moving to Win 8 anytime soon...
Who needs "touch" anyway?

Tom

Yes I know Tom - I'm not a 100% if I want to keep Win8. But it plays perfect besides the firewire sync issue, which also dont happen a lot. So my thought is if I can get this working with Win8, my DAW with FW1884 has suddenly several years left :)

My problem is:
(I do this)
-Copy all these files (win7 legacy drivers) into a folder of your choice on your Windows 8 computer.
Yep. 
Then follow this guide on how to reboot without driver signing enabled: http://www.windows7hacker.com/index.php … -windows-8 Yep. Once you have rebooted with driver signing disabled you can proceed. 
Yep. 
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. 8. You can then install the 1394 OHCI (Legacy) driver.  9. Windows will warn you about unsigned drivers, just accept and continue the install.

Yep. But when I do this last step, it warns me, I accept and it still gives me the same error message as before. 


The "disable integrity checks" thing as you say Tom, isnt that after it has been succesfully installed?

Kris,
I guess you are right, the "integrity checks" is after the "un-signed" install.

I don't know, hopefully someone will give us a heads up.

I (We) would love for the 1884 to work in Win 8.

Matt and Keith are you out there?

T

DeeringAmps


Kris,
I guess you are right, the "integrity checks" is after the "un-signed" install.

I don't know, hopefully someone will give us a heads up.

I (We) would love for the 1884 to work in Win 8.

Matt and Keith are you out there?

T

Acoording to the RMS thread, it is. But I just found this on the Tascamforums!


by jason5804 » Sun Feb 03, 2013 12:16 pm
YES. after many hours searching the web for a resolve i managed to get tascam fw 1884 working as it should under windows 8.this is how i did it on a 64bit win 8 system. firstly run cmd as administrator then type the following and enter/ exit bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS then follow these instructions from http://www.rme-audio.de/forum/viewtopic.php?pid=81012 then install fw1884 exe by right click and choose properties/compatibility/then run the trouble shooter/troubleshoot program/tick worked in previous/tick win 7/run and load successfull. if youve followed this then it should mean you now have fw1884 working correctly without having to disable signature on every boot.

Well, I managed to install the Legacy driver now - it was a bit unclear how to do this :)

Because of this: 
"Once you have rebooted with driver signing disabled you can proceed. "

The clue is, when you choose this it is only once.
So the next time you restart driver signing is enabled again (I didn't catch that one...)

So, I tried again and voilà - legacy driver installed. 


I have serious issues besides that though. 
I decided to chech my latencty before I installed the legacy driver, so with DPC latecy checker it is somewhat stable around aprox 1000mUs!

This is FAR more than I had with my Win7 setup, if I remember correctly was about 100?
(sorry - quite a time since I had it up and running, maybe a year)


- Disabling 1394 FW in the BIOS does not affect the latency.
- LAN, USB3, eSATA, internal audio, and other unnecessary things are also disabled in the BIOS.

Strange part, is when I check with Latency Monitor it says it is fine...
But I can see my Nvidia uses the most - so I'll try to change the PCI slot for this. 
And also upgrade the drivers for it.

Kris,
Thanks for all the updates.
Its all about drivers, isn't it.
Is Win 8 really worth it?
I know there are a handful pushing the bleeding edge,
and reporting good results; but at what cost?
I'm getting too old to try and balance the "left" brain, "right" brain stuff.

Good luck!

T

Yes Tom, some of us have to sacrifice so the rest can follow when the solution is ready :)
You know this :)

But I'm not giving up already. 
I'm not convinced it is the drivers, or should I say yet... 


It has nothing to do with the Firewire, is has the same DPC latency with:
- FW disabled in BIOS
- FW with legacy drivers
- FW with standard W8 drivers

I have disabled HPET in the bios just now. Same result.

I changed the PCI slot for the graphics card, nothing changed. 
the DAW did not like that the first boot though, I got a reboot and also Windows was not sure I had activated... 

Could it be something with shared IRQ's? 

Forget it...
Just googled windows 8 DPC latency...

And came to the developers site:

Windows 8 Compatibility:[font="arial, helvetica, verdana; line-height: normal"] The DPC latency utility runs on Windows 8 but does not show correct values. The output suggests that the Windows 8 kernel performs badly and introduces a constant latency of one millisecond which is not the case in practice. DPCs in the Windows 8 kernel behave identical to Windows 7. The utility produces incorrect results because the implementation of kernel timers has changed in Windows 8 which causes a side effect with the measuring algorithm used by the utility. Thesycon is working on a new version of the DPC latency utility and will make it available on this site as soon as it is finished.

So good news - it should be working nicely :)

My only problem now is to make the legacy driver to work at every boot. 

AFAIK, it uses the new win8 driver when you dont boot with the "special option".