Ok, this looks good. You can try to install Mint now.

If it still shows you error. You can try one more thing. Erase all partitions on disk, use Gparted to create a new partition table on the disk and choose "GPT". Then, without making any partitions on the disk, you tell Mint to install taking up whole disk. It will create its own partition and its swap. Later, you can shrink the system partition and add more partitions on the disk.

It still shows the error with that partition, scheme.
I can try erase disk and install ubuntu and see what happens.
I did erase disk before and windows 7 still showed that EFI 512mb partition. So erase disk and start over in the linux installer does NOT erase the disk.

But see, that makes me unhappy as I wanted a separate partition for the OS.

Last time I did erase disk, I got the error. If it happens this time, I will cancel the install, because it will not boot.

well, this time, installer immediately gave the UEFI warning on starting, I forced the install, told it to erase disk. I told it not to download updates or mp3 stuff to save time.

My guess is it will on restart simply give me aflashing white cursor. Too bad the linux programmers did not all have my system to experience when they made their installer, as then it would be working.

I understand, but maybe making a new empty GUID Partition Table (GPT) on the disk will work.

You said you booted Windows 7 on this computer? A gparted screenshot of that disk would have been informative.

Windows disk manager does not give useful information. From several of your screenshots the other hard disks looked like GPT, so we are assuming your system will boot UEFI. So, make sure there is no Legacy Boot activated in BIOS.

so your suggesting that running gparted from terminal as 'sudo gparted' in ubuntu 16.04 LTS can not create workable ext4 partitions that the installer can use? Which is what I have been doing.

Install has finished will now reboot.

Attached Thumbnails

 

No, I'm suggesting, since it is booting in UEFI mode, if you have already filled the disk with lots of partitions, the installer will not be able to install a bootloader on an EFI partition on the disk.

It fails to boot, just a blinking white cursor.
I am posting this from another pc.

my experience after at least 10 attempts to install is I always get the uefi error and it always fails to either install or boot after finishing the install.
Sometimes, earlier, maybe when the EFI 512mb partition was on there, when I had partitioned the drive manually, the installer could not update grub and it would just shut down.

Anyway this PC can run linux installed from another PC by swapping in an installed system,(meaning put in a working drive from another linux pc) but you can not install linux on this pc and have it boot.

I'll be frank with you, this does not sound at all possible. My best guess is that, since you took hard disk from another PC and brought it here, and honestly, I don't understand well what sequence of operation you did, there seemed to be a mix up between MBR and UEFI.

I think you can try what you suggested earlier:
For my part, I would have first verified that there is no legacy boot ON, then keeping only this disk in the PC I would have booted a USB Linux and run:
Then I would have created an empty GPT on the disk, an EFI partition and the rest (ext4, swap, ...).

I assure you it is most possible, I have done so many times and on many machines. Take a working install, stick into another PC and it boots, that is apparently the only way this motherboard can boot linux.

I see that the 512 EFI partion is created by the ubuntu linux installer, since it is back.

I tried ubuntu repair boot and tht fails to make it boot.

I know when I am beat, this is simply never going to work.
It wont do what I wnt, so I will have to install linux out at the boat on the PC out there.
This motherboard system here is crap regarding installing linux, but it does run really nice and fast linux.

Attached Thumbnails

 

ubuntu@ubuntu:~$ sudo gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help):

Wait a minute. Your screenshot shows a correct GPT. Get out of the gdisk. Try to see what is on /dev/sda1.

??ok, see what exactly?
And how to see this exactly?

If you mounted the /dev/sda1 you could see its content:
First see if it is not mounted:
Then create a mount point and mount it: