what is that boot64.efi attached to. I cannot find anything on that file, in what OS it is suppose to be. I trying to figure out How I got this laptop to be on pure UEFI (no Legacy support) for windows, slack, bodhi, and FreeBSD. and apparently with secure boot on in BIOS.

( the other one fbx64.efi may have been for FreeBSD, I don't know, I lost that one too after upgrading it to 13x it got screwed up just like slack did)

having to reinstall Slack after a 3 year hibernation upgrade that ended up in a catastrophically leaving me with having to reinstall slack, and I do remember 14.x grabbing efi and booting then giving me the option of elilo and this time with 15 it didn't so I put it in uefi w/ legacy support and it didn't even suggest anything efi.


so I'm reluctantly trying to get all of my OS's back like it was.

installing slack uefi
that is really vague. should that boot usb stick be created on a system that is already on pure uefi, when using dd?

because this install when I created it using dd it didn't boot, and I have to go back to uefi w/ legacy support, and now I'm starting to repeat umyself.

That directory, and the files in it, are not installed by Slackware. Probably one of your other OS installations, but if Slackware is to be the only OS on your computer you can delete the complete directory.

You are looking at information (without revealing its source) that mentions Slackware 14.1. Slackware 14.2 was released in 2016 so you are reading 6-year old documentation. Modern Slackware (I assume you will not want to try and install an old OS like 14.1) has no issues with UEFI at all. The official ISOs are hybrid (meaning you can burn them to a DVD but you can also 'dd' or 'cp' them directly to a USB stick) and the Slackware installation medium will detect whether it boots on UEFI or BIOS and proceed accordingly.
Please read the actual documentation that comes with Slackware 15.0.

To find out chainload the file with grub and see what boots or doesn’t boot.

Did you mean this one:
In Slackware 15, that file's usually the output of this script:
Where make-grub.sh does:
But if we're being realistic it could be anything, from anywhere. Unless you physically detach it from the computer and carry it with you at all times.

thanks for your time, I was just in my BIOS looking around and seen it set back to secure boot, turned it off and uefi only on, then tried a slackstick on it and it booted as it should and grub worked bypassing just windows booting.
gezz
marked solved.
(except bodhi usb telling me i have to load the kernel first for it to boot into it and or install it. but that's a completely different OS / issue)