Please rename your file to Using Chameleon 2RC, this is precisely the reason we didn't include all details in our official FAQ. Every subsequent RC release introduces new options, but till we get out of beta we cannot be sure which ones will stay and which ones will be dropped/changed.

• I thought that something about sourcecode was important and should be right at the top, but striking the right -> tone <- was difficult.

• The particulars of how Chameleon works & the boot* files may be wildly off

• I wanted to list where the Extra folder could go, but it looks like I may have confused the issue even more. I wanted "/Extra" to denote the root and "Extra" to just be any path, but I think for a new user, this could confuse the issue. The listing of the Extra/Extensions folder makes it look like a mess, but I wanted to cover all the bases (new & veteran users). Maybe a picture...

• somewhere it says to use the included fdisk. I don't think I used that fdisk for 10.6. This doc uses the stock OS fdisk in $PATH.

• for RAID, OrigDoc edit the /Library/Preferences/SysConfig/com.apple.Boot.plist, but this doc does it differently. My thinking was that since there will have to be an Extra folder somewhere, it should be in that Extra folder. Unfortunately, I put it onto the hidden partition which makes it more cumbersome. I think the RAID instructions should change to a root-based /Extra folder & skip the the multiple Extra folders on the hidden partition. This preserves a fresh com.apple.Boot.plist (admittedly a simple file, but when you wreck it & don't know, that doesn't help) with a single Extra folder.-----------changed:• In the EFI partition formatting, I changed the unmount to sudo unmount. You need admin privs to do that which the "exit" releases earlier in the process. I didn't want users making folders & copying .kexts that they couldn't get at in the Finder or easily edit a .plist in TextEdit.

One small point, in the section "Installing Chameleon into a hidden EFI partition on a hard drive (non-RAID):" you omit to put a step in to put 'boot' into the root folder of the EFI partition. This caught me, and took quite a long time for me to work out what I'd done wrong.

you omit to put a step in to put 'boot' into the root folder of the EFI partition.

there should be no OS on the EFI partition, therefor 'boot' should be not on the EFI partition. 'boot' should be in the root folder of the partition where your OS lives. That/your step is not right and shouldn't be done.

there is a note missing on the FAQ for those among us that use soft-raid, but also have other partitions of macosx. Like for example mainsnow ( a striped soft raid volume) and snowemergency a single partition after the raid set on one of the HD's here's the problem since chameleon boots and finds the plist's inside the boot OSX partitions it loads it even if you select snow emergency the boot flag with the partition uuid is loaded and you end-up on the mainsnow OS anyway and if there in different states of upgrades or are trying out kext's they can conflict with each other and not let you boot the snowemergency one at all. Been having problems with this actually but I figured it out, what you need to do is add the uuid of the snowemergency partition inside the boot.apple.plist inside the extra folder on the snowemergency volume to override the previous command that is loaded by the apple plist inside the Boot OSX folder.Now that I figured this out all I need to do is figure out how to hibernate a os that resides on a soft-raid volume, because I can hibernate on snowemergency, however I cannot hibernate MainSnow (which is striped over three HD's Over 300mb/s with large files )terramir