home *** CD-ROM | disk | FTP | other *** search
- PK361PAT.PAK contents and notes
-
- Contained herein are:
-
- $README.DOC This file.
- PK361PAT.WHY Some background.
- PKPAT.BAT A batch driver to apply the patches.
- PKPAK.CTL XPATCH control file to patch PKPAK.EXE
- PKPAKJR.CTL XPATCH control file to patch PKPAKJR.EXE
- PKUNPAK.CTL XPATCH control file to patch PKUNPAK.EXE
- PKUNPAKJ.CTL XPATCH control file to patch PKUNPAKJ.EXE
- XPATCH.EXE Version 1.0 of XPATCH, get XPATCH.PAK for source code
- and documentation.
-
- Basically, what all these do is provide a semi-clean way to change the
- built-in default filetype extension for archive files processed version
- 3.61 of the PKWARE archive management utilities (PKPAK, PKUNPAK, PKPAKJR,
- and PKUNPAKJ.) The default filetype as distributed is ".ARC", and
- enclosed patches change that to ".PAK". The original files are not
- modified in any way, if the enclosed procedure is followed, but new
- executable files (PK.EXE, PKJ.EXE, PKX.EXE and PKXJ.EXE) are created.
- The original files should be maintained for compatibility with other
- programs which might directly or indirectly call the PK utilities,
- while the shorthands may be used for keyboard convenience.
-
- ----------------------------------------------------------------------
-
- *** IMPORTANT: Please read the following carefully.
-
- The license included in PK361.EXE (the self-extracting archive file
- as distributed) states that the included programs may be
- freely used, copied and distributed "for NONCOMMERCIAL use if: No fee
- is charged for use, copying or distribution. [and] It is not modified
- in any way."
-
- This proviso clearly prohibits distribution of modified copies of
- PK361.EXE, and I respect and support that proviso for a number of
- reasons. It would also seem to prohibit modification of the PKxxx
- programs for personal use. While it is my non-expert opinion that
- this second interpretation is not enforceable, none of this should
- be taken as advice or encouragement to violate this proviso.
-
- IN ANY CASE, YOU MUST NOT DISTRIBUTE MODIFIED COPIES OF PK361.EXE, AND
- FURTHER YOU MUST NOT DISTRIBUTE COPIES OF ANY OF THE INDIVIDUAL
- COPYRIGHTED FILES THEREIN! ONLY THE UNMODIFIED PK361.EXE FILE MAY
- BE DISTRIBUTED.
-
- Mike Housky
-
- ----------------------------------------------------------------------
- DISCLAIMER
-
- The recipient assumes all responsibility for consequences and damages
- arising from the use of materials in this packages. No warranty of any
- kind is expressed or implied.
-
- ----------------------------------------------------------------------
- CAVEATS
-
-
- ----------------------------------------------------------------------
-
- If you should decide to use these patches, the following procedure
- should be used to install them.
-
- Requirements:
- 1. PK361PAT.PAK
- [this archive, may have been renamed PK361PAT.ARC
- by someone who has not adopted the ".PAK convention"]
- 2. PK361.EXE
- This must be the original version 3.61 distribution file,
- as distributed by PKWARE prior to Jan 31, 1989.
-
- Procedure:
- 1. Read the documentation and materials. Especially the disclaimer.
- You may not be interested in proceding.
-
- 2. Okay, you have decided to continue. Make an empty directory to
- work in. This will usually be on drive C: for a hard disk
- system, or on a blank formatted 360K or larger diskette in
- drive B: on a floppy-only system. For now, I will assume
- drive C, and that the directory name "PATCH" is acceptable:
- >C:
- >MD \PATCH
- >CD \PATCH
-
- 3. Copy the archive files into the working directory. Assuming
- these are on individual diskettes, in the root directory:
- [ Place PK361.EXE diskette in drive A: ]
- >COPY A:PK361.EXE
- [ Place PK361PAT.PAK diskette in drive A: ]
- >COPY A:PK361PAT.PAK
-
- 4. Extract the files:
- >PK361
- [At this point, you may want to delete ]
- [ "unnecessary" files to make room: ]
- [ >DEL PK361.EXE -- optional ]
- >PKUNPAK PK361PAT.PAK
-
- 5. Now, run the "driver" batch file:
- >PKPAT
- This will make copies of the original PKxxx programs to be
- patched, then invoke the enclosed XPATCH program on the
- copies to create the patched versions. If all goes well,
- PKPAT.BAT will terminate with the message:
- "All patches successful."
- If there is any error, PKPAT will terminate with the
- message:
- "XPATCH failed."
- The most likely case is that the wrong version of PK361.EXE
- was used, or perhaps there was insufficient disk space or
- memory or some other such error. Any resulting programs are
- NOT USABLE in this case, and should be deleted.
-
- 6. If there were no errors detected by PKPAT.BAT, then you should
- have renamed and patched copies of the principal PK archive
- utilities in the current directory as:
- PK.EXE Patched PKPAK.EXE
- PKJ.EXE Patched PKPAKJR.EXE
- PKX.EXE Patched PKUNPAK.EXE
- PKXJ.EXE Patched PKUNPAKJ.EXE
- These may be copied to your utility or system drive/directory
- as you choose, by:
- >COPY PK??.EXE d:\path\*.*
- where "d:\path" should be replaced with the drive/directory
- where you want to keep the patched copies.
-
- 7. Once again, these patched copies must not be distributed in any
- way to anyone else. Do not give a copy to a friend (or enemy)
- and do not make them available for download on on a BBS. These
- restrictions are the same as for the unpacked unmodified
- original commands. Commercial users must also satisfy
- additional, as described in the documentation enclosed in
- PK361.EXE
-
- That's it.