Built from source.

This morning I needed to choose a hex color, but I didn’t have easy access to the Color Picker utility in Mac OS X. So I spent about 15 minutes creating a Color Picker.app utility and installed some plugins. Yes, you can install plugins for Color Picker.

Download Color Picker.app here.

Just drag to /Applications/Utilities/ and then you can find the Color Picker in Spotlight.

While you’re at it, make Color Picker more useful by installing these plugins:

• Hex Color Picker
• Mondrianum (for Adobe kuler)

Leopard users know how useful Quick Look can be, but using it from the command line is harder than it should be. After looking at other people’s solutions, I decided to write my own.

#!/bin/bash

#
# ql(1)
#
# Quick Look command for terminal use
#

if [[ ${#} -lt 1 || ${1} == "-h" || ${1} == "--help" ]]; then
    echo -e "Usage: ql [options] "
    echo -e "\t-t\tForce text mode"
else
    if [[ ${1} == "-t" ]]; then
        shift
        qlmanage -p -c public.plain-text "${@}" >& /dev/null &
    else
        qlmanage -p "${@}" >& /dev/null &
    fi
    PID=${!}
    PID_IN_USE=1
    while [ ${PID_IN_USE} ]; do
        PID_IN_USE=`ps | awk '{ print $1 }' | grep ${PID}`
        read -sn 1 -t 1
        if [[ ${?} -eq 0 && ${PID_IN_USE} ]]; then # user quit via GUI
            kill ${PID}
            exit 0
        fi
    done
fi

Besides saving on typing, this script has a few other advantages over the qlmanage command:

• It automatically returns the command line to you if you close Quick Look with the GUI (after a short delay)
• You can force plaintext mode for text files that don’t have generators configured (for example, CSS files by default) with the -t option.
• You can hit any key to close the Quick Look window.

Download ql here.

Feel like wasting several hours? Try installing Windows XP with Boot Camp 2.0 (the version released as part of Mac OS X 10.5 Leopard) using NTFS, the file system required for partitions larger than 32 GB. Then watch as it fails miserably, again and again.

Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file.

Sound familiar? You didn’t do anything wrong—this is actually Apple’s fault. Hal.dll, the “hardware abstraction layer”, doesn’t have any particular significance; it just happens to be the first file that Windows looks for as it’s loading. Attempting to replace this file with the copy on disk won’t work, and your boot.ini is probably fine.

So how do you fix it, then? The solution is a bit involved, but not too bad all things considered. Here are the steps:

1. If you haven’t already removed the bad installation, you’ll need to do so. In OS X, open Boot Camp, click Continue, select “Create or remove a Windows partition”, click Continue, and then click Restore.
2. Create a new partition as you did before, and start the installation.
3. After the computer has rebooted and it’s booted from the CD, type “R” to go to the console. You should be dumped to the C:\ prompt.
4. We’re going to reformat the drive as NTFS ourselves instead of letting the Windows installer do it. Type the following and hit Return:

   format c: /q /fs:ntfs

   Then type this to reboot the computer:

   exit

5. Hold Option after it restarts, then boot to the Windows installation CD again (I believe it boots to the CD by default at this point, but this is just to be sure).
6. Install to C: (be careful not to select your OS X volume!), but—and this is important—choose NOT to reformat. Leave the file system as is.
7. Continue the installation process as you would normally.

That’s it! If things went well, the lovely 256-color Windows logo should load and you’ll be looking at Napa Valley in no time.