One thing I noticed in the logs you posted at the Apple forums:
Oct 24 22:07:34 Rick-MBP SecurityAgent113: NSExceptionHandler has recorded the following exception:\nNSRangeException -- *** -NSCFArray objectAtIndex:: index (0) beyond bounds (0)\nStack trace: 0x3719a 0x95e3ce3b 0x9392ef2b 0x9392ef6a 0x94c87bbf 0x94c05548 0x81f56 0x82795 0x6bc81 0x80213 0x73dc1 0x750f6 0x7d8d0 0x7e3cd 0x86d7d 0x940be3a5 0x8608d 0x9408a311 0x93fe7d0f 0x10fc7 0x202a 0x1
Oct 24 22:07:37 Rick-MBP authorizationhost112: MechanismInvoke 0x12e690 retainCount 2
The big gap in the startup is around this point.
http://discussions.apple.com/thread.jspa?threadID=1447051Note - the poster doesn't note any actual problems with startup. Interesting, nonetheless.
The hardware test disk often doesn't pick things up, in my experience. Take the new RAM out and put the old stuff back in and see if startup time is affected. You will see a slightly longer startup time with more RAM, but 6 minutes is not normal.
Also, as Kris suggests, turn off the autoconnection to the wireless network.
As for the firewire - sounds like you have a bad cable, since NEITHER machine can see the other.