Gallery

Annotated interface tour: each card pairs a screenshot with a short practical caption. Click any image for a full-size view.

Quadium 4004 Workbench — main execution view with CPU, bus, and disassembler in sync

CPU and bus state

Main execution view with CPU, bus, and disassembler in sync. This is where users inspect what each instruction is doing in real time.

Quadium 4004 Workbench — QuadBasic editor with one-step transpile to Intel 4004 assembly

QuadBasic transpiler

Write a compact QuadBasic program and transpile it to Intel 4004 assembly in one step. First-time users see how readable high-level code maps to mnemonics before they edit ASM by hand.

Quadium 4004 Workbench — assembler and disassembler side by side after assemble-and-load, listing aligned with ROM

Build and ROM flow

Assemble and load turns your edited ASM into the emulated flat ROM and refreshes the disassembler in one step. The paired panes make it easy to confirm that addresses, mnemonics, and bytes match your source—or to inspect the same way after loading an external image with Load ROM.

Peripherals and outputs

Add modules such as LCD, LED bar, seven-segment displays, DIP switches, and push buttons, then map each element to emulated MCS-4 I/O with the binding editor. Save profiles so the same wiring and aliases load instantly for labs, demos, or your own boards.

Quadium 4004 Workbench — Settings with IPS presets, default preset, and historical 4004 fixed speeds

Execution speed control

The Settings view is where you set your own IPS defaults: edit each of the ten named presets, choose which one is the default when the bench opens, and restore the recommended ladder whenever you want. The same page also lists two fixed speeds that match the historic Intel 4004 (about 46 kIPS for a two-cycle instruction average and about 93 kIPS for the single-cycle ceiling—labeled like the workbench UI), alongside fully user-tunable rates and an uncapped maximum for fast runs.

Quadium 4004 Workbench — PRINT @DSK mirrored to a UTF-8 printout file on Windows with console status

Host printout to disk (@DSK)

Whatever your program prints to @DSK—strings, numeric fields, line breaks—is appended to a UTF-8 printout file on your PC while the emulated CPU runs. Choose the destination in Settings, confirm capture from the console badge, then treat the file like any other build artifact (diffs, version control, lab hand-ins). Built-in rate and size limits pause execution before a bug can flood the disk.

Need runnable source ideas? Open examples.

Prefer a longer narrative preview? Watch the cinematic trailer.