READ.ME 	     TLIB Version Control 4.12s		28 August, 1992
                      with beta-test TLIB 5.0

 (C) Copyright 1986-1992, Burton Systems Software.  All Rights Reserved.


                      ** Late program notes **


** IMPORTANT!  If you bought the Network Edition of TLIB, be sure to
   also read the READ_ME.TOO file!

** Please take a moment now to correct the TLIB user manual as described
   under "Errors in the User Manual," at around line 192 of this file.

** You've received TWO different versions of TLIB on this diskette.
   What they are, and why you got both is discussed under "Two Versions
   of TLIB," starting at around line 74 of this file.


--------------------------------------------------------------------------

Your TLIB files are compressed into several large ".LZH" files.  To use
them, you'll have to first unpack them as follows:


               How to unpack .LZH files in 3 easy steps
               ----------------------------------------

1) Boot MS-DOS or PC-DOS, or switch to the "DOS Box" of OS/2.

2) Copy LH113C.EXE onto your hard disk.  Then run it.  It will create
   the following files:

      LHARC.EXE  - The LHARC public domain compressed-archive utility
      LH113C.FOR - A small introductory documentation file
      LHARC.MAN  - The LHARC user manual

3) Use LHARC.EXE to unpack the .LZH file(s) onto your hard disk.

   First, change to the directory into which you want the unpacked
   files placed.  Then use LHARC to unpack the files.

   This command unpacks TLIB 4.12:

        LHARC E -C A:TLIB4.LZH

   To unpack the TLIB 5.0 beta, first unpack TLIB 4.12 from TLIB4.LZH,
   and then unpack the remaining TLIB 5.0 beta files from TLIB5.LZH
   (which will replace some of the files from TLIB4LZH):

        LHARC E -C A:TLIB5.LZH

   Note: a few of the TLIB 5.0 programs will be functionally unchanged
   (or nearly so) from TLIB 4.12, so to save space we've not included
   those files in the TLIB5.LZH archive: LISTBLD, TABS, DSAPPADR, DIFF3,
   DSAPPPAN, TLIBSCAN, and TLIBSMP.  Use the copies in TLIB4.LZH.

   This command unpacks the public-domain and shareware collection
   which we include as "filler material" on the distribution diskette:

        LHARC E -C A:PUBLIC.LZH

   Some of the tools in PUBLIC.LZH are *very* useful to users of TLIB.
   Don't ignore them!

   You can retrieve individual files, too.  For example, to retrieve
   the TLIB 4.12 release notes:

   	LHARC E A:TLIB4.LZH 4PXXNEWS.DOC

   If there are other .LZH files on the diskette, you can use LHARC
   to unpack them in the same way.  Look for .DOC files that will
   explain what the contents are.


--------------------------------------------------------------------------

                         Two Versions of TLIB
                         --------------------

As you probably know, TLIB 5.0 has been setting industry records for
beta-test cycle length.

The good news is: the code is now essentially finished and stable.  Well,
there are a few details that we'll be taking care of before final release.
But it is essentially finished.

The bad news is that the manual is still not yet done.

So, we've included *both* TLIB 4.12 and the TLIB 5.0 beta-test version on
this distribution diskette.

You have received the old 4.12 manual, plus a "free upgrade" certificate
which entitles you to a free upgrade to the final TLIB 5.0 release, with
user manual.

TLIB 4.12 is the the old, tried-and-true Version Control System which
has gotten so many enthusiastic magazine reviews.  Thousands of programmers
use TLIB 4.12 every day.  It is rock-solid.

TLIB 5.0 is brand new.  It has many new improvements, but it has a few
rough edges... mostly in the documentation:  TLIB 5.0 is currently
documented only by a collection of rough .DOC files which document the
differences between TLIB 4.12 and 5.0.

If you are new to the TLIB Version Control System, you should start out
using TLIB 4.12, since it has an adequate User Manual.  Trying to dive
right in with TLIB 5.0 is likely to be very frustrating unless you've
first familiarized yourself with TLIB 4.12.

One suggestion, though: don't bother with pages 59-66 of the TLIB 4.12
manual (in the chapter on "File Lists, Branching and TLIBSNAP").  This
is the section which discuses the management of multiple levels of code
using TLIB 4.12.  TLIB 5.0 is so much better than 4.12 in this area that
you will be better off struggling with the crummy 5.0 documentation than
using TLIB 4.12 for this.

