In the following tutorial we used  Snow Leopard build 10A432 GM release (now confirmed that retail disc is build 10A432). Snow Leopard needs a Leopard Install so we need to two hard disk one with Leopard already installed and second hard disk for Snow Leopard. Also you need to download some files needed during the installation so download the files given below. We’ll update these files regularly when the new updates will available.

• Modbin Kernel, Tools, Kexts, Chameleon 2.0 And Boot file Download Here
• SMBios.plist Download Here
• Mac OS X 10.6 Snow leopard (Google is Your F.R.I.E.N.D.)

____________________________________________________________________________________

Phase One

____________________________________________________________________________________

Step One). Connect both of your Hard Disk one is blank and one is pre loaded with Leopard (10.5.X) already. Boot in to Leopard and launch Disk Utility to partition your second hard-disk with GUID partition scheme. Name the partition what ever you want in this tutorial we assumed Snow.

• Make sure that the new volume’s root directory is owned by the root user, just perform the following commands in terminal.

sudo –s

chown 0:0 /Volumes/Snow

Step Two). Mount the Snow Leopard DMG File, an installer window will appear here click on the free space anywhere in windows then press CMD + Shift + G . A little window will appear in the top of existing window in this little window type “Mac OS X Install DVD/System/Installation/Packages/” without quotes as given in image below and press Go.

Step Three). In the next window find the OSInstall.mpkg and double click this package file to start your Snow leopard Installation.

Note : Default OSInstall.mpkg works for GUID partitioned drive only, if you need to install on MBR then google for Modified OSInstall.mpkg for MBR, download modified one and replace with default one.

Step Four). Follow the On Screen instruction and in Destination Select Choose the Snow Partition which you created on a separate blank hard disk.

Step Five). In customization remove the unnecessary languages and Printers. Sit back and have a cup of coffee installation will take 15-25 minutes depending on your hardware. Once Installation finishes don’t reboot and follow the instruction care fully in phase 2.

____________________________________________________________________________________

Phase Two

____________________________________________________________________________________

In the second phase we’ll install Bootloader, some must required Kexts, System Files and Patching the DSDT.

Step One). Open the Chameleon Bootloader Zip you downloaded earlier and install the Chameleon-2-1.0-r640.pkg Make sure to install the Chameleon package to Snow Drive (Where you Installed the Snow Leopard). You can change the install location at the third option while Installing the package.

Step Two). Launch the “ShowAllFiles” (included in Tools) and click Show. Then Navigate to the root of your “Snow” Drive and delete the “boot” file you see. and replace it with the boot file included with Chameleon Download (you downloaded earlier). After replacing the boot file again launch the “ShowAllFiles” and click Hide.

Step Three). The most important step, Place the new kernel in the root of volume, Root means in Snow drive where you installed the Snow leopard.

Step Four). Now patch your DSDT, launch the DSDT Patcher (Included in Tools) and select Darwin/Mac OS X in Operating System, Select DSDT Patch in options and before hitting the Run DSDT Patcher button make sure to change the destination as Snow Drive (Where you Installed the Snow Leopard).

Step Five). Now put the following  kext file, “ FakeSMC.kext, PlatformUUID.kext, Openhaltrestart.kext, NullCPUPowerManagement.kext” you downloaded earlier and you can also add yours if you needed into /Snow/Extra/Extensions, and copy the Extensions folder in Extra to the desktop, and drag it over “Kext Utility” which you downloaded. Kext utility will repair your permission and generate a new Extension.mkext. Move that Extensions folder and the extension.mkext back to /Snow/Extra

Step Six). Now launch EFiStudio and look for your Video Card through the drop down menu. Click add device and you will see some alphanumeric numbers, copy these numbers. Add the following code to yourcom.apple.boot.plist in /Snow/Extra.

<key>Graphics Mode</key>

<string>1280×1024×32 </string>

<key>device-properties</key>

<string>Alphanumeric code you generated with EFiStudio</string>

Save and Exit…
Step Seven). Final Step open SMBios.plist and change the UUID with volume UUID With the UUID of your Snow volume. then place the SMBios.plist in to Extra/Extensions. Also place the UUID in the PlatformUUID.kext its located on PlatformUUID.kext/content/info.plist.

