"TLIB is the fastest and most flexible version-control system on the market."
VB Tech Journal
January 1997, p. 20
29-Jun-2001: TLIB 5.53c is released.
Fixes an installation problem which occurred when installing TLIB under
Windows 2000 with a user ID in the "power user" group.
We lost a telephone voicemail mailbox a couple of days
ago; if you called us and left a message, and we did not return your call,
please accept our apology, and please call again.
11-Jun-2001: An updated TESTLOCK.ZIP
is available in our download area. (There is only one minor
change: the Win32 executable has been fixed to not complain about "upper"
file attibute bits, such as the "compressed" bit which can be set under
NT and Windows 2000.)
30-May-2001: TLIB 5.53b is released.
Fixes a few minor bugs; see the
Release Notes file, release.txt.
2-May-2001: TLIB 5.53 is released!
New features include:
Improved support for sharing files between projects;
A new command to reclassify source file(s) from private to shared (or vice-versa);
A new scan-for-included-files option when opening
Borland Delphi project files;
A new, extended wildcard syntax to tell TLIB to find not just a named C,
C++, or Pascal source file, but also whatever include files
The new tlmerge utility, which is a 32-bit version of our venerable DIFF3
Numerous GUI usability improvements, such as an enhanced version
history list that is displayed when you double-click a file name, which lets you
immediately select, extract, inspect, and compare old versions;
Better right mouse button support, including the ability to edit
MRU (most recently used) drop-down lists by right-clicking in them;
Visual Compare improvements, such as the ability to drag the vertical divider
right and left, to resize the two panes;
and many other improvements.
For more details, including a list of recent bug fixes, see the Release Notes file, release.txt.
For upgrade pricing, click here. Your upgrade is free* if you purchased TLIB Version Control Combo Edition less than one year ago.
( * A nominal shipping and handling fee will be charged if not shipped electronically.)
27-Mar-2001: We're having email trouble again.
If you have difficulty sending us email please resend it to:
you for understanding!
14-Feb-2001: TLIB 5.52 is released!
(This is version 5.52f; versions 5.52a-5.52e were beta versions.)
New features include a runlength-compressed & CRC-checked binary storage
format; an an EOF-tolerant (ctrl-Z ignoring) ASCII storage format;
automatic save & restore of column and window sizes in the 32-bit GUI;
Visual Compare improvements, including customizable colors; jour2snp,
a tool to build after-the-fact snapshots from the TLIB journal file;
Migrate command improvements; display of current and project-level
version numbers when listing versions; native project support for
MicroEdge Visual SlickEdit project and workspace
files, and more.
21-Nov-2000: TLIB 5.51i is released.
27-Oct-2000: TLIB 5.51h is released.
It adds support for Inprise/Borland C++ Builder 5.0 .bpr project files.
Also adds support for Microsoft Developer Studio .dsw Workspace Files,
(which really just group multiple projects). Also made several of other
13-Oct-2000: JourJoin, in
our downloads area, is a little program to
"join" (combine) the comment records in a TLIB journal file, so that there
is only one comment field in the journal file for each U (Update) or N
(New library) command.
When you store a new version of a source file in a TLIB library, TLIB optionally records your action in a chronological Journal File, in CSV (comma-separated values) format. (This is useful for generating customized reports, as well as providing a chronological "audit trail" of version control activity.) You can configure what types of information you want recorded in the journal file, but most users let TLIB store the full version comments. When the version comments exceed one line, TLIB writes multiple records to the journal file, to record the additional comment lines.
However, if you would prefer a journal file format in which all the comments are combined into one big field, in one record, you can use the JourJoin utility. This is useful when importing the TLIB journal file into some kinds of databases, such as recent versions of Microsoft Access.
27-Aug-2000: TLIB 5.51g is released.
16-Sep-1999: Hurricane Floyd missed
us (mostly). We did experience a brief power hit, but we're up and
running today. Thank you for your patience!
15-Sep-1999: We've had sporadic
problems with our email system at burtonsys.com. If your email
to firstname.lastname@example.org fails,
please try it again, or else try sending it
email@example.com, or to
Or call us at 1-919-481-6658 or 1-919-481-0149.
Also, please forward any "bounce" messages to us!
Thank you for understanding!
12-Aug-1999: TLIB 5.51a is released!
The GUI and command-line Win32 versions of TLIB are finally out of beta.
Other new features include "FileType Auto" (automatic handling of binary
vs. text files), a beta Visual Basic 6.0 Add-In, and improvements to the
7-Jul-1999: We've just recovered from a mail
server crash disaster at Burton Systems Software. We lost a lot of pending emails
(and perhaps a fax or two). If you sent us email (or a fax) but did not get a reply,
please accept our apologies, and please resend it.
22-Jun-1999: TLIB 5.50y, added native project file support for
MultiEdit for Windows .PRJ files.
(Note: this is the same file extension used by Symantec
Visual Cafe for its project files, but TLIB can tell the difference and handle them both.)
25-Feb-1999: TLIB 5.50w, now with long file name support under NT, rather than just Win-95/98!
Supports quoted file names and file names containing blanks, too.
17-Feb-1999: TLIB 5.50v, added a
SourceSafe-to-TLIB conversion utility for customers who are
switching from Microsoft or OneTree/Icarus SourceSafe to TLIB Version Control.
We also improved several of the other conversion utilities, especially the
Intersolv/Merant/Sage/Polytron PVCS-to-TLIB converter. We now have tools to automate conversion from:
PVCS, SourceSafe, RCS (both MKS and GNU/Unix variants), MS Delta, and
Sourcer's Apprentice. See Features.
17-Dec-98: TLIB 5.50s, added
native project file support for Premia Codewright Editor
For upgrade pricing, click here.
Your upgrade is free* if you purchased TLIB Version Control Combo Edition less than one year ago!
( * A nominal shipping and handling fee will be charged if not shipped electronically.)
For over 10 years, TLIBTM Version Control has been one of the leading configuration management tools for the PC software development community. TLIB Version Control is distinguished by superb performance, extensive configurability, and powerful multilevel project support. Now, with the introduction of TLIB Version Control for Windows 5.53, Burton Systems Software brings new power, convenience, and ease of use to version control on the PC platform.
Why Version Control?
If you face challenges like these ...
TLIB Version Control for Windows supports three modes of operation:
The TLIB for Windows built-in Visual Compare can be used to show the differences between two disk files or between two versions of a single file. It is also available at the click of a button while you enter the comments for a new version, during an Update (check-in), to show the differences between the new version and its predecessor, regardless of whether you are running TLIB for Windows directly or via a TLIB Add-In. Unlike most compare programs, TLIB shows you what has changed within the lines, as well as identifying which lines have changed.
TLIBTM Version Control is the version control program of choice for many businesses and programmers! Read the accolades from the trade press about TLIB Version Control.
We've got lots of 'em! Old ones. New ones. And we just keep making it better.
TLIB Version Control is very affordable. Click here for a detailed price listing, which also includes upgrade prices.
Do you keep HTML files under version control?
The last-modified dates and version numbers on these Web pages are updated automatically by TLIB Version Control, through the use of TLIB's highly-flexible keyword feature. TLIB's keyword support lets you specify the format in which the keyword information is inserted, so there's no "$Revision:" garbage displayed along with the inserted version number on your Web page.
TLIB Discussion List
To join the TLIB discussion list, send the following two-line, plain-text (not MIME or HTML!) email message to firstname.lastname@example.org
You may leave the subject line blank; it is ignored.
Note: We've had some problems with our email recently, so
if your email to us bounces, or you get no reply, please resend it
to the alternate email address, above.
Also, we'd be grateful if you would forward the bounce messages
to us. Thank you for your patience!
Web Design by