|
Description
The ActivePatch Package control allows you to
create, apply and manage patch packages.
Reference
File Name
APATCH.OCX
Object Type
Package
Remarks
The Package control can be used in an application to create
patch packages, as well as apply those packages on a local system.
A patch package consists of one or more updated files and the
instructions to apply those updates on a target system. ActivePatch
supports four basic methods of updating files: creation,
replacement, byte-level patching and deletion. When creating the
package, the application specifies the directories which contain
the original version of the files and the updated version of those
files. The control then analyzes the differences between the two
sets of files and automatically determines the appropriate update
method.
If a file exists in both the original version and the updated
version, it is analyzed to determine if there are any differences
between them. If the file has changed, only those changes are
stored in the package. This can significantly reduce the size of
the update, and the package file overall, compared to simple file
compression.
When the package is applied on a local system, in addition to
updating the file data, ActivePatch will also maintain the correct
reference count for shared files, automatically register components
and validate any digital signatures.
Requirements
The Package control is designed for the 32-bit Windows platform,
and is supported on Windows 95, Windows 98, Windows ME, Windows NT
4.0, Windows 2000 and Windows XP. For Windows 95/98 and Windows ME
it is recommended that the system have at least 16 MB of physical
memory. For Windows NT 4.0, it is recommended that the system have
at least 32 MB of physical memory, and have at least Service Pack 5
(SP5) installed. For Windows 2000, it is recommended that the
system have at least 64 MB of physical memory.
Distribution
When you redistribute your application that uses the control, it
is recommended that you install the control in the Windows system
directory. The ActivePatch control does not have any dependencies
on additional libraries except for standard system libraries which
are included with the operating system.
ActiveX components must be registered during the installation
process or by using a component registration utility. The
registration process writes specific information into the system
registry so that an application can load and use the control. If an
application attempts to use an unregistered control, it will fail
to execute and return an error.
Copyright
Copyright 2009 Catalyst
Development Corporation. All rights reserved.
|