Did Win7 take care of firewire driver issues

(Asked this on the software forum but didn't get any response.  I'll ask it here too)

By this I'm asking: XP sp2 and later was such that the firewire driver would not work with 2 firewire interface daisy chained and those of use with those configurations had to resort to 3rd party drivers.

Did Win 7 resolve that issue?

In XP I need to use the AVT drivers with my two MOTU head.  Would like to think if I upgrade to Win7 I could get rid of them,.. An results or observations?

Focusrite says the legacy firewire driver needs to be used in Win 7, but when I upgraded to Win 7 I forgot about that and installed my Focursrite Saffire Pro 40 using the "regular" firewire driver and it's working without problems.  My motherboard is an Intel and it has a T.I. Firewire chip.

(I'm an ex-KCer)

Scott:  as I'm sure you know it was a windows problem when trying to use multiple firewire interfaces at the same time.  For me that was corrected by using the AVT firewire drivers.  I was just hoping that when I upgrade to Win 7 on my studio computer to not have to go through that whole rigmarole again.

Beagle, I think Scott's referring to xp sp1 and earlier firewire drivers.  I tried them and they did not work for me.  I went to the AVT drivers which have.

There is a very long chain regarding this over at Motunation.  I believe it has the instructions to using the old XP drivers.:

http://www.motunation.com...c.php?f=14&t=31518

and for using the AVT drivers here:

http://www.motunation.com...c.php?f=14&t=34558

And here is one with links to various MOTU drivers:

http://www.motunation.com...c.php?f=14&t=35607


I'm still not hearing that this is solved for multiple interface firewire users.  Did I miss something?

Here's a link for setting up the "Legacy" driver in Win 7
http://deeringamps.com/fw1884/sonar_fw1884.htm

funny i was just QAing a system yesterday with a Motu. it kept dropping (as in windows not seeing it)
once i switched to legacy, issues fixed.

frankly i have never liked motu drivers

funny i was just QAing a system yesterday with a Motu. it kept dropping (as in windows not seeing it) once i switched to legacy, issues fixed.

 
FWIW, The newer driver has (or at least had) a compatibility issue with some TI chipset FW controllers.
The TI controller worked fine with previous drivers... but was flakey with the new driver
Swapped out the controller (for a different TI unit)... and all was good.
 
Prior to this latest series of drivers... it seemed MOTU was going backwards (higher RTL, etc).
 

"""I've love the hardware but the support from Motu for Windows is like that of a bastard child"""

LOL i hear ya  funny story...
back in like 99 a buddy from my church asked me to build him a "DAW"  i am like huh?
a computer for audio.... ok i say.  well how hard can it be i am thinking to myself... (at that time we only did gaming rigs and a few basic video editing systems... my experiance back then was a sound blaster and cakewalk like 4? le that came with the sound blaster)
Guy owns one of the original mark of the unicorn...
windows drivers were not the best back then and we are taking about windows 98 again not the best..

long to short 3 subsystems later (mind you i am basically doing this for free other then him paying for the parts)
i finally get the motu recognized and synced.

i swore then i would never build another DAW.. all because of the MOTU. also i refused to sell Motu until just a few yrs ago
(got tired of people shipping me thiers from competitors to have installed)
glad i recanted!