UEFI Build Test

[gold_finger]

Yes, I installed LL as the only OS on the computer and wiped-out Windows. So if you want the "advantages" of the UEFI, you need to have a UEFI a build of LL. If you are satisfied with the legacy mode, the current build is fine even it you want more than one operating system on your computer?  :-\

@Coastie,

As far as daily operation of your computer goes, it makes no difference whether you've installed in Legacy or UEFI mode.  The firmware (UEFI or Bios) only comes into play for the first few seconds after powering on the computer.  After that, the operating system takes over and works the same no matter which mode you initially booted in.  You can install other OS's if you want -- just install them in Legacy mode too so that dual-booting will work properly.  It's only when you have OS's installed in different modes that you will have problems with dual-booting.  Perfect example of that is below.

If you've got further questions, Coastie, start a new thread please.  I think Jerry would rather this thread stick to posting results of tests.

Extended test:
First installed non-UEFI Windows7 Home Premium to one half of SSD.
Then tried to install alongside UEFI LinuxLite. Although the Windows partitions are visible from Live desktop, the alongside installation of LL is not offered at all - just "Erase Disk" option. In "Something else" option the Windows partitions are not shown and all disk is declared as free space.

These are common occurrences when attempting to do a "mixed-mode" install -- one OS in Legacy mode, the other in UEFI mode.  In this particular case, since Windows was installed first (in Legacy mode), the drive was automatically set to use MBR partitions.  A UEFI mode install (of Linux or Windows) requires the use of GPT partititons, so installer won't offer choice to install "alongside" if other OS is not already installed in same mode.  The drive will also need to be converted to using GPT partitions which might be the reason why installer shows the disk as empty.  (There are a few other possible explanations for this behaviour, but not worth going into now.)