- Joined
- Aug 30, 2018
- Messages
- 1,467
- Motherboard
- Asus ROG Strix Z390 I-Gaming
- CPU
- i7-8700K
- Graphics
- Vega 64
- Mac
- Classic Mac
- Mobile Phone
Need some help plz
What is the issue?
Need some help plz
Yes, many more benefits than just having a >2TB volume.Is there a significant benefit to using UEFI boot?
For Win10:
[...]Reboot to BIOS/UEFI and disable CSM. Save&exit, continue boot to desktop. Shut down, disconnect the drive.
With both drives connected boot to UEFI/BIOS. Set the Mac OS drive as first in BBS boot order. Save&exit, continue boot. It should boot to Clover and allow you to choose OS to boot.Thanks for the guide. I have Mojave running fine on a Hackintosh. Until now, Mojave has been the only OS on the machine. I want to add Windows 10 on a separate drive. I have followed your guide. The last step in your Win10 instructions - disabling CSM - is where I first run into trouble: CSM support is set to "ALWAYS" and greyed out in the BIOS/UEFI-interface, so I can't change its setting. (?)
More importantly, when both drives (Mojave and Win10) are connected, the machine will only start up in Windows. Clover is never initiated. If I disconnect the Win10 drive, Clover and Mojave start up as usual.
Any suggestions?
With both drives connected boot to UEFI/BIOS. Set the Mac OS drive as first in BBS boot order. Save&exit, continue boot. It should boot to Clover and allow you to choose OS to boot.
The correct Win10 icon is labeled Boot Windows EFI from EFI.Thank you very much! I didn't really find anything called "BBS boot order" in the UEFI/BIOS, but I did find some drive icons that seemed to be listed in a certain order. I tried dragging them around and found that I could change the order of them that way. This helped! Now the machine automatically runs Clover at startup - and I can see a couple of drives with a Windows icon in Clover.
However, when I choose the Windows drive that says EFI on it in Clover, Windows freezes at startup. If, however, I press F12 at startup and manually choose the correct Windows startup volume in the UEFI/BIOS (before Clover is initiated), Windows starts up just fine. Also, I notice that Clover is annoyingly slow at startup (reporting that it is checking hardware etc.). My son (it's my son's computer) says it been that way for a while (before we installed Windows) - slow, but maybe not THAT slow.
I am unsure of the correct etiquette here. Perhaps I should start a new thread about those problems?
Should not be. The only difference when you installed using bootcamp is that is placed the UEFI partition at the beginning of the drive. Windows usually installs the UEFI either second or third position and Clover does not like it there. You should have no problems.MY QUESTION IS.... is there any lingering screwy-ness from that bootcamp "efi" partition or whatever, and is that possibly affecting my Clover EFI installer -- maybe screwing up my windows somehow and not enabling certain hardware I'm not aware of, etc.? Everything seems pretty great ? I just want to make sure because.. .I have .. no idea.
Shut down, disconnect the drive.