Jump to content


  • Content Count

  • Joined

  • Last visited

About Cerberus73

  • Rank
    InsanelyMac Protégé
  1. Great list they have there but only go as far as 5th gen so a lot of them are not currently available.. thats the problem.. i need a current model I can purchase new. not much point buying a 3yr old model. its basically obsolete before you start.
  2. Right guys I'm off to NY in the next couple of weeks right around black friday. i live in the uk, so am going to take advantage of the cheaper hardware when I'm over. and buy a new laptop or 2 in 1, to replace my now elderly acer 5742. I need the following specs, 6th or 5th gen i5/core M 8gb ram, and full HD screen at a minimum (photoshop and illustrator are my living) a working trackpad (I see a lot of laptops have issues here) and swappable or compatible wi-fi.. i don't mind switching a card out or inserting a new one into a m.2 slot, but don't want a external inelegant dongle solution. and something that isn't a house brick. so slimmer the better. the budget isn't huge.. hence looking in sales for a last gen model. something between $400 to $800 max. I am comfortable with fiddling with bios settings, editing kext's, running scripts etc, but the results have to be stable, and the machine useable day to day.It will be a second machine as I have a very stable skylake desktop I built around 10 months ago. I have done a lot of reading on various hackintoshing sites, but a lot of the info is for older laptops that are not currently available new, or they seem to have major issues with soldered in wi-fi, and wonky trackpads. and as my time is running short, I figured it be easier to just ask what currently works and can be purchased. so if you can provide a make and model number and any changes that need to be done to get sierra installed. and if you have a link to a big retailer.. even better. I hope someone can help.
  3. Well Dremin, Thank you.. that did the trick, Downloaded the free version of Easy UEFI, set it to pick up the clover boot loader, and the windows boot loader, went into OSX, mounted EFI, and renamed the boot folder, Rebooted to clover, removed the extra boot entries in the shell, and jobs done, no more extra entries being created in my bios. I've checked a couple of times after reboots, and no new ones made.
  4. Thank you Dremin, i have created a EasyUEFI entry and it was still placing those extra entries. Now it makes sense since you say there is a known bug.. i shall go give that a try and rename the boot folder in the clover EFI partition to something else. i do have a rescue usb in case it all goes pear shaped.
  5. Thanks williamvinzant, already have CSM Disabled in the bios, and it is still adding all these extra entries, I have made some progress, after a lot of digging around old posts here and on other mackintosh related sites, i managed to get rid of all the extra icons on my clover GUI Screen. I set up a custom entry in clover configurator for my OSX System Drive, and My Windows 10 System Drive. For anyone else having issues with this, the procedure is simple enough, download clover configurator (google it), in the GUI section once you open your clover config.plist with it, select custom instead of auto in the scan section, select entries, and tools. now create a custom entry, you will need your efi folder(s) partition UUID, the path to the boot loader files (BootX64.efi in clovers, case, and bootmgfw.efi in windows case) i left it set as theme for icon, set osx to osx, and windows to windows, and set both as internal. gave them a name. Boot OSX and Boot Windows, saved config.plist, and bob's your mother's brother.. no extra entries in the GUI.. but i still have the problem of clover, the UEFI or whatever is creating these extra boot entries. They manifest in shell64 like thus.. PCI Root, Some hex numbers i guess point to the drive partition, then it has the HD, bracket,The drive partition UUID, some more hex and a closing bracket. This is really starting to get me down. as i have spent 3 solid days trying to beat this problem. and i can't get anywhere approaching a conclusive answer. it seems to be some weird mumbo jumbo voodoo stuff between clover, and the motherboards UEFI, it seems fairly common in the Hackintosh community, yet does not seem to affect everyones rig. I never seemed to have this kind of issue using legacy boot loaders like chameleon. there it was straightforward enough to get a dual boot up and running cleanly.
  6. I have exactly the same Motherboard as isotropy, and am having exactly the same issues. Surely there has to be some way to prevent all these extra boot option entries so it only reflects drives with bootable operating systems on them. The other solutions offered such as only using external drives.. No use to me. i need to dual boot to windows, and i need to have large amounts of storage. Surely the coders of clover have more than 1 drive attached to there rigs. and have included this in there code.
  7. Ok i finally got a mostly operational install of El Capitan 10.11.3 on my new dual boot Windows 10, OSX rig. Just to clarify this machine has an SLI setup under windows with a pair of 970 GTX 4gb, 1 dedicated Samsung Evo 850 250GB SSD for windows and OS X each.. as i thought having separate boot drives would be less hassle. Each OS also has a dedicated 4TB Hybrid HD each, and there is one old Maxtor 160GB SATA HDD i use for windows backup. And a Apple Native Broadcom WiFi Card. I have injected USB, entered all the fixes to raise the number of ports in Clover config.plist, added the entries to get the Nvida web driver for 10.11.3 to work, as well as the latest Cuda drivers for OSX, And done the edits to get the onboard Audio (ALC 1150) along with the shell script to get it all working. The Motherboard is a Gigabyte GA-Z170X-UD5 TH, and the SMBios entries are for mac pro 5,1. I Also have USB-SSDT.aml, and SSDT.aml for CPU in the clover patched folder. Processor is a i5 6600K, clover updated to latest as of time of posting.. right now i have the hardware and basic setup clarified. I shall get onto the niggling issues. In The Clover GUI i have the following entries from left to right: Boot Microsoft EFI from EFI (this if selected does boot into win 10) Boot Mac OS X from Mac (this works as intended, Mac being the name i gave the drive) Boot Recovery from Recovery HD (have yet to test whether it will boot but i suspect it will) Boot Windows from EFI (Black screen with a HD icon, does not boot, i suspect the EFI referenced is the Clover EFI not the Windows EFI Partition) Boot Windows from Windows 10 (Windows 10 is the name of the drive where windows is installed.. same result black screen HD icon, no boot) Boot Windows from (i suspect it should say Data as that is the other NTFS formatted Drive for Windows use) All drives are GPT Partitioned, there are no legacy devices, as i wanted to simplify any issues as far as i could regarding Dual Booting etc. Mac Drives are HFS+ Journaled, and Windows Drives are NTFS. Firstly i would like to find out how to remove the non bootable entries, so i only leave the Windows 10 SSD, And the Mac OSX, and Recovery Drives. and or modify the boot loader so everything is working nicely, it works at the moment but its messy and has other problems. The other issue i am having is every time i reboot it adds extra entries in my boot options in the bios, so after a few reboots it can have a string of extra entries. i have gone into the clover Command line and removed these by hand by typing: cfg boot dump, looking at the entry number and removing all except the ones pointing to HD directly by typing cfg boot rm XX (where XX is the boot entry number listed). I have read other posts on the web of similar issues, but as yet not found a fix. I have selected the Mac SSD as the 1st boot option in the bios and saved and exited. When i built the machine i installed Windows firstly, as there was no working solution to install OSX on this hardware, Windows is installed on the SSD that is Attached to SATA port 1 on the board, The Mac SSD is attached to SATA port 2, I don't know if this will have any bearing on the issues I'm experiencing, but id like to give as much clear info as possible, to hopefully find a solution. Does anyone know of a way to stop these extra boot entries being created after i remove them and set priority of boot in the bios? I'm VERY new to Clover having only used Chameleon on a somewhat elderly Core2Quad based hack running Mountain Lion. And is there a way to move the extra non bootable drives/partitions in the Clover GUI?
  8. Hi, i Have built a new PC, currently running windows 10 pro, and looking to dual boot OSX El Capitan. I have been patiently waiting to see what the state of play is regarding Skylake, and the 10 series chipset motherboards. Hardware wise it is a Skylake i5 6600K, Gigabyte GA-Z170X-UD5 TH motherboards, Apple airport native PCIe with Bluetooth 4, 32GB DDR4 2133, 2 x Samsung 850 Evo SSD, 2x Seagate 4tb Hybrid drives, and elderly maxtor HDD i use for backup purposes only. 2 x Gigabyte wind force 970 GTX 4gb. Now onto what I've found, the motherboard has been updated to F4 bios (last stable non beta at time of writing). I am trying to figure out what DSDT patches i would need to get a stable install of EL Capitan, I plan on using clover as the boot loader, and to dual boot win 10. There does not seem to be a lot of information regarding 10 series boards, and what is usually points to Asus 170 based boards. I would like to have as simple a list of required patches as possible. so i can enable them via MacIASL. I have extracted the DSDT and all 8.. yes 8 SSDT files. I want to have as "vanilla" a setup as possible. So far i have kexts to enable the Intel Ethernet i219 (mausi kext), latest FakeSMC, The USBInjectAll.kext to help enable the USB ports. I really want to get on with installing OSX onto this machine. So any pointers as to what else i will need to get a successful install done would be gratefully appreciated. I have a elderly mountain lion system running to do the editing of DSDT and build my installer from.
  9. Cerberus73

    Apple has seeded the first 10.11.2 beta

    Far more interested in if it sorts out support for skylake and Z170 than older hardware like 9 series boards. would be nice to know whether SATA, USB 3.1 etc are gonna work on Z170 and H170 based boards.
  10. Cerberus73

    New build soon, and reintroduction.

    I may purchase a second Evo 850 250gb to use as osX boot drive as it would be less hassle and less chance of disaster than partitioning 1 SSD to use as boot drives for Windows and osX. I just have to remain patient, and keep an eye on the forums to see if theres progress on El Cap on Skylake/Z170
  11. Cerberus73

    Apple has seeded the first 10.11.2 beta

    Hope they put better Skylake support, TB3 etc in it… I'm itching to build my new rig with Z170 mobo.
  12. Hi, its been a while since I've had need of building a new hackintosh, since my old system i built a few yrs back with the great info i got here served me well, and it ran flawlessly, but times move on and its long in the tooth now. So onto my planned replacement. Skylake i5 6600k, 32 Gb crucial DDR4, 2 x Gigabyte GTX970 Windforce 4gb, Gigabyte GA-Z170X-UD5 TH Motherboard, Apple native broadcom Wi-Fi card in a PCI-e adapter and a pair of 4tb Seagate SSHD hybrid drives with a samsung Evo 850 250gb SSD as boot drive. and a suitable Blu-ray burner once i decide or find out which work oob with osx. I shall be keeping an eye on the forums here for info on 100 series chipset, and board support. and on general apple news for a release of either a new mac pro with TB3, USB 3.1 and dual GPU's that we can use as a basis for a hack, and further support in upcoming point releases of El Capitan. as far as i can figure out that the 10.11.1 release recently does not implement fully the things we need to get OSx running anywhere close to native on 100 series chipset boards. But i am hopeful the good folks here can help me, and others get there new sky lake builds working.. but until such time that it is fully working with either native support, workarounds or kexts to get all the hardware working i will be holding off. as this new machine will be my daily driver. so it needs to be relatively stable. In my old hack i only ever ran OSx by itself, but in this new machine i plan to dual boot into windows 10, a quick question.. can i instal OSx after windows? as i will probably be building this rig soon, so will use windows for gaming, and want to install OSx El Cap later when support for my hardware becomes available (if it ever does) i do know i will have to format drives as GUID when i install windows instead of MBR so to make the OSx install process easier later on. any advice on dual booting procedures? I plan to use Clover as my boot loader, where my last hack used chameleon.
  13. Cerberus73

    Should Apple Sell OSX For Use On A PC?

    Apple could still have control of the os, and the hardware it runs on, by producing quarterly or bi - annual hardware compatability lists much like the ones found online for current hackintoshes, but slimmed down, and unlike the trial and error and patching that goes on at the moment to get it to run, it would be straightforward and just work, say maybe support a dozen or so motherboards, same with graphics cards, wireless etc, and offer os X at a premium price for generic hardware, ie the current price of $29 for real macs, and a more expensive one for generic PC hardware from there HCL lists, say for around $150, this would ensure the hardware mixes were supported, that the prices were lower, and types of system apple dont built could be had for us users whom want a mid tower somewhere between a mac pro and a imac. Hell they could even colaborate with mainboard manufacturers to produce boards with an apple approved EFI on it, and charge a little more for the board, say an extra $25 on top of the same model BIOS only board, and cream off profit from a mix of osx pricing for these boards, and licensing fees for the EFI code. market penetration would easily double, people would have more choice of the type of system to run os X on top. Sure people like us users on these forums get a kick from making it run on hardware it was never designed to operate on, but for joe bloggs on the street a official licenced for os X line of hardware would give them the re-assurance that they could buy hardware to ensure a smooth experience or a pre built system from the likes of dell, hp, lenovo etc that were made to work out of the box with no patching required. Apples claim that it would be solely responsable for support is wrong, in any pre-built system with windows the onus is on the manufacturer to provide support for windows issues on there hardware, apple could do the same therefore negating the argument that it would be a support nightmare. they could also market special applecare packages for these users as an extra layer of comfort, and another revenue stream. People will always buy Apple made hardware, because it looks better, or is percieved to be more stable etc, i doubt very much that sales of mac hardware would slump, if anything people would try the cheaper alternative, learn to love os X and the next time go for a proper Apple model, much like the mac mini was designed to do... but to be honest has not had the impact in doing so, being to underpowered for all but the most basic of tasks.