DO NOT ask where to get it.-----------------------------------------------------------------------------------
Before you Start:
-this DVD Made for Non-Apple Computers only so don't try it with Apple Hardware
-Snow Leopard Will run on both 32/64 bit PCs but better you have a 64 BIt Processor
- Better use PS2 Mouse and Keyboard
- Back-up All your Data Before Installation [Better Use a Empty Hard Drive ]
-Check your Processor For SSE2, SSE3 And 64 Bit compatibility With this toolhttp://www.cpuid.com/download/cpuz/cpuz_154_setup.exe
The Following Programmes will not work on a H@ackintosh -Boot-camp
-And Some utilities
ISO Info Title: Snow Leopard 10.6.1-10.6.2 [SSE2-SSE3]
MD5 - 8DF10E97E27BD38BC7FD96D97CB7A917
Size: 4.4 GB
Type : Single Layer DVD
ISnow Leopard InfoVersion : 10.6.2 + Combo]
Platform: PC [Intel/ AMD] [SSE2-SSE3] [better USe 64 Bit Processor
Language: English + Russian
Modified: Lots of Drivers Kext and Fixes
Whats Included Detail :
Install optionsMac OS X Update:
Mac OS X 10.6.1 Update
Mac OS X 10.6.2 Update Combo
Boot Loaders:Chameleon RC3 PCEFI 10.3
Chameleon RC3 PCEFI 10.5
Kernels:Intel Atom Kernel 10.2.0
Legacy Kernel 10.2.0 Intel AMD
Mobdin Kernel 10.0 AMD Only
Installation Guideif you want dual boot Guide go here
http://www.taranfx.com/how-to-install-mac-os-x-snow-leopard-on-pc-dual-bootScreenshots.
Things you Need- A PC with a Intel or Amd processor [SSE2, SSE3 64 Bit Processor][SSE2-SSE3]
-An Empty hard Drive
-At-least 1 GB of Ram
-DVD-Rom Drive
- An Empty DVD-R
-Image Burner Software [Nero/BurnAware/..]
-A Pepsi or Coke Bottle [optional]
Things you have to do before InstallationSetup Your Biosfirst try to install in a Default Bios Mode if you have problem try the following things
Detailed BIOS setup Images
Special Notes : American Mega-trends Bios Mainbards [Biostar,Foxconn,Gigabyte..]
1.Disable EHCI (set it to “disabled” its right down under USB Legacy support)
2.Disable Speedstep its under CPU settings.
Intel and Asus
1. Disable All Power Saving Features
2. No problem With SATA AHCI Features
if you have EP45-UD3R (and similar) BIOSes Please Disable All these Things if Previous Installation failed with Default Bios-CPU Enhanced Halt (C1E)
-C2/C2E State Support
-CPU EIST Function
-C4/C4E State Support
-Virtualization Technology
Preparing Snow Leopard DVD
For More info about thishttp://www.insanelymac.com/forum/lofiversion/index.php/t181903.htmlStep 11-Extract Archives And Burn the ISO in a DVD-R normally with nero or something
2-Now Restart the PC with Snow Leopard DVD inside [make sure you Have backed up all your Data or Using a New or empty Hard Drive]
Press F8 and Boot into Snow Leopard
Type Like This
you can also Try
"-V"
'cpus=1 -v"
without any quotes
Customize Option
Note: dont Select more than one Driver in a List
For Example : if you have Nvidia 7300 only select Nvidia in the Graphic Driver List dont select any other
Known Issues
Hackintosh Reboots Constantly After OSX86 Installation
Installing the OS X on your PC is difficult till first install. Successful OSX86 installation is depends on various combinations like right Distro, BIOS Settings, Hardware, Patch Selection etc. Most common problem for first time installer is my hackintosh reboots after installation finishes. For first time peoples make sure to read and understand the post given below and our OSX86 Basics section. We always recommend to install on a clean hard disk. If you are suffering from endless reboot after leopard hackintosh install, then follow these steps to solve it.
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
Kernel Panic
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=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
Download Kexts for Snow Leopard 32/64 Bits
* AHCIPortinjector: Add the name of the chipset (ICH9, ICH9R, etc.) when the AHCI controller is used.
* ApplePS2Controller: Enables support for PS2 peripherals
* AppleVIAATA: ATA Extension works with VIA chipsets
* AppleIntelPIIATA: ATA Extension works with Intel chipsets NEW
* AttansicL1eEthernet: Suport Attansic ethernet controller L1e
* Disable: Disables the only kext AppleUpstreamUserClient.kext responsible “mouse lag” in
the use of QuickTime and iTunes with Nvidia 8xxx
* fakesmc: emulation of the chip smc. replaces Appledecrypt and dsmos.
* HDAEnabler: Inject the input / output audio information system is used when a Legacy plist “audio or
AppleHDA changed.
* Intel82566MM: Driver for Intel 82566MM controller
* IOACHIBlockStorageInjector: Sets the orange icons problem when using AHCI Controller
* JMicronATA: Allows the JMicron chip is to function with more than 4GB of ram.
* LegacyJMB36xSATA: Allows the SATA controller JMB36X display info in System Profiler.
* NullCPUPowerManagement: neutralizes the kext AppleIntelCPUPowerManagement.kext
* NVinject: Injector for Nvidia cards (64bit only)
* OpenHaltRestart: re-active termination and reboot on many motherboards
* PlatformUUID: Sets the error “UUID Error 35″ by injecting a generic UUID to boot.
* RealtekR1000: active sharing hello and AFP for the Realtek network controller
* SKGE: adds functionality to certain network controllers Marvell
* SleepEnabler: re-active the day when AppleIntelCPUPowerManagement.kext is neutralized (see
NullCPUPowerManagement)
* UUID: Sets the error “UUID Error 35″ by injecting a generic UUID to boot.
* VoodooHDA + prefpane: universal sound driver
* VoodooPS2Controller + prefpane: Enables support for peripheral PS
How to Burn
it will Show the ISO size as 192 KB windows platforms and NON-Bootable
but no problem
in Magic ISo Just Burn the ISo in a slow Speed
