home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-385-Vol-1of3.iso
/
4
/
4os10d.zip
/
PAT10D.DOC
< prev
next >
Wrap
Text File
|
1992-09-30
|
8KB
|
204 lines
JP Software
4OS2 1.0 rev A / B / C ==> rev D Patch Documentation
September 30, 1992
Copyright 1988 - 1992, JP Software Inc., All Rights Reserved. Published
by JP Software Inc., P.O. Box 1470, E. Arlington, MA 02174 USA, (617)
646-3975.
This file explains how to install the 4OS2 1.0 rev D patches for 4OS2.EXE
and SHRALIAS.EXE.
To use these patches, you must have the PATCH.EXE program uploaded by JP
Software. This program is in a separate file, PATCH.ZIP or PATCH4D.ZIP
(depending on your download source). Instructions for running the PATCH
program are in the file PATCH.DOC which is distributed with PATCH.EXE.
PATCH.EXE should be in the same directory as the files to be patched, or in
a directory on your PATH.
Before using these patches, you must determine the revision level of your
copy of 4OS2. To do so, use the 4OS2 command:
VER /R
and find the "4OS2 revision level" in the output. If you have a downloaded
copy of 4OS2 you probably have revision B; if you have a copy supplied on
diskette you probably have revision C. (NOTE: If you have 4OS2 version
0.95, these patches will NOT work! You should upgrade to version 1.0 as
version 0.95 is now obsolete.)
There are three patch files:
PAT10B.RTP Updates 4OS2 1.0 to revision level B from level A
PAT10C.RTP Updates 4OS2 1.0 to revision level C from level B
PAT10D.RTP Updates 4OS2 1.0 to revision level D from level C
You should apply the appropriate patch files, in sequence, for the revision
of 4OS2 you are currently running:
If you are running Then apply patch files in this order
------------------ ------------------------------------
revision A PAT10B then PAT10C then PAT10D
revision B PAT10C then PAT10D
revision C PAT10D only
The level B and C patch files modify 4OS2.EXE only. The level D patch file
modifies 4OS2.EXE and SHRALIAS.EXE. Branding (name and serial number)
information in your original 4OS2.EXE file will be preserved in the
modified file.
To apply a patch, copy the corresponding .RTP file to the directory where
4OS2.EXE and SHRALIAS.EXE are stored. Then exit from all sessions running
4OS2, start a DOS session, change to the 4OS2.EXE / SHRALIAS.EXE directory,
and enter the command:
patch <patch file name>
where <patch file name> is PAT10B or PAT10C or PAT10D.
[Some of our documentation for PATCH.EXE shows a period between the program
name (PATCH) and the patch file name, for example:
patch . pat10d
This period may be used but is not required.]
PATCH.EXE is a "bound application" and will run in an OS/2 session, but
OS/2 will not allow you to modify 4OS2.EXE while it is in use; this is
why we recommend performing the patch in a DOS session.
The revision D patches fix the minor bugs and anomalies in 4OS2 1.0 which
are listed below. These problems are small and have not affected most
users.
Revision B:
* Descriptions were not always properly deleted when a file was
deleted.
* 4OS2 did not terminate properly when it reached the end of a
redirected input file (eg 4OS2 < cmdlist).
* DOS sessions did not always start properly when using START /DOS
with COMMAND.COM (rather than 4DOS) as the DOS command processor.
* If 4OS2 was passed a quoted string on the startup command line, it
trapped (SYS3175 error). This would happen if you added 4OS2 to
the Workplace Shell System Menu and OS/2 was booted from an HPFS
drive.
Revision C:
* REXX scripts that checked the number of arguments didn't work
properly when there were no arguments.
* The DRAWxxxx commands did not work correctly when drawing a line
in the rightmost screen position.
Revision D (changes affecting both 4OS2 and 4DOS):
* Key reassignments did not work properly for a few non-ASCII keys.
* F3 left incorrect characters on the command line when the new
line was longer than the original line.
* Leading whitespace on the command line was causing problems with
command completion.
* Testing for too many nested environment variables did not always
work correctly.
* Netware volume labels longer than 12 characters were not handled
properly.
* COLORDIR would not work properly when there were more than 64
extensions in the COLORDIR setting.
* %@EVAL returned random values when given invalid expressions like
%@EVAL[+]. Also %@EVAL was not checking for invalid numbers like
"1.1.1".
* The ? command did not allow output redirection.
* COPY did not work properly when appending very large files.
* DEL /Q was not returning a proper internal error level.
* DIR could cause a crash if it ran out of memory during a DIR /S.
* FOR /A caused conflicts when the FOR invoked a DIR /A. Also
conflicts could occur between FOR and SET in rare circumstances.
* Conflicts between FOR and SET have been fixed.
Revision D (changes affecting 4OS2 only):
* A startup command line passed to 4OS2 beginning "@name" could be
handled incorrectly if "name" was the name of a command and not the
name of an INI file.
* There were several minor problems with the REXX interface:
- Piping did not always work properly in REXX files.
- REXX did not always get the proper return code when executing
4OS2 commands.
- Ctrl-Break was disabled during REXX scripts.
* Ctrl-C and Ctrl-Break did not always work properly with recursive
file processing and directory commands (e.g. COPY /S or DIR /S).
* When a floppy disk was removed from the current drive 4OS2 would
display two errors rather than one.
* The "Cancel batch job" prompt sometimes ended up in redirected
output. It will now go to screen even if both STDOUT and STDERR are
redirected.
* Semicolons did not work in file names, because 4OS2 interpreted them
as separators in an include list. They can now be used if they are
in brackets -- for example abc[;]def is valid syntax for the name of
a single file (abc;def). Semicolons still won't work if they are
out in the open, even inside double quotes.
* Filename completion did not always work properly with HPFS quoted
names.
* Nested pipes could have problems if one of the programs in the pipe
sequence did not shut down properly.
* Icons for external programs started from 4OS2 were not always
displayed while the program was running.
* The @LINE and @LINES functions would hang if the file was over 255
bytes long.
* Arguments to variable functions were limited to 255 characters; the
correct limit is 511 characters.
* DIR output was sometimes misaligned on HPFS volumes. Also directory
colorization was not disabled when redirecting DIR output to a
device other than the console.
* COPY sometimes handled appending files incorrectly when no
destination name was specified (e.g. COPY FILE1+FILE2).
* HELP ON and HELP OFF now call the standard OS/2 file HELP.CMD, and
are not handled internally. Also HELP xxxnnnn was not working
unless "xxx" was "SYS" -- for example, HELP REX0003 did not work.
* SHRALIAS required both alias and history lists to be global. Now
SHRALIAS will work if either list is global, and will only fail if
both are local.