**>>  RESQ v1.7 <<**

RESQ saves buffered text, left in your computer's RAM before it was
written to disk.  If you've ever lost text due to a WordStar "disk
full" glitch, or forgotten to save that text file you just downloaded,
or frozen your console while testing a new program, or given the wrong
answer to "Abandon current version?", you can use RESQ.  Version 1.7
has a variety of changes in its algorithm which make it easier to use
and more accurate than the earlier released version, RESQ15.

                                RESQ

     *>  dynamically finds the limits of computer memory (the TPA)
     *>  hunts between those limits for a text phrase you supply
     *>  shows you the text in the area of the new-found phrase
     *>  asks "Is this your file?"
     *>  if you agree, finds the beginning of the text
     *>  shows and saves the text in RES.Q on your logged drive
     *>  closes the rescued file when you hit any key, or
     *>  when it finds the end-of-file character (^Z)

RESQ searches its own version of RAM with all high bits reset. Thus it
finds text made by WordStar as easily as ASCII text. It is unecessary
for you to remember the text which begins your semi-lost file. Just
give RESQ a phrase of up to 55 characters anywhere in the text, and it
will usually be able to get back to the head of the text before
beginning to save. If not, try another phrase which may come earlier
in the file. Occasionally, with simple phrases, there will be another
copy in RAM which is not in your file.  If what RESQ shows you (when
it asks: Is this your file?) is junk, or an accidental match to your
phrase, just answer "No" and RESQ will continue to hunt.  

Search phrases should be entered exactly as they occur; capitalization
and line breaks matter.  On the other hand, a single word is likely to
be unique in RAM, so a single well-chosen word will usually guide the
search successfully.

If you wish to stop a phrase search, type ^S while search addresses are
rolling, then type ^C to exit to CP/M.

RESQ works for any program which buffers regular text above the point
where RESQ itself leaves off, at about 2960h. For example, RESQ finds
text left in RAM by WordStar 2.26, WordStar 3.0, WordStar 3.3, Mex,
and the Turbo Pascal editor equally well. The search is unaffected if
you must reset (cold boot) in order to revive your console before
using RESQ to find your text.

RESQ cannot recover all text.  Some programs which handle text do not
store it in RAM, intact in a buffer, and in these cases, RESQ will
sign off, reporting the range of addresses searched unsucessfully. 
Another occasional cause of wierd results is that some programs (eg,
VDO and VDE) buffer their text in an encoded form which differs from
the onscreen version.  In that case, the best that RESQ can do is find
and save the encoded text by seeking a word which is not encoded.

Though it uses a different algorithm, RESQ was inspired by Chris and
Steve Rudek's MAGE, which is a Public Domain "saver" directed only at
the address of the WordStar text buffer.  RESQ was written for CP/M 2.2
and uses Z80 operations.  Because it searches from its own top to an
address which is determined from the structure of your computer's RAM
at the moment RESQ is invoked, it will probably work without adjustment
on most CP/M systems, and for most text-handling programs.

Good luck; but you'll need less luck if you have RESQ.


January, 1986                                Mike Yarus
                                             2231 16th Street
                                             Boulder, CO 80302

                                             Compuserve 73145,513