← Emulator CREDITS Home Help ROMs Report a problem
Credits

On the shoulders of giants

CLOADM is a newcomer. Every chip here was understood first by people who spent decades documenting, emulating and preserving these machines, mostly for free. We learned from their work, we test against it, and we wouldn't exist without it.

10 REM THANK YOU
20 FOR I=1 TO 5
30 PRINT "THANK YOU, ";
40 READ N$:PRINT N$
50 NEXT
60 DATA MAMEDEV,XROAR,VCC
70 DATA ARCHIVISTS,FANS
RUN█

The emulators that came first

MAME

OUR REFERENCE
The MAME team, with Nathan Woods (CoCo and Dragon drivers) and Phill Harvey-Smith (Dragon Alpha)

Every instruction CLOADM runs is compared against MAME 0.264 in lockstep, and every display mode pixel by pixel. When we say "identical", MAME is what we are identical to.

1,016,661 instructions checked against it
mamedev.org

XRoar

BENCHMARK
Ciaran Anscomb

The Dragon and CoCo emulator the community trusts. Its ROM file names are the ones we use, and it is our second opinion for the SAM's fast-rate timing and picture.

6809.org.uk/xroar

VCC

BENCHMARK
Joseph Forgione, and the VCCE community that maintains it today

The Virtual Color Computer, a CoCo 3 emulator. Its feature set is part of what CLOADM aims to match.

github.com/VCCE/VCC

The people who kept it all

Color Computer Archive

Software, manuals, magazines and the ROM sets XRoar uses, preserved and catalogued.

colorcomputerarchive.com

The Dragon Archive

The Dragon community's wiki and software archive, built on Ross Hamilton's original Dragon Software Archive.

worldofdragon.org

DriveWire

Boisy Pitre and Aaron Wolfe: the protocol and servers that connect a CoCo to modern storage. CLOADM's planned in-browser server will follow its specification.

github.com/boisy/DriveWire

Hardware documenters

Everyone who measured, traced and wrote down how these machines behave. MAME's sources cite, among others, the "Unravelled" ROM books (trs/coco.cpp), and Graham E. Kinns's DragonDOS notes and the PC-Dragon emulator (bus/coco/dragon_fdc.cpp).

Type

Archivo by Omnibus-Type and JetBrains Mono by JetBrains, both under the SIL Open Font License and served from this site.

Documents the code cites

Motorola MC6883 (SAM) data sheetCPU speeds, fast address ranges, the fast-rate picture: js/machines/sam.js
Motorola MC6801/MC6803 data sheetInstruction timing: js/cpu/cpu6803.js
Hitachi HD6301 documentationThe double-byte write and the undefined-opcode trap: js/cpu/cpu6803.js
Darren Atkinson's notes on the CoCo's floating data busReads from unmapped addresses: js/machines/coco3.js
Published MC-10 documentationThe POLCAT and CHROUT entry points used when running without ROMs
MAME's driver sourcesMemory maps, timing and ROM checksums, wherever a comment says "as in MAME"
MAME's gime.cpp, Copyright (c) Nathan Woods, used under the BSD 3-Clause licence (notice and conditions)The CoCo 3 composite monitor's measured colours and their phase-inverted set, included in js/chips/gime.js: the only code or data of theirs that CLOADM contains

And the people who made the machines

The engineers at Motorola, Tandy, Dragon Data and Microsoft who designed the chips, the boards and the BASIC. Their datasheets are still the final word wherever MAME and the hardware disagree.

And the magazines

For the type-in listings, the PEEKs and POKEs, and the issues that crossed the world in suitcases to reach kids who had no other way to learn: The Rainbow, Hot CoCo, Color Computer Magazine, Dragon User, INPUT, Your Computer, Popular Computing Weekly, Personal Computer World, Personal Computing Today and more. And to the archivists who keep them readable: the Color Computer Archive, os9projects.com, the Centre for Computing History and Retromags.