The Motion problem in Macbook Pro

Question

I am still waiting for Apple to fix the problem that appears to be between Motion 2 & 3 and MacBook Pro Software Update 1.0.
Meanwhile Motion is 100% usless, unless a reinstall of the entire OS X (anybody successfull with that?).
Today it's almost 4 weeks since Apple made public this problem. And like 3 weeks without any news or friendly solution about this. Check: http://docs.info.apple.com/article.html?artnum=306038
It means that almost everybody with a new MacBook Pro and Motion 2 or 3 is not able to run this application.
Notice this facts:
1)Motion is a PRO Application.
2)MacBook Pro is a PRO Computer.
3)MacBook Pro Software Update 1.0 is recommended by Apple to all 2.2/2.4GHz MacBook Pro models (http://www.apple.com/support/downloads/macbookprosoftwareupdate10.html)
because it fixes important bugs on this computers.
4)This update fixes some problems, yes, but causes another: Motion crashes 100% of the time you try to use it.
5)The need of making an Archive & install of the OS X in order to undo the Update is by far one of the less friendly solutions ever seen by any user. And it's worse when you don't know for sure that it will work.
6)Pro users are the supposed target of MacBook Pro and Motion, and it is supposed that they have to be able to their job with that. The second part of the last sentence is not true.
7)The Software and the Hardware that appear to be in conflict are both wrote and designed by Apple, and the solution of this problem it only can come from Apple. The second part of the last sentence is, still, not true.
As owner of a MacBook Pro, and owner of a Final Cut Studio 2 suite I expect some kind of respect and attention from Apple. Not to mention a fast and simple solutions that helps me, not makes everything WORSE.
It will be cool to know how many MacBook Pro users are having the same problem with Motion. And how many of them do not accept the actual situation. How many of them want to demand to Apple a fair solution to this, at least some kind of information about HOW MUCH MORE WE HAVE TO WAIT.
Anybody knows any way to accomplish this?
I'm a big fan of Apple computers and applications, but I am not going to accept all this without demanding some kind of explanation from Apple and a real solution NOW!

Answer 1

Maybe I'll try the FW drive solution. Thanks for the idea!
I agree with you that maybe there is no way to make Motion Engineers to work faster, I hope this problem is in some kind of priority for the Motion Team and that they can find a way to fix it.
But what is bothering me here is that Apple is not giving public information about this. The only public official article about this problem hasn't been updated by Apple since 20 July. I think they have to know something more by today.
As user I want to know what is going on or how much I will have to wait for some solution. I don't want to accuse the Motion Engineers, that's not my intention. Because I think it's not their fault. Here the problem has had to be a lack of communication between Apple divisions.
I want to accuse Apple in the way this problem is being treated. Not giving enough information to its users. And that the whole problem could have been avoided if they had tested the update before publishing it.
Maybe you can say that it always has been like this with other problems, but I don't think it's the right way. At least is not what I expected from Apple.