Full Description of File
4OS2 2.0 patch file, updates 4OS2 2.0 16-bit
and 32-bit versions from rev A to rev B.
ONLY USEFUL if you already have 4OS2 2.0 rev
A, not needed by new users. To check your
current 4OS2 version use VER /R. Also
requires patch program (see 4DPATCH.ZIP).
Contents of the 4OS220B.DOC file
4OS2 2.0 rev A ==> 2.0 rev B Patch Documentation
January 4, 1994
Copyright 1994, JP Software Inc., All Rights Reserved. Published by JP
Software Inc., P.O. Box 1470, E. Arlington, MA 02174 USA, (617)
646-3975. 4DOS is a registered trademark of JP Software Inc.
This file explains how to install the 4OS2 2.0 rev B patches.
To use the patch, you must have:
* JP Software's PATCH.EXE program. This program is in a separate
file, PATCH.ZIP on CompuServe, or 4DPATCH.ZIP on bulletin boards
and the Internet. [* See note below.]
* A copy of 4OS2 2.0 rev A. The simplest way to check your
revision level is to use the 4OS2 VER /R command. This command
will also show whether you are running the 16-bit version of 4OS2
("4OS2/16") or the 32-bit version ("4OS2/32"). You will need this
information to apply the proper revision B patch.
To use this patch, use the VER command to determine whether you are
running 4OS2/16 or 4OS2/32. Then copy the corresponding revision B
patch file to to the directory where your 4OS2 version 2.0 files are
stored. Copy 4O20B16.RTP for 4OS2/16, or 4O20B32.RTP for 4OS2/32.
(Note that the second character of each filename is the letter "oh", the
fourth character of each name is the digit zero.) Make sure JP
Software's PATCH.EXE is in the same directory, or in a directory on your
PATH, then enter the appropriate command:
patch 4o20b16 (for 4OS2/16)
patch 4o20b32 (for 4OS2/32)
(Don't worry about running the "wrong" patch by mistake. The PATCH
program won't patch your 4OS2 files unless the proper original file is
This patch converts 4OS2 2.0 rev A to version 2.0 rev B. It modifies
only 4OS2.EXE, all other files are unchanged from rev A. Branding (name
and serial number) information in your 4OS2.EXE file will be preserved
in the modified file.
If you want to test 4OS2.EXE to make sure the patch worked, restart your
4OS2 session, then use the VER /R command. This command will report
"4OS2 Revision A" (if the patch did not work) or "4OS2 Revision B" (if
it did work).
If you are short on disk space and receive a message that there is not
enough space to perform the patch, you can use a command like this to
reduce the disk space required:
patch /noundo 4o20b32
This will make recovery slightly more difficult in the unlikely event of
a power failure or similar problem during the patch process, but will
reduce the disk space required to perform the patch.
4OS2 version 2.0 revision B includes the following changes to version
2.0 revision A:
* Fixed date, time, and size ranges so that you can use environment
variables inside a range specification.
* Fixed a problem with using the 4OS2 escape character before a
* DESCRIBE: Fixed a problem where DESCRIBE would exit if you hit
Enter and were describing files with a wildcard file name.
* LIST: Fixed a problem in LIST /S with an empty pipe.
* LOG: Eliminated extra white space prior to the text in a "LOG /H