home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Elite Hackers Toolkit
/
TheEliteHackersToolkitVolume1_1998.rar
/
HACKERS.BIN
/
appcraks
/
POCKET_1.ZIP
/
RTPATCH4.TXT
< prev
next >
Wrap
Text File
|
1990-01-01
|
9KB
|
213 lines
.RTPatch(R) Professional
Version 4.00 for Windows, NT, and DOS
Evaluation Version
Patent Pending
(c) Copyright 1991-1997 Pocket Soft, Inc.
ALL RIGHTS RESERVED.
INTRODUCTION
This file describes .RTPatch Professional 4.00 For Windows, NT (Intel), and
DOS. .RTPatch Professional 4.00 for Windows, NT, and DOS supports the
following platforms:
Windows 3.1
Windows for Workgroups 3.11
Windows NT 3.1
Windows NT 3.5
Windows NT 3.51
Windows NT 4.00
Windows 95
DOS
There are other products in the .RTPatch series, namely:
.RTPatch Professional for NT Alpha(R)
.RTPatch Professional for UNIX
(supports build on SCO UnixWare, SCO OpenServer,
HP-UX, or Solaris/SPARC; apply on any UNIX platform)
Evaluations of the above are also available; please call (800)826-8086
or email sales@pocketsoft.com to obtain one.
Thank you for downloading the evaluation version of .RTPatch 4.00 for Windows,
NT, and DOS. We have provided the manual in Microsoft Word for Windows 2.0
format (RTPATCH.DOC), and in text format (RTPATCH.TXT). To get started,
you can print the manual (or view it on disk, if you prefer), and see
the Introduction, Chapter 1, "Getting Started", Chapter 2, "Building a
Patch File", and Chapter 3, "Applying a Patch File".
We have provided basic instructions for building a patch file and a complete
command reference in the file QUICKREF.TXT.
If you have any trouble at any point, just give tech support a call (see
below for contact information). We are happy to provide full technical
support for the evaluation version within the 30 day evaluation period.
TECHNICAL OVERVIEW
.RTPatch Professional revolutionizes updating text and binaries -- at the
binary level. It is used for bug fixes, program changes and additions, data
changes and text revisions.
When the contents of a software file or system change, the changes need to
be distributed to update others who use the software. The common method
of distributing updates is to send a complete copy of the new version to
replace the existing installed version.
.RTPatch makes updating software easier. It reduces the time, procedures,
cost, and problems associated with updating software files. With .RTPatch,
updating is achieved by patching changes into the old version at the binary
level. Patching will work on a single file or an entire system of files,
with just a few simple steps. This eliminates the need to re-install
existing portions of the software which have not been changed.
The patching process is achieved by creating and applying a patch file. The
patch file contains information necessary to convert the old version into the
new version. Creating and applying patch files can be automatic with the
.RTPatch product. Sophisticated safety features ensure proper building and
applying of patch files.
.RTPatch will work on any type of software file. With a single patch, you
can easily update a single file, a group of files, even a directory of files
with subdirectories; one patch file can be used to update an entire system.
.RTPatch consists of two parts: a build program (PATCHBLD) and methods to
apply patches to your end users' old files to turn them into updated files.
PATCHBLD compares the old version to a new version and builds a file which
contains the changes.
There are several ways to apply the patches to your end-users' files:
1. A provided Win16 or Win32 DLL and your own code can make your
end-users' application of the patch file seamless. You can also
bind your own interface to a patch file and the DLL for a custom,
one-file updating solution.
2. Either DLL can be used with a Win16 or Win32 apply program that we
provide.
3. You can bind a simple Win16 or Win32 interface which we provide to
a patch file and the DLL for a one-file updating solution.
4. You can run the patch application as a DOS program.
Building a patch can be almost automatic. However, there are many optional
commands which control a variety of valuable features that give the patch
builder very flexible control over the patch-building and patch-applying
processes. These features provide ways to handle customized situations such
as serialized files, security-coded files, adding or deleting files, renaming
files, etc. Numerous safety features have been built into .RTPatch to
ensure proper performance in both building and applying patch files.
For a complete command listing and instructions for getting started right
away, see the .RTPatch User's Guide (RTPATCH.DOC or RTPATCH.TXT).]
IMPORTANT NOTES
----------------------------
Character Set Considerations
----------------------------
Filenames containing non-ASCII characters are handled by all .RTPatch
executables, but there are the following caveats:
1) the filenames stored in the patch file are stored using the OEM
character set on the "build" machine.
2) all text passed to and from the DLLs uses the OEM character set.
3) files selected using Windows common dialogs are in the ANSI
character set.
4) the command line passed to Win32 console apps uses the ANSI
character set.
To avoid character-set mismatch problems, we advise that filenames be
limited to characters which are present in both the ANSI and OEM character
sets. This is particularly true in Windows and Win32 environments.
--------------------------------------------------
Building Patches for Compressed or Encrypted Files
--------------------------------------------------
PATCHBLD will build inefficient patch files for files that have
been compressed (with PKZIP, LHA, etc.), or for files that have
some kind of encryption enabled. When you apply a compression or
encryption algorithm to two files that are similar, the two files
become very different. You might find that the patch for two files
that have been compressed or encrypted might be larger than either of
the original files.
Certain compilers have an option that enables .EXE encryption at
compile time to prevent users from disassembling or decompiling
your program. Microsoft FoxPro is the most notable example; by
default, FoxPro encrypts the .EXE when it compiles. If both the
old .EXE and the new .EXE have been encrypted, then PATCHBLD will
build a patch file larger than either old or new .EXE. You can
use .RTPatch in conjunction with FoxPro executables if you deselect
.EXE encryption.
Keep in mind that if only certain regions of a file are encrypted
(for example, a password or a region that contains sensitive
information), then patching should work just fine.
Some compliers and utilities allow you to have an .EXE that is
compressed on disk and uncompressed when run. PATCHBLD will
build inefficient patches for such compressed .EXEs.
---------------------------------
PATCH.EXE Disk Space Requirements
---------------------------------
PATCH.EXE needs a varying amount of disk space to apply a patch, depending
on whether certain options are turned on at build time or with an apply time
switch. PATCH.EXE needs free disk space equal to the total system size if
BACKUP or UNDO is on at build time, or /B or /U is used at apply time. If
neither of these options are used, PATCH.EXE requires space equal to the
largest single file in the system.
OBTAINING TECHNICAL SUPPORT
To receive technical support during the evaluation period,
call 713.460.5600 or fax 713.460.2651. Please provide your
name, organization name, address, phone number, and fax number.
You can also e-mail us at rtpatch@pocketsoft.com.
LICENSING AND ORDERING INFORMATION
For evaluation copy licensing information, see the file LICENSE.TXT. For
production version licensing and ordering information:
Email: sales@pocketsoft.com
Call: (800)826-8086 (US and Canada)
(713)460-5600 (Countries outside US and Canada)
Fax: (713)460-2651
Mail: Pocket Soft, Inc.
P.O. Box 821049
Houston, TX 77282-1049
USA