ZIPKEY, V2.04e  Copyright 1991 Eric Isaacson.
ZIPKEY.OVL      Copyright 1989,1990,1991,1992 Eric Isaacson.
All rights reserved.

Eric Isaacson Software
416 East University Ave.
Bloomington, IN 47401-4739
(812)339-1811

This diskette contains the ZIPKEY zipcode directory and 
keyboard enhancement program.  Please feel free to distribute 
the files by uploading them to bulletin-board systems, and by 
copying and distributing the diskette to anyone interested,
anytime on or after March 1, 1993.

You can run ZIPKEY by copying ZIPKEY.EXE and ZIPKEY.OVL into 
your current directory, and typing ZIPKEY to the MS-DOS command 
prompt. 

Note that ZIPKEY's database is updated each and every month!
When you register ZIPKEY, you get current data.  For example,
I now have the new 909 CA and 210 TX area codes, added in
November, 1992, which are not on this evaluation version because
I constrain the evaluation data to be at least 6 months old.


What's New In This Version

ZIPKEY V2.04 fixes a few minor bugs.

If you have DOS V3.0 or later, ZIPKEY V2.03 can now find its
auxiliary files in the same directory from which ZIPKEY was
invoked, so you don't need to change the current directory
to install ZIPKEY in memory or run it in non-resident mode.

With V2.00 I added telephone area codes to ZIPKEY's
database.

Now when you specify a zipcode or a city, you'll also get
the telephone area code displayed in ZIPKEY's window.  You
can "play back" the area code with the T specifier in your
hotkey or exit key configuration.

Conversely, you can type a left bracket [ followed by an
area code to ZIPKEY's window to obtain the location of the
area code.

Of course, the data itself is updated every month.  The 
evaluation data is constrained to be at least six months old, 
so that you're now getting the data provided to registered 
users six months ago. 


File Name Conventions for BBS Uploading

If you distribute files in a compressed format, using PKZIP, 
ARC, ZOO, or a similar program, I recommend that the evaluation 
ZIPKEY.EXE file and the manual ZIPKEY.DOC/ZPROG.DOC be packed 
together into one file, and the ZIPKEY.OVL file be provided as 
a second file. 

If you are a BBS sysop, with the ability to delete files on 
your BBS, you can maintain the single name ZIPKEY for the 
package. The compressed EXE-and-manual file can have the 
extension (.ZIP, .ARC, etc.) reflecting the compressing program 
used.  The OVL file can keep its name ZIPKEY.OVL. ZIPKEY.OVL 
does not need to be compressed-- it's already so compact that 
there is little or no further gain from compression. 

If you are uploading to a BBS on which you cannot delete the 
previous version, I suggest that the names contain the version 
information. The EXE-and-manual file should be named ZKxxx, 
where xxx is the ZIPKEY.EXE version number -- for example, 
ZK204.ZIP for ZIPKEY V2.04e.  The ZIPKEY.OVL file should be 
stored using a compression program (not for the compression, 
which is minimal, but so that the file will be named ZIPKEY.OVL 
again when it is extracted). The compressed OVL file should be 
named ZKmmyy, where mm is the 2-digit month and yy is the year 
of the ZIPKEY database -- for example, ZK0992.ZIP for the 
September, 1992 version of the data. 

Here are sample directory lines for ZIP files, including 
recommended comment lines: 

ZK204.ZIP        ZIPKEY zipcode dir V2.04 prog/doc,1 of 2
ZK0992.ZIP       ZIPKEY.OVL 09/92 zipcode data,    2 of 2

Note that the data file does NOT contain the program version 
number in its comment line.  I release new data files more 
often than new program versions, so that the data file is not 
married to the program version number.  People can download new 
data files even if they already have the latest program 
version.