add a general understanding section in README.md #30
Replies: 3 comments 6 replies
-
I think every project needs a general understanding section in README.md, to help new contributors understand, well, here it wasn't really needed because the python code is SOOOOOOOOOOOOOO clean. tysm, I was really confused about the bootable magic, was doing tests, found this repo and it helped me understand, I don't think I could've otherwise also, I had to move or else it said module not found (I don't remember the exact error message, I'm on Windows now) should we move these ? |
Beta Was this translation helpful? Give feedback.
-
yeah... I think we shouldn't put it in the wiki because I totally missed it. a link to my favorite documentation is https://www.autohotkey.com/docs/AutoHotkey.htm where are the files to the wiki located ? can it only be edited on github ? |
Beta Was this translation helpful? Give feedback.
-
GENERAL UNDERSTANDING could help people do/write variations you don't need UEFI:NTFS you can use .EFI from GRUB and GRUB can do the chainloading:
of course this GRUB is for Ubuntu. But with this menuentry it can also boot Windows explaining the function of code so a file explaining function: not even pseudocode. |
Beta Was this translation helpful? Give feedback.
-
(use UEFI if you can)
UEFI: no MBR involved
UEFI looks for
.EFI
files in fat(32/16/12) partition.your Windows
.EFI
is in NTFS partition (UEFI cannot see it)we're going to make a fat32 partition with
.EFI
that will chainload Windows.EFI
(the chainloader.EFI
can see Windows.EFI
).EFI
files from UEFI:NTFS in the fat32 partitionwe download from here, it's an
.img
, if you mount it, you'll see.EFI
files.EFI
from UEFI:NTFSUEFI:NTFS will find the first Windows partition or NTFS partition
and chainload
.EFI
: for x64 systems, it's/efi/boot/bootx64.efi
BIOS: no .EFI file involved
BIOS looks in the MBR to see what to boot
by making
grub.cfg
exactly as such:BIOS is bad: MBR can only tell BIOS to boot one operating system, MBR telling BIOS to boot into GRUB let's us use many operating systems.
UEFI looks for .EFI files, if you have many .EFI files, you can have many boot options listed in UEFI boot order menu.
though having .EFI in NTFS doesn't help, because UEFI doesn't see NTFS.
some motherboards provide drivers to see NTFS: in this case, you don't need the fat32 partition, it sees the .EFI in the NTFS Windows Partition.
Beta Was this translation helpful? Give feedback.
All reactions