bcfg entries look the same, but don't work the same?

I'm confused about the UEFI boot entries on my system, and I would appreciate some help understanding them!

My Hackintosh is running AMI UEFI BIOS. It has two SSDs, one with El Capitan, the other with Windows 10 (in UEFI legacy mode). I have Clover installed. When I go into Clover's UEFI Boot Shell and run "bcfg boot dump", it shows me this. (please excuse typos, and I added dots to help preserve indentation)

Option: 00. Variable: Boot0000
. Desc - Clover start boot.efi at Macintosh
. DevPath - HD(1,GPT, [my drive's UUID],0x28,0x64000)/\EFI\CLOVER\CLOVERX64.EFI
. Optional - N
Option: 01. Variable: Boot0001
. Desc - Clover start boot.efi at Recovery HD
. DevPath - HD(1,GPT, [my drive's UUID],0x28,0x64000)/\EFI\CLOVER\CLOVERX64.EFI
. Optional - N
Option: 02. Variable: Boot0005
. Desc - Clover start boot.efi at Legacy HD1
. DevPath - HD(1,GPT, [my drive's UUID],0x28,0x64000)/\EFI\CLOVER\CLOVERX64.EFI
. Optional - N
Option: 03. Variable: Boot0081
. Desc - Mac OS X
. DevPath - PciRoot(0x0)/Pci(0x1c,0x4)/Pci(0x0,0x0)/Sata(0x0,0x0,0x0)/HD(2,GPT,[a different UUID])
. Optional - N
Option: 04. Variable: Boot0082
. Desc - Hard Drive
. DecPath - BBS(HD,)
. Optional - N
Option: 05. Variable: Boot0083
. Desc - CD/DVD Drive
. DevPath - BBS(CDROM,)
. Optional - N
Option: 06. Variable: Boot000A
. Desc - Clover start legacy at Legacy HD2
. DevPath - HD(1,GPT, [my drive's UUID],0x28,0x64000)/\EFI\CLOVER\CLOVERX64.EFI
. Optional - N

Do I need all these entries? What's "Recovery HD"?

Options 00 and 01 boot into Mac OS. Option 02 boots into Windows, and option 06 just hangs at a black screen with a flashing cursor. How do these options do different things, if the DevPath on all four of them is the same?

I'd like to be able to run EasyUEFI under Windows to straighten this out, but it refuses to run because Windows isn't installed in UEFI mode.

I've determined that:

(1) if the bcfg entries look like they point to the same place, then they actually do, and they're redundant.

(2) Clover appears to keep its own boot menu entries that are distinct from what's in bcfg.

I came to the second conclusion after I removed the redundant bcfg entries but was unable to fix Clover's entries - Clover still lists "Boot Windows from Legacy HD1", "Boot Windows from Legacy HD2", and "Boot Windows from Legacy HD3", all of which do the same exact thing (boot from the Windows drive's MBR). I could probably hide these via Clover's config.plist, but I'd like to find out - where is Clover getting these from, and is there any way for me to remove them instead of hiding them?

I tried to edit this list last night and had the weirdest problem

Most of the time I could not type more than a few characters at command prompt. The curser would snap back to the beginning of the line.

If I tried to type::
bcfg boot bump

I would get to the "f" and the curser would move back to the left and over write the letters.

I'm using a 3 or 4 year old Apple Aluminum keyboard. Keyboard works fine otherwise.

Can you still type the full command and have it give you output? Maybe it's just the display that's messed up.

No, it was not the screen not updating. As I typed it (the curser) would jump back to the left, sometimes I could get 4 letters type, sometimes only on 1. Completely random. I tried longer button pushes and shorter. After several tries I was able to type exit. I was able to type; bcfb boot dump only once.

JoelATX said:

No, it was not the screen not updating. As I typed it (the curser) would jump back to the left, sometimes I could get 4 letters type, sometimes only on 1. Completely random. I tried longer button pushes and shorter. After several tries I was able to type exit. I was able to type; bcfb boot dump only once.

Click to expand...

I know this is old, but just in case anyone else comes across this problem. I had the same weird behavior. I have kept a wired keyboard handy for working "pre-boot". The wired keyboard was behaving as you described. The strange behavior went away when I pulled out the bluetooth usb dongle (which was paired to an apple wireless keyboard).