Quote:
Originally Posted by soh
Plesae Answer me again
i try follow you comment my machine still cant boot from HDD
(install Chemeleon from legacy boot CD / copy file names boot from legacy boot CD and paste to root Directory (Delete old boot file and replace boot from legacy boot CD )
i cant find marc_kernel in legacy boot CD but i use marc_kernel from other osx 10.6.2 DVD
when reboot my machine still cant boot from HDD
and i try copy com.apple.boot.plist from legacy boot CD paste it to root directory my machine can boot from HDD them go to apple logo and cant go to osx follow this picture
Please help again
i fill not far from Hackintosh finishing
**sorry my english verry bad** |
follow this link:
http://www.mediafire.com/?3h53c803hctmdh4
the files above may work for you. You need to investigate how to edit the com.apple.Boot.plist file so it works with your system. I would advise removing the "Graphics Mode = 1600x900" from the Boot.plist boot flags, as my 23" monitor may be a little a bigger than yours.
so all you do is drop the mach_kernel (xnu Darwin 9.5 Kernel) into your root directory, my "boot" file into your root directory, and my "extra" folder into your root directory. If you installed chameleon correctly, that should be it. You may need more or different kext files in your "extra/extensions" folder as your system may require different drivers than mine.
here is how chameleon works as I understand it... the bootloader installs some instructions into a small partition in the master boot record (MBR) which are activated at boot time. these instructions access the extra folder, boot.plist and smbios in the root directory and basically trick the kernel into thinking it was booted from EFI. The Kext files from the extra folder load first in chameleon (and kind of provides a base for the kernel to operate in) these are the kexts that trick the system and provide power management, sleep etc. The kernel takes the information from boot.plist file, and smbios and boots your system using the information inside the files as variables to run the OS (what ram you have, what processor, what fsb speeds etc). That's how I understand it anyway, and it seems to have worked for me this long.
I have another suggestion for you, always boot with the boot flag "-v" for verbose, it will tell you what is loading and where your system is hanging. the photo that you posted earlier is really no use to anyone, but the line (example only) "eth0 linked, no flow control" with a kernel panic could tell you that the kext file for your ethernet, or the kext loading after your ethernet (usually audio) is hosing your boot. You then need to replace your audio kext or try a different ethernet kext.
Your English is fine and more coherent than many of the users around here (that's not a dig towards anybody in particular) LOL. What is your native language... I have a website that needs some translation, could you help?