This is a cache of https://vccplus.brianholman.com/vcc-plus/media/. It is a snapshot of the page as it appeared on 2026-11-21T00:01:03.574+0000.
Disks, media and a setup you can return to · VCC Plus
← VCC Plus product guide

Inside VCC Plus / Media, profiles and recovery

Disks, media and a setup you can return to

A Mac file can contain an entire CoCo disk. VCC Plus lets you work both with the image and with the files inside it, while keeping guest memory, saved media and machine configuration distinct.

Three names before every save

A filename in Finder identifies a disk image. FD0 identifies the emulated drive holding it. A filename in BASIC’s directory identifies a program inside that disk. Those are three different levels of the same storage path.

File → Open Media… or a supported Finder drop supplies media to the emulator. Choosing the image is like inserting a physical disk; it does not necessarily select or execute a program inside it. Use the guest’s directory and loading instructions to find that program. The profile and connected controller determine which device answers a particular guest command.

This is why “drive zero” needs context. Disk BASIC normally starts with the first floppy. Hard Drive BASIC can use a numbered volume on a virtual hard disk. SDC-DOS has its own mounts. An OS-9 device name is another naming system. Read the active setup before deciding an image contains the wrong files.

Mount a working copy deliberately

Open Media → Floppy Disks… to manage FD0–FD3. A connected floppy controller serves those drives. Media → Virtual Hard Disks… manages HD0/HD1, with its own controller. Their rows identify media, protection and saving state.

Write protection preserves a source you want to keep as a master. Temporary changes let the guest modify its mounted working copy without immediately writing those changes to the backing file. Use Save As… before leaving that experiment if you want to keep its result. Automatically saved writable media write guest changes back to the selected Mac file.

External-change detection helps prevent one program from silently overwriting another program’s version of the same image. If a backing file changed or a volume disconnected, preserve the emulator’s current copy under another name or restore access and retry as appropriate. An unsaved-change status is a reason to inspect, not an invitation to discard.

A native editor for the files inside a disk

Choose Edit… beside a mounted floppy or hard disk to open Disk Image Editor. The machine pauses and remains locked while the current mounted image is being edited. This prevents the guest and the native editor from changing the same filesystem independently.

You can also choose Open Disk Image… to inspect an unmounted image without inserting it or disturbing the running CoCo. If that file is already mounted, including through an alias, the mounted-media safeguards still apply. An image assigned through another device or an SD card folder must be unassigned before standalone editing.

The file table presents names, sizes, types and filesystem information. Import ordinary Mac files by dragging them into the table; drag selected regular files to a Finder folder to export copies. Toolbar actions also import, export, rename and delete entries. Undo and Redo work in the private editing copy.

Disk BASIC and OS-9 have different file models. OS-9 adds folders, attributes, modification information and ownership. Open the intended OS-9 folder before importing or exporting. Its File Information sheet edits owner/public permissions, single access and group/user ownership. Saving that sheet updates the working copy; committing the disk remains a separate action.

Move within a filesystem, then save the image

For OS-9 regular files, Move To… provides a keyboard-accessible folder chooser as well as drag-to-folder behavior in the table. Visit the destination, then choose Move Here. A move preserves the file’s contents, permissions and ownership. A conflicting destination name is refused rather than silently replacing another file.

The move operates inside the same image. It is not a cross-image file transfer, a folder move or a Disk BASIC directory operation. Use export and import when transferring files between separate images, and keep their format requirements in mind.

Save Edited Copy… produces a separate complete image. Save Changes… updates an unmounted writable source after checking for outside changes. For mounted media, Apply to FDn… or Apply to HDn… requires Restart and Apply so the guest cannot reuse stale filesystem state. Save guest programs before approving that restart.

Cancel or discard the private editor changes to leave the original intact. Closing the mounted editor releases its lock and leaves the CoCo paused; Run resumes it when you are ready.

Multiple volumes without losing the rest

Some raw images contain an OS-9 filesystem alongside numbered HDB-DOS disks. The editor’s Volume picker selects the filesystem you intend to inspect. A numbered volume inside HD0 is not the same as selecting HD1, and a missing or unsupported slot does not renumber the remaining disks.

Switching volumes visits the selected root while keeping private edits to the other volumes in the working copy. The space summary describes the selected filesystem. Save Edited Copy… keeps the complete image, including preserved regions and other volumes. A numbered disk overlapping declared OS-9 boot data is protected rather than casually offered for editing.

The editor supports raw images up to 512 MiB, with individual imported or exported files bounded to 16 MiB. It supports the documented Disk BASIC, OS-9 and numbered HDB-DOS layouts. It does not format, repartition, convert or repair an image, or edit encoded containers such as DMK and VDK. Supplemental floppy tracks outside ordinary Disk BASIC file space are preserved rather than counted as free room for new files.

Tape is still a useful storage lesson

Media → Cassette… accepts CAS and WAV. Play readies the transport; the guest’s tape operation controls when its motor runs. Rewind returns to the beginning. Fast CAS accelerates supported ROM loads and can be changed while stopped.

New Recording → CAS or WAV prepares an in-memory recording. Finish the guest’s save, stop the transport and Export Tape… to keep it as a Mac file. Closing the recorder window does not export the recording, stop the transport or erase it. Reopen the window to inspect what still needs saving.

This makes the distinction between a program and its storage tangible. A listing in RAM can vanish at a cold restart while an exported tape survives. The recorder’s presence beside the machine is not itself proof that the program was saved.

A profile remembers the equipment

Machine → Configuration Profiles… provides the standard Disk BASIC, Hard Drive BASIC, CoCo SDC and NitrOS-9 setups. Preview the description before Load…. Loading changes the hardware and file assignments through a restart; it is not a snapshot of all guest RAM.

Save Current As… creates a personal configuration with processor, memory, performance, display, input, cartridge layout and media references. Save as My Profile… can use the same working media as a system profile. Create Fresh Starter Media… makes separate clean copies for another experiment.

If two profiles reference the same writable disk image, later guest saves can be visible in both. A fresh profile name alone does not duplicate the disk. Similarly, exporting a profile preserves configuration and paths; take its ROMs and media files along when moving to another Mac and repair references before loading.

Pause and resume preserve the current execution point. Soft Reset retains RAM bytes while startup software decides their meaning. Cold Restart clears RAM. Profile loading changes the setup and clears guest working memory. Save the work you need before choosing among them.

Send a disk copy toward real hardware

With matching public versions installed, Send a Copy to DriveWire… sends the current floppy bytes from VCC Plus to a selected DriveWire session and DW slot. The separate DriveWire app must already have the serial session for your physical CoCo. The receiver asks for permission for that connection and preserves displaced disk bytes in its recovery area.

The sent copy includes current in-memory disk changes. It does not pause or restart VCC Plus, change the source saving mode or make the two copies permanently synchronized. The receiving physical CoCo should return to BASIC or reset before using replaced media so it does not keep stale disk information.

That path connects a virtual development session with a physical machine while preserving the distinction between them. See the DriveWire overview and hardware guide for the devices on either side.

Your next discovery

Choose the next part of your workbench.

Explore the machine, the development tools, and the books that connect them.

Back to the product guide
A closer look

Open original