just a quick note, or question, or both....

im wondering if the "FAT" (file allocation table) is even needed for a non DOS o/s... it might have been needed way back when, but i bet its not needed now. it might never have been needed.

 

 

Comments

Post a Comment

Popular posts from this blog

my latest os code, but its almost basically taken 95% from gemini. (i was on the right path, but i think my bad fat info ruined it)

 ; floppy_boot.asm ; A simple legacy boot sector example to read a sector from floppy and jump to it. ; ; To assemble with NASM: nasm -f bin floppy_boot.asm -o floppy_boot.bin ; To write to a floppy image (e.g., in a VM): dd if=floppy_boot.bin of=floppy.img bs=512 count=1 conv=notrunc org 0x7C00               ; Boot sectors are loaded at 0x7C00 BITS 16                  ; We are in 16-bit real mode start:     jmp short setup_segments ; --- Data --- ; These are placeholders for a typical boot sector. ; In a real scenario, you'd have more data here, including a Partition Table. OEM_ID                  db "MSWIN4.1"   ; OEM ID BytesPerSector          dw 512          ; Bytes per sector SectorsPerCluster       db 1            ; Sectors per cl...
Read more

woo hoo, here is an easy way to make UEFI boot code for YOUR os :D

 ok, i actually switched my code from old style floppy boot sector code, to UEFI boot code. now, its not as easy as compile and go, and you have to know C because there are some errors in the code you will have to fix to get it to compile properly, but "gnu-efi" makes it relativly easy to make uefi boot code. it can be found here: https://sourceforge.net/p/gnu-efi/code/ci/master/tree/ if you want to know how to use it? both co-pilot for windows 11 and gemini from google can answer your questions, no, im not joking, they are THAT smart :o ( i know, i was surprised too... they have also been helping me learn python!)
Read more