home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
PROG_GEN
/
OPR121.ZIP
/
OPR121.EXE
/
OPRO121.DOC
< prev
Wrap
Text File
|
1994-02-01
|
6KB
|
131 lines
Patching Object Professional version 1.20 to 1.21
-------------------------------------------------
TurboPower Software
Patch scripts updated 94/02/01
OPR121.EXE is a self-extracting archive that contains patch files
to transform Object Professional version 1.20 into version 1.21. The
patch file was generated using Pocket Soft's .RTPatch utility (version
2.01).
If you don't already have a copy of PATCH.EXE, you can download it
from the same place where you found OPR121.EXE. Store PATCH.EXE in a
directory that is on your DOS PATH. You'll probably want to keep a
copy of PATCH.EXE, since it can be used to apply all TurboPower
maintenance patches.
OPR121.EXE contains three patch files, which you should extract or
copy into your \OPRO subdirectory. Then move into that subdirectory
and enter the following commands at the DOS prompt:
PATCH \OPRO O121
PATCH \OPROOBJ O121OBJ
PATCH \OPRODEMO O121DEMO
If you didn't use our suggested names for your OPRO subdirectories,
replace the first option in each of the command lines with the
directory name you chose.
PATCH provides running status of the patch process, and displays a
summary when patching is complete.
You can delete the patch files (extension .RTP) from your \OPRO
directory once patching is complete. You'll probably want to keep
OPR121.EXE for a while, in case repatching is required (see below).
As with any TurboPower update, see the READ.ME, READ.1ST, and FASTUPD
files for information about the new version.
Download UPDATE.TXT from the same place where you found OPR121.EXE for
additional background information about the patching process,
available patch files, etc.
Be aware of the following limitations of the patching process:
--------------------------------------------------------------
1. The patch only works to bring version 1.20 up to 1.21. For example,
it cannot bring version 1.14 up to 1.21. You need a separate patch
file for each incremental version.
2. Dependent files that you can rebuild yourself are *not* patched.
This keeps the size of the patch file to a minimum. In many cases,
such patches would be wasted anyway, since there are so many different
ways the dependent files can be created (with varying defines,
compiler options, compiler versions, etc.). Files with the extensions
EXE, LIB, HLP, TPU, TPW, and TPP are not patched unless they depend on
source code or other files that aren't part of Object Professional. Be
sure to remake all dependent files after you install the patch. All
files but the HLP file can be remade by using the supplied make or
project files, or just by compiling them into your application. The
HLP file can be recreated by entering the following command in the
\OPRODEMO directory:
MAKEHELP /Q OPRO
Note in particular that DESKPOP.EXE, DPINST.EXE, MAKEHELP.EXE,
MAKEMENU.EXE, MAKESCRN.EXE, and POPHELP.EXE are not part of the patch.
If you use these programs, be sure to recompile them after applying
the patch. With the exception of MAKEHELP.EXE, they are not made by
OPRO.MAK. (Including these EXE files in the patch more than doubles
its size.)
3. If you didn't originally install all of Object Professional, then
of course PATCH can't update the uninstalled portion of the library.
This isn't a problem unless you later install the rest of the older
version. In that case, you must reuse the patch to bring the newly
installed files up to the current version.
PATCH does not attempt to patch archive (.LZH) files. You must
dearchive all files that you wish to patch. This applies to BONUS
files as well as production files.
4. PATCH can't find files that you have moved out of the three \OPRO
directories associated with the three patch files. It *can* find files
in subdirectories of those directories, however.
5. PATCH doesn't attempt to update certain files because they are
updated automatically during installation or when you configure the
library for your application. Because these files have been customized
for your system, PATCH cannot make reliable changes to them. Even so,
it's often important for us to distribute updated versions of these
files, since there may be new defines and dependencies in them. We
decide on a file by file basis whether to distribute a new copy of
these files or to allow your existing version to remain intact. Here
is a list of affected files for OPRO 1.21:
Directory Filename In Patch? New Name or Directory?
---------------- ------------ --------- ----------------------
\OPRO OPDEFINE.INC New copy OPDEFINE.121
various *.CFG No
When one of these files is distributed as part of the patch, a
complete new copy of it is included, since PATCH probably cannot patch
your modified copy. Where appropriate, the final column of this table
shows the name or directory of the new copy of the file. Be sure to
look at this new file, modify it as appropriate for your environment,
and copy it over the old version before proceeding.
6. If you modified the TurboPower source code, PATCH refuses to apply
changes to the modified files. (It uses a checksum algorithm to assure
that the file it is patching is the intended version.) In this case,
the only way to get a valid set of patched files is to reinstall an
unmodified copy of Object Professional and patch it, then make your
changes to the new version.
If you have questions or problems regarding the patch, please contact
us:
TurboPower Software
P.O. Box 49009
Colorado Springs, CO 80949-9009
voice: 719-260-6641
fax: 719-260-7151
BBS: 719-260-9726
CompuServe ID: 76004,2611
Pascal forum: PCVENB section 6
C/C++ forum: PCVENE section 1
Internet: 76004.2611@compuserve.com