GOTECH.TXT  V1.6 10-Jun-94
==========================
This file contains some technical information about the GOLIST program.

If you are having a problem running GOLIST, please read this entire file,
as more than one problem statement may apply to your situation.


HOW TO INSTALL:
===============
If you are reading this file, you in all probability have installed GOLIST
correctly.  Just log to the directory where you have placed the GOLIST files
and type GO### at a DOS prompt.  The ### represents the issue number and is
three numbers which must be typed as numbers.  This will run the GO###.EXE
file.   Example:  Type GO170 if the file is named GO170.EXE.

GOLIST may be run on a floppy disk or on a hard disk.  GOLIST will run 
faster on your hard disk, but you may find that its speed when run on a
floppy is adequate.  


RENAMING GOLIST FILES
=====================
The GO###.EXE file (the ### is the issue number) may be renamed 
GO.EXE, GOLIST.EXE or named as any other EXE file if you like.  
GO###.OVL contains all of the routes.  The GO###.OVL file may not be 
renamed.  There are several smaller files provided (like the file 
you are reading) which you may view with a DOS file viewer or print 
for reference.


PROBLEMS, GENERAL:
==================
Please read all of the problem help discussions.  Don't stop at the 
first one that sounds remotely like your problem.  There may be more 
later!


PROBLEM: Won't display HELP or other text files
===============================================
Instead of the display you expect, you get something like:

File not found in ......(followed by some computer babble)
Hit any key to return to system

And, when you hit a key, you are dropped unceremoniously to DOS.

This means that GOLIST can't find the file you want to display.  Use 
the DOS DIR command to verify that the file you want to review is 
present.  The file you are reading now, for example, is named 
GOTECH.TXT; this is the file displayed by GODISK when you type TECH.


PROBLEM: Can't access program when data has expired
===================================================
If the expiration date of your data has passed, you are asked to 
type "Yes", which signifies that you understand the information is 
out of date.  You are also asked to type in a "Key" which will 
change each time you are asked for the "Key".  You must type the
characters exactly as shown on the line above where what you type
is displayed.  For instance, if you are asked to type Yes Key=82,
then you must type exactly those 10 characters, including the space
between "Yes" and "Key=82".  You may use all upper case or all lower
case if you like.  Once you successfully answer, GOLIST won't remind
you again for a month.

See also "USE OF GOLIST IN LOGGING PROGRAMS", below.


PROBLEM: Computer date is wrong
===============================
If your computer date is set to some date which is a L O N G time 
ago, GOLIST will complain and ask you to set the date in your 
computer.  It really doesn't like January 1, 1980, for instance, as 
a computer date, and it won't run.  Use the DOS DATE command and set 
your computer date to the current date.


PROBLEM: "GO###.OVL missing or corrupt"
=======================================
If the GO###.OVL file distributed with your GO###.EXE file ("GOLIST")
cannot be found by the program, or if it does not pass validity 
checks on program startup, you will be notified by the above error 
message and the program will terminate.  Reinstall the program 
directly from the distribution disk or file.  
***See also "Bad file name in module....." below***


PROBLEM: "Bad file name in module RDR###  at address ####:####"
         or "GO###.OVL missing or corrupt"
======================================================================
One of these error messages will display when you are using SET GOLIST
and the final backslash is omitted from the SET GOLIST statement.  
Or, you may get these error statements if you have placed a SET 
GOLIST statement into your AUTOEXEC.BAT file and forgotten about it.


PROBLEM: Incorrect Environment variable
=======================================
Most of the reported problems so far have been as a result of an 
incorrect environment variable, also called a "SET" statement.

If, perhaps at the direction of a logging program, you have 
established a GOLIST environment variable and then not utilized 
that directory for GOLIST file storage, GOLIST won't even run on
the floppy disk.  Try this:

At a DOS prompt (C:), type SET<ENTER>. If the display includes 
GOLIST=anything, that is probably your problem.  At a DOS prompt 
type SET GOLIST=<ENTER>.  Note that there are 12 keys to press in 
SET GOLIST=<ENTER>, and the only space is between SET and GOLIST.  
Now type SET<ENTER> and the GOLIST environment variable should be 
gone (until the next time you start your computer).

Log to your floppy drive and attempt to run GOLIST on your floppy.  
If it works, you need to remove the SET GOLIST statement from your 
AUTOEXEC.BAT to run GOLIST directly on the floppy.  This proves that 
GOLIST is working!

To integrate GOLIST into your logging program, follow the 
instructions implicitly which are furnished by the logging program 
company.  You may have to copy the GOLIST files to your hard disk.

If you establish a GOLIST environment variable, for instance with the
statement "SET GOLIST=C:\GOLIST\" in your autoexec.bat file, then when
you type SET<ENTER> at a DOS prompt, you should see exactly what is in
your autoexec.bat file.  If, however, you see "GOLIST=C:\G", for example,
rather than "GOLIST=C:\GOLIST\", it is likely that you have exceeded your
DOS environment space and may need to either remove some of your SET or 
PATH statements or expand your environment space by using the DOS SHELL
command.  It is beyond the scope of the GOLIST program or technical 
support for GOLIST to provide guidance in setting up your computer's
environment.  Please refer to a technical book on DOS for additional
information.


