Archive for January 2012

How to update iATKOS L2 to 10.7.3 [ Easy way ]

The original installation media for Mac OS X Snow Leopard was a 10.6 DVD. The DVD was only updated once to version 10.6.3. In order to provide more frequent updates to users, Apple is now slipstreaming the latest version of Lion directly into the download. Upon fresh installation, no updating is necessary!

If you purchased Lion from the App Store prior to February 1st, 2012, you most likely have 10.7.2. To re-download Lion and update your App to 10.7.3, simply log into the Mac App Store and click Update.
When the download finishes, the app will automatically open. The updated 10.7.3 Install Mac OS X Lion App can be found in the Applications folder.

If you don't see the Update button, follow this simple procedure.

     1. Delete your existing copy of Install Mac OS X from Applications folder.
     2. Hold down the alt/option key on your keyboard, and click the App Store icon.
     3. With alt/option key held, click on Purchased
     4. With alt/option key held, click on OS X Lion
     5. With alt/option key held, click on Install

If either of the above processes don't work for you, try creating a new User account. You can delete it later.

     1. Open System Preferences
     2. Click on Accounts
     3. Click Lock Icon
     4. Click (+) to add a new User
     5. Create a new Admin User
     6. Log out, and log into new User
     7. Proceed with steps above.


Sent by Mandura

UNIX, APIC and PCI Flags [ Fix ]

Unix Flags that might work in OSX. See subcategories for details

This list is mostly AMD specific boot options & for 64bit CPU's. Might also help with Intel CPU's. This list needs extensive testing & feedback but most of these flags do work in OSX. Once more info is gathered They will be categorized into the lists above

Machine check Options Flags

= Disable machine check. For compatibility with i386. Might help boot some AMD systems. nomce does the same same as mce=off

= Enable logging of machine checks left over from booting.
Disabled by default on AMD because some BIOS leave bogus logs. If your BIOS does not do that it's a good idea to enable this log to make sure you log every machine check event that result in a reboot. On Intel systems it is enabled by default.

= Disable boot machine check logging.

tolerancelevel (number from list below)

0: always panic on uncorrected errors, log corrected errors

1: panic or SIGBUS on uncorrected errors, log corrected errors. Default is 1
2: SIGBUS or log uncorrected errors, log corrected errors
3: never panic or SIGBUS, log all errors (for testing only)

APIC Flags

= Use IO-APIC. Default

= Don't use the IO-APIC.

= Don't use the local APIC

= Don't use the local APIC (alias for i386 compatibility)

= Don't set up the APIC timer

= Don't check the IO-APIC timer. This can work around problems with incorrect timer initialization on some boards.

= Run time keeping from the local APIC timer instead of using the PIT/HPET interrupt for this. This is useful when the PIT/HPET interrupts are unreliable.

= Don't do time keeping using the APIC timer. Useful when this option was auto selected, but doesn't work.

Either set to 0 or 1. Same as apicmaintimer=1/0. Do APIC timer calibration using the pmtimer. Implies apicmaintimer. Useful when your PIT timer is totally broken. Sometimes there are timer routing problems on some Nvidia and ATI chipsets. Assuming you're using 64bit then you can try apicmaintimer or apicpmtimer. On 32bit you can try pci=noacpi noapic. Needs testing.

/ enable_8254_timer = Enable interrupt 0 timer routing over the 8254 in addition to over
the IO-APIC. The kernel tries to set a sensible default.

PCI Flags

= Don't use PCI

= Use conf1 access.

= Use conf2 access.

= Assign ROMs.

= Assign busses

= Don't use ACPI to set up PCI interrupt routing. 

Flags for hacked kernels ONLY [ Fix ]

kernel name "mach_kernel" This flag simply tells the system to boot from another kernel available in / (aka root).

= Most of the hacked kernels include the possibility at boot to chosen FSB frequency. These flags DO NOT work with any known vanilla kernel. Do testing with the below values to see what works for you. The default value is 200Mhz. If you want different value, you have a few possibilities.

Ex: kernel name "netkasSS_kernel"

Ex: fsb=800 or use one of these flags below:

= For frequency's multiplied by 100 Mhz
-y = For frequency's multiplied by 133 Mhz
-z = For frequency's multiplied by 166 Mhz

