If you’re one of the people and you’ve tried the various fixes that can be found, but you’ll still having issues, then this is what worked for me:

1. Download ProKit 5.1 from Apple.
2. Double-click ProKitUpdate5.1.dmg and you’ll see ProKitUpdate5.1.mpkg.
3. Right-click (or Ctrl-click) ProKitUpdate5.1.mpkg and click Show Package Contents.
4. Expand Contents and Packages revealing ProAppRuntime.pkg and ProRuntime.pkg.
5. Right-click (or Ctrl-click) ProAppRuntime.pkg and click Show Package Contents.
6. Expand Contents and copy Archive.pax.gz to your Desktop.
7. Double-click Archive.pax.gz and the Archive Utility will extract the contents to a folder called Archive.
8. Within the Archive folder, navigate to System/Library/PrivateFrameworks and copy the ProKit.framework folder to your Desktop.
<br/>You now have version 5.1 of the ProKit.framework ready to replace the 6.0.1 version.
9. Open up Terminal (which can be found in /Applications/Utilities) and enter the following command:

sudo pkgutil --forget com.apple.pkg.ProAppRuntime

Since you’re running the command through the Super User account, you’ll be prompted for your Administrator password. Type in your password and click OK.
10. In Finder, navigate to /System/Library/PrivateFrameworks and copy the ProKit.framework folder to your Documents folder.
11. Delete the ProKit.framework folder from /System/Library/PrivateFrameworks. You’ll be prompted for your Administrator password.
12. This is important. I’ve seen users inadvertently copy ProKit.framework 5.1 into the existing ProKit.framework folder. Deleting the existing ProKit.framework folder will ensue this does not happen.
13. Copy the ProKit.framework folder from your Desktop to /System/Library/PrivateFrameworks. You’ll be prompted for your Administrator password again.
14. Launch Final Cut Studio and you should be good to go.

How cool is that?! Next up: designing and implementing a couple of project ideas I’ve been mulling for the past 6 months. Should be interesting.

For the intrigued geek, this is how I got to see the data:

Using a USB-Serial converter dongle, I connected the cable to the Mac and opened terminal. Next, I needed to grab the name of the USB device so I could open it. I did that by using the following command:

ls -l /dev | grep cu.usbserial | grep -v grep

When I had the name, I could then use the screen command to open the serial port at 2400 baud:

screen /dev/cu.usbserial-0000201A 2400

The baud rate will depend on the actual version of monitor you have. Newer versions operate at 9600 baud. To terminate the screen command, hit Ctrl-a, Ctrl-, y.

I ended up putting all this together as a Bash script (below) so that I can quickly call it up at will.

#!/bin/bash


export cmd=ls -l /dev | grep cu.usbserial | grep -v grep | awk {'print "/dev/"$10'}
screen $cmd 2400
clear

Fatal malloc_jumpstart() error

If you get this error, check the version of emacs you are using by issuing the following command:

emacs --version

On my machine, this was 21.2.1. The version of emacs that ships with Leopard is 22.1.1. To fix this error and make sure the Leopard is using the correct version, you first have to blast the emacs-i386 folder under /usr/bin. My advise is that you back it up:

sudo mv /usr/bin/emacs-i386 /usr/bin/emacs-i386.bak

Next, you have to rebuild the emacs-i386 by issuing the following command:

sudo /usr/libexec/dumpemacs -d

You will see a lot of text scroll back fairly quickly. After the command has completed, check the version of emacs again. This time around it should be 22.1.1 and you’re good to go!