HELP! Can someone send me the firewire legacy driver for Win7?

http://social.technet.microsoft.com/Forums/en/w7itprohardware/thread/65cb7a25-2a84-4875-aa27-b084537e8da1

from what I gather it should be included with win 7..

is your firewire chipset a Ti one ? if not that might be the problem.

Hi, those are not included in my win7 installation. i already tried the suggestion above, they are not there.

that's why i would love for somebody to send me the file via mail...

Msi motherboard, firewire via chipset compatible to my audio interface.

It's not a T.I., it's a "VIA" firewire chipset.  The legacy driver may only be available if you have a T.I. chipset.

But I also agree that not having a T.I. chipset is probably most of the problems.

Fog


so the firewire is onboard and *NOT* Texas instruements,  by "via" or someone.. maybe thats the issue?

I had that problem with a USB card , that didn't use an NEC chipset.. and it didn't do what it was supposed to and I'm guessing that your chipset isn't Ti and thats the problem..

I don't think anything but TI is crap. In my test of 4 different firewire boards, 3 with TI and one with VIA chipset the VIA worked just fine and with less cpu consumption actually.

Sonar had problem with TC Eletronics drivers for Impact Twin(transport took 2-3 tries before it ran), but Focusrite Saffire Pro40 ran just fine.

Very important overall that firewire cable was good quality and not having any tension at all, or audio would start to fail. Tiny bend with my terminal table towards wall was enough to make it crack up.

Okay, to clarify: i have a fire wire pci express card for audio. Via chipset on the pci card. My audio interface is supposed to work best with ti OR via chipset using the legacy driver. (according to tc electronic forums, the manufacturers of my audio interface)

So it is possible to have a via firewire card AND use firewire drivers. Can nobody locate them on their harddrive and mail the file to me?

cyphersuit


Can nobody locate them on their harddrive and mail the file to me?

I'm not a computer guru, so I'll admit that I may be wrong but I don't think finding the driver and emailing it to you is going to solve your problem.  From what I think I know, the driver is part of a whole package of files, including an installation file that is specfic to the driver.  You need to have the whole package in order to have it installed where it needs to be and properly set up in the registry. 
 
Tom gave you the correct instructions for locating the legacy driver and I'm not sure why it isn't there.  Microsoft provided the legacy driver in all flavors of Windows7 for backwards compatibility with Firewire device drivers that are not compliant with the new Windows 7 1394ohci.sys driver architecture. 

lfm

 I don't think anything but TI is crap. In my test of 4 different firewire boards, 3 with TI and one with VIA chipset the VIA worked just fine and with less cpu consumption actually.

Sonar had problem with TC Eletronics drivers for Impact Twin(transport took 2-3 tries before it ran), but Focusrite Saffire Pro40 ran just fine.

Very important overall that firewire cable was good quality and not having any tension at all, or audio would start to fail. Tiny bend with my terminal table towards wall was enough to make it crack up.

I just like an easy life, that sound card is discontinued also? . the driver should pick up in windows regardless *IF* it's finding the right chipset on that card.

A Ti based card would fix the issue and be found.. instead of using some consumer grade firewire chipset that's for hooking up an external drive / camera to. how much is that Ti interface, $50 or something.. so not gonna break the bank.

it reminds me of my friend abroad who raved on about RME card, and top end MOBO.. RME card was great (and yer he's german, so slightly biased anyway hehe) .. anyway in his case his "top end mobo", firewire I told him to replace the firewire.. and it worked .. it only took him 2 days of wasted to realise I was talking sense

I'm surprised TC haven't suggested that.. 


speccy should tell you the chipsets hopefully

http://filehippo.com/download_speccy/

the tool speccy didn't list the pci-e card at all?!? i will try to connect my audio firewire interface to the mainboard now, we'll see if that changes anything for the better.

Fog



I just like an easy life, that sound card is discontinued also? . the driver should pick up in windows regardless *IF* it's finding the right chipset on that card.

A Ti based card would fix the issue and be found.. instead of using some consumer grade firewire chipset that's for hooking up an external drive / camera to. how much is that Ti interface, $50 or something.. so not gonna break the bank.

it reminds me of my friend abroad who raved on about RME card, and top end MOBO.. RME card was great (and yer he's german, so slightly biased anyway hehe) .. anyway in his case his "top end mobo", firewire I told him to replace the firewire.. and it worked .. it only took him 2 days of wasted to realise I was talking sense

I'm surprised TC haven't suggested that.. 


speccy should tell you the chipsets hopefully

http://filehippo.com/download_speccy/

Yes, firewire is made for completely different devices, that can be bursted in chunks. It's not made for continuous realtime data at all.

And the drivers I tested was poorly written in the sense that it does not allow for less data and cpu consumption using less of the inputs/outputs. If you have to transport 10 input plus 10 inputs all the time, whether they are used or not - it's a waste of cpu. The drivers ran 4500 context switches per second, and that is a lot comparing to anything going on in computer. Overall 7% of new i7-computer just keeping audio up. This was just turning the soundcard module on.

I found the connectors very poor design, very long contact surfaces and slight bend caused instability in stream.

Your RME story I did not understand the point of at all. He had an RME card he was happy with and you told him to change firewire card? Was RME card firewire and not internal soundcard, or?

I went RME internal card and are not looking back for firewire anything. Any host in future will have RME or Lynx internal cards. I want to focus on music and not technology failing me.

first firewire is tc electronic second is onboard didn't manage to embed the image here. edit: connecting my tc electronic to the motherboard (instead of the pci express card) strangely seems to have bettered everything. watch this space :)

lfm
Your RME story I did not understand the point of at all. He had an RME card he was happy with and you told him to change firewire card? Was RME card firewire and not internal soundcard, or? 

I went RME internal card and are not looking back for firewire anything. Any host in future will have RME or Lynx internal cards. I want to focus on music and not technology failing me.

my point with the RME story is he had a great card.. and a decent enough mobo BUT the firewire chipset on that card was crud.. *THATS* what was letting him down, with everything.. instead of messing around for days and getting nowhere he could have just bought the Ti card, and got on with music making.

he didn't like to tell me that I was right about it about it 2 days earlier... as he was so SURE prevoiusly and well I wasn't telling him it for the sake of telling him.


I'm assuming if a Ti Card will perhaps mention it's make mode in the device manager sig? 


I don't use firewire, I either use pci or usb , but well the OP either needs to sort out a Ti card or ditch that interface altogether.. been there , done that, got the t-shirt with my dsp factory in the past.