Chameleon 2 Rc4 Install Download

Downloaded 653270 times. Size: 3.4 MB • For Mavericks you will need the Install OS X Mavericks.app or the InstallESD.dmg from it. • For Mountain Lion you will need the Install OS X Mountain Lion.app from the app store or the InstallESD.dmg from it. • For Lion you will need the Install OS X Lion.app from the app store or the InstallESD.dmg from it. • For Snow Leopard you will need a Snow Leopard Retail DVD or a DMG of it. • An External Hard Drive or Flash Drive w/ at least 8GB of space. Native Instruments Komplete 5 Serial Keygen.

You will also need access to an x86 system (PPC is not supported) that is currently running OS X 10.6 or newer to prepare your installation device (this can be a real mac, a hackintosh, or an OS X virtual machine). Note: An internal drive can be used as well but keep in mind any drive you use will have the chameleon bootloader installed on it – it is best to use a drive which is physically independent of your actual OS X installation. In the event that something goes horribly wrong with your actual OS X installation the myHack OS X install disk you have prepared will prove to be an invaluable tool with which you can repair your OS X installation and get it working again.

Jan 14, 2010. Chameleon RC3 brought a number of Stability fixes. Chameleon RC4 was released recently, adds couple of New Features that can come handy: Hide Partition Define all partititions that you wish to hide from boot menu. Define following in com.apple.Boot.plist to hide partition 2 on BIOS drive 0 and. Oct 29, 2010. This guide shows you how to install both Windows XP and Mac OS X 10.6.4 (retail version) on your Asus 1000HE netbook, with Chameleon bootloader to. This is where Chameleon 2 bootloader wil be installed. OSX Partition (Mac OS Extended Journaled). This is where Snow Leopard will be installed.

Hardware Requirements: A system capable of running a “vanilla” OS X kernel Including but not limited to the following: • Processor: Intel Core 2 Duo, Core 2 Quad, Core i3, Core i5, Core i7 *[1] • Motherboard: Intel chipset with AHCI enabled • At least 2GB of memory (4GB or more strongly recommended). • Most Nvidia 8xxx 9xxx 2xx 3xx 4xx 5xx 6xx 7xx graphics cards *[2]. • Most ATI HD 5xxx/6xxx/7xxx series graphics cards *[3].

• Intel HD3000/HD4000 Integrated Graphics *[4] • USB Keyboard and Mouse. (Apple keyboard recommended) *[5] • At least 40GB of internal hard disk space attached to Intel SATA controller running in AHCI mode. *[1] LGA 1155 chipsets (P55 for example) and Core i5 processors are only supported by the vanilla kernel on OS X 10.6.2+. Core i3 processors are only supported by the vanilla kernel on OS X 10.6.5+. “Sandy Bridge” intel processors are only supported by the vanilla kernel on OS X 10.6.8+ and work better in Lion and Mountain Lion.

LGA2011 chipsets with “Sandy Bridge-E” processors are only supported by the vanilla kernel on OS X 10.7.3+. “Ivy Bridge” processors are supported by the vanilla kernel on OS X 10.8.0+. *[2] Some people with Nvidia cards still have issues using Graphics Enabler, particularly users on “GTS” models of these cards.

The 5xx and 6xx series has only begun to really work properly with in OS X 10.8 Mountain Lion. 6xx and 7xx work the best in OS X 10.9 Mavericks, no GraphicsEnabler is required and you will benefit from the OGL improvements apple has made to Mavericks.

NVidia has the slight edge over ATI currently because nVidia released drivers for Mac Pro users. The further back you go in OS X versions, the fewer of the cards I listed will work. *[3] Most reference design HD 5xxx and 6xxxx ATI graphics cards will work oob on Lion and Snow Leopard but on Snow Leopard you will need to install the ATI kexts from the 10.6.7 MBP update. The 69xx series ATI graphics cards appear to be working on ML, but they did not work on Snow Leopard or Lion. 7xxx works well on Mavericks. *[4] To get HD3000/HD4000 IGPU working may require the use of an smbios.plist from a mac model that has one of these devices, in addition to GraphicsEnabler and/or a DSDT modification. Note: HD4000 will only work in OS X 10.8+ and HD3000 will only work in OS X 10.7+.

