I was running 3.0 on 10.5.3 (Mojo) and it gave me this message and I had to reboot about 5 times a day.

So I took one of my internal drives installed a clean 10.4.11 and put 3.01 on it.

That didn't change anything. I get the same message about 5 times a day.

2.8.4 didn't make any difference. Same error.

Now what?

You are running into the Apple bug that prevents Avid's DNA boxes from working with Leopard. This information is widely available here, on Avid's support and product pages and in the readme for the software.

If you want to run 3.x with a DNA, you need to be running 3.0.1 on 10.4.11.

That's what I did and I still run into this problem. As I wrote: new clean drive, 10.4.11, 3.01 and I still get this message.

Upgraded to 10.5.5 and QT 7.5.5. Three days now and didn't have a single crash because of 1394...

Gone?

Still the 30" monitor thing and one or two bus errors a day. But I don't have to reboot the whole machine. Simple restart of MC does it.

There is hope...

Yes 10.5.5 fixed Apple's bug.

 Do you have a firewire connected deck in your system? If so, turn it off while editing.

 Folks,

Mac OS X 10.5.5 has not been qualified by Avid yet.  Engineering and SQA tested the pre release and are now testing the final drop from Monday's release.  While the FW driver issue is listed as fixed by Apple, Avid has to test it to make sure all is well and that nothing else cropped up.

Net net..............   10.5.5 is NOT qualified yet on v3.0. 

Marianna

Marianna is correct. Avid has not yet qualified 10.5.5 so, if you upgrade to it you join those of us who like to live on the bleeding edge.

Anyone who does make the leap, please let us know if you run into any weird repercussions. So far I haven't noticed anything.

Wow.  Could this really be true?  My days on a dual 2.7 are numbered?  Here's to 8 core Mac Pro's all around on the day its qualified!  

.- The fresh install of 10.5.4 in a brand new Macpro I use at work (less than two weeks old) has been giving me so much trouble that I decided to not to wait for Avid's certification, since things couldn't be worse.

So I desperately updated to 10.5.5 and Qucktime 7.5.5

My impressions so far:

The bad: Now I have a new "MAIN BUS THREAD" error I didn't have before, which causes the Avid to quit unexpectedly. 

The same: I'm still having "power up hardware, please recycle" error, still I have to force quit to close Avid, still freezings and lock ups.

The good: At least is not loosing my settings and, unlike before, seems to be saving my work, which I'm very happy for.

The lock ups are less  (from incredibly many to five a day aprox)

Well, we made sure we had some bandages on hand (not used to this bleeding edge thing...) and made the leap... dusted off the Mojo (analog) and fired it up. Edited all day yesterday. Did some capture trials... batch included, and have had no problems yet. Still early... but looking good 

Yahoo! back from the dead!  Will try it this weekend. 

Thanks

max

respago,

I see you implied that you were losing work when running 10.5.4.  Could you explain what exactly was happening. We are running MC 3.0, OSX 10.5.4 and about once a day (on several systems) get an error that says "This bin cannot be saved. Would you like to save a copy."  We cannot find any reason that we can't save the bin. On several occasions the editor comes in the next morning to find that several hours from the previous day had been lost. The attic nor the project folder was saving anything.

Just curious what your symptoms are/were ...

Thanks.

-cablet

Just curious what your symptoms are/were ...

.-Well, I was (and still am) having a lot of problems, not only that.

The Avid used to crash badly and lost everything I had done for the last hour or so.

And worse, sometimes when I rebooted, the Avid was in the same state as when I started working, nothing saved. That was simply terrifying.

So I decided to desperately upgrade to 10.5.5 and that specific behavior hasn't repeated (so far), although I'm still having lockups, main thread errors and other weird things.

But I'd recommend you to upgrade to 10.5.5, at least it seems to save my work.

Just curious what your symptoms are/were ...

.- BTW, what storage are you using?