"README" file for Unix/C version of "Trek Guru", by Rob Seace.


    If you make ANY changes to the code, and re-distribute that code,
PLEASE, PLEASE, PLEASE make note of those changes both here and in the
code, and increment the version...  That's really the only rule I have.
Other than that, do whatever you want to the code.  I hereby declare
the code to be Public Domain.  Feel free to make any changes necessary
to port it to any system you like (though I tried to write it with
portability in mind, using only standard functions).  Note: It would be
senseless for you to port it to DOS, though, as I already have a DOS
version of "Trek Guru" available (it came before this, and was the
inspiration for this).  And, the DOS version is FAR flashier and better
than this version.  Check "archie" for an FTP site near you that has
it (one I know of is ftp.shore.net, in /members/ras/trekguru.zip)...

    At the time this was distributed, there were only data files for
TOS, TAS, and TMS.  However, I've already programmed in TNG and DS9
compatibility for the future.  This way, when/if I finally get around
to entering that ton of data for TNG and/or DS9, I can just distribute
the new datafiles, without having to worry about changing and
re-distributing the new code, too...  In fact, if some enterprising
soul really WANTS to enter all the TNG/DS9 info, feel free. ;-)  Just,
send me copies of the data files or tell me where I can FTP them from.
(I'm ras@shore.net, on the Internet.  Phone (617) 277-8835.)  It
shouldn't be too hard to figure out my data file format (just check
my "trekguru.h" file for the structure definitions; if you are a C
programmer, you'll understand it easily enough)...



    Command Line Usage:  guru [?] [+f] [d=<dir>]

                ?         - Prints out usage summary.

                +f(ile)   - Uses file-access for all searches.  Normally,
                            the program will read all the information
                            into memory after a series selection has
                            been made, and search from memory.  However,
                            if you are short on memory, or enjoy horridly
                            slow searches, then you can use this option
                            to force the searches to be done directly
                            from the data files.  I would only recommend
                            this option as a last resort.  (Note: If you
                            have a max limitation like 64k of data, then
                            you'll likely have to use this option.  Take
                            a look at the file sizes to see how much data
                            memory you'd need.)

                d=<dir>   - Where "<dir>" is the directory that the
                            data files are in.  If they are in the
                            current directory, this is not necessary.



    If you spot any bugs, either fix them yourself (and make note of it),
or let me know about them, and I'll see what I can do...  Though, I don't
plan on really supporting this code TOO much once it's out there...  If
you enjoy this program, let me know.  If you have a DOS machine, I
recommend getting my fancier DOS version (color, mouse support, printer
output, hotkeys, etc.).  If you like that one, I ask for $10 in the
"README.DOC" file for that version.  Though, if you don't really want
to send it to me, I won't hunt you down and arrest you. ;-)  However, I
WOULDN'T mind the little bit of extra cash.  I would ask for some for
this version, but since I'm distributing the code as PD (the only thing
to do, really; I KNOW hackers would play with it, even if I demanded
that they didn't, so I might as well give my ok for it ;-)), it wouldn't
make much sense...  However, if you really WANT to send me money, feel
free; I will appreciate it... ;-)  Enjoy.

                Robert Seace
                120 Brainerd Road
                Apt. 2
                Allston, MA  02134  (USA)

                (617) 277-8835

                ras@shore.net