Many UEFI firmware implementations are unfortunately buggy, as mentioned earlier. Despite the specification for boot entries and boot order being quite clear about how things should work, there are lots of systems in the wild which get it wrong. Some systems simply ignore valid requests to add new boot entries. Others will accept those requests, but will refuse to use them unless they describe themselves as "Windows" or similar. There are lots of other similar bugs out there, suggesting that many system vendors have done very little testing beyond "does it work with Windows?"
]]>EDIT:
I used q4os-1.6.2-x64.iso
First I created my usb stick using rufus (I was in windows at the time) be sure to write in iso mode and NOT dd mode.
Next when rufus has finished open the disk using file manager and create a directory named EFI (capitalization IS important) enter that directory and create a directory named BOOT and in that directory place the efi shell file that can be downloaded from the page I got my instructions from HERE.
Next create a plain text file named startup.nsh (this is different from the instructions I found but works automatically) and put into it live\vmlinuz initrd=live\initrd.img append boot=live components and save it to the root of the usb stick.
Now reboot and select your usb drive from the boot menu, in my case I had to press F12 to get there, but other systems will be different.
As I have put in my other post on this issue after performing the installation you will not be able to get into the system until the boot manager has the .efi file available to boot Q4os (hopefully will be fixed sometime soon), but It is installed in EFI mode.
]]>I do realise the the other distro I used is based on debian testing and therefore would probably expect this would only be available for the scorpion version but that would probably be better for testing on new machines anyway really.
Just something for my wish-list that I thought I would share.
Dai
]]>