Conti

You are going to need to use a legacy_kernel, No Sandy bridge system can be booted on snow leopard with a vanilla kernel (at least not before 10.6.7 MBP update iirc).

Helps to read the blog... http://myhack.sojugarden.com/2011/08/ch ... k-2-0-rc4/ & http://myhack.sojugarden.com/2011/08/up ... eleon-bug/ So after reading those try the following boot flags: ncpi=0x2000 -v -f Then add the VESA resolution to your boot.plist as described in that post i linked you to. Let us know how it turns out.

This is why in my Guide I suggest backing up S/L/E prior to running an update, some updates will overwrite useful extensions. Glad to hear you sorted it out though.

Any reason why you don't want to just go with lion? If you really do want Snow Leopard though either will work just fine, I doubt you will find anything circulating other than 10.6.3 at this point anyway, but it won't matter since you will just run a combo update after installation to get yourself up to 10.6.8 anyway.

If you add resolution to the boot plist correctly it will work... I tested it over 100 times. The information is on the blog.

There is no such thing as a retail copy of OS X 10.6.7 - there are only 10.6.0 and 10.6.3 retail copies. You may be attempting to use one of the 10.6.7 disks that was shipped with a mac system. Discs that come with mac computers are locked to that specific model so you can't install on a different type of machine. This also can be caused if no (usable) disks are detected by the os x installer, ensure that you have enabled AHCI for your SATA devices in your system's bios. But since you mentioned that you are trying to install from a copy of 10.6.7 what I mentioned above is the more likely situation. You will need to obtain a legitimate retail copy of OS X.

No they were removed intentionally. Why would you want an older version anyway?

Ya your posts was one of the reasons I dug into that bug, I was fortunate to be able to reproduce the problem on my own system, most of the chameleon developers weren't able to - it seems to be a rather selective issue - it only effects a few graphics cards (framebuffers). As of build 1407 it's *mostly* fixed, there is still a bit of a bug in rendering but at least the system will boot. In future versions of myHack I'll just be including some VESA definition in the generic Extra to avoid confusion if they are on a system that experances the issue.

You have failed to adequately meet the guidelines for posting your introduction thread. Please read THIS again - carefully - before trying again.