Jump to content

Search the Community: Showing results for tags 'for'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 2 results

  1. Recently, I have been having weird issues installing Sierra to my newly created partition. It always ended up with a NASTY error message saying that it could not unmount the volume for repair (what repair, anyway?). At the first, I thought the volume was dirty, so I booted to my working El Capitan again and had formatted the partition again. It still failed. Then, I thought it was the fact that I was using the installer in El Capitan to install it to the new partition. So, I created an installation USB. The problem surprisingly appeared! The problem: The problem I believe was due to the createinstallmedia tool. If the USB is in fact created with that tool, the installer divides the installation process into two. First, it copies the installation files to the HDD partition (that part creates problem), and then it reboots from that partition to install the files and eventually create the Recovery partition. The problem is that it for some reasons tries to unmount the partition it has booted from, which is obviously not possible; hence, it fails. The root problem probably has much to do with the partitions structure. In my case, I used MiniTools Partition Manager to migrate my Windows installation from my HDD to the new SSD drive. It could have been due to that, although MSR partition is also known to cause problems in some situations. The partition structure was as follow: ESP = EFI Partition MSR = Microsoft Reserved (culprit, too?) Win10 = Windows drive Sierra = New partition created for Sierra Macintosh HD = El Capitan drive (already installed and working) RecoveryHD = El Capitan recovery drive. The solution: Use the "Restore BaseSystem.dmg" method to create the installation USB. Follow these steps: I assume that you have downloaded the installation from Mac App Store. If so, then right click on the file, click "Show Contents Packages". Click on "SharedSupport". You should see InstallESD.dmg. Double click on that file to mount it. Open the OS X Install ESD partition. Make sure that hidden files visible (there are many ways, use Google). Right click on BaseSystem.dmg and click open to mount it. Open Disk Utility. Plug in your USB drive. Click "Partition" and create too partitions. One with 200MB and the other one with whatever size you want. The 200MB partition format should be MS-DOS (FAT) and give it CLOVER as name. The second one's format should be OS X Extended (journaled) and give it USB as name. And click "Apply" to format the USB. Of course, everything on that drive will be destroyed. It's needless to say that you should backup its contents first. While still inside Disk Utility app, click the second partition (it's should be named USB). On the status bar, click on "Edit" and choose "Restore". You should see "Restore from: OS X Install ESD" click on "OS X Install ESD" and choose "OS X Base System" from the dropdown menu. Now click "Restore". You might need your password to complete this task. If so, type it in and click ok then wait. Upon finition, smartly unmount OS X Base System disk under "Disk Images" in Disk Utility. Open the USB drive (the name "USB" will become "OS X Base System", that's why you need to smartly unmount the other one using Disk Utility to avoid confusion.) Inside the USB drive, go to "System" then "Installation" remove the file named "Packages". That's actually an allias (or a shortcut if you want). Go to OS X Install ESD drive. Copy "Packages" folder from there and paste it in your USB/System/Installation. The same way, copy the other files from OS X Install ESD drive to the root of your USB (the root, not inside a folder on the USB drive). You need to typically copy the following files: AppleDiagnostics.chunklist, AppleDiagnostics.dmg, BaseSystem.chunklist, BaseSystem.dmg Install Clover to the first partition of your USB drive named CLOVER (unless named otherwise). Reboot from the USB drive and everything should go smooth and without this error. This should also work for Chameleon bootloader. You might of course not need to create two partitions in this case. You should probably not directly upgrade from El Capitan to avoid this problem. If it happens while you were trying to do an upgrade, you might need to do these steps inside a virtual machine or a working hackintosh.
  2. For some reason i can run ML on VMware with this machine but I cant install for the life of me. I followed this Tut: Click here For some reason I am getting stuck at Still waiting for device. (picture attached) My Rig: CPU: Intel® Core™ i7-3630QM Processor Graphics: NVIDIA® GeForce® GTX 670M with Optimus™ Technology 3GB GDDR5 Memory: 12GB DDR3 1600MHz memory HDD: 1.0TB: 500GB (7200rpm, Serial ATA) + 500GB (7200rpm, Serial ATA) Optical: DVD-SuperMulti drive (+/-R double layer) Wifi: Intel® Wi-Fi® Wireless networking (802.11b/g/n + WiDi Capable) Bluetooth: Bluetooth® V4.0 USB:4-USB (3.0) ports Any one help me PLEASE! UPDATE: So I was able to Boot and install ML using a boot CD which was from OSX86.net But I cant boot into the OS I have tried the following boot flags; -v -F -x maxmem=4084 busratio=18 npci=0x3000 PCIRootUID=0 and 1 This is what I get Instead of getting Still waiting.... Error I get a Kernel Panic. But I myself cant figure this out. Any help would be awesome.