If your graphics does NOT work out of the box or with chameleon’s GraphicsEnabler one of the best resources for more information on graphics card support for OS X is. Also feel free to ask on the.

*[5] Most PC notebooks have their keyboard and touchpad wired internally to ps2. Even brand new 2012 sandy bridge based notebooks still use ps2 It really is amazing that this decades old technology is still hanging on. You can usually get ps2 HID’s working by using AppleACPIPS2Nub.kext+ApplePS2Controller.kext (these are now included in the Generic Extra supplied with myHack 3+). Some other users are not so lucky and will need to resort to other solutions. Section 1: Installation Step 1 – Create OS X 10.6, 10.7 or 10.8 Installer Make sure that the internal/external stick/drive that you will be creating the OS X installer on is mounted and it has an empty HFS+ formatted partition of at least 8GB in size on it. You can partition and format it using Disk Utility, under Applications/Utilities.

The partition scheme may be either “GUID Partition Table” (GPT) or “Master Boot Record” (MBR). If you are creating a Snow Leopard installer make sure that you have inserted the retail DVD or mounted the dmg image of it prior to proceeding. If you are creating a Lion or Mountain Lion installer make sure that you have downloaded the Install OS X (Mountain) Lion.app from the app store and have it, or the InstallESD.dmg from it, somewhere on your filesystem. If you haven’t already done so, download the myHack dmg (the link is above in the basic requirements section). Mount it and drag the myHack app to Applications to install it or double click to run from the dmg itself.

Run the myHack.app, myHack will ask you to enter your administrative password, enter your password and proceed to the next step, the password will only be stored in your system memory it is not recorded, stored, or transmitted anywhere. Note: if the user account you are running myHack on does not have authorization to use “sudo” you will need to logout and run again from an authorized administrative account with access to the “sudo” command. Select your install type – Create OS X Installer >Create OS X 10.8 Install Disk, Create OS X 10.7 Install Disk, or Create OS X 10.6 Install Disk for Mountain Lion, Lion, or Snow Leopard respectively. Select the target volume – this should be the internal/external stick/drive that you will be creating the OS X installer on. MyHack will now attempt to locate the installation source. If this is for a Snow Leopard installer it will look under /Volumes/ for a Snow Leopard install DVD or mounted dmg – if this is for a Mountain Lion or a Lion Installer it will prompt you if you want to have myHack attempt to locate it for you or browse manually (I suggest using browse only if search does not locate it) – if you choose to browse it will accept the location of Install OS X (Mountain) Lion.app or InstallESD.dmg. MyHack will then prompt you to warn you that all data on the target you selected will be erased.

Once you press ok it will ERASE all data on the target volume you selected and copy the OS X installation files to it. Note: If the file copy progress appears to be stalled, don’t worry, the progress bar can only calculate based on files completely transferred – large files may take a while to completely transfer to the destination prior to the progress being reported. Also if it appears to be transferring slowly, remember that the speed of transfers will be limited only by the speed of the device – some USB sticks and SD cards are very slow. After all files have been transferred it will automatically install Chameleon, myHack utilities, a Generic Extra, and make all necessary modifications to the installer.

That is it, assuming you followed the steps correctly (the app is rather foolproof, assuming you have read and followed these simple instructions) you may now reboot, select the device that contains the myHack OS X Install Disk at your bios boot prompt, and boot to your installer! Wasn’t that easy? Step 2 – BIOS Setup This is just a quick/general checklist, if you can not find these values in your bios ignore them for the time being unless you run into a problem: • Ensure you have your SATA controllers in AHCI mode. • Ensure you have enabled your CPU’s C states. • Ensure you have HPET set to 64bit.

• Disable any devices you do not intend to use (extra SATA, Firewire, etc). • If you have a UEFI system, ensure that you boot in legacy (bios boot) mode. Step 3 – OS X Installation Assuming everything is configured properly for your system you should be able to boot to your USB device and be greeted by the OS X installer. This part is just like any typical OS X Installation, click on the language you want to use, go to the utilities menu, open disk utility, partition and/or erase the device you want to install OS X on, exit disk utility and then proceed with the OS X installation.