* You can easily add either the -y, -g, or -z options to your boot.plist file or use the fsb=<mhz> flag to give it an exact figure. I have not tested the fsb=<mhz> flag but the -y gave me the correct 800fsb (100mhz x 8) and boosted my performance to where it should be in OSX. This may not change the FSB in about this mac on a hack, it did not for me. You would need to test with a benchmark app to see the gain. Hopefully hardcoded front side bus speeds can be added to SMBIOS files at some point in the future by netkas or Mac.Nub.

= Force vmware support, with hacked kernels. Needs testing.

= Force 64bit mode for AMD 64 bit cpu's. Needs testing.

= Number of physical cpu's installed NOT CORES. Also needs testing


Darwin flags for and more [ Fix ]

Note: Any flag can be added to your boot.plist but these are just the common ones.

"Boot Graphics"=Yes
= Yes or No. Use graphics mode or text mode when starting. Turns off vesa mode graphics at boot.

"Quiet Boot"=Yes
= Yes or No. Use quiet boot mode (no messages or prompt). Same as adding -v option.

= Any number 1-100. Number of seconds to pause at the boot prompt.

When added as a boot flag to your will give you details about a kernel panic you have at any time when running OSX. I believe it is the same as debug=0x100, not sure.

Kernel level flags:

= The flag attempts to enable the L2 cache if not already enabled. Not sure if this works on hacks. If your having an L2 cache issue try this flag.

Tells the kernel how many cores there are in place. Ex: cpus=1 OR cpus=2

Lets you set two values ether 1 or 0 stating true or false, if set to true then at idle time the cpu will halt causing power saving and cooling of CPU, if set to 0 then the cpu will allways run even in idle time.



Lets you set two values ether 1 or 0 stating true or false. This flag is exactly the same as the one above I believe. Please correct me if I'm wrong.



= causes the system to load in 32 bit mode while running on 64 bit version of OS X

= To show information about kernel panics & other useful info from system at startup. If you are getting a auto rebooting from bad kernel or kext being loaded use this flag to see what it is. Will help when posting information on this forum for diagnoses.

= This allows you to specify maximum memory used by the system. Not sure if the rest of the memory is used for apps or not. Many people have to use this if they have 4GB of memory in a 32bit OS. Ex: maxmem=2048

Darwin boot loader level flags [ Fix ]

-v = verbose mode. Basically tells you wants happening during boot up.

= Safe mode. Basically boots your system with the bare minimum kexts.

= Single user mode. Command line only mode. Allows you to run commands as root to fix system.

= Tells the machine to reload all kext and dump the boot configuration cache, (kext cache found in: /System/Library/Extensions.mkext, you can delete it manually and the system will recreate it).

"Graphics Mode"=
Tells the system what resolution width, height, color depth & refresh rate to boot the OS with.

Ex: "Graphics Mode"="1024x768x32" WIDTHxHEIGHTxDEPTH

For VESA 3.0 graphics, you may append a refresh rate after an "@" character

Ex: "Graphics Mode"="640x480x32@60" WIDTHxHEIGHTxDEPTH@REFRESHRATE

This parameter state what is the boot disk to use (instead of using the boot menu appearing before the prompt) you state the drive and partition in here: diskXsY where X stands for the disk number (first disk, usually primary master in IDE or SATA) 0 second disk is 1 etc.) and Y stands for the partition on that disk starting with 1 as the first partition.

Ex: rd=disk0s1 If you have one disk and one partition the parameter will look like this.

You can also use rd=*<IODeviceTree path> for booting from a PCI RAID card for example. Ex: of this would be rd=*/PCI0@0/CHN0@0/@0:1

this parameter sets the platform to use at this boot time.

Examples of this flag are:

platform=ACPI (ACPI support)

platform=X86PC (non ACPI support)
platform=ACPI|86PC (try to support ACPI if fails do not support it)

= this info screen display information about the memory on the machine

= this info screen display information about the video card supported graphic modes

ACPI Flags

= Don't enable ACPI

= Use ACPI boot table parsing, but don't enable ACPI interpreter

= Force ACPI on (currently not needed)

= Disable out of spec ACPI workarounds.

{edge,level,high,low} Set up ACPI SCI interrupt. EX: acpi_sci=edge

= Don't route interrupts 

VIDEO: A little more about Kernel Panics


VIDEO: Hackintosh Overview 2012


The true is this happen for a lot of things, but this guide will help a lot of users.

