You are not logged in.
In case this is not already known, Microsoft has released a hotfix for the Windows 7 firewire driver, 1394ohci.sys, to resolve an issue with data corruption or data transfer interruption during isochronous data transfers between a PC and a 1394 device:
http://support.microsoft.com/kb/981613
This is probably a good driver hotfix to install for all Fireface 400/800 users with Windows 7 PCs. Link to download the hotfix is provided at the upper left of this KB article.
Offline
Thanks alot for the information! 
Offline
Thanks for that one. We were not aware of this issue nor of any upcoming hotfix. Will be interesting to see if some users get better with that one.
On the other hand it is disappointing that the main bug that we discovered (and which forced us to implement a workaround in the latest firmware) is still not fixed. Well, it should be included in SP1. Let's hope so...
Edit: as noted this (1394ohci.sys) is an update for the new W7 internal FireWire driver. If you changed to Legacy (Alt) then you use a different driver (ohci1394.sys) and will not notice any change.
Offline
thanx
gonna try it. This bloody soundcard is driving me crazy in win 7 64. Keeps dropping out. hope this fixes it
/
Offline
If you want to try it, maybe you should use this one:
http://support.microsoft.com/kb/2315295
From a search on microsoft's site it seems to be the most recent 1394ohci.sys available...
Offline
For those who didn't notice: One of the fixes included in the latest hotfix can affect us audio interface users.
http://support.microsoft.com/kb/982669
Seems as if there was a memory leak in the Firewire driver when it's used with isochronous (audio/video) interfaces.
Offline
Timur wrote:
For those who didn't notice: One of the fixes included in the latest hotfix can affect us audio interface users.
The hotfix I posted above is more recent that the one you have just posted, so it includes that fix in addition to a few others.
Offline
Yes, but I wanted to point out the "memory leak" issues, which is why I linked to the hotfix. 
Offline
Sorry, I misunderstood your post. I thought you were saying that the latest fix was the one you linked...
I also noticed that fix and thought it would be important for us, but then searched for the most recent and linked that instead. 
By the way, a new search gave me a new link that might also affect us. However, this is not a downloadable hotfix, but tips to overcome the potential problem described. Only RME could tell us if this would be a problem for us...
http://support.microsoft.com/kb/2450963
Offline