- Joined
- Jun 28, 2010
- Messages
- 72
- Motherboard
- Gigabyte Z68XP-UD3
- CPU
- i7 > Need full CPU name > See Forum Rules!
- Graphics
- GTX 970
- Mac
- Mobile Phone
Solution: I installed the UEFI BIOS upgrade for my originally legacy motherboard. 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. 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. Also now I can even utilize the Startup Disk pane which is very convenient for rebooting into Windows remotely.
Background: Many months ago I did a fresh El Capitan install on a drive it shared with Win 7. Shortly after that I split them onto two separate drivers. 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. 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. FYI I think I have a weird hybrid legacy/UEFI board but I've mostly used it as legacy over these years.
Issue: My primary issue is that when I try to boot Win 7 from the Clover menu I am greeted with a boot error. My workaround has been to just boot straight into the Win 7 drive from the BIOS boot drive select which has worked fine.
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.
Is there some way for me to force Clover to boot into whatever that second menu is so it'll properly boot Windows?
Background: Many months ago I did a fresh El Capitan install on a drive it shared with Win 7. Shortly after that I split them onto two separate drivers. 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. 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. FYI I think I have a weird hybrid legacy/UEFI board but I've mostly used it as legacy over these years.
Issue: My primary issue is that when I try to boot Win 7 from the Clover menu I am greeted with a boot error. My workaround has been to just boot straight into the Win 7 drive from the BIOS boot drive select which has worked fine.
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.
Is there some way for me to force Clover to boot into whatever that second menu is so it'll properly boot Windows?
Last edited: