[program-l] Re: uefi and legacy, help!
- From: "Lukasz Golonka" <dmarc-noreply@xxxxxxxxxxxxx> ("lukasz.golonka")
- To: program-l@xxxxxxxxxxxxx
- Date: Fri, 14 Jan 2022 17:26:09 +0100
Hello,
On Fri, 14 Jan 2022 12:15:26 +0100
"germano carella" <dmarc-noreply@xxxxxxxxxxxxx> ("gcarella") wrote:
With help of sighted User, I entered my bios settings and I discovered my
bios boot option is set to "uefi and legacy"; other options are: "leacy onli"
and "uefi onli".
I suspect the problem is that my primary disk is formatted with mbr, not gpt.
Now, I think I can keep my bios setting to uedi and legacy, and operate only
on disk.
That depends on your mother board and can be discovered only by trial
and error unfortunately.
There is a way to perform a uefi conversion without help of sighted user?
Yes, you can certainly do the conversion yourself, but it would require
some preparatory steps.
Firstly, and I cannot stress this enough, you need to backup your entire
hard disk and have a way of independently restoring it.
While the next steps are pretty safe you can never be sure.
You would also need a bootable disk with Windows 10 and a Linux
distribution such as Arch Linux or GRML (the important point is that it
needs to contain Speakup and a GPT fdisk).
You also need to have a small (around 1GB) amount of unallocated space on
the disk that is where you will create an efi partition in the next
steps.
After booting from the Linux distribution you should follow
https://www.rodsbooks.com/gdisk/mbr2gpt.html
to convert your hard disk to GPT using gdisk and then create a efi
partition in the unallocated space.
After these steps you Windows would no longer be bootable, so you need
to start from the Windows 10 installation disk, format the efi partition
into fat32 and then generate boot files using bcdboot
(
https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdboot-command-line-options-techref-di?view=windows-11)
-
Good luck
Lukasz
** To leave the list, click on the immediately-following link:-
** [
mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [
mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
Other related posts:
