5/19/2023 0 Comments Clover efi legitIf I set it to anything with UEFI in it I would get the low res bootloader that would give me the Windows boot errors. In order to finally get it to work I set it to "Boot legacy only" and set my boot device to P0 (the Clover drive). That being said, I think I may have my issue mixed up, I think my issue may be that it was booting UEFI and I needed the legacy entry. I can even use the Startup Disk pane now to tell it which OS to reboot. After that I had more flexibility in selecting the boot entries and was able to default it to go into the entry that was giving me a proper Windows boot. What I WAS able to do though was upgrade my board to UEFI, they were released on the cusp of UEFI and shipped with a legacy BIOS despite supporting UEFI. I tried reinstalling the EFI with Multibeast but I wasn't able to get it to work. Is there some way for me to force Clover to boot into whatever that second menu is so it'll properly boot Windows? Proposed solution: I noticed today that if I exit what appears to be the Clover legacy bootloader, I am then taken into the Clover UEFI bootloader (it's higher res, more devices show up, mouse semi-works), and selecting Windows will in fact boot it. My workaround has been to just boot straight into the Win 7 drive from the BIOS boot drive select which has worked fine. Issue: My primary issue is that when I try to boot Win 7 from the Clover menu I am greeted with a boot error. FYI I think I have a weird hybrid legacy/UEFI board but I've mostly used it as legacy over these years. I believe one of the issues I created may have been from installing both the legacy and UEFI version of Clover and fudging up the boot entries. There was a absurd amount of troubleshooting (primarily isolating the Win 7 install) and along the way I created, resolved, and created more boot issues with the Win 7 boot entry. Shortly after that I split them onto two separate drivers. Also now I can even utilize the Startup Disk pane which is very convenient for rebooting into Windows remotely.īackground: Many months ago I did a fresh El Capitan install on a drive it shared with Win 7. That being said, I think my issue may have been mixed up, I think I had Clover in UEFI instead of legacy which I needed to boot Windows, if that makes sense. I was able to get more boot entry flexibility and was able to choose the correct version of Clover that'd boot my Windows properly. Solution:I installed the UEFI BIOS upgrade for my originally legacy motherboard. Building a CustoMac Hackintosh: Buyer's Guide
0 Comments
Leave a Reply. |