If a disk is ejected or Merceq closes

When a problem occurs during a transfer, the aim is to continue without losing completed files again and to avoid presenting an unfinished file as complete.

• If a disk is ejected: The relevant job may wait. If the same disk is reconnected while the app is open, the job may continue; another disk with the same name won’t be accepted by mistake as the continuation disk.
• If Merceq closes or reopens: A prompt to resume the saved job appears. The task isn’t expected to continue on its own while the app is closed.
• If the task is interrupted partway through a file: The unfinished individual file is copied from the beginning; it doesn’t resume from the byte where it stopped. Files completed earlier and recorded may not need to be copied again.
• If temporary files remain: Merceq removes them on a retry or through its cleanup mechanism. Temporary remnants may remain on disk immediately after an interruption; these aren’t verified final copies.

These behaviours are documented for the Import, Copy to disk first, Copy to disk, then import, and Export job logs. Quick copy uses the same file verification engine, but doesn’t have a separate job log, ASC MHL, or resume feature for this task.

Limit: The code contains these safeguards and related tests, but the results of some hardware tests, such as a real power failure, haven’t been reported yet. No software can give an absolute guarantee in the event of sudden disk failure or physical data loss.