Files and recovery
Close
Drive to view or edit
A:
B:
I have saved and exited
the guest program. Unsaved RAM cannot be recovered.
Enter disk management
Cancel changes
Apply and restart
Guest stuck or disk will not boot?
Recovery starts from the last saved disk without saving the running
guest. Download its latest checkpoint first if you need to keep it.
Applying a replacement preserves the saved disk as a backup, but
discards guest RAM and any changes not saved in browser storage.
I accept losing
unsaved guest state when I apply a replacement.
Recover from saved disk
Files on the committed disk (user 0)
Stage file imports
Use CP/M 8.3 filenames. Empty imports and read-only replacements are
rejected. A batch is applied in full or not at all. Downloads retain
128-byte record padding.
Development tools
Nucleus source project
Edit the separate source files, save and exit, then prepare their
single-file build input here. Apply and restart before running
NUC GAME.NU, then GAME. This is host-assisted
packaging; the released CP/M compiler still reads one input file.
Project file
Stage adventure starter
Prepare build
Preparation stages the generated source and its source map together.
Source order comes from the project file; import comments are not
resolved.
Nucleus diagnostic
Locate in saved sources
The original diagnostic is preserved. Mapping requires unchanged saved
source and build bytes; it does not describe unsaved editor text.
Disk capacity
Target two-MiB drive slots
Stage drive configuration
Stage blank selected drive
Stage ejection of selected drive
Choose 1–16 slots, usually 2 or 4. Empty slots remain configured and
reserve the same guest memory. A must be inserted to boot. Applying a
configuration replaces A's resident system, preserves existing two-MiB
filesystem bytes, backs up all preceding media and reboots. Historical
files are migrated only if the complete retained contents fit.
Stage upgrade of drive A to 8 MiB
Upgrade a legacy disk while preserving files in all user areas. Apply or
cancel other pending changes first. Applying the upgrade replaces the
resident system, restarts CP/M and backs up the complete old disk. This
profile supports drive A only; additional drives are not enabled.
Stage eight MiB A/B system
Stage blank B
Stage removal of B
A/B explicitly replaces A's resident system and preserves its files. B
can then be a new blank data disk or an attached eight MiB image.
Applying any change backs up both drives and their bootstrap together.
Selecting A or B above only changes the Files view, not the CP/M default
drive.
Whole-disk replacement
Stage disk image
Adapt external image with
this release's CCP/BDOS/BIOS (changes system bytes)
A image resident profile
Keep the current bootstrap and profile
Legacy E400, one drive
Eight MiB E400, one drive
Eight MiB E300, A/B
Leave adaptation unchecked for exact recovery. Applying a disk, files or
tools preserves the previous committed disk as a backup.
Stage complete drive-set archive
Drive-set archives include the exact bootstrap and all media slots,
including empty slots. No adaptation is applied when restoring an
archive.
Recovery backups