autosave or crash-proofness
Posted: Tue Jun 03, 2003 10:56 am
it's no use to expect computers not to crash.
we're in the microsoft age, and macos isn't very much better.
i was fumbling around with quite a nice live set when the system
freezed on me. after reboot all work was gone. could i have done
anything to protect myself from this?
cooledit has this absolutely fabolous capacity of restoring
the complete state from harddisk, but even something ugly
as autosave every two minutes would do.
i mean this is ugly in whatever way and should not happen
in a live performance. but what's the use of should if it does?
i am sure the problem is not with live, but still.. where's the
autosave function?
or alternatively.. can i use live on unix natively?
we're in the microsoft age, and macos isn't very much better.
i was fumbling around with quite a nice live set when the system
freezed on me. after reboot all work was gone. could i have done
anything to protect myself from this?
cooledit has this absolutely fabolous capacity of restoring
the complete state from harddisk, but even something ugly
as autosave every two minutes would do.
i mean this is ugly in whatever way and should not happen
in a live performance. but what's the use of should if it does?
i am sure the problem is not with live, but still.. where's the
autosave function?
or alternatively.. can i use live on unix natively?