If, after familiarizing yourself with TLIB 4.12, you find that you need
more advanced features, then by all means dive right in and give TLIB
5.0 a try.  First, though, take a look at the file dates.  If they are
more than a month old, then give us a call to see whether we have the
"real" documentation ready yet, or newer program versions.

What kind of advanced features does TLIB 5.0 offer that are not in 4.12
(nor in some competing products which cost 2-8 times as much)?

  * Whole-level change migration.  This feature, which is exclusive to
    TLIB, allows you to easily do wholesale migrations of changes from
    one level of code to another.

    For instance, if another team of programmers has made bug fixes to
    "release 1", you could migrate the fixes into the release 2 level
    without losing the work that you've already done there, and usually
    without tedious and error-prone manual comparing and merging of each
    source module.

    Or, you can easily migrate the improvements that you've made to your
    standard level into each of your customized levels, without losing
    the customizations.

    Or, when you receive a new release of a 3rd party source code library
    to which you've made modifications, you can combine the vendor's
    improvements with your own, for all the source modules at once.

  * Project-level support.  You can define several levels, and various
    relationships between them, to simultaneously manage several different
    versions of your software.

    For example, you could define a DEVELOPMENT level and a RELEASE
    level, and "promote" modules from DEVELOPMENT to RELEASE when they
    are tested and working.

    Or, you could define a STANDARD level and a number of customization
    levels for semi-custom software.

    A single set of TLIB library files thus supports as many "current"
    variants of your software as you need.

  * Promote command.  Lets you "throw the code over the wall" to the
    QA department's project level when you finish your "unit testing."

  * Automatic branching.  TLIB can keep track of what source file versions
    you are working with, and create branches when necessary to maintain
    an unbroken ancestory chain.  Also, you can configure some project
    levels to be branch levels, so that source files stored at those levels
    will be stored as branch versions.

  * N-way branching.  You can have as many branches as you wish from any
    source file version.  This is needed if you have multiple customization
    levels, all derived from the same standard level.  TLIB 4.12 supports
    only "binary" branching, which is fine if you use branches only for
    bug fixes, but inadequate for multiple, customized versions.

  * Branch locking, and weak locking.  These locking modes allow several
    programmers to work on the same module at one time, without subverting
    the safety of the system.

  * Native OS/2 version available (which also works well under Windows-NT).

  * Simple "snapshot" version labeling, even when you use branching, as
    part of the main TLIB program (not a separate utility).

  * Advanced wild-card file matching.  TLIB can apply your wild-card
    specifications to any of six different file "name spaces": source files,
    library files, locked files, owned files, files defined in the current
    project level, and files defined in any project level in the current
    chain of project levels.  Additionally, you can specify multiple
    file specs with commas, and you can filter ("AND") with yet another
    wild-card spec.

  * Tree-structured directories.  TLIB 4.12 kept track only of source file
    names and their version numbers.  TLIB 5.0 can also keep track of the
    "relative directories" in which the source files belong, if need be.


--------------------------------------------------------------------------


			Errors in the User Manual
                        -------------------------

There is an error in all printings of the TLIB 4.12 Users Manual, in the
example of the FILETYPE configuration parameter on or near page 156.  To
correct the example, cross out the last line (which says "filetype text"),
or move the last line to the beginning (before "IF *.WK*").

There are two other errors in the first printing of the TLIB 4.12 Users
Manual (the title page of the manual indicates which printing you have):

1) The description of the REPLROBR configuration parameter, pp. 151-152,
indicates that it only affects the operation of "browse-mode" extract
commands.  This is incorrect.  Configuring "REPLROBR Y" with "READONLYB Y"
allows all extract commands, including E and X, to replace read-only
files which are not already checked out.

Please take a moment to cross out the words "browse-mode" in the first
sentence of the description for REPLROBR.

2) In the middle of page 158 is a paragraph which begins, "It does not
matter whether...".

It is incorrect.  To fix it, cross out the first four lines.  What will
remain is the following statement:

"parameters are processed in the order that you specify them: if a
single parameter is set more than once, only the last one has any effect."



--------------------------------------------------------------------------

                        Omissions from the Manual
                        -------------------------