Note: If you can not select your drives or you see nothing but the USB drive, go into your bios and ensure that your SATA device is running in AHCI mode. Alternatively you can try to install an IOATAFamily.kext as it will allow many systems to access SATA (and even some PATA) devices without the need for AHCI but it is not recommended. In the last two minutes or so of the OS X installation a series of growl-like notifications and dialogs will prompt you. This is myHack running it’s post installation functions. MyHack will prompt you if you would like to install the generic Extra & Extensions bundled with myHack or if you would like to supply your own. Using your own is particularly useful if you already have a finely tuned OS X installation – you can simply provide the Extra of your choosing and it will migrate it properly for you. The generic bundle will boot most vanilla systems perfectly, but does NOT contain any extensions for audio/ethernet/acpi/ata/etc or dangerous DSDT “auto patchers”.

After installation completes you should be ready to reboot your system without using the myHack OS X Install Disk. Reboot the system with the internal drive that you just installed OS X on. Congratulations, If all went well you now have a functional OS X operating system running on your system! Step 4 – First Boot Go ahead and go through the initial OS X configuration, I tend to advise against using migration assistant, unless you are absolutely certain it was a completely clean installation. There are a number of reasons for this that I may write about later.

Step 5 – Post Install This is the section where I used to have instructions on running tools within myHack for post installation, but now that it’s done during OS X installation about the only thing to say here is this is where you begin your journey (if you did not already have a perfectly tuned extra for your system) and find the extensions you need to get the rest of your system working perfectly. For help in this portion of your journey, I suggest you join us in the or on. Important Note for OS X 10.7+ and OS X 10.8 Installs: If you do not have an smbios.plist in /Extra/ made for your system, based on the mac model which your system most closely resembles, several things will not function correctly (Appstore/Facetime/iCloud /Intel HD Graphics/etc for example) and the system may not boot at all (You may receive a kernel panic related to ApplePolicyControl if you have not removed it). The solution is to create an smbios.plist for your system and place it in /Extra/ – if you need help figuring out how to create one feel free to ask in the or on. Section 2: Basic Troubleshooting What I am placing here is primarily for common issues faced when booting OS X Installers or first boot of an installed OS X system using the Generic Extra bundled with myHack. It does not cover the many issued that can be faced during post installation when using additional Extras.

For help with problems not covered here I suggest you join us in the or on. When I say “Boot with ____” it means to type in those flags at the chameleon boot prompt and press enter. You will see the chameleon boot menu and prompt by pressing any key at the first chameleon screen you see.

• Symptom: The system fails to boot but I don’t know why • Resolution: Boot with -v and watch carefully to determine at which point the system is failing • Note: When trying any of the suggestions below it is best to add the -v flag each time until the system is booting correctly, this is the most used of all boot flags. • Symptom: The display goes blank or system reboots instantly after booting OS X or Installer • Resolution 1: Boot with PciRoot=1 • Resolution 2: Boot with GraphicsEnabler=No (Only use if resolution 1 fails, will not work on ML unless you have one of the graphics devices which will provide hardware acceleration without GraphicsEnabler, or you have removed system extensions in order to force VESA mode). • Note: ML will not boot without graphics support as there is no longer VESA support. You will have to either replace your graphics card or find a method to get it working if it is not supported by GraphicsEnabler • Symptom: System hangs at “PCI configuration (begin/changed/end)” • Resolution: Boot with npci=0x2000 or npci=0x3000 • Note: If neither of the above boot flags help you with this problem you will need to install a patched IOPCIFamily.kext, simply place in /Extra/Extensions/ and run myFix. You can obtain the latest patched IOPCIFamily.kext from netkas.

• Symptom: System fails to boot or runs extremely slowly with mouse jumping around • Resolution: Boot with cpus=1. Section 3: Software Updates Generally speaking with vanilla OS X installs you can use software update without much concern. The updates you should avoid to install through software update are the “10.X.x Updates” which will contain a full revision # (10.6.1, 10.6.2, etc).