COMMAND LINE ARGUMENT:
USE OF GOLIST IN LOGGING PROGRAMS:
=========================================================
GOLIST can be executed with a "command line" argument and can be 
instructed in that argument to "redirect" its output to a file.  

GOLIST looks for an "environment variable" called "GOLIST" which, if 
present, provides the path for the TXT and OVL files supplied with 
GOLIST (The GOLIST environment variable must end with the \ 
character).  

The GOLIST file, called GO###.EXE (the ### is the issue number), may 
be renamed as required by the calling program.  Please see the 
documentation provided with the logging program for further details, 
which are beyond the scope of this tech file.  

If the expiration date of your data has passed, you must access GODISK 
via DOS and answer the "Key" request (see "data expired" problem
description, above) if you wish to temporarily extend the expiration
date.  Once you have successfully responded to the "Key" request,
the program expiration date, including the "command line" access, will
be extended a month.

To enter the program with a command line lookup argument and then 
stay in interactive mode, place a @ character in front of the
callsign.  For instance, the command line argument GO160 @FO0JO will 
look up FO0JO and stay active.


Exit with a Q instead of "Enter":
---------------------------------
If you run the program with a /Q command line argument, the keystrokes
required to exit are changed.  Example command line for GO159 is:
     GO159 /Q
If you run the program this way, instead of pressing "Enter" to exit,
you must press Q and then press "Enter".


DXBASE VERSION 2:
=================
This is ONE way to implement GOLIST with DXBase Version 2 and some 
other logging programs such as Turbolog.  This is experimental and 
may or may not work.  Proceed at your own risk.

1. Make a C:\GOLIST directory.  Place all GOLIST files in that directory.
2. Add C:\GOLIST to the DOS path statement in AUTOEXEC.BAT.
3. Add to AUTOEXEC.BAT: SET GOLIST=C:\GOLIST\
4. Rename GO###.EXE as PCDB.EXE.
5. Reboot your computer.


DXBASE VERSION 3:
=================
A user option entry is provided in the "GO file field" of "Auxiliary 
Programs".  With Version 3, you may tell DXBase what the GOLIST 
program name is.  DXBase will then access that program.  When you 
obtain newer issues of GOLIST, the GO###.EXE file will change its
name to reflect our issue number.  You may tell DXBase Version 3 
what our file name is, rather than renaming the file as is necessary 
in DXBase Version 2.  DXBase Version 3 also requires the GOLIST files
to be in a directory defined with an environment variable and on the
DOS path statement, similar to the example below.  Refer to DXBase
documentation for details.

1. Make a C:\GOLIST directory.  Place all GOLIST files in that directory.
2. Add C:\GOLIST to the DOS path statement in AUTOEXEC.BAT.
3. Add to AUTOEXEC.BAT: SET GOLIST=C:\GOLIST\


COPYRIGHT and LEGAL STUFF
=========================
This file, all GOLIST files, the programs and algorithms used are 
copyright (C) 1993-4 Electronics Enterprises, W6GO/K6HHD.  GOLIST is 
licensed for the use of one owner only.  Duplication of GOLIST for 
use by more than one user is prohibited and is a violation of our
Copyright.

GOLIST is NOT licensed for use on Packet, BBSs, Clusters, nodes, or 
any use other than by one user at one computer. 

The data contained in GOLIST is only licensed for access by the 
GOLIST EXE file provided by Electronics Enterprises, W6GO/K6HHD. 
That file is provided as GO###.EXE where ### is the issue number.  
GO###.EXE is copyrighted by us even if renamed by the user.

Do you want us to continue to produce the W6GO/K6HHD QSL Manager 
List?  Then please do not steal from us by duplicating and/or 
distributing this product without our express written authorization.


BETA TESTERS:
============
Thanks to AA4LU, AA6WJ, AA7EN, K4CEF, K6HHD, K6LLK, K6PBT, KI3V, 
KJ6NN, N6IXX, N6IYS, N6PYI, and W8ZF for their hard work and helpful 
suggestions.  

AA7EN found that the first version of GOLIST triggered the Norton 
Virus scanner, even though there is no virus.  Thankfully he 
identified that problem, because I sure didn't want to get in an 
argument with Peter Norton, even though there is not and has never 
been a "virus" in any W6GO/K6HHD product!


PC-GO and PCDB:
===============
GOLIST completely replaces PC-GO.  If you own PC-GO and PCDB, you may
delete them from your computer if you wish.  If you desire to use PCDB 
to acess PacketCluster format databases, you may continue to do so.  
PCDB can also be used to maintain your own personal database through
UPDATE/QSLNEW.  See the PCDB manual and review the SYSOP.DAT file for
assistance in editing SYSOP.DAT to delete the QSL database files.


CHANGES:
========
V1.1: "Key" password now required only once a month if past expiration
      date rather than required every time the program is run. This 
      allows command-line access (used by logging programs) after the
      expiration date.  Command line access was shut off after expiration
      prior to issue 158 because the user query caused computer lockup.

V1.2: Added conditional "Q" to quit capability, /Q command line argument.
V1.3: Added @ prefix for callsigns for command line "stay active" mode.
V1.4: Added missing backslash environment variable problem discussion.
V1.4a:Minor editing, copyright date update.
V1.5: Minor editing, more discussion of environment variable
V1.6: More discussion of environment variable
