Archives / Search ›

So I'm sharing a hotel room at MacHack with Robert Chin, an undergrad at the U of I who is a relatively recent Mac user. He has a weblog, of sorts. Robert was the main instigator behind 3DOSX. I don't know him very well, but that will probably change…

Listening to Radio Paradise finally playing B&S. No, I'm not off them yet. I'll have to drive to Michigan alone, again, because I couldn't get anyone else to come with me, and much B&S will be heard along the way. I'm really not going to enjoy giving back the iPod when I get back.

I haven't had OS X display a bizarre error message in a while, so it was about time for another. This one was precipitated by my trying to eject a FireWire hard drive in the Finder.


Amazingly, authenticating caused my disk to properly unmount. autodiskmount was already running as root, though.

root       132   0.0  0.1     2408    500  ??  Ss     0:01.78 /sbin/autodiskmount -va

Marco Scheurer: A tutorial on unit testing in Objective-C using the OCUnit framework. Been meaning to check this out for years, as I used to use unit testing a lot in Smalltalk.

Some tips that would have saved me half an hour of troubleshooting tonight…

If you are trying to start Mac OS X and it hangs with a black screen instead of the happy Mac, the OS X kernel may be panicking before BootX can initialize the video settings. If you start up in Open Firmware first (command-option-o-f), then type 'mac-boot', OF will initialize video first, and you should be able to read the panic message displayed on top of the happy Mac screen.

Don't forget to unplug external devices if you're having startup problems. Mine turned out to be an external FireWire drive which needed some repair because I had unplugged it from my TiBook without unmounting it first. The panic message included IOFireWireFamily, which was an obvious clue.