TLIB 4.12s has three features which are not described in the TLIB 4.12
User Manual.  Plus, we're now including a greatly improved PCOM/PCOMS
parallel-port-based communications program.

1) We're now including version 5.0 of PCOM and PCOMS.  The manual does
not describe many of the new features (like remote-control, and the
ability to transfer an entire "tree" of subdirectories), so run PCOM
without parameters for instructions.  The cable wiring is unchanged.

2) The network edition of TLIB can now automatically set your TLIB
user id according to either your workstation's network "machine name"
or, for Novell users, your Novell login name.  (TLIB 5.0 can also look
up your user ID via NetBIOS.)

(Note: This feature is not included in the one-user editions of TLIB.)

To use your network machine name, set your TLIB user id to "*machine*".
(Note that some networks may not set the machine name, so this may not
work for you.)	The most convenient way to do this is to configure:

	id *machine*

To use the Novell NetWare login name, set your TLIB id to "*novell*",
perhaps by adding the following line to your TLIB configuration file:

	id *novell*

With TLIB 5.0 (but not TLIB 4.12), you can use NetBIOS to set your
user ID to your network login ID.  Set your TLIB id to "*netname*",
perhaps by adding the following line to your TLIB configuration file:

	id *netname*


3) We've added the TLIBSMP program (the name stands for "TLIB Set
   Multi-Pass").

This program may be useful if you are managing large files with
TLIB and need to change your configured "maxlines" and "multipass"
parameters.  Don't worry about it now, though.	We've added an
informative message to TLIB so that if you ever experience the
problem which TLIBSMP solves, TLIB will display a message suggesting
that you run TLIBSMP.

Most users will never need TLIBSMP.


4) Starting with TLIB 4.12f, we added a new command: C (configure).
With the C command, you can specify or override any configuration
parameter, either on the DOS command line or interactively.

Example:

    TLIB c "readonlyb N" b myfile.c
    (means disable read-only-browse mode, then do browse-mode
    extract of myfile.c)

The C command can be specified several times, if you wish, to change
several configuration parameters:

    TLIB c "keyflag 0" c "logflag 0" e myfile.c
    (means disable keyword and revision history log insertion,
    then extract myfile.c)

Even the INCLUDE directive is allowed, so you can use it to specify a
large number of configuration options, like this:

    TLIB c "include special.cfg" e myfile.c

The only things allowed in the configuration file which you cannot
specify with the C command are the 'IF' and 'ENDIF' pseudo-parameters
(this restriction can be circumvented by putting the IF/ENDIF block in
a file and loading it with the C command and the 'INCLUDE' directive).

We are grateful to Mr. Michael Mather for this idea (and many others)!

Note: you can disable the C command just like any other command, with
the COMMANDS configuration parameter.


--------------------------------------------------------------------------

				 OS/2
                                 ----

TLIB 5.0 for OS/2 is available in "late beta-test" form (though, as
previously mentioned, the manual for TLIB 5.0 is still not done.)  If
your TLIB didn't come with an OS2TLIB.LZH archive, give us a call saying
that you'd like to be a beta-tester for the OS/2 version.  Please have
your TLIB serial number ready when you call.

There is no TLIB 4.12 for OS/2, but it works fine from OS/2's "DOS
compatibility box."

TLIB 5.0 for OS/2, like TLIB 5.0 for DOS, is essentially done except
for the user manual, and except that several of the auxilliary programs
(notably DIFF3) are not yet working in OS/2 protected mode.  However,
these programs work fine in an OS/2 "DOS Box."

TLIB 5.0 for OS/2 has much better performance than under DOS.  We utilize
heavy buffering and multi-threaded file I/O to overlap computation with
file access as much as possible.  As a result, we've seen TLIB 5.0 for
OS/2 run as much as 40% faster than TLIB under DOS.



			       Windows-NT
                               ----------

The OS/2 and DOS versions of TLIB both work well under Windows-NT (the
alpha test version which Microsoft distributed with the SDK).  However,
the OS/2 version of TLIB works best, because it runs in protected mode
and therefore has more memory available and runs faster, especially if
you need to manage large files (or lots of small files).



--------------------------------------------------------------------------

			        DOS 4.0
                                -------

