MMCE Backup History

Versioned local backup protects an active MMCE card without creating an identical copy after every return.

Local history

The workflow exports an MMCE card image into WLE-MMCE-Backups, verifies it against the source, and publishes the completed snapshot through a same-folder rename. During export it has a .PART suffix, so interrupted writes cannot be mistaken for completed .mcd or .ps2 history or uploaded to Drive. Retention runs only after publication and never removes previous snapshots on a failed export, comparison, or rename. The retention setting can keep all history or prune older versions.

Skip unchanged cards

Before adding another history entry, Launchstation can compare the active card with the latest backup. If it is unchanged, the UI reports that no duplicate history was saved.

Verification matters

A copy is not treated as a successful backup merely because file creation returned. The backup path verifies the output before reporting success or allowing the next automatic step.

Non-destructive local recovery

In Settings > Storage & devices > MMCE backups, choose Recover saved card image... to browse your configured local WLE-MMCE-Backups history and select a complete .mcd or .ps2 snapshot. You can also select the snapshot in the File Browser and choose Recover as new .mcd....

To back up a specific MMCE card, highlight its .mcd under mmce0:/MemoryCards or mmce1:/MemoryCards and select Back up selected MMCE card to history.... Both routes use verified copies and leave the original emulated card untouched.

From the File Browser, highlight a complete .mcd or PCSX2 .ps2 history snapshot, open the options menu and choose Recover as new .mcd.... Launchstation validates the card image first, asks you to select a USB/HDD folder, writes to a distinct .PART file, reads it back and verifies the copy, then publishes a new RECOVER-###.mcd image. Existing files and MMCE cards are not replaced or activated. Choose the separate recovery file for further inspection or manual installation after verification. To store a verified snapshot on the adapter using the unchanged sd2psXtd firmware, highlight a local USB/HDD .mcd or .ps2 file and choose Store NEW snapshot on MMCE..., then choose the adapter slot. Launchstation creates and verifies a new mmceN:/WLE-Recovered/RECOVER-###.mcd with staged .PART output. If adapter rename fails but the stage remains and the final name is free, a separate read-back-verified copy is used instead. This separate holding folder is not an active/selected card directory; the adapter does not automatically mount it. Direct replacement or activation of an emulated card remains disabled. No firmware fork, update or custom protocol is required for the new-file storage workflow. To create a new selectable card rather than a holding-area snapshot, select the completed local .mcd/.ps2 or a WLE-Recovered image in File Browser and choose Install as NEW selectable MMCE card.... Launchstation selects an entirely unused MemoryCards/PS2/CardN directory, verifies its new CardN-1.mcd image, and leaves adapter card selection unchanged. It never replaces an existing numbered, BootCard or GameID image. If rename is unsupported, the verified-copy fallback still cannot guarantee atomic power-loss publication; never select a failed/interrupted installation until that new directory has been inspected.

IGR integration

When Automatic IGR backup is enabled, an OPL return through WLE-IGR can capture a changed card before continuing. This keeps the safety-critical local copy independent of network/cloud availability.

Browse and recover remote backup history

In Tools > Google Drive backups > Browse cloud history..., explore the app-created WLE-MMCE-Backups folder on Google Drive. The paged browser lists folders and available .mcd/.ps2 snapshots. Selecting one with an uploaded SHA-256 allows verified download to a NEW RECOVER-CLOUD-###.mcd on USB/HDD. Launchstation checks the complete downloaded SHA-256, validates the card image, converts PCSX2 snapshots where needed and publishes only a verified staged recovery. Google Drive history and emulated MMCE cards are never modified; direct replacement of an MMCE card remains disabled.

Cloud is additive

Optional Google Drive synchronization is performed after the verified local backup. A cloud failure does not erase or invalidate the local history entry. See Native Google Drive Cloud Backup.

Sync all cards

Sync all cards scans both MMCE units, creates history only for changed cards, and summarizes new/unchanged/failed cards. If Google Drive is linked, pending local history is uploaded afterward.

Automatic sync modes

The single Automatic sync control replaces two separate toggles with three clear modes: Off, Local backup, and Local + Google Drive. Cloud mode requires a linked account.

IGR helper control

The MMCE backup page now exposes the existing verified WLE-IGR installer/update/remove flow directly, alongside the after-IGR destination.

Recovery safety summary

Remote entries without the expected saved digest may be inspected but are not eligible for the verified download workflow. Incomplete .PART files never count as completed backups. For step-by-step recovery, see the wiki index and recovery guide.