Docs / Safe Mode
| Level | Blocks | Use it when |
|---|---|---|
| Off | Nothing | Day-to-day editing. |
| Images | Writes inside opened CBM disk images | You're browsing a curated D64 collection and don't want to accidentally save into them. |
| C64U | Writes to the Ultimate | Demo'ing the device, presenting at a workshop, or browsing a friend's setup. |
| Images + C64U | Both of the above | Strong combination for read-only sessions. |
| All | Also blocks writes to the local PC filesystem | Looking only - no edits anywhere. Useful when handing the keyboard to someone else. |
What "blocked" looks like
Operations that would write are stopped before any change is made, and the app tells you Safe Mode blocked them. The source stays untouched and the destination is unchanged - there is no half-applied state.
Safety nets that are always on
Even with Safe Mode off, Retro Commander 1.0 guards your disks: Ctrl+Z undoes up to 64 steps, saves write the whole image or nothing, a disk changed outside the app (by an emulator, say) is reloaded instead of overwritten, and a copy that won't fit is stopped before a byte is written. More in the feature tour.
What's not Safe Mode's job
Safe Mode does not prevent destructive operations on the C64 itself - for instance, a PRG you launch can still trash the device's RAM or write to a mounted disk via the Ultimate's drive emulation. It only governs the host (your PC) initiating writes through this app.