OSDev.org

I have been using a couple of tutorials and using QEMU and VirtualBox to learn OS development. I have recently made three bootloaders which are a basic bootloader prints letter A using 0x10 interrupt, a bootloader that uses 0x13 to access disc and jumps to it, a bootloader that calls external C code.

I compile the code to .bin format using nasm and gcc -ffreestanding and then combine them using cat (in case of c kernel). The images work on qemu and if I turn them into floppy images they work on virtualbox too. When booting on a real computer the invalid partition table error is thrown so I followed the first part of this tutorial (https://wiki.osdev.org/Bootable_Disk#Creating_a_File_System_on_the_First_Partition) and used fdisk to just create partition table using option 'o' (DOS/MBR) then the last part adding the BIOS bootloader. This did not work. I have tested it on three computers, the first one says invalid partition table but does print letter B using the second bootloader if enter key is pressed, the second and third one does nothing except a blinking cursor. I have used legacy mode on all three computers. The third bootloader with external C code does not work or print anything on the real computer at all. Code for the first two bootloaders is below but I can post the bootloader with externel C code too if needed, it is just longer which is why I have not posted it.





Any guidance on what I am doing wrong? Thank you.

Bootloader tutorials are usually not very good. Also, writing your own bootloader takes time away from writing your OS. If you want to write an OS, you should use an existing bootloader like GRUB or Limine.


That doesn't sound like the correct way to use GCC...


Huh. That tutorial has terrible advice, you don't need GPT or an ESP system partition to boot from USB.


If you want to partition your USB drive for boot, your MBR must include exactly one active primary partition. Some BIOSes are picky about the geometry, too.


There are several websites (including GitHub and Gitlab) that can host all of your source code plus version history. You can use one of those to share your code. (You should use version control even if you don't want to use one of those websites.)


The comment is incorrect. That value determines how many sectors to read, not which sector to read.


You should use an aligned address. Also, you have no idea where the BIOS might have put its stack, so you might be overwriting the stack when you load data.