You're welcome, I'm glad you find my posts useful.
Is the numbering is off between what Diskutil -list shows and what Chameleon is looking for?
The drive number that goes in Extra/com.apple.Boot.plist seems to be relative to the drive that Chameleon is installed on. But I've never tried using Chameleon on one drive to boot OS X on another, physical drive. I don't know what would happen then.
The order the drives are plugged in and the order your BIOS is set to boot from them doesn't seem to be as important to Chameleon in regards to what it sees as the first drive, as where Chameleon is actually installed.
If you consider this for a while it seems like bad behavior for a boot loader - but since Chameleon is also kind of a BIOS replacement (well, EFI replacement) I think it makes some sense.
On my system, physically, the first drive (SATA port 1 and drive 1 in the BIOS) is actually my Windows drive.
I use the BIOS' built-in boot selector (F8) to pick my second hard drive whenever I want to boot OSX.
From then on in, according to Chameleon and Disk Utility, this drive becomes the first drive. So I use hd(0,2) in com.apple.Boot.plist. 0,1 is the EFI partition, where Chameleon is installed and 0,2 is my Snow Leopard installation.
I've sometimes seen Disk Utility getting confused and seeing my OSX drive as the second disk though (which, in all fairness, it is). But Chameleon always auto-boots with hd(0,1) no matter what Disk Utility says once the system is running.
As for the kext, when I drop them into the /Extra/Extensions folder - does Chameleon present that to the OS as if it were coming from the /Library/Extensions folder?
It's irrelevant. You could load a kext from your desktop if you wanted to. Extra/Extensions just happens to be where Chameleon looks for them.
The FAQ makes it sound as if I only need the kexts or the mkext, but not both - is that right?
I've found that some kexts will only work when loaded from the .mkext, some won't. I keep both an mkext and an extensions folder, it doesn't seem to cause any problems with particular set of kernel extensions I'm using and this way I don't have to think about it.
As for Kext Utility, just drag and drop your /Extra/Extensions folder on its icon and it will create an mkext for you in the Extra folder. Don't use it to fix kext permissions in S/L/E though (it does that automatically if you run it by itself) because it sets the wrong permissions.
If you can't find it at applelife.ru, visit insanelymac and search for user cvad, there's a download link to it in his signature.
"
...and the music keeps on playing on and on.."