1. Boot from the rBoot CD
2. While hovering over the OSX partition, type in mach_kernel  rd=disk0s2
3. OSX started up fine, and then to avoid the need of keeping the rBoot disc in 24/7 to get into OSX, simply reinstall Chameleon.



You only need to add:

 npci=0x2000 to Kernel Flags in /Extra/org.chameleon.Boot.plist


DSDT for DELL Studio XPS [iATKOS v7, S3 and L1-L2 ]

Fix video, wifi, LPC, SD-card reader.  LINK

iATKOS L2 [ Installation Guide ]

Change Log from L1 to L2:

- 10.7.2 main system > Finally, Lion main system is completely OK for this release, though we are running it on real Macs. We discovered that previous release L1 and most retail installations starting from 10.7.0 have problems, especially for sandybridge hardware, tested on real Macs.. Upgrade installations from Snow Leopard are OK but they work slower than usual.
:arrow:I recommend iATKOS L2 release or retail installs using only the full 10.7.2 retail package.

- Bootloaders updated > Chameleon 2.1 svn r1650, Chimera 1.6

- DVD boot > updated to Chameleon 2.1 svn r1650, patched IOPCIFamily driver added, Non-AHCI ICHX SATA/IDE driver added, AHCI SATA driver updated, npci=0x2000 flag added

- Updated drivers, packages >
/Extra/Extensions option removed
AHCI SATA driver updated
Intel Non-AHCI ICHX SATA/IDE driver added
SSD Trim support added
USB 3.0 driver updated
PS/2 driver updated and laptop keyboard problem solved
Laptop Battery driver added
GF100 and ATI 48xx driver updated for 10.7.2 system
Realtek RTL8111/8168 wired ethernet driver updated to v0.0.90
Ralink and Realtek wireless network drivers removed
Atheros AR8121/AR8113/AR8114 wired network driver added
Atheros AR9285 and AR9287 wireless network driver added

- System Updates > Some more drivers will be protected after the update, read the related section in the "read me".

Tips for iATKOS L2 installations:

- For iCloud and FaceTime > use Champlist to modify smbios.plist after the installation.
Champlist is located at /Applications/Utilities/Tools

- To activate AirDrop for all devices >
execute "defaults write BrowseAllInterfaces 1" using Terminal

iATKOS L2 Installation Guide

The oscar goes to Apple and OSX86 community..

Thanks to all of our forum operators..

All the GGRN people, hey folks :)

Our team OSX86.Türk, EVOSX86, Project OS X, InsanelyMac, tonymacx86 and other OSX86 development platforms and the developers are the reason for this system to survive..


a) This is an OSX86 installer and this is only designed for Non-Apple X86 Intel CPU computers.
b) Includes Apple's Mac OS X Lion 10.7.2 (Build 11C74), X86 patches and some basic drivers.
c) You do not need any other OS X system on your target computer, you only need iATKOS L2 burned to 4.7G DVD or restored on a USB media to install OS X Lion.

Hardware Compatibility is the most important subject for this OS.
Requirements for OSX86 system:
- Compatible motherboard
- Intel Core CPU
- Compatible VGA card
- Minimum 1GB RAM
- Minimum 15GB free space on target partition

So, you need to know about the compatibility of your hardware before installing this system. To get your hardware details (Vendor IDs, Device IDs):
-Fire up a Linux Live CD (ie. Ubuntu Live CD), type "lspci -nn" in terminal and take notes.
-Windowsers, get Everest Ultimate Edition and export the information.

After getting your information, you will need to visit Wiki HCL pages and OSX86 forums on the internet.
Mostly, compatible chipsets and device id's work but this is not a rule, same models of different brands with same chipsets and id's may have differences that can result with incompatibility.
Search before asking "Will this hardware work with iATKOS L?".
Simply, if a hardware that is not compatible for OSX86 10.7.2, then it is also not compatible for iATKOS L2.

Make sure that the md5 checksum of your iATKOS dmg file matches the one posted on our website. If not, then you have a faulty dmg image file.

If something goes wrong, please don't panic. Scroll down for the Troubleshooting guide. If that fails, take a screenshot (or a picture) of what went wrong and post it in the forums. Make sure you have done the 3 Revival steps and troubleshooting steps before posting in the forum!


- You can make clean, upgrade and refresh installs to your existing OSX86 system using iATKOS L2. Please read the related section below.

- Easy installation on Software RAID volumes, no additional user actions needed. Please read the related section below.

