So at boot you will have two options: boot macOS Mojave or Windows 10
STEP 2 - Using a drive without Windows 10 installed
Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )
STEP 2 - Using a drive with Windows 10 already installed
Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.
But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )
If Windows 10 install is MBR / Legacy BIOS then simply convert to GPT / UEFI following instructions below ( read video summary and view video )
** To use Windows 10 MBR2GPT tool you must have Windows 10 version 1703 ( creators update ) or later and less than 3 partitions on
the Windows 10 drive **
Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management )
Reboot into Windows PE ( Advanced Startup )
Convert from MBR Legacy BIOS to GPT UEFI ( using commands below )
Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )
After conversion Windows 10 is ready to use at the Clover boot menu
I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
Chipset Intel 7 series, no patches needed
Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
USB3.0 works natively if not disabled in DSDT
PS2 keyboard and touchpad works with VoodooPS2.
WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
LCD Screen 1366x768
BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
As well a patch for channels.
I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
In Bios we can set Optimus = Enable/Disable
If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
But here there is contradiction with WiFi with required Board-ID from MacBookAir.
So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
Set BoardID like iMac13,2 to make Nvidia working.
Patch BoardID in Brcm4360 to make WiFi working.
Now I have
and SSDT-3.aml in ACPI\patched folder. This SSDT will switch off Nvidia if Intel card ON.
For Intel graphics there is a patch against 8 apples at start.
No special kexts.
The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here #72
DSDT and SSDT
This is very long story and finally I have working sleep in both cases Intel or Nvidia.
I use my HWSensors3 with FakeSMC 3.5.0.
I got monitoring:
GPU main frequency
GPU shader frequency
Battery state % full, time to charged or time to empty.
Battery voltage dinamically.
Battery amperage dynamically. I can see it changes on heavy games.
I like VoodooHDA and have no problems with it.
The sound is clear, loud, and switchable between internal speaker and headphone.
Mic is working.
Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
For 10.13.6 there is other kext BRCMInjector.
Keyboard, Touchpad and Touchstick
My config, ACPI files and kexts are in attachment.
Better DSDT in the post #6.
Sleep working even when AC inserted.
Now I have HighSierra and this is my EFI folder
Welcome to discussion!
I was trying to repair permissions today on my Mac so I ran the Disk Utility's First Aid on my drive and it said that there was an Invalid Index Key and that my disk was corrupt and I needed to run the first aid in Recovery mode.
So I opened in recovery mode and ran the first aid and it tried to fix the B-Tree of the catalog file, however there wasn't enough disk space to do this.
Then it tried to restore the disk to it's original state on mount but it couldn't do this either, I'm guessing because of lack of disk space.
(I had about 13GB of free space at this time)
Sorry I didn't get any screenshots or anything but that is basically what happened.
Now the disk is greyed out in disk utility and I can't reinstall mac os x because I would need to erase all of the data on the drive and I don't want to lose the files I have on it.
So what I thought I could try is delete my BOOTCAMP partition, which is about 100GB, and then merge the free space into the problem partition so that I can run fsck -fy in single user mode to try to repair the volume which now will have enough space to complete the operation.
However the option to delete the BOOTCAMP partition is disabled in Disk Utility.
So I did some research and found another post on AskDifferent that explained how to delete a partition from terminal (in recovery mode) by first unmounting the physical disk using diskutil unmountDisk /dev/disk0 and then deleting the partition using gpt remove.
Now I tried to unmount the disk using that command and even with the force wildcard but it said:
The volume with PID 0 from the list provided by diskutil list is called GUID_partition_scheme.
This is as far as I got through searching for solutions online. I need help deleting the BOOTCAMP partition and merging with the greyed out Mac HD partition so that I can run fsck to hopefully restore my mac os to working order. At the moment I can't boot into the OS and can only boot into recovery mode or single user mode. Hopefully I will atleast be able to retrieve files from the HD if all else fails.
"The all-new 2019 version of the graphic design software suite is compatible with not only Windows but also Mac, complete with support for Dark Mode on macOS Mojave and the Touch Bar on the latest MacBook Pro models, providing quick access to layout settings, text controls, and more." ~ macrumors
More details: https://www.coreldraw.com/en/product/coreldraw/mac/