Apple released Mac OS X 10.6 aka Snow leopard on 28th of August, we published a guide to install Snow Leopard on PC on 26th of August.  Yes you heard it right, we posted a guide to hack Snow leopard two days ahead of scheduled release. Here is the link of very first guide on internet to Install Snow Leopard (10A432) on PC Hackintosh.

Later in 2009 we published a detailed guide to install Snow Leopard in VMWARE 7 and Windows, that post was a super hit and featured on various frontline technology blogs including Lifehacker, Redmond Pie, Stackoverflow and more. Now we got our hands on the very first seed of Mac OS X Lion (thanks to Apple developer program), and we are ready to have some fun.

We are trying to install Mac OS X lion on PC and VMWARE, and you can find all our progress updates and information related to this project on this single page. Bookmark this page, join us on Facebook, follow us on Twitter and last but not least, you can also subscribe to our free once in a day e-mail news letter to get all the latest updates on Apple related hacks and news directly in your Inbox. Which will provide you with all the news before anyone else knew about it.

Facts about Mac OS X Lion :

• Apple released a developer’s preview of Lion (Build 11A390) on February 24, 2011, to subscribers of Apple’s developers program.
• Mac OS X Lion is set to be released in summer of 2011.
• Mac OS X Lion requires hardware with a Core 2 Duo processor or better. Dual core processors aren’t supported.
• Rosetta, software which makes possible the execution of PowerPC software on x86 hardware, is no longer available. So far best way to run it seems to be VMware fusion.

This article will discuss the first “snow” assembly SnowOSX Universal 10.6 v3.4. Distribution is based on the Snow Leopard 10A421 and installed on a PC computer based on Intel processors with support for instructions SSSE3. First, you need to download the distribution from the Internet. Image SnowOSX Universal 10.6 v3.4 is distributed in ISO format and has a size 4.34Gb, and thus can be written not only under OS X, and Linux or Windows, with an ordinary single-layer DVD. The disc must be burned to a minimum speed x2 or x4.

Where to Download SnowOSX Distro

SnowOSX distro is available on usual places like Bay of Pirates, Mininova or your favorite torrent site. Please don’t ask us or post the links of torrent link in comment because of legal issues. We’ll cover a how to guide very soon so keep following iHackintosh your one stop place for all Apple hackz

General Information about the SnowOSX Distro

Version : Mac OSX Snow Leopard Build 10a432 v3.5
The developer : Apple + dan1234
Platform : Intel only
System requirements : PC computer with an Intel SSSE3 processor, 1GB of memory, 8GB free disk space
Interface language : English + Russian

Kexts Included in SnowOSX Distro

AppleACPIPS2Nub.kext
AppleIntelPIIXATA.kext
ApplePS2Controller.kext
AppleRTL8139Ethernet.kext
CPUi_snow.pkg
dsmos.kext (from Netkas to 10a432)
HDEFInject.kext
LegacyAppleAHCIPort.kext
LegacyAppleIntelPIIXATA.kext
LegacyAppleYukon2.kext
LegacyIOAHCIBlockStorage.kext
LegacyJMicronATA.kext
NVInject.kext
OpenHaltRestart.kext
PlatformUUID.kext
SleepEnabler.kext
SMBIOSResolver.kext
TARUGA_SNOW
VoodooHDA.kext

FYI

If you have any question we’ll love to hear back from you on twitter via @ihackinjosh You can also subscribe to our daily free e-mail news letter and keep your self updated with the latest of community.

Inspiron 1525 is one of the bestseller from Dell Computers. The Dell Inspiron 1525 is an excellent budget notebook with good looks and solid performance. This isn’t a gaming machine, but the 1525 can handle everyday computing tasks with ease. If you are an experimental person like me then obviously you’d like to Install and run OS X on your Inspiron. If you wants to install Mac OS X on your Dell Inspiron 1525 here is the handy guide to do so. In the following tutorial we used iPC 10.5.6, you can download iPC from Bay of Pirates or Green Demon. Please don’t ask or post for the download links for iPC.Google is your F.R.I.E.N.D.

Image [Flickr] ____________________________________________________________________________________

Procedure

____________________________________________________________________________________

Step 1. Grab the iPC 10.5.6 ISO and burn it at very low speed.

Step 2. Read this guide twice or thrice before getting started.

Step 3. Put your DVD in rom and restart your computer with the DVD in Drive,now you should see Darwin load screen.

Step 4. As counting starts press F8 key and you will be able to have some more option’s.

Step 5. Now type -V and press enter now entered in VERBOSE mode here you are able to see any error if your screen freezes for more than 15 minutes than note last three lines and Google them to find out a solution for your problem. If every thing goes fine after 15-30 minutes installation screen appears hold your breath we are not quit yet here.

Step 6. On the top a menu bar appears click Utilities >> Disk Utility.

Step 7. Here select the destination drive where u want to install Mac OSX.