- Using software updater to apply main system updates just like real Macs on most PC hardware is possible, but we can never know what Apple will do in their upcoming updates, so it may not result in %100 success, also some of the drivers should be reinstalled after updates. Please read the related section below.

- This installer may not include all the necessary drivers required by your setup. Additional steps may be needed to be taken by the user to setup and use such components.

- Main system is fully stock. @Karmic Alice and I are running L2 main system on our MacBooks. After working on real Macs, finally Lion system is now completely OK with this L2 release. Thanks to @Karmic Alice for participating on the experimental work.

- AppleHDA patches, some VoodooHDA kexts and the Chimera bootloader is from

- Artwork by @denizckosar

- Spanish translations by @Karmic Alice.

Before Installation:

-Backup your personal data

-Check your BIOS settings >>
Execute Disable bit: Enabled
XD: Enabled
Limit CPUID Max: Disabled
Virtualization: Disabled or Enabled, try it.
Hyper-threading: Disabled or Enabled, try it.
HPET: Enabled

-A target partition (primary partition for MBR) or disk will be needed for installation. If you are not an advanced user, then use a clean harddisk with no personal data/OS as for target and unplug all the other harddisk drives connected to your motherboard just to be safe.

-If the target disk includes personal data and/or any OS, we advice Parted Magic Live CD for partitioning and such operations for preparing a target. You can also do the partitioning and create targets by using OS X Disk Utility.

Starting the Installation:

- Boot using the iATKOS L2 media (DVD or USB)

- If you have a NetBook with an Intel Atom CPU, then press F8 at boot screen, type "mach_atom" without quotes and hit enter.

- Select the language

Clean Installation:

1- Run Disk Utility via Utilities menu and erase the target for clean install

- You can choose MBR (Master Boot Record) or GPT (Guid Partition Table) via partitioning options. If you want to change your existing partition table type, note that all your existing data on disk will be gone! Please do not play with partitioning options if your are not an advanced user.

2- Select the destination for installation

3- Click Customize* and select what you need

4- Click Install

Upgrade from previous versions:

You can upgrade your existing Snow Leopard or Lion installations to Lion 10.7.2 or make a refresh install to your 10.7.2 system (keeping your applications, data, user settings and accounts) by using iATKOS L2.

Some of your drivers/applications just may not be compatible with Lion, know that they may fail after upgrade, this may also cause kernel panics. So search for your existing software/driver compatibility for Lion, before upgrading to Lion.

Your 3rd party applications, personal data, user settings and user accounts will be reserved but all system files/drivers/applications will be gone, so you will need to setup your selections just like a clean install.

1- Select the destination for upgrade installation

2- Click Customize* and select what you need

3- Click Install

* Customize:

This is the most important part of the installation. List of selections..
There is already a basic default profile chosen. You should add only device drivers for your hardware setup at first trials of your OSX86 installing adventure if you are a newbie, then you may try adding other packages to find out the best combination for your PC. Adding a few packages to default profile will probably be enough for most computers.
Please read the descriptions of the packages carefully.

Basics you should know:

- Do not select more than one item for one operation. ie. graphic cards or bootloaders. Only select one bootloader, one enabler method for your graphic card, one method for your sound card, etc..

- "Graphics Enabler" option of the bootloader should be the first choice for activating the OS X driver for your VGA card.

- You can of course try the drivers or methods to make your hardware components work but, it is better to google it before trying the packages. You can easily find the solution for i.e. nVidia 5xx cards inside the iATKOS L2 by searching on google (select ATY_Init and after install, add your device id.. etc.).

- Most ATI Mobility VGA cards are not compatible with this system and most compatible ATI cards need their custom packages/modifications which is not included in this release. You must search and find the appropriate driver/solution by your own for such ATI hardwares, so do not continuously ask for ATI support on forum.

- You may not be able to have success at first trials, so keep on trying.. If you are complaining about having no success on 3rd install, then install Windows XP.

Software RAID:


- Software RAID combines two or more physical harddisks or their partitions (RAID slices) into a single logical unit. RAID's various designs involve two key design goals: increase data reliability and/or increase input/output performance.

- You can create RAID volumes and install Lion on RAID using iATKOS L2.

