So be careful not to run out of batteries!!!
But MuPO does a good job in saving your data. The worst case is to lose those changes you have just made to an element or group, or which you just created (it could also happen that an item you just deleted/cut will not be deleted/cut due to the crash). However, this is the worst case. If the agenda writes a file just when MuPO tells it to, nothing worse can happen.
- ...MuPO is simply running
should be no problem, at least when incremental files had already been flashed. No interaction can improve the situation.- ...writing an incremental file
the most current incremental file will be corrupt, MuPO tells you about it. Save the named file and more current incremental files (if any) to another directory so you can take a look at them (using a text-editor) and re-do changes by hand later. Delete the original files which you just copied. Start MuPO again, it should work. Now redo changes by hand.- ...moving backup files
see 1.- ...writing the master data file
master data file will be corrupt, MuPO tells you about it. See below.- deleting incremental files
no problem, unless you synchronize files after it died and before starting MuPO again. So, if your agenda crashed: don't synchronize at once, but run MuPO before.
What to do?
- Save this file to another directory, you might need it.
- Save incremental files to this directory as well.
- Copy the latest backup-file (name of master data file +'b0') to the master data file. If MuPO ran for the first time after a sync when it crashed, you can't use the incremental files with the latest backup file. Delete the original incremental files. Even in this case your changes are not really lost. They are in those backup files, but you can only take a look at them using a text-editor and re-do them by hand.