Step Eight). Must for those who added any driver kext to Snow/System/Library/Extension, This step will rebuild the Extensions.mkext cache while booted in Snow Leopard. Reboot and go to Single User mode by typing this flag.

-x32 –s

When you are in the console, type the following command

/sbin/fsck -fy
/sbin/mnt -uw /
kextcache -v 1 -t -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions/

Disclaimer : All the instruction and Files are correct in my information. Use this guide on your own risk, we are not responsible for any kind of damage (If Any). Use this guide for experimental purposes only if you likes the Mac then buy a new one

It takes days and hours of me to make this guide as easiest and advanced for you, In cash-back i need only a Digg to the story. So guys go ahead and add your count at the top right hand of the corner where the post starts….

For MAC OS X user Zef released a warning, Chameleon is developed to boot Darwin/Mac OS X on PCs, it doesn’t work on Macs. Please don’t install Chameleon to your system drive, we got many failure reports with unbootable Macs after installing Chameleon.

Download Links

• Download Binaries here: Chameleon-2.0-RC2-r640-bin.tar.gz
• Download Installer Package: Chameleon-2.0-RC2-r640.pkg.zip
• Download Sources: Chameleon-2.0-RC2-r640-src.tar.gz

Credit for this new release goes to:

1. Developers: Crazor, Dense, fassl, iNDi, Kabyl, kaitek, mackerintel, mercurysquad, munky, Turbo, zef
2. Thanks to: bumby, cosmo1t, dfe, Galaxy, kalyway, netkas, sckevyn, XyZ

What you need
1. Original Leopard developers seed (.dmg)(6.55Gb)
2. One blank DVD (+1 backup blank just in case you screw up)
3. Mac OS X 10.4.X Tiger (This is important, leopard screws up disc burning)
4. 6.55Gb+6.55Gb+4.7Gb=17.8Gb of hard disc space
Method
1. Mount the Original Leopard DMG (jus double click u idiot!!)
2. Open Disc Utility (under Applications -> Utilities)
3. Click on New Image (at the top u fool!!)
4. Name the image as dump (save on desktop!!)
5. Put the type as sparse image
6. Put the size as DL-DVD (8Gb), and click create
7. Mount dump.sparse
8. In disc utility, select the dump image and click the restore tab
9. Drag the mounted Mac OS X Install DVD to the Restore from field
10. Drag the mounted dump to the Restore to field (or equivalent)
11. Click Restore and wait.. (have some patience… ZEN…)
12. Once that is done, open up the dump mounted image
13. Remove the Developers Tools under Optional Installs
14. Use finder’s Go to Folder option and navigate to /Volumes/dump/System
15. Go to Installation -> Packages
16. Proceed to remove anything that has Printer in it (u can always get from vendors)
17. Proceed to remove languages that you do not need (like french, german)
18. Verify in Disc Utility on the size of your dump (should be 4.3Gb or less)
19. Return to Disc Utility
20. Click on New Image
21. Name the image as burn (save on desktop!!)
22. Put the type as sparse image
23. Put the size as SL-DVD(4.7Gb), and click create
24. Select the burn image and click the restore tab
25. Drag the mounted dump to the Restore from field
26. Drag the mounted burn to the Restore to field (dont mix up!!!)
27. Click Restore and wait.. (have some patience… ZEN…)
28. Once its done, burn it to DVD (in Tiger, not leopard)

Here is the official announcement
- This DVD is designed for Non-Apple x86 computers (PC). So, do not try to boot it on Apple Hardware!
- This DVD includes Apple’s Mac OS X Leopard 10.5.7 (9J61) installation for Intel and AMD CPUs, some basic drivers and x86 patches.
- Make sure that the md5 checksum of your iATKOS iso image matches the one in md5.rtf file. Do this MD5 check just before mounting or doing anything with the iso image! Otherwise you may have a faulty DVD image. Use quality media/burner and burn slowly.
- The oscar goes to Apple and OSX86 community..