We have a report of problems with DOS 4.00 if the FASTOPEN parameter is
specified in CONFIG.SYS.  The symptom is erroneous "disk full" errors
when trying to extract large files from TLIB libraries.  This might be
related to use of a "look-ahead" count on the BUFFERS parameter (e.g.,
the "3" in "BUFFERS 25,3").

This is probably due to a bug in DOS 4.00, so we recommend that DOS 4.00
users not install FASTOPEN in the CONFIG.SYS file, and not specify the
second number on the BUFFERS statement.  There is apparently no problem
if FASTOPEN is installed in AUTOEXEC.BAT.

We've heard no reports of the problem with DOS 4.01.



			        DOS 5.0
                                -------

The DOSKEY program that comes with DOS 5.0 is better than nothing, but
it does not work as well with TLIB as public domain and shareware
alternatives like CED and DOSEDIT.  The problem is that DOSKEY does not
keep a separate command history for applications.

We recommend that you use CED (from the "Public Domain & Shareware"
files that you got with TLIB), rather than DOSKEY.

There is more information about CED below, and also in the printed TLIB
manual (look in the index under "CED").



--------------------------------------------------------------------------

                  Public Domain and Shareware Collection
                  --------------------------------------

Some of the public domain and shareware programs that we "throw in" as
"disk filler material" are VERY, VERY useful.  All are certified
virus-free (we either wrote them ourselves, got them directly from the
author, or recompiled them from source code).

