Page 1 of 1
New PC for Ultralite MK3 : guideline for Firewire Chip
Posted: Mon May 03, 2010 4:16 am
by Ultrabra
I am getting a new PC custom-built, and will use it along with my Ultralite Mk3.
Can someone give some guideline on the Firewire Chip that I can pass to the builder of the PC so I can be sure it will be compatible.
And any other suggestions/advice on anything additional I could tell to the builder of the PC, that will make sure my Ultralite works as smoothly as possible.
Thanks
Re: New PC for Ultralite MK3 : guideline for Firewire Chip
Posted: Mon May 03, 2010 7:32 am
by RonaldDumsfeld
I can only tell you what works for me and maybe others will chime in.
ASUS P6T Deluxe Vn2 mobo which uses a VIA VT6308P Firewire controller chip. Never given my any trouble in that regard.
You should be able to check what type of IEE 1394 (FireWire) controller is installed on any board you propose to purchase by looking it up on the manufacturers website. If you cannot then buy another board. Or a Mac

Re: New PC for Ultralite MK3 : guideline for Firewire Chip
Posted: Mon May 03, 2010 11:37 pm
by Ultrabra
Thanks for the reply.
I checked that motherboard out on the ASUS web site. Previously I was working with a PC with another ASUS board along with my Ultralite Mk3 : ASUS P5Q Pro, which had LSI®L-FW3227 controller. MOTU do say on their web site the firewire should have TI or LSI chip. I had a few issues with this set up, but I could not say 100% it was down to the Firewire set up. Your board (according to the web site) has a VIA® VT6308 controller. I've no idea what the difference between the 2 boards, and these 2 controllers are - any idea?
Re: New PC for Ultralite MK3 : guideline for Firewire Chip
Posted: Sun May 09, 2010 7:03 pm
by WayneM
Use this firewire card and you will have no problems Pyro AV Turbo 3 Port 1394a/Firewire 400 PCI Card
http://www.pyroav.com/products/PVC-315/ ... tails.html" onclick="window.open(this.href);return false;
or the PCIe version
http://www.pyroav.com/products/PVC-316/ ... tails.html" onclick="window.open(this.href);return false;