- RAID levels or types for OS X:
Striped RAID (RAID-0): A RAID-0 set splits data evenly across multiple disks with no parity information for redundancy. RAID0 is normally used to increase performance for both read and write. It can also be used as a way to create a small number of large virtual disks out of a large number of small physical ones. Simply it is a way to use the disks like using the dual or more channel RAMs, so it increases the read and write performance more than a bit. RAID0 sets are advised for the main system volumes to increase the performance of the OS.
Mirrored RAID (RAID-1): A RAID-1 set creates an exact copy of a set of data on two or more disks. This is mostly for data safety and also an increase of performance for read operations is expected. The RAID array can only be as big as the smallest member of the slices. RAID1 sets are used for security and advised for data storage volumes.
Concatenated Disk set: Which is not exactly a RAID level. The slices are merely concatenated together, end to beginning, so they appear to be a single large disk. It provides no data redundancy. This may be thought of as the inverse of partitioning. Whereas partitioning takes one physical drive and creates two or many more logical volumes, concatenation uses two or more slices to create one logical volume. No increase in performance is possible and neither increased data reliability is possible.

- Boot helper partition: OS X Software RAID systems boot using boot helper partitions and so the bootloader will be installed to boot helper partition instead of the RAID slice. If one of the RAID slices of your target RAID volume is disk0s2, then its hidden boot helper partition named as "Boot OS X" is disk0s3. Do the math for the others.

- Create RAID volumes: You can easily create RAID volumes using OS X Disk Utility. Do the partitioning if you need to, click on the target disk and then click on RAID tab, choose RAID type, name it and by pressing "+" create a new RAID set. Add the target partitions or disks to RAID set by dragging them and when you are done, click to "Create" button. The added partitions or disks will be the slices of your RAID set, in a few seconds your RAID volume will be mounted and ready for installation.

- iATKOS L2 RAID operations:
-L2 installs the bootloader of your choice to the boot helper partition of the preceding disk of the RAID set, so the first disk by your bios will be the Mac OS X boot disk. You can install any foreign bootloaders to other harddisks of your RAID set, there will be no harm to your RAID set. On my 3x RAID0 system, second HDD has Grub bootloader and the third one has Windows bootloader installed seperately and all running fine. I am using Grub to boot all.

RAID Install Steps:

1- Create RAID volume as described above

2- Select it as destination for install

3- Click Customize and select what you need

4- Click Install

Main System Updates:

As you know, using software updater to apply main system updates is possible for most PC's. Your custom kernel and many drivers will be protected after the update but some drivers and patches will be overwritten and some will be non-functional, so computers that need these drivers and patches will need to take some actions after updating. These packages are:

- USB: IOUSBFamily.kext and IOUSBMassStorageClass.kext
- GF100: GeForceGLDriver.bundle
- SSD Trim support: IOAHCIFamilyTrim.kext

The files will also be installed to /Library/Temp folder. So, you will need to re-install them after applying the update. Kext is located at /Applications/Utilities/Tools. Drag the kexts on to Kext Utility.

- VoodooHDA: Any of the VoodooHDA versions may cause kernel panic after updating your system. Solution is deleting AppleHDA.kext from /System/Library/Extensions directory after applying the update.
- ATI 48xx: This driver will be non-functional after applying main system update. You need to search for new version of this patch. Follow Netkas' blog.

Every main system update had some issues with our PC hardwares that had been covered mostly after the release of the update, so updating like real Macs is not a thing that you can always count on because we can never know what Apple will do for the next update. Until now it had no major problems with X86 PC hardwares.


iATKOS L2 has no integrated procedure for multibooting but preparing a multiboot GPT or MBR system with this release is easy.

Here is a ''How To'' for GPT and MBR triple boot including Mac-Win-Linux. iATKOS L2, Debian GNU/Linux DVD and Windows7 DVD installers are used in this example.

- MBR (Master Boot Record) triple boot -

- Nearly all PC's work on MBR partitioned harddisks, check it with Disk Utility, if so do no touch it. If it is GPT then you need to repartition your harddisk by loosing all the data in it. Click to partitioning options, select MBR and do the partitioning.

- Create 3 or more partitions by using iATKOS Disk Utility or Parted Magic Live CD. Mac OS Extended Journaled (HFS+) format for OS X target, MS-DOS (Fat32) for the others. OS targets must be one of the first 3 partitions creating with Disk Utility.

- Add boot flag to Windows or Linux target and install the operating systems in any order you like.
For windows, make sure the windows target disk is the first preceding disk by your BIOS, unplug the other harddisks if needed. This is a general windows issue.
For linux, do not install linux bootloader to MBR, install it to linux root.

