thanks. now i'm ready to start as soon as my time machine is fully done with the backup. i'll hopefully be reporting back from my vanilla system.

This is cool! Nice one Dalton, thanks to both Munky and 18seven.

Dalton when do you install 10.6.1 after the Vanilla install and the fixer was run?

Should we install 10.6.1 as soon as we finish 10.6.0 install before we run the finisher?

okay, i've found out that you cannot have anything inserted upon booting, only your internal drive when using the update.sh. this is imperative.

i had the install sd card mounted and the script did something, but not the right thing, since GUID id's used to change and my internal drive became disk1s1(efi) and disk1s2(machd). i installed the 10.6.1 update, ran the update.sh and upon next reboot.. no trackpad sidescrolling and other weird things.

so i had to reboot with absolutely nothing hooked up to the usb ports, and then the script worked (i saw the 'EFI' partition appearing while it was doing its job, so i'm sure) as intended.

This was also the case with the first EFI Finisher package that I updated. If you noticed it says Updated. I redid the package so that it wont matter what your disk number is. Of course, the update.sh scripts still do need disk0

one more thing: you forgot to (or intentionally didn't) include cybergreg's trackpad kext in the EFIkext folder, so i moved ApplePS2Controller.kext to the _disabled folder, copied CGPS2Controller.kext from the alternatekext folder, ran update.sh again, and now all is well. this is not really a problem, just some people will be surprised.

almost all is well, that is.. :sigh: i have the annoying weird resolutions bug with the left-justified 800x600 and the blankscreen 640x480, but that might be sorted out like last time: after a few restarts it just fixed itself. and this, again, isn't a major issue, since at 1024x600 it's working nicely.

now for the migration.. :huge sigh:

all in all, great job, as always, dalton, thank you for all your hard work.

and i'm happy to report that hibernate works. even without quitting the wlan client utility (that was a known source of sleep problems). and it's awesome. it only takes seconds, and when resuming.. well, it's even more awesome. it looks like a real mac, and in five seconds i'm at the desktop. good times..

Yay! Turns out the no terminal method is just what you needed huh?

I created a sandisk cruzer and it boots to the selection screen when I go to select the Mac OSX Install I see ann error at the top can't find mach_Kernel. Any idea what is wrong?

P.S. I used my retail 10.6 disk as the restore source.

Isn't the same part written twice? As far as I understand, the first paragraph (before the "Vanilla Install") should be removed (also in the Wiki). Otherwise, the instructions calls for the installation twice.

LOL Wow! I didn't do the Wiki, but thanks for noticing.

I think we should try to bring the different methods/scenarios together and clarify what's the limitations of each. Checking around, it seems that MS XP and Vista (32 bit) still cannot understand GUID natively. Only the later versions of Vista (64, server) and now the Windows 7 start to understand GUID.

So if I want to keep using the XP that came with the MSI U-100, I better keep the MBR scheme.


Yes. The hidden EFI is created automatically when we repartition using the GUID. BUT: Are you sure that we cannot 'fake' it and create a small partition under MBR, call it EFI, and put all our customized stuff there, as someone (Mars478?) suggested? [same way as we could use a separate partition to put GRUB there]


I tried to look at the Boot Camp solution, but it seems that it is not a good solution for the long run. It takes advantage of the GUID/MBR Partition scheme hybrid, but is limited to only 4 'real' partitions (ie: Primary) (GUID/MBR hybrid cannot handle Extended partition and its Logical sub-partitions). Any future manipulation of the partitions such as moving, growing/shrinking, or adding partition will destroy the MBR-GUID synchronization.

So it seems that Boot Camp is not really a good solution in the long run.

Which bring me back to the need for the 'old' MBR scheme if we want to use the XP, until Windows 7 gains approval (remember Windows ME?)

What you'all think?

After I have installed a software update from apple (Like from 10.6.0 to 10.6.1) do I have to do anything like fixing kexts or is it all fine like a real mac?

you have to write this into the terminal after the installation of the update but BEFORE you restart:
cd ~/Downloads/Vanilla/EFIkext
./27ae.sh
./update.sh

or you use daltons app:
http://insanelywind.com/forum/viewtopic.php?f=11&t=332

I created the flash drive as required and as soon as Chameleon boots I get an error can't find Mach_Kernel. I do see the OSX Install button as well as my Leopard install button. How do I get past the Mach_Kernel problem?

Two Partitions
BOOTLOADER=201.01MB
untitled 1=remaining space

I used a real Mac OSX 10.6 DVD as the restore item

did you restore the dvd image to your 'untitled 1' (quick tip: i would remove all spaces from the partition name, just for safety) before installing chameleon to the 'BOOTLOADER'? i'm sorry for that pm, i mixed up the order, i was in a hurry. i'm assuming the chameleon installer detects the other discs and it couldn't locate the system on the 'untitled 1' partition, since there was none.

to fix this, just format the 'BOOTLOADER' and install chameleon onto it again.

again, i'm terribly sorry for misguiding you.

I first restored the image to the untitled 1 then I loaded Chameleon to the BOOTLOADER partition. I can rename the partition but I can't see b how it would make a difference. I am restoring now to untitled I took the one out.

hm.. i don't think that's the problem either, but it's worth a try. other than this, i really don't know..

I hope Dalton has a answer, but so far I haven't heard from him, after all this is his baby and if anyone has a clue it is him.

UPDATE: Still get the "Can't Find Mach_Kernel" on Chameleon boot.