Can't get thru Motu 828 install
Moderator: James Steele
Forum rules
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
Discussion related to installation, configuration and use of MOTU hardware such as MIDI interfaces, audio interfaces, etc. with Windows
-
- Posts: 2
- Joined: Tue Mar 20, 2007 11:13 am
- Primary DAW OS: MacOS
Can't get thru Motu 828 install
Hi, my Motu 828 was working fine before I did a fresh Windows XP installation. Weird.
I am trying to install the Motu 828 on Windows XP SP2 32bit. My motherboard is Asus a8v deluxe. I am connecting the 828 via the onboard firewire. (This is after installing the latest drivers). When I power on the 828 I get the "found new device" and I am about to install the Motu Wave driver but after that Windows gets unresponsive as it tries to install the second driver (GSIF or something).
If I turn off or unplug the 828 during this, I'll either get a BSOD or the computer returns to normal.
This happened when trying to install the new drivers. I tried installing the the old drivers and they work in Windows but the ASIO driver for it stopped working in Cubase. Please help!!
I am trying to install the Motu 828 on Windows XP SP2 32bit. My motherboard is Asus a8v deluxe. I am connecting the 828 via the onboard firewire. (This is after installing the latest drivers). When I power on the 828 I get the "found new device" and I am about to install the Motu Wave driver but after that Windows gets unresponsive as it tries to install the second driver (GSIF or something).
If I turn off or unplug the 828 during this, I'll either get a BSOD or the computer returns to normal.
This happened when trying to install the new drivers. I tried installing the the old drivers and they work in Windows but the ASIO driver for it stopped working in Cubase. Please help!!
XP firewire fix
I know there is a firewirefix for xp, and it's not included in the servicepacks or windowsupdate. Maybe you had applied it on your old installation? I can't remeber the KB numer now but if you search for 1394 or firewire and microsoft you will probably find it. RME also have links to it out on their web.
Joakim Lundberg (Sweden)
--------------------------------
Cubase 4.X, MOTU 828 mk3
--------------------------------
Cubase 4.X, MOTU 828 mk3
Indeed weird, and exactly what happened to me.
Im afraid what you _might_ be looking at is the issue of the onboard firewire chipset. I too had a working motu 828 that began not working with a fresh xp install. Im sorry to say those fixes for windows may indeed not work.
Reference my post "MOTU and TI Chipset- whats the deal" will tell my sad tale with a final resolution of purchasing a new firewire card (after much difficulty).
But before that, go to My Computer>Hardware>device manager and scroll down to the 1394 controllers and see what it says your chipset is. If it says VIA, Motu tech support will flat out tell you you need to get a new firewire card. Never mind your 828 was working fine before those windows upgrades. Those upgrades, you will be told "triggered" the incompatibility.
IF it says Texas INstruments, then you are not going to be sucked into the vortex I was and we'll help you to the next troubleshooting step from there.
Unless in the meantime youve fixed the problem, in which case, please share!
Im afraid what you _might_ be looking at is the issue of the onboard firewire chipset. I too had a working motu 828 that began not working with a fresh xp install. Im sorry to say those fixes for windows may indeed not work.
Reference my post "MOTU and TI Chipset- whats the deal" will tell my sad tale with a final resolution of purchasing a new firewire card (after much difficulty).
But before that, go to My Computer>Hardware>device manager and scroll down to the 1394 controllers and see what it says your chipset is. If it says VIA, Motu tech support will flat out tell you you need to get a new firewire card. Never mind your 828 was working fine before those windows upgrades. Those upgrades, you will be told "triggered" the incompatibility.
IF it says Texas INstruments, then you are not going to be sucked into the vortex I was and we'll help you to the next troubleshooting step from there.
Unless in the meantime youve fixed the problem, in which case, please share!
By the way, just re-reading your post and it looks like you powered on the 828 _before_ installing the drivers? That wont work. You must have the 828 disconnected and then install the drivers. Then restart the machine (this isnt always a necessary step, but it cant hurt), THEN you can hook up the device and see what happens.
Mucking up the order of this will cause problems from the beginning, so you should probably uninstall those drivers and reinstall them with the 828 completely out of the picture. And yes, you will see about five different drivers being installed one after the other, as they are all bundled together. That looked weird to me too, but just let the installer do its thing.
In the meantime check that chipset spec as well.
Your position is exactly the one I found myself in last week- I use Cubase also.
Mucking up the order of this will cause problems from the beginning, so you should probably uninstall those drivers and reinstall them with the 828 completely out of the picture. And yes, you will see about five different drivers being installed one after the other, as they are all bundled together. That looked weird to me too, but just let the installer do its thing.
In the meantime check that chipset spec as well.
Your position is exactly the one I found myself in last week- I use Cubase also.
http://support.microsoft.com/kb/885222
Here is the link to a windows fix, but I would try everything else first.
Here is the link to a windows fix, but I would try everything else first.
ive got the same prob installing my new mkIII this evening, gsif driver has been installing fof half an hour, nearly there, gonna see what happens, any way heres something interesting, i checked my firewire ports, motherboard one (that im not using says VIA) and other FW card says texas instruments (im using this one and it has worked perfectly with my mackie onyx FW for 2 years) should i be disabling the via FW on the motherboard or will this upset things
At least your firewire card hasn't blown two 828MKIII's
Yes thats right, I bought a texas instrument firewire card that was made by a company called Sunix, turns out the firewire card blew the firewire controllers on the MOTU, and when they declared the first one faulty they sent me another replacement and tested it and assured me it would work, then same thing happed again I blew the second one, very bad MOTU !!!
Anyways the reseller claims that there is voltage flaw on this firewire card, they have recomended an altenative to me that they assure works flawlessly with the MOTU 828mk3, so I have yet to try a third 828mk3 with this new recomended firewire card, cross my fingers.
Far out dudes, how many firewire cards do we have to go through before we can get the damm thing working....are audio interfaces always this fiddly?? far out, you know MOTU I would have been more then happy to pay extra dosh for a firewire card included in the box...
Yes thats right, I bought a texas instrument firewire card that was made by a company called Sunix, turns out the firewire card blew the firewire controllers on the MOTU, and when they declared the first one faulty they sent me another replacement and tested it and assured me it would work, then same thing happed again I blew the second one, very bad MOTU !!!
Anyways the reseller claims that there is voltage flaw on this firewire card, they have recomended an altenative to me that they assure works flawlessly with the MOTU 828mk3, so I have yet to try a third 828mk3 with this new recomended firewire card, cross my fingers.
Far out dudes, how many firewire cards do we have to go through before we can get the damm thing working....are audio interfaces always this fiddly?? far out, you know MOTU I would have been more then happy to pay extra dosh for a firewire card included in the box...
hey thats a great idea, every companies FW interfaces have issues with certain FW cards, why not put one in the box with each interface, im sure people would be happy to pay an extra 30$ just to know that its gonna work, motu mk3 running fine until i tried to adjust the sliders in the mixer panel of cuemix fx software, froze the software, soundcard and daw software, had to ctrl alt del end unresponding cuemixFX, then all was well, sound came back immediately, daw back to life, and restart cuemix and back to where i left off, im happy if i dont have to restart my DAW software, but the cuemix FX looks like it has a few bugs or incompatiblities.
im using winXPsp2 dualcore intelcpu and mackie tracktion as host software
im using winXPsp2 dualcore intelcpu and mackie tracktion as host software
This may be irrelevant, but I have had absolutely no issues with this ugly firewire card and my 828mkII:
http://www.bestbuy.com/site/olspage.jsp ... 4787927900
Using intel 935g chip mobo, xp sp2 and the above mentioned firewire fix.
...running nuendo 3 as my DAW. ....Which I can't say enough about. I was using DP and ptle on the mac, but I switched to PC/nuendo. The ASIO hardware direct monitoring is great along with the ability to use outboard gear in real time. Before, I thought PTHD was the only DAW that would do that right. It'll even compensate for an external reverb unit on an aux channel. Think about that: it has to delay compensate ONLY the sends of the channels using that aux. Well done, Steinberg.
http://www.bestbuy.com/site/olspage.jsp ... 4787927900
Using intel 935g chip mobo, xp sp2 and the above mentioned firewire fix.
...running nuendo 3 as my DAW. ....Which I can't say enough about. I was using DP and ptle on the mac, but I switched to PC/nuendo. The ASIO hardware direct monitoring is great along with the ability to use outboard gear in real time. Before, I thought PTHD was the only DAW that would do that right. It'll even compensate for an external reverb unit on an aux channel. Think about that: it has to delay compensate ONLY the sends of the channels using that aux. Well done, Steinberg.