- Boot iATKOS L2 and install OS X to target as usual.

- If Windows fails to load then you may need to repair Windows (win7 or vista) (mostly you will not face this issue): Add boot flag to Windows partition, boot Windows DVD, select repair, add boot flag to OS X partition.

- You can also add boot flag to Linux partition to use Linux bootloader for multiboot manipulation if you want to.

Now you have triple boot on MBR.

Note: Adding boot flag to MBR partitions: Boot Parted Magic Live CD, right click to partition, select flags and click to boot.

- GPT (Guid Partition Table) triple boot -

- Check the partition table type with Disk Utility. If it is not GPT then repartition the drive and change the partition map scheme to GPT by pressing partition options. You will loose all the data on target disk by repartitioning.

- Create 3 or more partitions by using iATKOS Disk Utility. Mac OS Extended Journaled (HFS+) format for OS X target, MS-DOS (Fat32) for the others. Windows and Linux targets should be of the first 3 partitions.

- Boot Windows Media and install it to its FAT32 target.

- Boot iATKOS L2 and install OS X to target as usual. You have dual-boot with OS X and windows right now.

- Boot Linux media and install the operating system (OS) to its FAT32 target.
Do not install the linux bootloader to MBR, install it linux root.
Do not change the boot flags.
Do not modify the partition table, it can be risky for some distros, just erase the target and do the install.
Use grub2.

- Now you can boot to OS X and Linux using OSX86 bootloader which boots by default, but windows fails at this stage because Linux installation broke the hybrid GPT, so we will bring it back on this step.
Boot iATKOS L2 and enter "gptsync /dev/diskX" command on terminal. X is the BSD number of your target disk, run disk utility and right click on your disk, you will see it.

Now you have triple boot on GPT. By default, OS X bootloader will take the control by these steps. It can boot all of them by just selecting. If you want linux or windows to take the control of multibooting then go on reading, it is described below.

All the OS' are independent by this way, you can re-install each of them one by one when needed. You just need to care about 2 things:
- gptsync will be needed after Linux re-install
- you need to re-install OS X bootloader after Windows re-install. Boot iATKOS L2, install the bootloader using terminal. If you use linux for multibooting then this step is not necessary.

There are more combinations to make multiboot work on especially on GPT. If you know the procedures as well, there is no thing like an unrecoverable multiboot error. i.e. > keep in mind that hybrid GPT may fail when dealing with linux stuff, then windows will not boot. Do not use parted magic live cd for Hybrid GPT, it breaks Hybrid GPT causing an unbootable windows. There comes the gptsync, it creates a fake MBR code on GPT drives that make Windows feel like it works on MBR partitioned hdd.

You can always apply gpysync if hybrid GPT is broken somehow. After bringing back the hybrid GPT partition using gptsync, windows will work again. After gptsync, you can add boot flag to other partitions by using OS X or Linux fdisk if you like to boot from another OS. i.e. >> booting from linux and using grub for multiboot manipulation instead of chameleon.
For OS X fdisk, boot iATKOS L2 and open terminal:

fdisk -e /dev/diskX # X is the BSD number of your target disk
p # p is the fake MBR partition list
f Y # f for adding boot flag to the target partition, Y is the partition number you want to boot from
w # w to write changes
q # q for quit.

In this multiboot example I created 4 volumes, 3 for OS' and 1 for storage. OS volumes are first 3 ones. As you see on this fdisk print out and disk utility screen below, fdisk lists the 4 partitions of fake MBR of my hybrid GPT. You can not see the "Data 2" partition (disk0s5) there because it is the 5th one. 1st partition is the hidden efi, for this reason the OS' are to be installed to first 3 volumes.

Enter 'help' for information
fdisk: 1> p
Disk: /dev/disk0 geometry: 30401/255/63 [488395055 sectors]
Offset: 0 Signature: 0xAA55
#: id cyl hd sec - cyl hd sec [ start - size]

1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639]
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 97656256] HFS+
3: 07 1023 254 63 - 1023 254 63 [ 98328576 - 97654784] HPFS/QNX/AUX
*4: 83 1023 254 63 - 1023 254 63 [ 195983360 - 97654784] Linux files*
fdisk: 1> _

disk utility layout:
250.06GB WDC WD250…
-Data 2

