GitHub - skx/cpm-test: Testing code for running against CP/M emulators

This repository contains some simple programs to test CP/M 2.x emulators. To ease usage the tests are supplied as both Z80 assembly source files, and compiled binaries. The supplied Makefile can compile each example with the pasmo compiler if you wish to extend or rebuild them.

The following table shows the syscalls which are exercised, note that we exclude system calls relating to reading console/auxiliary input, and those that refer to tracks, sectors and cylinders. With the exception of CONOUT.Z80 all the test programs are targeted at the CP/M BDOS interface.

Limitations

Not all emulators care about user-numbers, because little real-world software seemed to use them, the same applies to the I/O byte. Similarly a lot of emulators assume there is A: and nothing else so they don't need to handle keeping a persistant "active drive".

So a failure to run these examples does not mean a particular emulator is broken; it might be that they deliberately chose not to implement specific things.

Extra Tests

This repository is supposed to handle CP/M (BDOS) code, but I added an extra test which relies upon a clock-interrupt being generated. Real systems would have had this, and so it's a good test. This is skipped in the "scoring" tables:

• TICKER.Z80 - Use interrupts to output a message.

I'd be happy to accept additional "extra" tests, as long as they're related to CP/M on a Z80 system.

"Portable" Tests

To allow testing to be carried out on alternate implementations of CP/M, such as source-based ports, there is a simple unified test-program written in C:

• COMPLETE.C - Standalone test of "everything", to be compiled with Aztec's C compiler.
  • Binary included for ease of use.

This compiles with the Aztec C compiler.

Usage

Using the supplied Makefile each of the tests can be executed in turn via:

This will default to running them with my own emulator, cpmulator, by executing cpmulator -input=stty $BINARY. If you want to run the tests with another driver set DRIVER when you execute make - the expectation is that this will be a complete command-line to which the name of a binary will be added, for example:

• David Lee's ntvcm:
  • make test DRIVER=ntvcm
  • Which then executes ntvcm $BINARY.
• Iván Izaguirre's iz-cpm:
  • make test DRIVER=iz-cpm
  • Which then executes iz-cpm $BINARY.

You might need to make more effort for other emulators, as some emulators insist the name of the binary to execute is specified without the .COM suffix - just like the CP/M CCP. An example of that is cpm.

Test Results

Tests will change over time, and of course emulators might get updated to add/remove/alter their BIOS and BDOS implementations so these tests are just a point in time record.

That said you can run the tests yourself to receive current results.

• Run ./setup.sh to clone each emulator from source.
  • If the repository is already present it will be updated via git pull.
  • You'll need a rust compiler, a golang toolchain, and a C and C++ compiler to compile all the emulators.
• Run ./run.sh to output a markdown table of results.

Test Results 28/10/2026

Failures for cpm

===== AWRITE.COM =====

A>

A>

Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0050  HL=d659  SP=d471
Stack =	 107 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0041  HL=d659  SP=d471
Stack =	 10e db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0053  HL=d659  SP=d471
Stack =	 115 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0053  HL=d659  SP=d471
Stack =	 11c db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0045  HL=d659  SP=d471
Stack =	 123 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=0044  HL=d659  SP=d471
Stack =	 12a db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=002e  HL=d659  SP=d471
Stack =	 131 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=000a  HL=d659  SP=d471
Stack =	 138 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 4:
AF=0044	 BC=0004  DE=000d  HL=d659  SP=d471
Stack =	 13f db69 d588 4f43  14d 2424 2024 2020

===== DRIVE.COM =====

A>
FAILED.

A>
===== LOGVEC.COM =====

A>
FAILED.

A>
===== RO1.COM =====

A>
FAILED.

A>

Unrecognized BDOS-Function 28:
AF=0044	 BC=001c  DE=0001  HL=0000  SP=d471
Stack =	 122 db69 d588 4f43  14d 2424 2024 2020


Unrecognized BDOS-Function 28:
AF=0044	 BC=001c  DE=0002  HL=0000  SP=d471
Stack =	 12e db69 d588 4f43  14d 2424 2024 2020

===== USERNUM.COM =====

A>
FAILED.

A>

Failures for iz-cpm

===== WRAP1.COM =====

thread 'main' panicked at src/fcb.rs:78:26:
attempt to add with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
===== WRAP2.COM =====

thread 'main' panicked at src/bdos_environment.rs:102:43:
attempt to add with overflow
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Failures for ntvcm

===== DRIVE.COM =====
FAILED.
===== IOPORT.COM =====
FAILED.
===== LOGVEC.COM =====
FAILED.
===== RO1.COM =====
FAILED.
===== USERNUM.COM =====
FAILED.

Failures for tnylpo

===== AWRITE.COM =====
===== DRIVE.COM =====
tnylpo: access to invalid/unconfigured disk
===== LOGVEC.COM =====
FAILED.
===== READWRITE.COM =====
FAILED.
===== WRAP1.COM =====
tnylpo: invalid argument in BDOS call
===== WRAP2.COM =====
tnylpo: invalid argument in BDOS call