← All spotlightsPrograms / Features

Spotlight › CP/M

RunCPM on os8088

CP/M 2.2 services and an assembly Z80 core, with host directories as drives and user areas.

RunCPM
An os8088 window filling the top of the screen with a CP/M boot banner in it, ending in an A greater-than prompt with a block cursor.
CP/M console.
Guest CPU
Zilog Z80
C source
4,679 lines
Target CPU
4.77 MHz 8088

01 / Implementation and provenance

Implementation and provenance

The port follows Marcelo Dantas's RunCPM behaviour, adapted to the os8088 C toolchain and package API. Its Z80 execution core is 8086 assembly. The upstream command processor and configured software set are fetched at pinned versions when the disk is built.

This is CP/M-80-style software execution through a Z80 model, not CP/M-86 native execution. The supported OS interface is CP/M 2.2; it does not imply a full hardware model for each original CP/M machine.

02 / CP/M captures

CP/M captures

DIR
The CP/M window showing the output of a DIR command: four columns of eight-character file names with three-letter extensions, filling most of the terminal.
Configured master-disk software set.
MBASIC
Microsoft BASIC-80 running in the CP/M window, with a three-line program typed in and its output: the numbers one to eight and their squares.
Unmodified Z80 BASIC executable.
The RunCPM disk
The os8088 file window open on drive B, listing 1STREAD.ME, a folder called A, CCP-DR.60K at 2,048 bytes, LICENSE, RUNCPM.O88 at 39,412 bytes and RUNCPM.OVL at 7,389 bytes.
Package, command processor and drive folder.
About
A small About box over the CP/M window naming RunCPM, its version, its author Marcelo Dantas, what this port is, and the MIT licence.
Port attribution.

03 / CPU and scheduling

CPU and scheduling

The core holds guest registers in host registers and allocates guest 64KB memory separately from the package. ZEXDOC's 67 groups pass both in the package and in a standalone harness.

Execution is divided into cooperative slices; waiting for console input suspends further work until an input event. The terminal keeps a previous-state buffer so echo and scrolling update changed cells instead of repainting 2,000 characters.

04 / Drive mapping

Drive mapping

Drive A, user 0 maps to A/0 on the host FAT volume. Other drives and user areas follow the same layout. Copy a compatible CP/M .COM there from the host to make it available. No CP/M disk-image geometry is emulated.

The shipped software manifest and omitted-file list define the contents; those bytes are not copied into the website source.

05 / Port limits

Port limits

Files are limited to 65,535 bytes with eight simultaneously open. The terminal handles the implemented cursor/erase controls and reverse video; colour, bold and underline are not rendered.

No CP/M 3 banked memory, XMODEM, upstream hardware-I/O backends or debugger. There is no fixed-speed throttle; execution rate depends on the host. ZEXDOC validates documented CPU behaviour, not every application or undocumented hardware dependency.

06 / Run CP/M

Run CP/M

Launch RUNCPM.O88 from its dedicated image or RUNCPM folder. Keep the auxiliary package and command processor beside it. DIR, MBASIC, TE and ZEXDOC are useful checks when present in the chosen software set. Alt-F exposes the full terminal width.