Information:
- This OSX86 installation DVD release supports both GPT and MBR partitioned hard drives.
- Full retail main system like boot132 installation.
- You can make Clean, Upgrade (from previous versions of OS X on Intel/AMD), Refresh (renew your existing 10.5.7 installation) and driver-only installs using iATKOS v7 DVD. Upgrade/Refresh is highly successful on previous iATKOS installs and will mostly work for other installations too, read the readme for the process.
- You can update your running system using software updater just like real Macs on most PC hardware(Intel/AMD).
- Easy installation on RAID targets with manual bootloader installers and packages.
- Enhanced hardware compatibility: various systems including ATI, SiS, VIA chipset motherboards, enhanced nVidia VGA support with universal efi string and modified enablers.
Minimum hardware requirements: x86 SSE2 CPU, 512MB RAM, 10GB free space on target partition, OpenGL VGA card.

Recommended hardware requirements: Intel Core or AMD x2 CPU, 1GB RAM, 15GB free space on target partition, nVidia GeForce 6600 or better – ATI X1300 or better – Intel GMA 950 or X3100 VGA card.
Motherboard (the most important part) should be compatible for you to boot iATKOS v7 DVD and install natively.

What can you do in “Single User” Mode?

since single user mode is for administrator and no GUI is available then every task you can do from terminal (command line) as root user you can do here, which is practically everything (on the current system) it wasn’t meant to be used for regular work such as surfing the web (there is no network) or reading files etc. you can use all the unix commands available for OS X and all the command line utilities and applications available on that machine.

How to enter Single User Mode :

1. Restart your Mac or Hackintosh.
2. Continuously press F8 until you see the Darwin boot prompt
3. Type “-s” without the quotation marks and press enter.
4. You will soon reach a command prompt
5. Note the lines written to the console about fsck and mount
6. Type : /sbin/fsck -fy
7. Type : /sbin/mount – uw / this will mount your file system
8. thats it now you are in “Single User Mode”

In single-user mode, not all functions of Mac OS X are available. To use the Mac OS X interface or other high-level aspects of Mac OS X, you need to start up in the standard mode.To switch back to the Mac OS X interface, type reboot and press the Return key. The computer restarts and you see the login dialog or the Mac desktop, depending on your login preferences.

Step 1 Jumper Settings : If your system contains IDE hard disk or DVD RW then you need to play with your jumper settings. If the following settings are not working for you try vice versa. if you have Sata Hard Disk and DVD RW skip to step 2.

• Your rom/writer must be set as Primary Master.
• Your hard-disk must be set as Primary Slave .

Step 2 Tweaking the BIOS : If you satisfies step 1 then time is to play with BIOS settings. Open your BIOS settings by pressing DEL or F2 key continuosly as you starts your PC. Once the BIOS screen appears try to find and change following options if they are available.

Step 3 Download Another Distribution : This is the most effective there are many OSX86 distro in the wild but you have to choose select one for your hardware configuration. For selecting the right one search on Wiki.OSX86project.org and forum.insanelymac.com if you find anyone who posted a success message with his details then you are lucky otherwise download the various flavours and try them.

_________________________________________________________________________________

Still Waiting For Root Device Error After Installing The OSX86

iClairified Guide :

1. Boot up using the LeoV3 DVD as if you are going to install Mac OS X again.
2. Select Terminal from the Installer’s Utility Menu.
3. Now we are going to copy all the the ATA kexts from the install DVD to your hard drive. To do this enter a command like this:

cp -pr /Volumes/Leo4allv3/System/Library/Extensions/*ATA* /Volumes/MacHD/System/Library/Extensions/.

NOTE*: Replace Leo4allv3 with the name of your install dvd and replace MacHD with the name of your hard drive volume.

4. Now we need to set the permissions for those kexts we copied

chown -R root:wheel /Volumes/MacHD/System/Library/Extensions/*ATA*
chmod -R 755 /Volumes/MacHD/System/Library/Extensions/*ATA*

NOTE*: Replace MacHD with the name of your hard drive volume.

5. To remove the kextcache execute the following:

rm -rf /Volumes/MacHD/System/Library/Extensions.*

Note* Replace MacHD with the name of your drive volume.

You may now restart your computer. I would suggest pressing F8 while booting and then entering -f as a boot option to force reloading of the kexts.

___________________________________________________________________________________________

Apple2PC Guide :

If you know the number of your Hard Drive then at the Darwin prompt (after boot press F8) write: rd=DiskX where X is the number of your OSX hard drive.

___________________________________________________________________________________________

Tags : kalyway still waiting for root device, iatkos still waiting for root device, still waiting for root device sata, mac os still waiting for root device, still waiting for root device leopard, jas 10.4 8 still waiting for root device, still waiting for root device ide, osx still waiting for root device

1. Check your BIOS setup and use the following setting if available :

• Set Core Mutil-Proccessing disable (if all goes well set enabled)
• Set ACPI 2.0 Support to yes
• Set ACPI APIC Support to enable
• Set CPU Internal Thermal Control to Disabled or Auto
• Set the Max CPUID Value Limit to Disabled
• Set the “Execute Disable Function” to Enabled
• XD (eXecution Disabled) Disabled

Set ATA/IDE Mode Settings:

• Set Configure SATA as: AHCI
• Set S.M.A.R.T: Enabled

IDE Settings:

• Set ATA/IDE Mode: Legacy
• Set Configure SATA as: IDE
• Set S.M.A.R.T: Disabled

2. Try to Boot using some Darwin Bootloader Switches (or combinations of them):
cpus=1
-f
-x
-v
-legacy
platform=X86PC
platform=86PC
rd=diskXsY (where X is the number of the leopard drive starting from 0 and Y is the number
of Leopard partition starting from 1 example: rd=disk0s1)
see “Darwin Boot Options” for more details

3. if you are using kalyway 10.5.1 then try “TOHKERNEL” at the darwin boot prompt it will boot TOH kernel instead of the vanilla one (this solution is mostly for when the DVD reboots befor getting to the graphical install screen).

4. Make sure you have at least SSE2 Processor.

5. Reinstall OSX86 with minimum options in customization.
 
6. Remove hardware parts you don’t need for the install process (like PCI cards, 1.44, USB deices etc.) 

7. Try to install OSX86 on a blank Hard Disk.

Darwin boot loader level flags, for Darwin version 8.0:-

• -v = verbose mode. Basically tells you wants happening during boot up.System in Verbose mode display a lot of log lines during boot time and does not display the apple gray boot screen, it is good to use this option if things go wrong, or if you get an error screen and you want to know the reason.

• -x = Safe mode. Basically boots your system with the bare minimum kexts. This option boot the system into safe mode ignoring kext cache and loads only necessary kext

•  -s = Single user mode. Command line only mode. Allows you to run commands as root to fix system.This mean you would like to enter “Single User” mode which doesn’t load GUI and doesn’t mount partitions but gives you a prompt so you can make system maintenance and recovery procedures.

•  -f = Tells the hackintosh to reload all kext (Kernel Extensions = drivers) and dump the cache, not rely on it (kext cache found in: /System/Library/Extensions.mkext, you can delete it manually and the system will recreate it)
• cpus= this parameter tells the hackintosh how many cpus to use, for instance if you have dual CPU or dual Core then you can state cpus=2, so the system will use both cpus, and if you get reboot without loading GUI or boot screen then you may use cpus=1 to allow use of one cpu and avoid reboot

• “Graphics Mode” = this parameter tells the hackintosh to use stated graphics resolution and color depth, the pattern to use is: WidthxHeightxDepth@RefreshRate for instance a resolution of 1024×768 with 32 bit color depth and 60 hertz frequancy refresh rate will look like this:

“Graphics Mode”=1024×768x32@60

• config= this parameter tells the system to load using different copy of the boot config file, the default copy used is kept in:

/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

The content of this file state boot options such as:

1. timeout (how much time to wait for user selection in boot prompt)
2. Kernel (what kernel to use)
3. Kernel flags (what kernel flags to use in each and every boot)
4. Quiet boot (weather to display boot menu or not)
5. Boot graphics (if to boot with apple spinning circle)

ACPI Flags are as on :

• acpi=off = Don’t enable ACPI
  
• acpi=ht = Use ACPI boot table parsing, but don’t enable ACPI interpreter
  
• acpi=force = Force ACPI on (currently not needed)
  
• acpi=strict = Disable out of spec ACPI workarounds.
  
• acpi_sci = {edge,level,high,low} Set up ACPI SCI interrupt. EX:
  
• acpi_sci = edgeacpi=noirq = Don’t route interrupts

Kernel Panic Example 1:

Unresolved kernel trap(cpu 0): 0×300 – Data access DAR=0×0000000030D6334E PC=0×0000000027B5CD3C
Latest crash info for cpu 0:
Exception state (sv=0×27CA4500)
PC=0×27B5CD3C; MSR=0×00009030; DAR=0×30D6334E; DSISR=0×40000000; LR=0×27B5CD24; R1=0×0D80BAE0; XCP=0×0000000C (0×300 – Data access)
Backtrace:
0×27B5E6C4 0×27B5D82C 0×27B5607C 0×27B45C74 0×002E9A80 0×002EB94C
0×0008C248 0×00029234 0×000233F8 0×000ABEAC 0×8001016C
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0×27b3a000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0×1d8f7000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0×27867000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0×2788b000
dependency: com.apple.NVDAResman(4.1.8)@0×278a1000
Proceeding back via exception chain:
Exception state (sv=0×27CA4500)
previously dumped as “Latest” state. skipping…
Exception state (sv=0×1D92D280)
PC=0×9000B348; MSR=0×0200F030; DAR=0×02A8A000; DSISR=0×42000000; LR=0×9000B29C; R1=0xBFFFE900; XCP=0×00000030 (0xC00 – System call)
Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0×300 – Data access
Latest stack backtrace for cpu 0:
Backtrace:
0×000954F8 0×00095A10 0×00026898 0×000A8204 0×000ABB80
Proceeding back via exception chain:
Exception state (sv=0×27CA4500)
PC=0×27B5CD3C; MSR=0×00009030; DAR=0×30D6334E; DSISR=0×40000000; LR=0×27B5CD24; R1=0×0D80BAE0; XCP=0×0000000C (0×300 – Data access)
Backtrace:
0×27B5E6C4 0×27B5D82C 0×27B5607C 0×27B45C74 0×002E9A80 0×002EB94C
0×0008C248 0×00029234 0×000233F8 0×000ABEAC 0×8001016C
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0×27b3a000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0×1d8f7000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0×27867000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0×2788b000
dependency: com.apple.NVDAResman(4.1.8)@0×278a1000
Exception state (sv=0×1D92D280)
PC=0×9000B348; MSR=0×0200F030; DAR=0×02A8A000; DSISR=0×42000000; LR=0×9000B29C; R1=0xBFFFE900; XCP=0×00000030 (0xC00 – System call

You should understand that what happened here is that the OS has stopped working since it has a problem, the first thing it does is look for a debugger to pass the control to (since this is not a Mac OS X developer station it will not find one), next thing it will do is dump to the screen all the data it can on the incident so you or a qualified technician can understand what the problem is.

the first part (blue part) display data of the CPU registers, program control exception state for CPU number 0 (this is your first CPU) at the time of crash, this data is hex address in the memory, it will not do you much good unless you are a mega advanced user.

next part Backtrace (green part) also uses hex memory address to point the command the CPU ran before crashing, again will not do us any good.

next part (bolded black) is still regarding backtrace (what happened before the crash), but it tells us what modules (usually kext) where loaded, usually this part can tell us allot, since this loading sequence ended with crashing the OS. in this section we see the last loaded module (in this example the GeForce) and the modules it depends on that needed to be loaded before it so they probably did not cause the crash since they are already loaded (although still possible that they are the fault – but rarely they are).

next part (Red part) is the exception chain, again stating the data as hex memory address and the CPU registers, will not help us.

last interesting part is the kernel version part (orange part) this part will state what kernel you are using, name version build date and platform in this example:

Darwin

8.11.0

oct 10

PPC (Power PC)

Conclusion 1 : The problem is with the GeForce kext.

_____________________________________________________________________________________

Kernel Panic Example 2:

panic(cpu 0 caller 0×001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0×8001003b, CR2: 0×00000024, CR3: 0×00d7b000, CR4: 0×000006e0
EAX: 0×00000000, EBX: 0×02bacc00, ECX: 0×025dc9a4, EDX: 0×00000000
CR2: 0×00000024, EBP: 0×14053ef8, ESI: 0×00841684, EDI: 0×0083df64
EFL: 0×00010206, EIP: 0×003bd3b3, CS: 0×00000008, DS: 0×14050010
Backtrace, Format – Frame : Return Address (4 potential args on stack) 
0×14053d38 : 0×128d08 (0×3cb134 0×14053d5c 0×131de5 0×0) 
0×14053d78 : 0×1a429b (0×3d0e4c 0×0 0xe 0×3d0670) 
0×14053e88 : 0×19ada4 (0×14053e98 0×14053ea8 0xe 0×48) 
0×14053ef8 : 0×83df81 (0×2bacc00 0×841684 0×14053f28 0×38073e) 
0×14053f28 : 0×39c536 (0×2bacc00 0×28b9880 0×8 0×2) 
0×14053f78 : 0×13d7d9 (0×28b9880 0×2686021 0×0 0xbffff378) 
0×14053fc8 : 0×19ac1c (0×0 0×0 0×4 0×207) Backtrace terminated-invalid frame pointer 0×0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.IOBluetoothHIDDriver(1.7.2b2)@0×8 37000
dependency: com.apple.iokit.IOBluetoothFamily(1.7.14f14)@0×6be 000
dependency: com.apple.iokit.IOHIDFamily(1.4.10)@0×531000

Conclusion 2 : We probably have a problem with the Bluetooth kext. so up to here it was easy and straight forward, the next doesn’t have the loaded module part.

_____________________________________________________________________________________

Kernel Panic Example 3:

Unresolved kernel trap(cpu 0): 0×300 – Data access DAR=0×0000000000000010 PC=0×00000000000819E8
Latest crash info for cpu 0:
Exception state (sv=0×3D849280)
PC=0×000819E8; MSR=0×00009030; DAR=0×00000010; DSISR=0×40000000; LR=0×000819CC; R1=0×2720BB00; XCP=0×0000000C (0×300 – Data access)
Backtrace:
0×00032AC8 0×000823DC 0×00075F58 0×00075918 0×0006B45C 0×0006B730 
0×000578A0 0×0002921C 0×000233F8 0×000ABAAC 0×414C5945 
Proceeding back via exception chain:
Exception state (sv=0×3D849280)
previously dumped as “Latest” state. skipping…
Exception state (sv=0×42AF9280)
PC=0×9000AB48; MSR=0×0000F030; DAR=0×011DB004; DSISR=0×42000000; LR=0×9000AA9C; R1=0xF0101080; XCP=0×00000030 (0xC00 – System call)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0×300 – Data access
Latest stack backtrace for cpu 0:
Backtrace:
0×00095138 0×00095650 0×00026898 0×000A7E04 0×000AB780 
Proceeding back via exception chain:
Exception state (sv=0×3D849280)
PC=0×000819E8; MSR=0×00009030; DAR=0×00000010; DSISR=0×40000000; LR=0×000819CC; R1=0×2720BB00; XCP=0×0000000C (0×300 – Data access)
Backtrace:
0×00032AC8 0×000823DC 0×00075F58 0×00075918 0×0006B45C 0×0006B730 
0×000578A0 0×0002921C 0×000233F8 0×000ABAAC 0×414C5945 
Exception state (sv=0×42AF9280)
PC=0×9000AB48; MSR=0×0000F030; DAR=0×011DB004; DSISR=0×42000000; LR=0×9000AA9C; R1=0xF0101080; XCP=0×00000030 (0xC00 – System call)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC

Conclusion 3 :

1. first option is a random memory access error, meaning that the memory has been accessed to an area that wasn’t expected or allowed, maybe even an application has written into memory that it shouldn’t have (that was not its space) and by that caused the OS/kernel to crash, you should check what recent applications/utilities/kext/bundle/plugin/login items you have installed and remove it or disable its launch for a while until you can sort it out.

2. second option is usually the case for real macs but also possible for PC, as simple as a hardware problem, or bad memory card that causing the problem, maybe it act badly only if it is cold (immediately after booting the machine) or when it is hot (after several hours of work, depends sometimes minutes is enough on a sunny day), another hardware problem can be any hardware that access memory asynchronously, like IO (bluetooth card, modem, wifi, network card, etc.).

3. another option is that your combination of kext and bundles is not working (maybe versions of them some are older then should be?) so for such a case i always keep a bootable/loadable System/Library/Extensions folder on the disk.

4. this option is rarely the case, but can happen, if the main boot partition doesn’t have enough free space it could cause the problem, so all you need to do in this case is to boot in safe mode and free some space.

5. another simple option is the case of a kext/application/kernel trying to access a file that it doesn’t have a permission to access to, this can be caused due to wrong unix file mod, in this case boot into single user and fix permissions.

6. last option (that i can think of) is a bad kernel, so since the kernel itself is badly behaving that is why there are no kext loaded yet, since the kernel hasn’t finished loading the core. this is why i keep a spare bootable/loadable copy on the disk so i can boot from it on a rainy kernel problem day.

_____________________________________________________________________________________

_____________________________________________________________________________________

• Login as Root

“ sudo –s ”

After typing that, it will prompt you for your user password, assuming you’re on an administrator account. Once you are accepted, you can do the rest of these commands.
OR:
“ su “, which asks for the root password. If you don’t have the root user enabled, follow the directions below. NOTE: Enabling the root user can be dangerous.
Again, after typing that, it will ask for the root password.

• Change root password
  If you don’t like your root password, use:

“ sudo passwd root “

Then type in your old root password, then give it a new password. If you had no root password before, it will simply ask you to enter a new password. 

• Change directories
  To move around in the various directories, use cd. Example:

“ cd /applications “

That will move you into the applications folder.
Typing cd with no argument will return you to the directory you were in before.
To change to a directory with spaces in the name, surround the directory name in quotes Example:

 “ cd /Applications/”XChat Aqua”

That will move you into a folder called XChat Aqua in the applications folder.

• Move to other volumes/disks/partitions
  To move to different volumes/disks/partitions, use cd again Example:

“ cd /volumes/Mac “

That will move you into the root (/) directory of the volume named Mac.
You can also change to a volume with spaces, much like the last hint Example:

“cd /volumes/”Mac OS X”

• Remove a file from your Mac
  This will remove a file from the same directory you are in:

rm <filename>

Example: “ rm something.txt “

You can specify a path to a file to delete, if it is in a different folder.
rm /path/to/something Example:

 “ rm /Applications/Candybar.app “

This will remove the application Candybar from your applications folder:

This will remove a directory/folder on your Mac:

rm -d <folder>
Example: ” rm -d delete_me “

(Say you had a folder called delete_me in /, your start disk’s main folder)
Note: You can specify a path for this too, like the previous rm commands.

• Copy a file
  To copy a file, use:

cp <filename> <name_of_copy>
Example: “ cp something.txt somethingelse.txt “

This will make a duplicate of something.txt and name it somethingelse.txt

• Move a file
  To move a file, use:

mv <filename> <destination>
Example: “ mv something.txt /Applications “

This will move something.txt to the Applications folder.

• Find a file
  To find a file, use:

locate <filename>
Example: “ locate Callisto.kext “

This will look for anything related to Callisto.kext on your system.

• Find a binary file
  To find a binary file, like rm, use:

whereis <binary file>
Example: “ whereis rm “

This will look for the rm command.

• Create a folder
  If you want to make a folder:

mkdir <name_of_folder>
Example: “ mkdir directory “

Will make a folder called directory in the current folder you are in.

• Move a folder
  If you want to move a folder:
  mv folder_name path Example:

 “ mv folder /applications “

Will move a folder called “folder” to applications.
NOTE: You can also specify a path if you want to put the folder somewhere specific. Example:

mkdir /Applications/directory

• Repair Permissions of a folder
  If you’ve been naughty and messed with the System/Library/Extensions folder at all, you can repair the owner and permissions of the folder by doing:

chmod -R 755 <path>  
chown root:wheel <path>

Example

“ chmod -R 755 /System/Library/Extensions “
” chown -R root:wheel /System/Library/Extensions “ 

• Repair permissions in Terminal without DiskUtility
  To repair permissions on your whole system without the need of disk utility, do:

“ diskutil repairPermissions / “

• List Files in a directory
  If you want to view files in a folder, do:

“ ls “