sourcedoc: gzzEMERG-D1 === 13.01.13

hide references

gzzEMERG-D1 === 13.01.13

EMERGENCIES IN GZZ—WHAT TO DO

1. You can undo any number of steps with U (Undo).

UNLESS YOUR DATA HAS BEEN CORRUPTED, in which case you must start over or go back to a previous save.

2. STARTING OVER WITH A NEW DATASET.

Quit with Q.

“ZigZag-Gzz.jar” is the gzz program. Leave that alone. “Adam'sRoyals” is the data package. DELETE IT.

Copy “Backup of Adam'sRoyals”. This is an uncorruped data set. Change its name to “Adam’s Royals”.

Begin the program again.

3. MAKING BACKUP SAVES.

Close the program.

Copy “Adams Royals” and give it a new name—for instance, 1 Adam’s Royals

And do this from time to time, so you’ll have 2 Adam’s Royals

3 Adam’s Royals

THEN, IF YOUR FILE BECOMES CORRUPT, go back to the previous version, throwing away the current “Adam’s Royals” and taking the number off the last save.

4. THE SIGN OF DOOM

If you see the words “RASTER ERROR” -- STOP!

Your data is corrupted. This was intended as a specific warning but is the sign that you’re dead. (It may be possible to go on a little further, but the data is corrupted, so there’s no point.)

Go back to the previous save.

Unfortunately there is no way to be sure it was not corrupted earlier.

=30=

raw

span:

References

There are no documents that refer to this sourcedoc.