They include:

    COMPARE   - A nice file-compare utility, with source code.

    CONCOPY   - Chris Dunford's indispensible tool to create a log file
                of console activity.

    SCOPY     - Shared-access file copier, for copying the TLIB journal
                file w/o the potential for interference with TLIB.  Use this
                to make a copy of the journal file before processing it
                with AWK to generate custom reports.  By Burton.

    CED       - Chris Dunford's handy DOS "command line editor".  (Look
                up "CED" in the index to the TLIB 4.12 manual).  CED is
                copyrighted -- please observe the restrictions in the CED
                User's manual, CED.DOC.

                We recommend that you install CED on the last line of your
                AUTOEXEC.BAT file.  CED works better with TLIB than does
                the DOS 5 "doskey" program.

    AWK214    - Rob Duff's complete implementation of the AWK programming
                language.  It runs a lot slower than the industry-leading
                AWK complier from Thompson Automation, but it is very
                nice in every other respect.  There is full source code
                in the AWKSRC archive (but if we run out of diskette
                space, this'll be the first file to go).

                Unpack the AWK files (warning: there are a LOT of them)
                with LHARC, and then run DEMO.BAT for a demonstration.

                You can print AWK.MAN & AWK.DOC for limited instructions.
                For a more thorough treatment, buy the book, "The AWK
                Programming Language," by Aho, Weinberger and Kernighan,
                Addison-Wesley 1988, ISBN 0-201-07981-X.

                This implementation of AWK was written by Rob Duff.
                It is copyrighted, but Mr. Duff has made it available for
                unlimited free use and distribution in both commercial
                and individual settings, with just one proviso: you may
                not sell this AWK.

                Support and the latest version of AWK (both source code
                and executables) are available on Mr. Duff's BBS, phone
                number (604) 877-7752.  AWK is included with TLIB by
                permission of the author.

    CTMAP09C  - Memory manager for users of Chips & Technologies-based
                AT clones.  Allows use of upper memory blocks, and loads
                TSRs "high" even on some '286s, and does it on '386s
                without putting the CPU into protected mode, so it won't
                interfere with Borland's TD386 debugger.  Include's
                Jim Kyle's DEVLOD (device driver loader); the rest of
                CTMAP09C is by Burton.

    PMAP132   - Chris Dunford's utility to display a DOS memory map, and
                to show where TSRs are loaded and how much space they take.

    MERGE100  - Chris Dunford's tool to MERGE two versions of a source
                file, adding conditional-compilation directives so that
                the combined file is equivalent to either of the original
                source files, depending upon your compile options.

    CRC16     - Rob Duff's tool to calculate and display 16-bit CRC
                checksums of files.  It is very useful for ensuring that
                a program or data file is not damaged.  It includes
                full "C" source code, and it is true public domain
                (not copyrighted).

    DSAPP     - "Delta-script applier."  DSAPP is a program to apply
                INSDEL-format "delta" files, which can be generated by
                TLIB's CMPR utility.  DSAPP is mentioned on pp. 95-96 of
                the TLIB 4.12 manual.  Public domain, by Burton.
                (Note: TLIB also comes with DSAPP-like programs for
                Pansophic PANVALET/P-COMPARE and ADR LIBRARIAN delta
                formats, but they are not public domain.  They are
                called DSAPPPAN.EXE, and DSAPPADR.EXE, respectively.)

    XBASE     - Includes COPYSTEX and other goodies for for dBase/Clipper/
                Foxbase/etc. users.

                COPYSTEX was written by M. J. Magan.  The name "COPYSTEX"
                is short for "copy structure extended."  You can use it
                to extract the sturcture of your .DBF files into new
                files which are easily maintained in TLIB libraries (use
                TLIB's binary format).

                Mr. Magan gives away COPYSTEX for free (although it is
                copyrighted).  All he asks is that if you find it useful,
                send him a postcard at:
                    M. J. Magan
                    van der Helmstraat 43,
                    3067 HA Rotterdam
                    The Netherlands


    MAKE      - Landon Dyer's simple, public domain MAKE utility.
                Similar to (but much more primitive than) the famous
                Unix program by the same name.  MAKE is not copyrighted,
                so there are no legal restrictions on its use or
                distribution.  However, the author, Mr.  Landon Dyer,
                asks that you do not SELL his Make utility.  Please
                respect his wishes.

                This MAKE has two interesting features: it is "integrated"
                with both TLIB and PKPAK.  That is, it can check the
                dates of specific versions or branches within a TLIB
                library, and it can reference a file within a PKPAK-style
                archive file, just as if the archive were a directory.

                The complete source code for MAKE is in the MAKESRC
                archive file.  However, you do not need anything from
                MAKESRC to use MAKE.

                If you need a more sophisticated MAKE, we suggest that
                you contact our friends at Opus Software (415) 644-7901.
                Opus MAKE is the simply best MAKE utility in the world.
                Period.

      And maybe others...


These programs are included at no charge, but not all are public domain.
Some of them have usage restrictions or require that you purchase a
license (from the author) under some circumstances (if you decide to use
them.  The documentation files which come with each of them have details.


--------------------------------------------------------------------------

                              Copyright/License
                              -----------------

Note that the programs in TLIB*.LZH are copyrighted by Burton, and are
not to be distributed (a summary of the laws pertaining to copyrighted
software can be found on page 3 of the TLIB manual).  Also note that the
single-machine-at-a-time rule applies to all of the TLIB programs at
once; that is, if ANY of them are in use on one computer, NO ONE may use
ANY of them on another computer at the same time (the manual makes a minor
exception to this rule for users of PCOM; see p. 176-177).  Please respect
our copyright.



--------------------------------------------------------------------------

		                Editor Macros
                                -------------

There is now an especially nice TLIB editor macro for users of Multi-Edit,
from American Cybernetics, (602) 968-1945.  They have versions for TLIB
4.12, and (probably now available) for TLIB 5.0.  This is the best editor
macro we've seen for version control integration.

Also, there is a very nice macro in the works for SlickEdit, from MicroEdge,
Inc..  Contact MicroEdge, (919) 831-0662, if you need it.

Also, there is a TLIB.PEL macro for the Sage Professional Editor (SPE)
available on our BBS as SAGEPEL.ZIP.  This macro was written by our friend,
Mr. Andrew Hargreave.  Thanks, Andrew!  (The BBS is at 919-233-0106.
It is just for file transfers; you cannot leave messages.)

There are now two versions of the BRIEF Editor macro, TLIB.M.  Rename
either TLIB.M2 or TLIB.M3 to TLIB.M, according to which version of BRIEF
you have.  You may also have received a TLIB macro with your copy of
BRIEF.  If so, compare the file dates with the ones you received with
TLIB: the newest is probably the best.  The Brief macros are not as good
as the MultiEdit (and upcoming SlickEdit) macros; but for that matter,
Brief is not as good as MultiEdit or SlickEdit, either.


--------------------------------------------------------------------------

			     Old Release Notes
                             -----------------

For customers upgrading from earlier versions of TLIB, we've included:

4PXXNEWS.DOC  -  release notes for various older TLIB versions

The information in 4PXXNEWS.DOC is also in the current edition of the
TLIB manual (except for descriptions of how TLIB 4.12 differs from
earlier versions).

This file is stored in TLIB4.LZH.  To retrieve it, use LHARC:

	A:LHARC A:TLIB4.LZH 4P*.DOC


--------------------------------------------------------------------------

				Files
                                -----


TLIB4.LZH - TLIB 4.12 files:
---------------------------

4PXXNEWS.DOC	Release notes
ADMIN.CFG	Sample config for all 17 commands
ANSI.CFG	Fancy TLIB config, uses ANSI.SYS
AREACODE.SOR    Telephone area code & country code list
BRANCHES.CFG	TLIB configuration w/ branching
CMPR.EXE	Delta-script generator
DIFF3.EXE	Program to merge or undo changes
DSAPPADR.EXE	Delta Script Applier, ADR format
DSAPPPAN.EXE	Delta Script Applier, Pansophic format
EXPANDIR.EXE	Program to expand DOS subdirectories
GOODBYE.TLB	Sample TLIB library file
IBMUPDAT.EX     Example VM/CMS `exec' to apply IBMUPDATE delta
JOURNAL.AWK	Sample AWK program which reads a TLIB journal
LISTBLD.EXE	Automatic file list builder/manipulator
MASM.CFG	A sample TLIB configuration file
NORMAL.CFG	A sample TLIB configuration file
PCOM.EXE	Fast PC-to-PC file transfer
PCOMS.EXE	A memory-resident server for PCOM
TABS.EXE	Fast tab/blank and blank/tab conversions
TLIB.EXE	TLIB version 4.12
TLIB.M2 	BRIEF editor macro for BRIEF 2.01/2.1
TLIB.M3 	BRIEF editor macro for BRIEF 3.0
TLIBSCAN.EXE	Fast file scanner (aka: WHAT or IDENT)
TLIBSMP.DOC	Documentation for TLIBSMP.EXE
TLIBSMP.EXE	TLIB-Set-MultiPass utility, for large files
TLIBSNAP.EXE	Version labeling for TLIB 4.12
TOUCH.EXE	Utility to update file date/time
UNCMPR.BAT	reverse of CMPR.COM (see also DSAPP in PUBLIC.LZH)
0368.A through
2579.A		Quick configuration files - see "Getting Started" in manual



TLIB5.LZH - TLIB 5.0 (beta) files:
---------------------------------

5P00NEWS.DOC    Main documentation for TLIB 5.0      [Read this 1st]
CONFIG.DOC      More TLIB 5.0 documentation          [ "    "   2th]
COMMANDS.DOC     "    "    "       "                 [ "    "   3nd]
TRACKFIL.DOC     "    "    "       "                 [ "    "   5th]
PROJLEV.DOC      "    "    "       "                 [ "    "   6th]
NEWVERSN.DOC     "    "    "       "                 [ "    "   7th]
TLIB.EXE        TLIB version 5.0
TLIBCONF.EXE    TLIB 5.0 configuration setup utility
TLIBCONF.DOC    Documentation for TLIBCONF.EXE       [ "    "   4th]
WHEREIS.EXE     Multi-volume file finder
CMPR.EXE        Delta-script generator
COPYTRAK.EXE    A tool to manipulate tracking files
POKETRAK.EXE    A tool to manipulate tracking file entries
BETA_FIX.DOC    Bug fix list for old TLIB betas      [Don't bother to read]



PUBLIC.LZH - Public Domain and ShareWare:
----------------------------------------

AWK214.LZH	The AWK Programming Language
AWKSRC.LZH      Source code for Duff AWK (included if we had room)
CED.COM 	DOS command line editor
CED.DOC 	Documentation for CED.COM
COMPARE.EXE	A file compare program
COMPARE.PAS	Source for COMPARE.EXE
CONCOPY.LZH     Console logger - VERY useful
CRC16.LZH	File checksum generator/checker
CTMAP09C        Memory management for Chips & Technologies-based ATs
DELBAT.BAT	Part of the MAKE package
DSAPP.EXE	Delta-script application (like UNCMPR)
DSAPP.PAS	Source for DSAPP.EXE
MAKE.BAT	The MAKE command, runs MAKEEXE
MAKE.MAN	Documentation for Dyer MAKE
MAKEEXE.EXE	The program run by MAKE.BAT
MAKESRC.LZH	Archive of all MAKE source files
MERGE100.DOC    Notes on MERGE & other Dunford tools
MERGE100.LZH    File MERGE tool
PMAP132.LZH     DOS memory map displayer
SCOPY.DOC       Documentation for SCOPY.EXE
SCOPY.EXE       Shared access file copier
XBASE.LZH       COPYSTEX and other XBase-related files
ZIP.ASM 	Source code for ZIP.COM
ZIP.COM 	Memory initializer
ZIP.DOC 	Documentation for ZIP.COM


--------------------------------------------------------------------------

			   Credits & Recommendations
                           -------------------------

1) We got COMPARE.PAS from our friend, Kim Kokkonen, of TurboPower Software.
TurboPower sells several fine products for use with Borland's Turbo Pascal.

TurboPower Software is at:  3109 Scotts Valley Drive, Suite 122-B,
Scotts Valley, CA  95066.  Tel: (408) 438-8608


2) The best-kept secret in small-scale software duplication is FastDup,
from LogiCom, Inc.  Just $39.95 (includes shipping in the USA) turns a PC
into an easy-to-use, reliable, disk duplicator.  It formats, copies and
verifies 360K disks at a rate of about 60 per hour (720K, 1.2M and 1.44M
take longer, of course).  LogiCom is at P. O. Box 27465, Lakewood, CO
80227.	Tel: (303) 986-6651.


3) dBase and Clipper users can automatically generate TLIB-compatible
file lists using "dBfind 3.0", from The Software Development Factory.
dBfind also provides cross-reference and "lint-like" programming
utilities.  It lists for $99.

The Software Development Factory is at:  P.O. Box 1106, Hunt Valley,
MD 21031.  Tel: (301) 666-8129.  Ask for Steve Johnson.


4) The TLIB Version Control System is now integrated with two full-
featured commercial MAKE utilities: Opus MAKE and Slick MAKE.  Both are
fine products, and each has its advantages, but our current overall
favorite is Opus MAKE.

Opus Software is at 1032 Irving St., Suite 439-B, San Francisco, CA 94122.
Tel: (415) 664-7901.

Opus Make is also integrated with SLR Systems' OPTLIB Object Module
Librarian.  OPTLIB produces standard LINK-compatible object module
libraries, but it is 5-10 times faster than Microsoft's LIB.EXE, and
OPTLIB provides a number of additional features.  It is wonderful.

SLR Systems is at:  1622 North Main Street, Butler, PA	16001.
Tel: (412) 282-0864.

We use Opus MAKE, OPTLIB, and SLR's linkers (OPTLINK/OS2 and OPTLINK/
Compress) to build TLIB 5.0.  Were it not for these fine tools, TLIB 5.0
would be even later than it is.


5) This product uses the TesSeRact (tm) Ram-Resident Library and supports
the TesSeRact Standard for Ram-Resident Program Communication.	For
information about TesSeRact, contact the TesSeRact Development Team at:

      TesSeRact Development Team
      1657 The Fairways, Suite 101
      Jenkintown, PA  19046
      1-215-884-3373
      Compuserve:    70731,20
      MCIMAIL:	     315-5415

This MCIMAIL Account has been provided to the TesSeRact Development
Team by Borland International, Inc.  The TesSeRact Development Team
is in no way associated with Borland International, Inc.  TesSeRact
is a trademark of the TesSeRact Development Team.

If you develop TSR (terminate & stay resident) "popup" or "background"
programs for MS-DOS, then do not write another line of code without
obtaining a copy of TesSeRact (tm).

We used TesSeRact to build PCOMS.

TesSeRact is the result of a lengthy collaborative effort by a number
of shareware authors (and some commercial vendors) to solve all the
"hard" problems associated with writing TSRs.  It includes instructions,
examples and runtime libraries for writing TSRs in Turbo-C, Microsoft C,
Turbo Pascal, and Assembler.

TesSeRact dramatically simplifes the task of writing code to "pop
up" reliably (via hot keys or timer interrupts), or run in the
background, and your TSR can use almost all of the normal high level
language facilities, including file I/O.

You can get a registered copy of TesSeRact for $25; add another $25
for full source code; add another $10 for a 1-year subscription to
their newsletter.  Shipping in the USA is included (Canadians add $10,
Europeans add $15).

Visa/MC orders for TesSeRact can be placed with:
"The Public (Software) Library", (800) 2424-PSL.

