File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change @@ -118,6 +118,10 @@ ld -T kernel.ld -o kernel.bin start.o kernel.o
118118
119119## Creating a bootable image
120120
121+ All Pure64 binaries are in the ` bin ` directory.
122+
123+ ### BIOS
124+
121125After creating a kernel this is a possible routine to create a bootable image.
122126The commands require Pure64 to be build and ` pure64.sys ` and ` mbr.sys ` to be in the same directory
123127as your kernel with the name ` kernel.bin `
@@ -133,6 +137,18 @@ dd if=software.sys of=disk.img bs=512 seek=16 conv=notrunc
133137After creating a bootable image it can be tested using qemu:
134138` qemu-system-x86_64 -drive format=raw,file=disk.img `
135139
140+ ### UEFI
141+
142+ For UEFI systems you'll need ` pure64-uefi.sys ` , ` uefi.sys ` , and a FAT-formatted drive/partition.
143+
144+ ```
145+ cat pure64-uefi.sys kernel.bin > software-uefi.sys
146+ cp uefi.sys BOOTX64.EFI
147+ dd if=software-uefi.sys of=BOOTX64.EFI bs=4096 seek=1 conv=notrunc > /dev/null 2>&1
148+ ```
149+
150+ The resulting ` BOOTX64.EFI ` can be copied to the ` \EFI\BOOT\ ` folder on the storage device you plan on booting from.
151+
136152## Memory Map
137153
138154This memory map shows how physical memory looks after Pure64 is finished.
You can’t perform that action at this time.
0 commit comments