BMCoCo-Pi 0.1.0rc3 · Linux console and model downloads; Windows planned.

Profiles, presets and media

Prepared presets

The engineering builder has five baseline presets and two additional MOOH presets when the owner supplies matching firmware/virtual SD. These have passed native load/validation/Apply tests; that is not full Pi hardware acceptance or a released downloadable preset pack. A kernel update alone does not install the extra files on an existing card.

Profile filename	Configuration
`coco1-basic.cfg`	CoCo1 BASIC, 16K base RAM
`coco2-basic.cfg`	CoCo2 Disk BASIC, 64K base RAM
`coco3-basic.cfg`	CoCo3 Disk BASIC, 512K base RAM
`mc10-mcx128.cfg`	MC-10, 20K base RAM plus separate MCX128 expansion
`coco2-mpi-rsdos.cfg`	CoCo2, MPI with RS-DOS in physical slot 4
`coco2-mooh.cfg`	CoCo2, standalone MOOH, read-only virtual SD
`coco2-mpi-mooh-rsdos.cfg`	CoCo2, MOOH slot 1 / RS-DOS slot 4, initial slot 1

Profiles live in bmcoco/profiles/. Apply one from Profiles & startup or the OSD saved-profile browser, review it, and confirm replacement/reset. It does not automatically become the next startup selection. presets.json describes the catalog; it is not a guest configuration to Apply.

The optional builder can also create GMC, floppy-in-drive-0 and stopped-input- cassette presets when suitable media are supplied. Those are not automatically part of the seven-profile engineering bundle. A preset referencing missing media must not be offered as ready to run.

Where files belong on the card

SD-relative directory	Content
`bmcoco/roms/`	Required system/DOS/MCX128 ROMs
`bmcoco/carts/coco/`	CoCo cartridge ROM software, including supplied GMC/MOOH firmware
`bmcoco/carts/mc10/`	Supported MC-10 cartridge software
`bmcoco/disks/coco/`	CoCo floppy images
`bmcoco/cassettes/coco/`	CoCo raw cassette images
`bmcoco/cassettes/mc10/`	MC-10 raw cassette images
`bmcoco/images/mooh/`	MOOH virtual SD images
`bmcoco/software/coco/`, `bmcoco/software/mc10/`	Other program files; storage alone does not provide a loader
`bmcoco/profiles/`	Saved configuration and independent host settings

Uploading a file does not attach or execute it. In SD files, select the proper folder, upload and wait for verified completion. Then select that Pi-resident file from the appropriate Media controls and review Apply. Back up writable images first. The browser does not expose boot files as an ordinary media folder. Do not rename/delete files still referenced by profiles.

Current format boundaries

Local CoCo floppy support uses standard raw 161280-byte images. Other sizes or containers are not implied by the .dsk extension. MC-10 has no floppy FDC binding.
Tape input supports nonempty raw .cas / .c10 up to 1MiB in the current adapter. WAV/K7 and CUE timing containers need separate decoders and are not accepted. Attaching/playing a tape does not automatically type CLOAD.
MC-10 tape playback starts stopped. Enter the appropriate guest load command, use the live tape Play control, then resume. CoCo tape relay behavior differs.
.zip, .7z and .rar software archives are not mounted media. Extract a supported file first; automatic online-library extraction is not implemented.
A generic cartridge, GMC and MOOH are different types. Use the supported type and correct image rather than renaming arbitrary files.

Expansion RAM is not motherboard RAM

MC-10 + MCX128 keeps 20K base RAM in the baseline preset, with a separate 128K cartridge expansion. CoCo2 + MOOH keeps 64K base RAM with separate 512K MOOH expansion RAM. Do not change the base RAM dropdown to the expansion's capacity. MOOH needs compatible sdboot firmware and an existing virtual SD image; the engineering presets default to write protected. Its virtual SD is a file on the Pi's physical card, not permission to access raw card sectors.

Only one MOOH is supported; use Local SD. Standalone MOOH has no floppy FDC; use MPI with RS-DOS when both are needed. The engineering owner image targets CoCo1/2; do not infer CoCo3 OS compatibility. Never ship that private image as starter content without separately reviewed permission and provenance.

Starter software and the Archive

An original BASIC example is available to type now. The Color Computer Archive is an authorized source to investigate for optional starter content, not a blanket declaration that every hosted title may be redistributed. Each proposed item needs source, author/permission, checksum, machine/format compatibility and test records. No Archive software is bundled or downloaded by these docs.

A built-in Browse online library feature is not available. Use the existing PC-upload picker for supported files. Until implemented, download suitable owner-authorized media on the PC, extract it, upload through SD files, then attach through Media.

Guide edition: November 2, 2026.