Tons of Script Errors and Slow Redraw

Question

I recently setup CS 5.5 with Bridge 4.1.0.54 on a new MacBook Pro.
When I launch Bridge I get the following messages:
I'm confident of a few things. First, it's obviously somewhat related to this issue:
http://forums.adobe.com/message/3083307
Second, it has nothing to do with CFS or Samba shares.
Lastly, the error has something to do with the output module script- if I startup without it on, no errors.
Currently I have my MBP setup with two drives. A SSD for the system software and a second SATA drive for content. All my system software is on the SSD boot drive, however, my users folder is split between the two. Everything but ~/users/xxx/library is symbolicly linked on the second drive.
If you look closely at the thread referenced above, all the errors are the same except for the "could not create" error. In the thread, it lists a specific user, my error lists Volumes/Null/...
Here is what I've tried so far:
Reset the app
Trashed the prefs
Started up w/o scripts
reinstalled the entire CS 5.5 Suite after Uninstalling and using the cleaner tool
To add insult to injury, When the output script is off and bridge does load, it does it painfully slow to the point where it is not usalbe. It is also having a ton of redraw issues.
Any advice?

Answer 1

I think I may have found a workaround.
I've been racking my brain over the past few days to figure this one out. I've tried at least a dozen permsissions fixes, both through the apple utility and manually. I've reinstalled both bridge and CS 5.5 three times using the cleaner script and a fresh install. NOTHING.
So I went back to the original error message:
One thing I noticed was that everytime Bridge was starting, it created a folder in /volumes called "null". I checked three other macs setup the same was as mine and NONE of them created this folder during bridge startup.
I still have not figured out why my laptop is doing this.
However, I looked at the error and it seemed that bridge was looking for a path that didn't exists, which was /volumes/null/Adobe/Adobe Bridge CS5.1/Adobe Output Module/Mediagallery
the path Adobe/Adobe Bridge CS5.1/... is the same path as my ~/library/application support/... folder for adobe.
First I created a regular alias to that folder to create the fake path. No dice. Then I tried a symlink to creat the fake path /volumes/null/Adobe/Adobe Bridge CS5.1/Adobe Output Module/Mediagallery
Voila. Worked like a charm. I can now start up Bridge without any errors, script errors, etc. I also have all the functionality of my Output panel back and I'm able to use it without getting the insufficiant disk space error.
Now to figure out why Bridge is creating a "Null" folder.