Since writer:PDP-8 has shown awareness of the problem we face:
>1) Only run distros that have paid the tax for the microsoft approved uefi key.
>2) OR, be sure to turn OFF "secure boot" and try again.
>3) Make sure you have burnt the iso in a UEFI compatible format. That is, ...
does he accept that new/cheap laptops will have problems booting linux?
---
Rather than seek <propriety> solutions, I advocate general/universal weapons:
UEFI <government> has made available the UEFIshell, which seems very powerfull,
but needs competent-familiarisation, rather that the M$pook attitude:
"what can I get, which someone ELSE has already made to solve this problem".
It's better to know the <algorithm> to multiply ANY 2 integers, than the
result of some currently usefull products.
---
Have any Tinycore readers, who will share/expand our knowledge:
used/tested the UEFI-shell?
I'll write [with inevitable typos, since can't yet see how to
copy/paste from UEFI-shell results] my efforts to leverage UEFIsh's power;
ie. to really see into the guts of OS/kernel...drivers, <pciBus>...
First I tried to <extract basic *nix cmnds> like: ls, pwd, cd, df ...
==> replies to colaborators will follow.