Unmounted disk0s4 volume is ext4 linux partition (hd0,4) in this example. I added the boot flag to Linux partition using OS X fdisk and modified the grub.cfg file to boot all of them via grub2.

### here is the grub.cfg lines of this example for multibooting
menuentry "Lion" {
insmod hfsplus
set root=(hd0,2)
multiboot /boot
menuentry "Windows 7" {
set root=(hd0,3)
chainloader +1
menuentry "Debian GNU/Linux……

Simple Troubleshooting guide:

At times after installation, your system may not work properly as in - it may restart, not boot at all or hang at a certain point. This is quite normal and there are many ways for it to be fixed. It varies from one case to another case. However this basic troubleshooting guide would help you to fix most of the common problems.

- If you're facing hangs, freezes or kernel panics (which is present as a shutdown symbol on the screen just after boot) type in "-v" (without quotes) in the boot command of the bootloader. This would give you verbose output which is useful for the solution.

- "Waiting for root device" - It means that OS X doesn't see your hard disk or boot device. You can face with this during dvd boot or after system install during hdd boot.
Change your SATA mode from IDE/RAID to ACHI by your BIOS setup and also you need to check other BIOS settings that might be the problem. This usually fixes the problem. If not, then you can try to install using a USB media. If still no light, then you may have an incompatible hardware for this OS.
If you face with this problem after installation during hdd boot, then reinstall iATKOS L2 by selecting the SATA/IDE drivers for your hardware during install.

- White or black screen during HDD boot - This means that OS X doesn't see your monitor properly or your graphics card isn't working correctly. Firstly boot with "-x -v" to reach up to GUI, then you can search the internet for the solution for your graphics hardware. Secondly reinstall the OS again, but this time make sure you don't select any graphic drivers. If you can login to GUI, you know what to do so.

- Keep in mind that sometimes certain kext patches may not work for your system even though they are the same chipset but a slight variation may cause it not to work on your PC. The result may be a kernel panic again, reinstall back but this time don't select any funny patches/drivers. This would resolve your problem.

Use iATKOS on your own risk.
IRC: #iATKOS #uphuck.DVD

Good luck. If you enjoy your Mac OS X Lion System, then buy a real Mac. Remember that this system is only for testing Mac's amazing system. Using OS X without a license is not right.

by uphuck

VIDEO: Explanation of the law SOPA [ Hackintosh will die? ]

Setup your Trackpad with iATKOS [L1, L2 Compatible]

For the Trackpad - I suggest you try the Kext from the following link:
Its from the GM of Lion, but for us - it actually worked, where as the 10.7.2 kext did not. Don't bother with the prefspane install if you simply just want the trackpad working.

Replace the two kexts with the one from the zip, then use kext utility to repair permissions (inlcuded in L2. Use finder to goto Utilities/Tools.

Thanks to mrotacon

Install Mac 10.7 Lion on VMware – Windows 7 Intel PC [Working Method]

Probably this is the first complete and working guide available on internet to install Mac OS X 10.7 Lion on VMware in Windows 7 Intel PC. After several days of searches, attempts, reading and collecting information from different places, I managed to install latest Mac OS X Lion 10.7 on my Intel Core2duo computer with VMware workstation in Windows 7.

This method should work in VMware Player also, but I prefer workstation because of Snapshot feature. I don’t think you would face any issues on other types of Intel processors, but make sure you have Hardware Virtualization Technology (VT), 64 Bit, and Core2duo or later supported processor. I’m not sure about AMD processor users. Someone please try and update in comments area for AMD processor with Lion on VMware.

This method is completely for testing and learning purpose only.

What You Need?

  1. VMware workstation 7
  2. Lion OS X bootable VMDK file created from original installation medium (DVD or ISO file) – Check this guide and make this bootable image as described.
  3. Additional Files (Click here to download) – Its a zipped file from two sets of files and a darwin.iso file.
    One for patch your VMware software to support Mac OS X server guest ( Original Source), second  one with pre configured Virtual machine files (Original source) and darwin.iso file to install VMware tools on guest to get more screen resolutions  and VMware shared folders.
  4. Check the VT in your host BIOS as shown here with some tools.
  5. Just little bit time to read the complete guide :)

The Demonstration PC Configuration

I’m doing and taking screenshots for this guide from my Intel Core2duo 2.66GHz, 3GB RAM, Intel P35 chipset and Windows 7 32 Bit host Operating System

Steps to Install Mac 10.7 Lion on VMware–Windows 7 Intel PC

1) Download the additional files and extract the macosx_guest_vmware_7.tar.gz.
Before run the patch, I highly recommend to take a full backup of VMware Workstation/VMplayer programs files (Normally located under C:\Program Files\VMware).
By running this patch, it will modify some VMware exe files and unlock VMware to support Mac OS X server guest versions in Windows host.
Close the all virtual machines and VMware program completely, then open the command prompt as administrator in Windows OS, execute the windows.bat file.

2) Extract the file which you download in additional files set. Make sure extracted file location is having enough of disk space to grow (may be up to 10GB).
Open Mac OS X Server 10.6 64-bit.vmx file in VMware workstation or VMPlayer.
Go to the settings of virtual machine and add a hard disk, select existing option and browse the Lion installer image VMDK file we created by previous guide.

