Guest & machine
Navigation keeps your drafts. Only a confirmed Apply changes the guest.
Guest controls
Reading active guest…
Machine configuration
Apply starts the selected machine with local SD storage and the selected MC-10 expansion. Other attached media and MPI are cleared; unsaved guest work is lost. MCX128 adds separate cartridge RAM, not base RAM. Use Profiles & startup to save/select startup, and Media for attachments and MPI/MOOH.
Cartridge attract mode
Manually rotate compatible game carts using the current CoCo machine. No idle or startup activation. Stop or physical keyboard/controller input keeps the current game running. The display stays awake during rotation.
Create the folder and add your own .rom/.ccc/.bin games in SD files first. One flat folder, up to 128 carts / 512 entries; no disks, tapes or system firmware. Use a separate folder for each machine or cartridge type. Start resets the guest and clears other media; saved profiles and startup stay unchanged.
Saved profiles
Save copies the live guest configuration, media paths and controller mappings, not an unapplied form draft or running program memory. It does not reset the guest or select startup. Existing files require confirmation and retain a verified backup.
Refresh to browse profiles and read the separate startup selection.
USB controllers
Wired USB gamepads/joysticks recognized by Circle only; no Bluetooth, rumble or generic-hat mapping. Device numbers follow USB discovery, not permanent identities. Axes/buttons are 0-based. Auto buttons: A/B/Start for known pads, raw 0/1/9 for generic HID. Start (or Guide on known pads) opens/resumes the OSD; stick/D-pad navigates, fire selects, fire 2 goes back. Release all controls after connection, Apply, reset or menu transitions.
Controller Apply changes live mappings without resetting the guest or changing media. Save a profile separately to persist them. Fire 2 is guest-visible only on CoCo 3. MC-10 supports controller OSD navigation only; text fields require a keyboard.
Remote storage backend
HTTP/instance are used only by pyDriveWire. Becker/FujiNet disks are service-managed: eject local floppy selections first. Existing machine, video, controller, cartridge/MPI and cassette settings are retained and validated; incompatible combinations reject without silently clearing media. MC-10 remote/EmCee transport is not implemented. Services run on another host, not inside the Pi.
Apply resets the guest and reloads retained media from SD; unsaved program/RAM disk changes are lost. Backend and service reachability are separate: a configured Becker/FujiNet endpoint is not a successful service connection. Saved/startup profiles remain unchanged.
SD media
Attach or eject software already on the Pi SD card. Applying media resets the guest and reloads retained attachments from SD; unsaved program and RAM disk changes are lost. Other machine settings are retained. Startup profiles are unchanged.
Floppy disks
Multi-Pak / MOOH configuration
MOOH adds separate 512K banked cartridge RAM; leave base RAM at the machine setting. Select its sdboot ROM and an existing virtual SD image. Use a copy: writable images retain guest changes. Only one MOOH is supported. RS-DOS uses the configured Disk BASIC ROM.
Apply resets the guest and reloads attachments from SD. Unsaved program and RAM-floppy changes are lost; unrelated settings/media are retained when editing MPI/MOOH. Loading a preset replaces its configuration. The startup profile is unchanged.
File locations on Pi SD
These are folders, not guest configuration. Uploading or selecting a folder does not attach media. Use the Media page to mount a disk, tape or cartridge.
SD library
| Name | Size | Actions |
|---|
Waiting for the Pi…
Pause emulation on Guest & machine before large transfers or full-file verification. Heavy SD work can interrupt guest audio and timing.
Add files to this folder
Drop files here, or choose them from your computer.
Destination: bmcoco
Uploads are fully hash-verified. Existing files require confirmation and retain a backup. Storing a file does not mount it or start guest software.
Guest screenshot
Capture the guest display only, not the OSD or whole TV/HDMI screen. Preview and PNG use the same pixel-aspect correction as the Pi display. Captures stay in RAM; Download saves a PNG on your computer, not the Pi SD card.
Capture a guest frame, or select an image from your computer to view here.
Display / screen blanking
Off by default. A black picture is sent to HDMI; this does not turn off the TV or HDMI signal. The guest, audio and network keep running. The first keyboard/controller action only wakes the display—release it before continuing. Guest screenshots still capture the guest, not the blanked HDMI picture.
Apply saves this Pi-wide preference on SD for future boots, separately from guest profiles. No guest reset or kernel update is needed to change it.
Kernel update
Reading running kernel build…
Choose the correct BMCoCo-Pi kernel image for this board. Upload and verify first; a separate reviewed Apply installs it and preserves the previous kernel as rollback. No automatic reboot.
Kernel verified on SD. Use Reboot Pi or reboot locally when ready. The new kernel is not running until reboot. Automatic-network builds reconnect after guest startup; wait, then reload this page.