"No MOTU FireWire Audio could be found" - Install

[TonyVT]

Hello,

I have seen similar problems regarding "No MOTU FireWire Audio could be found", and their solutions. I am having the same problem, however, I am not able to have a successful outcome.

I am using an Apple iMac Intel Core-Duo and operating in the Windows XP SP2, via Bootcamp. Note: My 828mkII is working perfectly while operating in the Mac OS X environment.

This is what I am doing: (In Windows)

1 - My 828mkII's firewire cable is unplugged
2 - I use the installation CD to invoke the Windows setup for my 828mkII
3 - I restart as prompted
4 - I then plug the firewire cable into the back of my Apple iMac and turn on the 828mkII

At this point, I simply go to the Start menu, All Programs, MOTU, and the select MOTU FW Audio Console.

I now receive a message box with the following text:

"No MOTU FireWire Audio could be found. Make sure your MOTU FireWire Audio Device is connected, powered on, and that the drivers are installed"

I am at a loss as to what to do next.

Any help would be appreciated.

Thank you

Tony

[djsound]

same here... =( Ive installed a few times too.......also core 2 duo intel mac......

edit - to get mime going i had to go to the device manager and 'update driver' on the ones with the little yellow icons......so then it recognized the device...

BUT.......the thing wont work now that its installed...

[malexii]

Same problem on my PC. No device found. I've had it over a month. I give up, time to sell it.

Max

[Gerry G]

I had the first problem of no recogniton and then had the second of no device found after I installed the drivers and updated them in device manager.

I have fixed it and have done so many things that I am not certain what worked. I did roll back the firewire port using the patches. The first two are here in my post with links to the Microsofty site:

http://www.cockos.com/forum/showthread. ... #post81583

http://www.cockos.com/forum/showthread. ... #post80858

The last was a duo core patch which I am not sure you would need under Bootcamp.

Anyway there was this rollback mainly to a 2001 firewire patch and then I added a Sidspeed key to the registry and gave it a value of 3. You will find this if you follow the above posts and links.

I just cannot backtrack there as it was too painful and I spent a lot of time on it. Following the above though you may find the solutions quicker.

The last thing I had to do was to be very careful of the order of switching on the programme, Reaper in my case, and the Traveler.

Once you set a programme to the MOTU drivers you have to switch the MOTU on first or else the programme will go looking for the Traveler driver and will not find it.

Then when closing out you have to close the programme first and then switch off the MOTU.

Errors in this switching process can cause hanging and I think the programme can remember the hanging and does it again later.

Once you have the sequence right though it is very rewarding and mine has been rock solid for a couple of days now.

G.

[BradLyons]

Okay, this post isn't helpful at all and I am absolutely a DIE HARD WindowsXP/PC guy---but why on earth would you buy a Mac computer and then try to run Windows on it, let alone windows audio?? Seriously, I'm trying to see the logic here!

[Gerry G]

I was referring to a pc but some of the problems set out above seem to relate to very similar issues with these Macs running bootcamp.

Hope that helps the Intel Macs.