********************************************************************

	           sourcesaver  1.0  doc file

             coded by chrome of exit usa  march 1990

  released europe : december 1990 at the theatre/network copyparty
********************************************************************

about the utility

most ordinary, mortal coders have at one time or another crashed
their computer without saving their sourcecode first.
sourcesaver is a utility that will relocate your seka sources in ram.
it scans through memory, and if it finds a source, it will either
display the source, save the source or continue searching.

instructions

the important thing about sourcesaver is something called the
"id-line".  this is the first line of your source. when you begin
coding a demo, game, utility or whatever, reserve line 1 for
sourcesaver. enter a semicolon, followed by 6 - six - letters.
these letters are you id code. choose any id code you'd like;
 it could be your pseudoname, your group, your favorite
pizza, etc.  all of my sources start like this:

1 ;chrome
2
3 ;*** name of program ***
4 
etc ....

make sure beginning with an id code becomes a habit.
if something goes wrong and the amiga resets, all you need to do is
run sourcesaver. (keep it on your workdisk ... it's less than 5k)
now enter your id, and hopefully your source is undamaged somewhere
in ram.
sourcesaver will give you a hint as to the status of the source.
if sourcesaver finds codes in the source that do not normally occur
in a sourcefile, you will be warned that the source may be damaged.
if everything seems okay to sourcesaver, it will tell you this.
however : the source may still be damaged !!! if, for instance, a
large portion of the source is overwritten with "a"s, then
sourcesaver will assume this is data or labels and ignore it.

important note:	when you're working with seka, parts of your source
		are located elsewhere in ram (when you copy blocks
		for instance.)  sourcesaver will also find these
		blocks (provided they contain the id code, of course.)
		to make sure you've found your source, and to certify
		that it's undamaged, there's a display source option.
		use it !

oh... the id code does   n o t   include the semicolon, i.e. the code
i would enter in the example above would be
chrome   (not ;chrome)

note: you can enter the id as either lower case or upper case, or a
combination of these. sourcesaver checks both.


not having a 1mb expansion, i do not know whether the fast-mem scan
option works or not. i read somewhere that fast-mem uses memory
locations $80,000 to $ff,fff   -   so that's the block the fast-mem
option scans. if you're a 1mb user, it would be nice if you'd let me
know whether the routine works or not !


my (chrome's) address is:


torbjørn norbye
skogveien 6
n-2500 tynset
norway

this address changes july 1991  -> i'm going to states to go to college.

nb! no swapping !
if you would like to swap with exit usa,
write to comic:
		scott meeker
		1236 dry creek drive
		derby, ks 67037
		usa
(i think his address too changes next year - he's a senior now.)