I will make a post in the FAQ section of the forum with what we know about each software update as it becomes available and what benefits/potential problems will result from installing it. Imagequant Software Free Download For Mac on this page. It is important that you do not install these updates until you have researched and ensured your system will not be negatively impacted by them. A few general notes that are true of all updates: Always backup your system prior to running an update, if you don’t want to create a complete system backup at the very minimum backup all the files in /System/Library/Extensions and /Extra to your USB Installer or other convenient location and ensure that the USB Installer is functioning correctly (it boots and you can use the terminal on it) prior to running the update. This is critical in case something goes wrong, a bootable installer will enable you to fix the problem from the installer’s terminal app (available under the utilities menu) without having to completely format and reinstall your OS or use a separate machine/operating system to attempt to repair it.

After you have successfully booted and logged into a freshly updated system, wait a few minutes for the system to finish background processes and become idle, then run myFix. Running myFix will ensure that everything is tuned properly and that the system caches are happy. This may not be necessary, but if you have noticed after a few boots that it is still taking “longer than normal” to boot and get to the login screen that is a sign that something isn’t right in your kextd/kextcache/kernelcache/system cache. Running myFix should correct it. If you get a kernel panic during reboot, the first thing you should try is booting to your USB Installer, opening the terminal and running myFix, sometimes kextd doesn’t properly rebuild your system caches after an update. If you still receive a kernel panic on reboot, boot in -v (verbose) mode and see if you can narrow it down to a suspect kext, the SleepEnabler.kext in /E/E has been a notorious source of these issues after a kernel update. If you can figure out the kext that is causing the problem you can move it out of /S/L/E or /E/E and then run myFix from the USB Installer – this will prevent it from loading.

If that still doesn’t work you may need to replace the suspected kext with a newer or older version of it from a fresh download or a backup you have. If you follow these few general notes you should seldom have a problem, and even if you do, you should be able to fix it quickly and easily.

Section 4: Credits myHack was made possible by: The hexadecimal strings used to patch the OSInstall.framework for MBR installation were developed and contributed to me by nawcom. The bin patching functions used in myHack themselves were based on code snippets provided by meklort.

The method used for running myHack during OS X post installation was based on work originally developed and suggested to me by meklort. The method used for merging /Extra/Extensions into /System/Library/Extensions was based on work originally developed and suggested to me by the crew. Graphical front end development was aided by the use of,, and.

I would also like to personally thank the following people for helping to make this possible and for all the help they have given to myself and others over the years: (in alphabetical order) apocolipse, aschar, blackosx, Bronx Teck, cosmo1t, fassl, Galaxy, JaS, Kabyl, Krazubu, lastExile, meklort, modbin, monsti, Mushishi, nawcom, netkas, p astikman, PolishOX, prasys, RampageDev, schnitzel, Signal64, XyZ Additionally thanks go out to everyone who has worked on the Chameleon bootloader, without which none of this would be possible, and everyone else who has contributed to the hackintosh scene! I’ve seen a lot of speculation out there asking the above questions. I can now finally answer. MyHack v4 was nearly ready a few months ago but I have been so preoccupied there was simply no time to complete it and prepare it for release. Because approximately 4 months ago my family and I decided to move back to the United States after 7 years in South Korea. This was a difficult decision to make, and was incredibly complex and time consuming to accomplish.

I did however take the time to migrate this website to a new host to ensure there would be minimal disruption or downtime while myself and my hardware traveled across the globe. I wanted to explain this months ago, or at least before I left but there were personal and professional reasons for not doing so. Not everyone was aware that I was intending to move and I wanted to keep it that way until I was gone.

We arrived here about two weeks ago and are adjusting to our new timezone and environment. With the holidays we are also distracted by reuniting with family whom we have not seen in many many years, some whom have never even met our children. So it may still be a little while before I can get everything done on here that I have planned but it is most certainly going to be done. I have not abandoned the project but it does require a rather large investment of time to keep it going.

Despite what some people have speculated I make no profit from this so it is low on my priority level, perhaps in the future that may change. MyHack 4 actually supports Yosemite fine, I had it working within 12 hours of DP1 being seeded by apple, there are other portions of myHack v4 that must be completed prior to me being able to release it to the rest of you however. Posted in • Comments Off on Explanation of downtime • • •.