Kudos.. very comprehensive explanation. Like all "innovations" the increased complexity leads to increased failure. Those who have had to repair UEFI boot failures and corrupted configurations resulting from Microsoft update baloney, will understand this. BIOS was the rope-and-tire-swing method... all it did was work. It would be nice to see the author do a second take on UEFI... bug fixing. The steps required for resetting, clearing, repairing and fixing UEFI problems. BCDEDIT /export is your friend.... make a backup before your UEFI system takes a dive.
Glad you liked the video. You are right, UEFI is a lot more complicated than BIOS so good when it works. We will consider doing a video at some stage on UEFI related problems.
FOR INTEREST ONLY: (1) All GPT drives still have an MBR ! You can make a dual boot disk which uses both methods and will boot to Windows 11 on a new PC and Windows 10 on an old one. (2) I have an Intel i3-4130 motherboard running original IBM-PC software and using all the original ports by never switching out of 16 bit mode. (3) I have an 8-BIT BIOS chip from 1978. Because EPROM was so expensive I had to get the BIOS in 512 bytes. That's why early controllers for networks and HDD used to have their own BIOS "extension" chips on board.
Thanks for the comment. GPT has a protected MBR for compatible with old disk software as without it, the old disk software not knowing what GPT is may overwrite it.
Just a hobby-horse of mine. I wrote the firmware for an early IBM PC clone. MBR drives are NOT limited to any capacity. It depends on both the SECTOR size of the drive and the version of FAT used by the operating system. I have devices with 128 bit, 512 bit and 4096 bit sectors and formatted in FAT8, FAT12, FAT16 and FAT32. The smallest is a 40 year old 35 track single sided 5.25" FDD and the largest is a 2023 Seagate drive with 4K sectors.The drive capacities vary from 37KB to 16TB ! All the HDD and USB drives BOOT on a 2015 SuperMicro Dual Xeon server board with unmodified BIOS (latest update).
You are correct, thanks for the comment. We should make it clearer the limitation is using the 512 byte sector size. It is possible to increase the size by increasing the sector size if you have software and hardware that supports it.
We have this video which goes through the BIOS and UEFI. ruclips.net/video/a2GGSb18Zqs/видео.html We are working on an updated UEFI video which will released as soon as we can.
that bios ship is labeled as bios but its meant that its the uevi nvram, and this chip doesnt even content the uefi but the uefi boot manager which boots an uefi on an uefi partition of a hard drive. right?
UEFI maybe labelled as BIOS although technically not correct. The UEFI will access the code from nvram like most modern BIOS will. UEFI has the option to store additional data on a UEFI partition. This is often used for a recovery partition.
Boot your UEFI computer into the UEFI Shell environment. Change to the directory where the "doom. efi" exec is stored (change the current filesystem drive to the one that contains the exec e.g FS0: ) Type "doom" to start DOOM. github.com/Cacodemon345/uefidoom We are in the process of updating this video, so we will give it a go. Thanks for the idea. :)
Kudos.. very comprehensive explanation. Like all "innovations" the increased complexity leads to increased failure. Those who have had to repair UEFI boot failures and corrupted configurations resulting from Microsoft update baloney, will understand this. BIOS was the rope-and-tire-swing method... all it did was work.
It would be nice to see the author do a second take on UEFI... bug fixing. The steps required for resetting, clearing, repairing and fixing UEFI problems.
BCDEDIT /export is your friend.... make a backup before your UEFI system takes a dive.
Glad you liked the video. You are right, UEFI is a lot more complicated than BIOS so good when it works. We will consider doing a video at some stage on UEFI related problems.
FOR INTEREST ONLY: (1) All GPT drives still have an MBR ! You can make a dual boot disk which uses both methods and will boot to Windows 11 on a new PC and Windows 10 on an old one. (2) I have an Intel i3-4130 motherboard running original IBM-PC software and using all the original ports by never switching out of 16 bit mode. (3) I have an 8-BIT BIOS chip from 1978. Because EPROM was so expensive I had to get the BIOS in 512 bytes. That's why early controllers for networks and HDD used to have their own BIOS "extension" chips on board.
Thanks for the comment. GPT has a protected MBR for compatible with old disk software as without it, the old disk software not knowing what GPT is may overwrite it.
perfect ,simple and best thanks 🙏🙏🌹🌹
Most welcome 😊
Very informative, thanks!
Thanks very much, and thanks for watching.
This tells us that enabling CSM increases the booting time, because it allows you to boot via UEFI even if the system has MBR partition.
CSM allows compatibility with older hardware. As a result, it can slow the booting processing down. Essentially allows UEFI to use some BIOS features.
Very good information. thanks
Thanks for watching.
Day 5 dont give up
Thanks for watching.
Great video. Thanks.
Glad you liked it!
Very Useful Video
Thanks
outstanding... All drivers to be digitally signed, for secure boot to be successful
Glad you liked the video.
Just a hobby-horse of mine. I wrote the firmware for an early IBM PC clone.
MBR drives are NOT limited to any capacity. It depends on both the SECTOR size of the drive and the version of FAT used by the operating system. I have devices with 128 bit, 512 bit and 4096 bit sectors and formatted in FAT8, FAT12, FAT16 and FAT32. The smallest is a 40 year old 35 track single sided 5.25" FDD and the largest is a 2023 Seagate drive with 4K sectors.The drive capacities vary from 37KB to 16TB ! All the HDD and USB drives BOOT on a 2015 SuperMicro Dual Xeon server board with unmodified BIOS (latest update).
You are correct, thanks for the comment. We should make it clearer the limitation is using the 512 byte sector size. It is possible to increase the size by increasing the sector size if you have software and hardware that supports it.
Wonderful
Thank you
How could you record the UEFI demo??
We have this video which goes through the BIOS and UEFI.
ruclips.net/video/a2GGSb18Zqs/видео.html
We are working on an updated UEFI video which will released as soon as we can.
thank you very useful video
Thanks very much.
well done
Thanks.
that bios ship is labeled as bios but its meant that its the uevi nvram, and this chip doesnt even content the uefi but the uefi boot manager which boots an uefi on an uefi partition of a hard drive. right?
UEFI maybe labelled as BIOS although technically not correct.
The UEFI will access the code from nvram like most modern BIOS will.
UEFI has the option to store additional data on a UEFI partition. This is often used for a recovery partition.
Good video
Thanks for the visit
Thank you
You're welcome
minunat !
Thank you.
The dada man
Thanks for watching.
Yes Sir, give more information
Thanks very much,
but can it run DOOM?
Boot your UEFI computer into the UEFI Shell environment. Change to the directory where the "doom. efi" exec is stored (change the current filesystem drive to the one that contains the exec e.g FS0: ) Type "doom" to start DOOM.
github.com/Cacodemon345/uefidoom
We are in the process of updating this video, so we will give it a go.
Thanks for the idea. :)