Build a real UEFI-native operating system from scratch. The complete path to a polished desktop is free. Paid members continue through storage, networking, applications and DOOM.
Every free OS-dev resource teaches the same thing: legacy BIOS, QEMU, a kernel that prints text and stops. That path skips the two questions that actually stump people — how do I get off the emulator, and how do I do any of this under UEFI instead of BIOS. This course is built entirely around those.
No 16-bit real mode, no GRUB, no bootloader you didn't write. Your code is what the firmware loads. This is how machines actually boot today — and almost nobody teaches it.
Every phase ends on physical hardware. You'll hit the bugs emulators hide — uncached framebuffers, DMA alignment, firmware quirks — and learn to read the machine, not the emulator's polite fiction.
Compositor, windows, a file manager, settings, a hand-written TCP/IP stack, USB. You build a system a person can actually use — then you boot DOOM on it to prove it's real.
Modules 01–04 are free and end with a decent bootable desktop. Every paid plan unlocks all written sections. Downloads depend on your plan.
Install the toolchain, build a UEFI application, boot it in QEMU or from USB, and draw correctly into the firmware framebuffer.
Own the memory map, install interrupt handling, bring up timer and keyboard input, and establish the kernel foundations.
Build double buffering, dirty-region rendering, text and the drawing primitives required by the desktop.
Finish the free path with draggable windows, a desktop, consistent controls and a bootable visual system.
Read and write real files, load assets and make the OS useful beyond the initial desktop.
Bring up Ethernet and build the network layers required for connected ForgeOS applications.
Integrate doomgeneric, provide display/input/time/file callbacks, use a legally obtained WAD and verify the port in QEMU before real hardware.
Protected processes, user memory, ELF loading, file descriptors, threads, shared objects and native applications.
AHCI, NVMe, USB storage, display modes, CPU capabilities, memory pressure and performance profiling.
HTTP/TLS, certificates, package detection, downloads, updates and the path from network stack to a usable web client.
VMX capability, guest memory, executable/runtime requirements and the staged route toward hosted emulation.
A window manager, draggable and resizable chrome, a dock, and a desktop. Build a small UI toolkit so every app shares one consistent, themeable look.
Bring up the xHCI controller, claim it from the firmware, talk to a USB drive over Bulk-Only Transport, and read & write real FAT32 files. Then a working file manager on top.
Drive the Ethernet NIC directly, then hand-write ARP, IP, ICMP, and TCP. Watch your OS answer a ping and open a socket using nothing but code you wrote. Settings, Wi-Fi status, NetMon.
Port doomgeneric onto your OS: WAD loading off your filesystem, your framebuffer as its display, your keyboard as its input. The universal proof that you built something real.
I detached UEFI's own USB driver mid-boot and the firmware started spamming write errors. I hit a 64 KB DMA boundary that silently corrupted transfers. I shipped a UI that ran flawlessly in QEMU and black-screened on real silicon. You'll learn this from someone who has already walked into every one of these walls.
// PixelsPerScanLine != HorizontalResolution // works in QEMU, shears diagonally on real panels buf[y * pitch + x] = color; // RIGHT buf[y * width + x] = color; // WRONG — the trap // firmware left the framebuffer UNCACHED: // 3.7M single bus writes per fill on a 1440p panel. // instant in QEMU, a slideshow on metal. enable_write_combining(fb_base, fb_size);
All paid plans unlock every written section. A$9/month is reading only. A$39/month adds every Section 1 download through DOOM. Lifetime includes all current and future important-module and section downloads.
Secure card checkout is handled by Stripe. Apple Pay and Google Pay appear when supported by the customer’s device and your Stripe settings.
Module 01 is completely free — the toolchain, the bootloader, and your first pixels on real hardware. No account, no card. Just build it.
Open module 01 →