You can modify the memory size and increase number of processors based on physical computer processor cores.
Remove the CD/DVD drive file attached with this pre configured file.
3) That’s it. Start the virtual machine now. It should boot now. It will boot from 5GB vmdk file we created as bootable installer image.
Select the Language in first screen and start the installation.
4) Select ‘Macintosh’ disk in the next screen. If you can’t see the disk to select and continue, then go to ‘Utilities’ and click on ‘Disk Utility’. Create a partition as shown below.

5) I’m sure installation will end smoothly. Complete the initial configurations and setups at the next boot. You can remove the 5GB installer VMDK file from virtual machine to avoid any over writing on this virtual hard disk.

6) Here is the working Mac OS X 10.7 Lion on VMware workstation as a virtual machine in Windows 7 Intel based computer. It’s really nice to run and play around with Apple’s latest OS on normal PC. I’m sure this method will work with final release of 10.7 too.

Take a Snapshot before do anything now!

Some Post Installation Checkups and Configurations

1) Network
Network inside Lion virtual machine worked out of the box. I configured NAT and Bridged network types which worked nicely with my physical internet connection.
2) USB storage Access
USB storage access including Flash disk and external hard disk works fine in VM.

3) Increase Screen Resolution and VMware Shared Folders in Lion OS X
You will get only one screen resolution size inside Lion OS in VMware. Install VMware tools to increase the screen size and get more resolution options, also VMware shared folders work fine without any network between Lion guest and Windows 7 host. This helps to share data between host and guest easily.
There are two issues in VMware tools.
a) Full screen view is not working properly. You can’t switch the guest lion virtual machine to‘Full Screen’ in View menu, its just breaking the desktop and need to be restarted.
What I did was, setup the resolution size to match my physical monitor’s size then used ‘Quick Switch’ in View menu. Its very similar to full screen mode as I’m getting the virtual machine’s screen fully in my monitor with 1400×900 resolution.
b) Sound is not working. The pre configured VM file (VMX) which you download already not having sound card. After adding sound card to virtual machine and install VMware tools, still sound is the problem.
I have tried several other packages including EnsoniqAudioPCI and AppleAudio kext files, but no luck. If sound works for someone, please share how you did.
To Install VMware tools, mount the darwin.iso to DVD/CD drive and run the installation. Restart the VM.
Here are the available screen resolutions after VMware tools installation to increase the screen size.

4) VMware Shared Folders in Lion OS X guest and Windows 7 Host
Go to Settings of virtual machine and select ‘Shared Folders’ under ‘Options’. Select ‘Always Enabled’ and add the Folder or Partition from Windows host Operating System. That’s it, now try to open the ‘VMware Shared Folders’ shortcut from desktop of guest machine.
You should be able to access the host’s shared folder or partition from Lion virtual machine now.

5) Sound
As I said earlier, its not working with me now. I’ll be keep trying possible methods to make this work in Windows host. It may work inside Lion virtual machine when you run this Mac host with VMware Fusion.

I’m not a Mac user, but while comparing with Snow Leopard 10.6, Lion 10.7 looks good with new features and new interface to work.
Now, I expect your comments, successful and failure attempts by this method. Feel free to drop a comment if this works or not. As I said earlier, I did this in Intel Core2duo computer, So I need your inputs on other types of processors including Intel i-series and AMD processors.
Help others by your comments and share this guide to install Mac OS X Lion on VMware with Windows 7 host.

Finally, Dual Booting with iATKOS and Win7