bMETAL / DOS64
bMETAL disk logo

bMETAL

DISK OPERATING SYSTEM 64

Ready-to-use system image

Download image

Download the prepared x86-64 UEFI disk image, try it in a virtual machine, or write it to a USB drive and boot on compatible hardware. No source tree or build tools are needed to try this image.

Raw disk image229 MiB UEFI x86-643 FAT32 partitions

Image build: · Published on this website:
File: bmetal-dos64-usb.img · 240,123,904 bytes
SHA-256: 5fe10aa5f8b6511a6fdc34a83578e4675333b7979d632de5ac736e53085e0657

Provided as-is, with no warranty or guarantee. Use at your own risk; what you see is what you get. DOS64 is experimental. Back up important data, use a VM or disposable test media, and see the full disclaimer and license notice. Writing the image erases the selected USB drive.

A whole-disk IMG (not an ISO): 50 MiB EFI boot partition, 100 MiB C: system volume with tools, PE32+ examples and SDK files, plus a 78 MiB empty D: data volume.

Image contents: all 15 programs and games

Inventory of the image built on , published here on . Publication does not mean the system was rebuilt. All programs below are in C:\EXAMPLES\W64. Change to that directory, then run the filename. Built-in shell commands are part of DOS64, not separate executables.

ProgramTypeDescription
breakout.exeGamePaddle-and-bricks arcade game.
maze3d.exeGameFirst-person 3D maze exploration.
edit.exeToolASCII text editor. Pass a text filename to open or create it.
mixer.exeToolAudio volume control with a test tone; also installed in C:\BDOS.
syscheck.exeToolSystem diagnostics; also in C:\BDOS and run by AUTOEXEC.BAT.
alphademo.exeGraphics demoMoving translucent layers, alpha blending, FPS display, and optional audio chirps.
cubedemo.exeGraphics demoRotating translucent cube.
fpsdemo.exeGraphics demoFrame rendering and frame-rate demonstration.
gfxdemo.exeGraphics demoDrawing primitives and graphical input demonstration.
fsdemo.exeFilesystem demoFile creation, reading, and directory operations. Writes test data.
reloc.exeLoader demoChecks executable base relocations using absolute data pointers.
sounddemo.exeAudio demoGenerated sound playback; optional WAV saving.
threaddemo.exeConcurrency demoCooperative workers, joins, mutexes, conditions, and bounded queues.
timedemo.exeTiming demoMonotonic timing and real-time clock queries.
wavplay.exeAudio playerPlays a WAV file; bundled chime.wav provides a test sound.

Other files: C:\EXAMPLES\W64\bmetal.dll, chime.wav, C:\AUTOEXEC.BAT, and the SDK headers/runtime/import library under C:\SDK. The EFI partition contains EFI\BOOT\BOOTX64.EFI and startup.nsh. C:\EXAMPLES\LINUX and D: are empty. No Doom executable or game data is included.

Browse real application screenshots and launch commands.

Standalone SDK

No disk-image extraction needed. API 14, runtime 1.0, all 12 public headers, MinGW import library, startup object and source, updated Windows test runtime with a three-second startup splash for GUI apps, example source and executable, and build instructions. No kernel sources, compiler, or system image.

SDK build: · Published on this website:
File: bmetal-dos64-sdk-api14.zip · 206,899 bytes
SHA-256: 33a083793e51f93024a6c0da1e43b81ca2d2f8d613b91824638fa604096d8903

01

How to boot

Requires an x86-64 machine with 64-bit UEFI, GOP graphics and Secure Boot disabled. Hardware support is experimental; try QEMU first. A successful VM boot does not guarantee laptop compatibility.

In QEMU (recommended)

On Linux with QEMU and OVMF installed, open the image directory and run the command below. It allocates 1 GiB RAM; adjust the OVMF path if your distribution installs the firmware elsewhere.

$ qemu-system-x86_64 -m 1G \
  -device qemu-xhci \
  -device usb-kbd -device usb-mouse \
  -drive if=none,id=dos64,file=bmetal-dos64-usb.img,format=raw \
  -device usb-storage,drive=dos64,removable=on \
  -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd \
  -boot order=c -display gtk -serial stdio
Image safety: close the virtual machine before replacing, copying, or modifying its image. A running guest may be writing to the disk.

On a USB drive

Use a USB drive larger than 229 MiB.

Destructive operation: writing the image erases all data on the selected USB drive. Confirm the whole-device path carefully; never select your system disk.

Identify the USB device

On Linux, compare lsblk -o NAME,PATH,SIZE,MODEL,TRAN,TYPE,MOUNTPOINTS before and after connecting the USB drive. Confirm its model and size.

Use an image writer

Select the downloaded .img as the source and the verified whole USB device as the target. It is already a raw whole-disk image; do not format it or copy it to a FAT volume.

Boot from USB

Restart, open the firmware boot menu, select the USB device's UEFI entry, and keep Secure Boot disabled. Leave all three partitions intact.

The data volumes keep their fixed sizes on larger USB drives.

First boot: AUTOEXEC.BAT runs a system check. At the prompt, try help, dir, or cd EXAMPLES\W64.

USB not listed, a blank screen, frozen loading indicator, or no keyboard response? Follow the boot troubleshooting guide for checks and diagnostic collection.