Step 8. Now click on ERASE on right hand side and under the format option select
” MAC OSX Journaled Extended ” and click Erase. Now the disk will be erased and mounted once this done you are very near to near to your destination.

Step 9. Now close the disk utility and click on the partition which you created at previous Step.

Step 10. In Customize option select the following patches.

• Chipset Drivers >> Intel ICHx SATA Drivers
• Wireless Driver >> Broadcom Driver
• USB Drivers >> Patched USB Driver
• Power Management >> Clamshell Display Support
• Fixes and Patches >> USB Mount Fix
• PS/2 Device Support >> PS/2 Keyboard Fix
• DSDT Patches >> Patch DSDT
• AppleSMBIOS Patch >> AppleSMBIOS-27 Rev6 MacBook

Step 11. Now your disk will be checked for consistency than installation begins. It will take 30-45 minute’s as your hardware.

Step 12. Now that you’re done installing you can remove the disc and on the boot screen press “F8″ and type “-v -f” When the screen loads up it should just be a black screen, after this close the lid till you see the power light slowly “breathe” or pulse. When you open the lid you should be greeted with the Post-Install screen. Type all your info and stuff.

Step 13. From here you’re going to need the 1525 Driver Pack. Everything in the pack has a readme. Download Here

Important Note :

1. Now you can run all of your software updates and when you come back you wont have wi-fi, simply go into the misc folder and run the broadcom patch and you’ll be back in business.
2. Anytime you install a patch, you should run -v -f to make sure everything loads properly.

Last time we published to Install Snow Leopard (10A432) on Intel PC or Hackintosh, now we got the Modbin’s kernel for AMD systems so it’s possible to run Snow leopard on AMD systems too. Hats off to Modbin for releasing the kernel in such a short time. Please note that the Kernel is still in testing phase so there may be some bugs. Although we have got some successful installation reports like this one from Aryajuanda (Infinitemac). In his thread he used Chameleon rc 2.640 pkg. and PCEFI V10, DSDT patch, Some kexts and Modbin Kernel. The Installation procedure is very similar to our guide on Intel PC, the major difference is we placed the new kernel in the root of volume.

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….

Updating the Hack-i-ntosh or OSX86 install is a very panic process for newbies, so we advise you to make the backup of your system before hitting the update process. If this is the first time you are updating your hackintosh then read this guide twice before getting started. This guide is for Non vanila or hacked kernel & INTEL based system only. Vanilla users just update and restart. You can also use this guide for updating 10.5.X to 10.5.8 with Combo Update remember you must have patched your DSDT. If you are upgrading from 10.5.7 then download Delta Update. Updating Process is same as usual like you updated from previous one. You can download Delta update (274MB) and Combo update (759MB). Before starting the process download & install osx86tools from PCWIZ.

Second Phase :

Open osx86tools  >>> Check repair permissions >>> Set kext permissions >>> Clear extensions cache >>> Restart.

Boot using -v to see if any errors.

More guides of Interest :

• Basics of OSX86 for Noobs Start From Here
• What is kext,Where is kext, how to Install kext.
• Make Bootable Mac OSX86 USB Stick Installer Yourself.
• How to Install Chameleon 2.0 RC1.
• Dummies guide to Add OSX into XP,LINUX,VISTA Bootloader’s
• Install Mac Leopard OS X Retail DVD on a Ordinary PC with Boot 132 hack.

A kernel panic is an action taken by an operating system upon detecting an internal fatal error from which it cannot safely recover. You may encountered with a kernel panic while installing OSX86 or Hackintosh. There are plenty of reasons why Kernel Panic occurs some of them are Defective or incompatible RAM, Incompatible or corrupted kernel extensions, Incompatible or corrupted drivers, Hard disk corruption, including bad sectors, directory corruption, and other hard-disk ills and most possible Incompatible hardware. Attempts by the operating system to read an invalid or non-permitted memory address are a common source of kernel panics. A panic may also occur as a result of a hardware failure or a bug in the operating system. In short there are plenty of reasons and resolutions for kernel panic. Here we study three different Kernel Panic case  Apple2PC Described it very beautifully. You can read the Panic errors given below and understand why it happens.

Kernel Panic Example 1:

Unresolved kernel trap(cpu 0): 0×300 – Data access DAR=0x0000000030D6334E PC=0x0000000027B5CD3C
Latest crash info for cpu 0:
Exception state (sv=0x27CA4500)
PC=0x27B5CD3C; MSR=0×00009030; DAR=0x30D6334E; DSISR=0×40000000; LR=0x27B5CD24; R1=0x0D80BAE0; XCP=0x0000000C (0×300 – Data access)
Backtrace:
0x27B5E6C4 0x27B5D82C 0x27B5607C 0x27B45C74 0x002E9A80 0x002EB94C
0x0008C248 0×00029234 0x000233F8 0x000ABEAC 0x8001016C
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x27b3a000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x1d8f7000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0×27867000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x2788b000
dependency: com.apple.NVDAResman(4.1.8)@0x278a1000
Proceeding back via exception chain:
Exception state (sv=0x27CA4500)
previously dumped as “Latest” state. skipping…
Exception state (sv=0x1D92D280)
PC=0x9000B348; MSR=0x0200F030; DAR=0x02A8A000; DSISR=0×42000000; LR=0x9000B29C; 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:
0x000954F8 0x00095A10 0×00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x27CA4500)
PC=0x27B5CD3C; MSR=0×00009030; DAR=0x30D6334E; DSISR=0×40000000; LR=0x27B5CD24; R1=0x0D80BAE0; XCP=0x0000000C (0×300 – Data access)
Backtrace:
0x27B5E6C4 0x27B5D82C 0x27B5607C 0x27B45C74 0x002E9A80 0x002EB94C
0x0008C248 0×00029234 0x000233F8 0x000ABEAC 0x8001016C
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x27b3a000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x1d8f7000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0×27867000
dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x2788b000
dependency: com.apple.NVDAResman(4.1.8)@0x278a1000
Exception state (sv=0x1D92D280)
PC=0x9000B348; MSR=0x0200F030; DAR=0x02A8A000; DSISR=0×42000000; LR=0x9000B29C; 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 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0×00000024, CR3: 0x00d7b000, CR4: 0x000006e0
EAX: 0×00000000, EBX: 0x02bacc00, ECX: 0x025dc9a4, EDX: 0×00000000
CR2: 0×00000024, EBP: 0x14053ef8, ESI: 0×00841684, EDI: 0x0083df64
EFL: 0×00010206, EIP: 0x003bd3b3, CS: 0×00000008, DS: 0×14050010
Backtrace, Format – Frame : Return Address (4 potential args on stack) 
0x14053d38 : 0x128d08 (0x3cb134 0x14053d5c 0x131de5 0×0) 
0x14053d78 : 0x1a429b (0x3d0e4c 0×0 0xe 0x3d0670) 
0x14053e88 : 0x19ada4 (0x14053e98 0x14053ea8 0xe 0×48) 
0x14053ef8 : 0x83df81 (0x2bacc00 0×841684 0x14053f28 0x38073e) 
0x14053f28 : 0x39c536 (0x2bacc00 0x28b9880 0×8 0×2) 
0x14053f78 : 0x13d7d9 (0x28b9880 0×2686021 0×0 0xbffff378) 
0x14053fc8 : 0x19ac1c (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)@0x6be 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=0x00000000000819E8
Latest crash info for cpu 0:
Exception state (sv=0x3D849280)
PC=0x000819E8; MSR=0×00009030; DAR=0×00000010; DSISR=0×40000000; LR=0x000819CC; R1=0x2720BB00; XCP=0x0000000C (0×300 – Data access)
Backtrace:
0x00032AC8 0x000823DC 0x00075F58 0×00075918 0x0006B45C 0x0006B730 
0x000578A0 0x0002921C 0x000233F8 0x000ABAAC 0x414C5945 
Proceeding back via exception chain:
Exception state (sv=0x3D849280)
previously dumped as “Latest” state. skipping…
Exception state (sv=0x42AF9280)
PC=0x9000AB48; MSR=0x0000F030; DAR=0x011DB004; DSISR=0×42000000; LR=0x9000AA9C; 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 0x000A7E04 0x000AB780 
Proceeding back via exception chain:
Exception state (sv=0x3D849280)
PC=0x000819E8; MSR=0×00009030; DAR=0×00000010; DSISR=0×40000000; LR=0x000819CC; R1=0x2720BB00; XCP=0x0000000C (0×300 – Data access)
Backtrace:
0x00032AC8 0x000823DC 0x00075F58 0×00075918 0x0006B45C 0x0006B730 
0x000578A0 0x0002921C 0x000233F8 0x000ABAAC 0x414C5945 
Exception state (sv=0x42AF9280)
PC=0x9000AB48; MSR=0x0000F030; DAR=0x011DB004; DSISR=0×42000000; LR=0x9000AA9C; 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.

_____________________________________________________________________________________

Kexts, or kernel extensions are drivers that are installed to /System/Library/Extensions/.Kext files often have the “.kext” extension and allow for extra hardware support and and in the case of OSx86, to replace Appleʼs original drivers with ones that are optimized for use on PCs. Leopard holds kext files/folders in the /System/Library/Extensions folder, at boot time the relevant kext are uploaded from Extensions.mkext this is a cache folder that contains kext related to the installed hardware. If you loves your hackintosh then take a full backup of your kexts because some kexts may disappear after the update procedure.

For making backup of your Kexts open Terminal and type in these commands:

sudo -s
[enter password]
cp -r /System/Library/Extensions /System/Library/Extensions.backup
cp -r /mach_kernel /mach_kernel.backup

For restoring your Kexts open Terminal and type in these commands:

sudo -s
[enter password]
cp -r /System/Library/Extensions.backup /System/Library/Extensions
cp -r /mach_kernel.backup /mach_kernel