Jump to content


  • Content count

  • Joined

  • Last visited

About xtraa

  • Rank
    InsanelyMac Legend

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location

Recent Profile Visitors

6,056 profile views
  1. Looking at the global marketshare, we have 59% mobile devices (increasing) and 41% desktops (decreasing). Like any other company, Apple will focus on the market where the money is. Mainly there are three reasons for Cupertino to switch IMO. First is quantum tunneling. Moore's law will end probably at 2022 because we can't get any smaller in terms of nm without errors and simply adding multi cores does not fix the problem either. This is or should be enough for an exit strategy to leave this CPU technology and look for a new but also downward compatible solution. Second thing I thought of is that Apple by now is developing it's A-Series for years, and particularly the A11 is interesting because it already has a built in a neuronal network hardware part to speed up face recognition and other tasks that can be computed much faster and more efficient with AI than with todays standard architecture alone. So what would you do if you were Apple? I would develop a CPU that can be used in all of my devices, so I can start research and development for the years ahead and use my already available resources. Finally, with Intel stepping back from (or at least delaying the development of) 10nm CPUs (if even possible) this was a clear decision to not be left in some uncertain future. But this does not have to end hackintoshs because the quantum limitation affects all CPU manufactors and there could be the uprise of something fundamental different in the next 2 to 7 years that will still be downward compatible of course.
  2. xtraa


  3. I think we've all been at that point a few times. This happens when you do it right. (instead of doing it wrong and use some ready to go thing that will patch your system with loads of modded kext files but you don't know exactly what's going on and for the price of what) If you can get to the desktop with -x it's not that bad. Without knowing your system I'd recommend this: In most cases it's the best option to start excluding the graphics drivers first. You are booting VESA mode anyway, so I'd recommend to start with an mkdir an make a new folder called e.g. extensions_disabled and move your graphics drivers there from S/L/E. From there you can see if it boots fine w/o -x and start adding drivers back. You can always move them back by booting into -s, doing fsck and mount and after that just cd .. in your directory and move files with mv.
  4. RX480, i5-HD530 and GA-Z170 fully working with Sierra modifications and apfs. After digging through some threads I was preparing for a painful upgrade. Instead, it turned out to be one of the smoothest transitions ever. I started with an external testdrive and installed on apfs to see if Clover is ok with the new filesystem. After that I updated my existing Sierra. I'm using Clover v.4128 with GM apfs.efi driver, own dsdt & ssdt and same patches as in Sierra. Just started the inplace update and boom, everything works like a charm. I really did not expect that. The RX480 is detected correctly as a Radeon Pro 480/575 and my idle Intel HD Graphics 530 also supports Metal. Recovery also boots fine and the "Preboot Filevault" does too, even if I have to take a deeper look in here. (only have an idea what it's purpose is, yea filevault obviously).
  5. For me it's very different. I need to work in x-code and Windows at the same time, like to access my iTunes library from there because of the playlists and most of my personal bookmarks etc are under OS X. But as I already mentioned above, it's not for gaming or other metal/opengl/opencl relevant programs but I think this is true for any VM. It works fairly good with anything else tho.
  6. Hi, this tutorial is about running your physical hackintosh installation in Windows. It's not about setting up a new OS X VM. As always it's very simple once you know, but it however took me a while to figure out the settings, especially using IDE in the VM and using the Clover/EFI partition or not. Luckily, it turned out we have to skip it, so we can leave Clover (or any other bootmanager) untouched. What's the point? If you have to do tasks in Windows, be it mining bitcoins, 3D-rendering, gaming or simply work with a windows-only software, you probably at the same time miss your OS X. The advantages over a simple new virtual machine running with your personal setup are many: Imagine you can use all your data, listen to your iTunes library, use your installed and configured programs and work with your settings. It also comes in handy when you messed up your installation for some reason and want to conveniently fix it. And last but not least don't forget you save the 25GB minimum space for a virtual disk what is probably not sooo insignificant since (I assume) most of us already switched to SSDs and only a few may have picked the models above 500GB because they are still pricy. tl;dr Gain advantages by hooking up your existing Hackintosh installation in a VM and work in your personal OS X environment whenever you like, even under Windows. If you have High Sierra with APFS installed it will most likely not work (yet), because Paragon and probably VMWare don't support the filesystem (yet). That being said, let's get started: 1. Preparing Instructions - do all possible reboots as required while installing - install Paragon HFS+ 11 or above (buy or know where) - install VMWare Player (free for private use) - install Unlocker from Insanelymac (free) 2. in VMWare, set up a new virtual machine - choose "I will install the operation system later" next > - choose "Apple Mac OS X" and "macOS 10.12" next > - choose "Store virtual Disk as a single file" next > and next> - choose 5GB Maximum disk size (we delete it later) and pick "Store in a single file" next > - Finish 3. in VMWare, configure your new machine - click on "Edit the virtual machine settings" - delete your new 5GB virtual Hard Disk (SATA) - click Add... on the bottom, select Hard Disk - select SATA (IDE works, too but I'd prefer SATA in 2017) (UPDATED) - pick "Use a physical disk" - select your harddisk with your OS X installation on it and pick "use individual partitions" - now do not select your UEFI partition, select the partition with your OS X: Example: My Sierra is on my PhysicalDrive 3 which I selected before. As we all know, the EFI partition is always the first partition (0), so my OS X (and probably yours, too) is on the second partition (1). So I check partition 1 and click next and finish. - if all is set and done, close VMWare. 4. check your VMWare .vmx file - replace the green parts with your data and move to "C:\Users\YourWindowsUsername\Documents\Virtual Machines\YourVM-Name\" - open yourVM-name.vmx with the Windows Editor and add the folowing lines only if they are missing: smc.version = "0" firmware = "efi" Click save. 5. VMWare optimization I choose half of my physical RAM, maxed out the graphics RAM and choose half of my physical CPU-Cores in the VM settings. 6. Finalize (UPDATED) Go to your VMWare program folder, right-click on vmplayer.exe and under Preferences > Compatibility > check the "Run as administrator" checkbox on the bottom. And that's it! Screenshots for reference. Now you have your OS X install available in Windows, too. If it asks you for updating the VMWare Tools, click yes or install them with one of the tools in the download section here on insanelymac. You can also add other Harddrives to your VM. What will not work: VMWares unity-mode in Windows - it's not supported for OS X yet. Gaming, the graphic is slow-ish but enough for coding, office, music and all basic tasks.
  7. Ok, got it working. I now can boot my native hackintosh partition in a Windows VM. If someone has the same idea, I will explain, as soon as I have time.
  8. Hi pippox0, thanks for your reply! This seems to be an interesting idea but currently no option for me because I'm lacking on SSD space. My progress: So far I'm able to boot the physical hackintosh recovery partition vanilla when pointing a new boot entry in VMware BIOS. But no dice and KP with the main installation. It's either a "wrong firmware" error when I use Clover, (SMC Version = 0 in .vmx) or I get a KP when I try to boot without (well, pretty obvious but sometimes weird hacked machine magic make things possible one never thought of ). A bigger problem seems to be the Windows rights-management with Apple Bootcamp HFS+ drivers. I don't want to use the Paragon drivers because VMWare don't like it and they are not very reliable. So I came to the conclusion to use my physical recovery, set up a new virtual Disk and install xcode there to work with. And take my time to figure out how to work around the rest. When (if) I figured it out, I'll post a tutorial.
  9. Hi, I am not into that topic and google magic does not apply because everyone tries to tell me how to make a fresh install of Sierra in a VM what I know but don't want to. Instead, I'd like to run my existing installation of Sierra from the harddisk in VM-Ware or Virtualbox when I'm working in Windows X. I have it all set up here with player, tools and unlocker, but it does not compute yet. Reasons for running the hackintosh installation are obvious: Skip 25GB virtual disk image and have your Sierra all set up and configured as you like it. Is it even possible or does it mess around with bootcaches etc? I know it used to work back in 10.4.8. but dunno about Sierra. Thanks in advance for any hint pointing me in the right direction.
  10. xtraa

    Mac os High sierra installation attempts

    You don't have to do this in Sierra anymore. Just hit CMD + SHIFT + . (Dot) in any Finder window to switch instantly. Topic related updates about apfs.efi: http://enterprisemac.bruienne.com/2017-02-27-apfs-boot-quickpost/ https://twitter.com/TylerLoch/status/834096046800257024
  11. Skylake is fine with the update. However: - Radeon RX 480 works (metal support) but needs to be repatched with .plist edits of x4000/x4100 kexts – so no native support yet. - Intel HD 530 works (metal support) with old patches, but I had to repatch the display-framework for 2560x1080 resolution.
  12. DVI could be the problem although it worked oob with my ga z170. I'm currently on mobile but took a peak at your config.plist. You should replace all gfx0 to igpu, too. If you use ssdt's make sure that you rename all gfx0 entries there, too or change the drop oem. Also, you don't need to specify an ssdt order anymore, just drop them in your /acpi/patched/ and I'd recommend to name them something more intuitive like ssdt-cpu etc. edit: <dict> <key>Comment</key> <string>change GFX0 to IGPU</string> <key>Disabled</key> <false/> <key>Find</key> <data> R0ZYMA== </data> <key>Replace</key> <data> SUdQVQ== </data> </dict> plus manually replace them in every ssdt that has entries. Should be one or two of them.
  13. Natively it is not possible so here is the fix: Just in case, make a backup of your IODisplay.Framework. (The script does that, too, but you know... ) Go to Floris497, download the scripts as a .zip, follow the instructions. Then apply the CoreDisplay-patcher.command as described. Reboot. Go to display-settings, and while holding the ALT-Key, select the scaled resolutions and pick your match. Enjoy a new native resolution on your Ultrawide. Tested with Sierra 10.12.1 and 10.12.2 on Skylake.
  14. xtraa

    Clover General discussion

    Hi Clover-team, Slice et al., I have a request: Can you make it possible to hotpatch frameworks from Clover like the .kexts, too? For example, I have z170 HD530 with a resolution of 2560x1080 over HDMI. What is not possible natively. I patched CoreDisplayFramework using this method on github and it works. But what the patch basically does is using xcode cmdline tools and replacing oToolCoreDisplayUnpatched=( 49cd8062ed1c8f610b71e9a3231cf804 '10.12 16A254g' 1 8e1030235b90d6ab0644bd7a1b6f9cdb '10.12 16A284a' 1 f4c6e84ffa97e06624e5504edd87bf7d '10.12 16A284a' 1 # I don't know why these two are different 4cba52b41ceee7bc658020c9e58780a3 '10.12 16A294a' 1 d41d8cd98f00b204e9800998ecf8427e '10.12 16A313a' 1 aa7607dd72a2a4ca70ce094a2fc39cce '10.12 ' 1 # Sierra 10.12 release 172b7e2fe2e45e99b078e69684dd3c10 '10.12.1' 2 0657d9fee305e1beeea8ddf0c833d9d5 '10.12.2 BETA: 16C32f' 3 with this oToolCoreDisplayPatched=( 4e469fbf1c36d96fc25fb931c6670649 '10.12 16A254g' b6ee4943c2fce505faceb568e1c8f4b1 '10.12 16A284a' 82f97933a3ae90d47054316fa8259f6c '10.12 16A284a' 1371f71ca7949cfbe01ede8e8b52e61d '10.12 16A294a' f9c185d9e4c4ba12d5ecf41483055e39 '10.12 16A313a' eb27b5d68e9fb15aa65ea0153637eae2 '10.12 ' # Sierra 10.12 release cf8373138af4671a561c1a4d6cdba771 '10.12.1' b57e581f4d047848cf288a8a6c39c7ce '10.12.2 BETA: 16C32f' ) It would be so much safer and convenient if you could add a feature for future framework-patching to your beautiful bootloader. Another option would be to hardlink the framework executeable in a fake.kext but duh Too messy. xtraa
  15. xtraa

    Z170A Gaming M5 + 6600K Sierra install

    Assuming you have - not updated to the latest beta BIOS 1.C with "support for next generation intel cpus" - formatted the stick with GUID (because OS X likes to have MBR preselected for sticks) and you also - picked the UEFI entry from your F12 boots selection menu, not the legacy entry, - made the standard UEFI configs, like setting your drives to ACPI and disabling CSM under Boot Options > Windows etc. - placed all your kexts in EFI/Clover/Other/ and deleted the old folders, - plus you have either OsxAptioFix2Drv OR OsxAptioFixDrv installed but not both at the same time, the folder /EFI/Clover/drivers64uefi/ should contain the following files HFSPlus.efi PartitionDxe-64.efi EmuVariableUefi-64.efi OsxAptioFix2Drv-64.efi FSInject-64.efi OsxFatBinaryDrv-64.efi Maybe if you check these points, you'll already find the error. there is also an entry from a German hackintosh board, and the dude has nearly the same setup so you may try his files, too. click. Hope that helps and good luck!