Replies: 2 comments
-
|
Beta Was this translation helpful? Give feedback.
0 replies
-
Oh! what a simple oversight! Many thanks Eugene. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Today I got my PC working with Windows 10 on both a HDD and as SSD (using a non-bootable NVMe-PCIe adapter).
It's taken some time as I needed to convert the HDD from MBR to GPT and in the processes ended up with Windows Boot Manager present on the HDD EFI partition.
I wrote up my issues and solution at AskWoody Go straight down to my post on January 30, 2024 at 12:53 pm . This starts off with the conversion to GPT and formatting the SSD and HDD and ends with part installing Clover. The following post then completes the Clover installation.
What I've yet to get working is for Clover not to display all the non-bootable partitions in its menu screen - over 10 of them! I edited the config.plist file and added the partition IDs (labels) to the Hide key but it didn't work. Any ideas welcome.
<key>#Hide</key>
<array>
<string>Win 10 SSD</string> <<< example entry added of SSD C: partition
<string>Win 10 HDD</string> <<<< ditto of HDD C: partition
<string>Windows</string> <<<< config.plist example
<string>BOOTX64.EFI</string> <<<< config.plist example
</array>
Win 10 SSD and Win 10 HDD are the C: partitions, not the associated EFI partitions. EFI partitions is what Clover uses.
Alan
Beta Was this translation helpful? Give feedback.
All reactions