Dec 272017
 
Fixes many problems with OS/2 2.1.
File PJ09986.ZIP from The Programmer’s Corner in
Category OS/2 Files
Fixes many problems with OS/2 2.1.
File Name File Size Zip Size Zip Type
DOSCALL1.DLL 91032 38861 deflated
INSTALLF.EXE 81408 35062 deflated
MOD 95 71 deflated
MODULE.LOG 480 159 deflated
OS2KRNL 738648 428591 deflated
README.1ST 15431 4849 deflated

Download File PJ09986.ZIP Here

Contents of the README.1ST file


*****************************************************************************

(Please note that before installing this fix you must first go to the drive
where OS/2 is installed and then enter the following:
>ATTRIB -S -H -A -R OS2KRNL
after you have installed the fix using INSTALLF
enter the following:
>ATTRIB +S +H +A +R OS2KRNL

******************************************************************************
APAR PJ08161
TRAP 000D AT 0150 : 00005E79 IN MKNODE$BLANKSBEFOREDOT IN
IN 6.466 (SP) KERNEL -- 160 : 6DA5 IN THE DEBUG KERNEL.

APAR PJ09906
LOTUS NOTES 3.0 TRAPS THE LOTUS NOTES SERVER WHEN RUNNING THE
CHRONOS MACRO

APAR PJ09081
RING 0 TRAP REGISTERS NOT DISPLAYED

APAR PJ09736
TRAP 0008 AT 0160 : FFF5EED4 OR FFF5EED3 REVISION 6.514

APAR PJ10456
LOADER INIT IS EXECUTING DLL INIT'S IN INCORRECT ORDER CAUSING TRAP

APAR PJ10641
DOS EDIT PROGRAM FAILING ON PENTIUM MACHINE.

APAR PJ10202
IPE IN 2.0 AND 2.1 DUE TO RSC: SFT NOT IN SFT LIST


APAR PJ06367
CUSTOMER CANNOT USE TURBO DEBUG IN WINOS2

APAR PJ10274
TRAP 000E AT 0160 : FFF793BF INTERNAL REVISION 6.514 AT
_TKWAITTHREAD + B9

APAR PJ10275
PERF HOOKS IN KERNEL NOT FREING ALL ALLOCATED MEMORY.

APAR PJ10163
PC SUPPORT - MULTIPLE DPMI CLIENTS DO NOT RUN IN ONE VDM - THEY
CAUSE TRAPS.

APAR PJ09700
ERROR ON PAGEFAULT OF 16 BIT SHARED RO SEG DATA WITH LDR FIXUPS

APAR PJ09643
TRAP 000D CS:EIP 0140 0000B853 CSLIM 0000E973 RUNNING
RM *\*\FILENAME PRORGRAM FROM MKS DEVELOPERS TOOLKIT.

APAR PJ09563

IPE AT 0160 : FFF5DA0A INTERNAL REVISION 6.466. IPE IS
RMN: MFT_LPTR OR MFT_SPTR FIELD NOT 0 IN DEBUG KERNEL

APAR PJ09481
DOSKILLTHREAD RETURNS RC != 0 EVEN WHEN SUCCESSFUL

APAR PJ09026
UNABLE TO TAKE DUMP IN 2.1. C/A/NL-NL DOESN'T DO ANYTHING.

APAR PJ09050 DOS APPS LIKE DOSKEY, LOTUS, ETC. PULSE SHOWS 100% CPU
UTILIZATION EVEN THOUGH APPLICATION IS DOING NOTHING. DOSAPAPAR

APAR PJ09970
FS REG BEING SET TO 0 BY FAILURE OCCURRING DURING DOSMUXSEMWAIT.

APAR PJ09695
DOS APPLICATIONS HOOKING INT 08 OR INT 1CH FAILING WITH
LOCKUP OR TRAP 000D ON PENTIUM PROCESSOR EQUIPPED MACHINES.

APAR PJ08837
LOTUS 2.4 FILE RESERVATIONS NOT WORKING UNDER OS/2 V 2.1 & SERVI
CE PACK # 1. INT 21 FUNCTION 440A FAILING DOSAPAPAR

APAR PJ08412
LOST SYSTEM SEMAPHORE NAME

APAR PJ09138
PAGE MANAGER CORRUPTS PAGE TABLE LINKED LIST

APAR PJ05253
TRAP D WHEN RETURNING FROM DOSQPROCSTATUS

APAR PJ08658
UNDOCUMENTED RESTRICTION IN CONFIG.SYS

APAR PJ09138
PAGE MANAGER CORRUPTS PAGE TABLE LINKED LIST

APAR PJ09666
VDISK OS2 2.1 MOD 77 HPFS HANGS FOR SIZES GREATER THAN 11M ON
SOFT BOOT. COLD BOOT WORKS OK.

APAR= PJ09122
IPE 7028 236 VDMTIME:VDHARMTIMERHOOK 6.514

APAR PJ09191
TRAP 000E AT 0160 : FFF5FC82 IN 6.514 KERNEL

APAR PJ09893
NETVIEW MONITOR APP. GIVES TRAP D ON DIRTY HPFS

APAR PJ09537
INT 21 440E FOR A CDROM DRIVE IS NOT COMPATIBLE WITH DOS

APAR PJ09478
TRAP 000E CS:EIP 0160 : FFF8D109 OR FFF8D10B

APAR PJ09643
TRAP 000D CS:EIP 0140 0000B853 CSLIM 0000E973 RUNNING
RM *\*\FILENAME PRORGRAM FROM MKS DEVELOPERS TOOLKIT.

APAR PJ09215
DOSPEEKNMPIPE RETURNS STATE=4 DURING 1ST DOSCALLNMPIPE

APAR PJ08496
DIRTY SHUTDOWN ON HPFS386 VOLUME CORRUPTS DISPLAY ON BOOT IN XGA
MODE ON 8515 WITH XGA-2 CARD.

APAR PJ10247
NAMED PIPE CONNECTION BROKEN WHEN THIRD WINDOW GIVEN FOCUS.

APAR PJ09986
SYS3171 IN DOSCALL1.DLL WHILE PRINTING CS:EIP 005B : 1A02CA39

SS:ESP 0053 : 012A00C8

APAR PJ09657
SYS 3171 OS/2 SYSTEM ERROR DUE TO INSUFFICIENT STACK
SPACE DOSCALL1.DLL

**** DISCLAIMER ****************************************************************

This fix will only be supported until the release of the Service Pack for OS/2
2.1 which contains it. At that time, to receive continued support you should
obtain that Service Pack.

********************************************************************************

INSTALLF.EXE --

Please read the following information about the fix installation program BEFORE
you attempt to install the fixes provided. The ABSTRACT explains how the fixes
are applied to your system, and how they are managed so that additional fixes
can be applied in the future. Following the ABSTRACT are the installation
instructions, complete with examples of how to invoke the installation program.
Following the installation instructions are the descriptions of the fixes you
have received and the OS/2 system module being fixed.

ABSTRACT:
---------

The fix diskette you received contains the following files:

INSTALLF.EXE -- the fix installation program.

MODULE.LOG -- input file that tells the installation program which OS/2 system
modules are being fixed, the file containing the fix for each
module, and the location of the modules following an OS/2 2.1
installation.

*.* -- the modules containing the fix for each APAR described above.

README.1ST -- this file, which contains the description of each APAR fixed in
the modules provided, an explanation of the files contained on
the diskette, an explanation of how fixes are applied to your
system, and instructions on how to invoke INSTALLF.EXE.

Presently, the fixes provided are new full-sized system modules, which will
replace the corresponding OS/2 2.1 GA-level system modules. Eventually, fixes
will be applied to your system modules using "patches" instead of replacing them
with new full-sized system modules. A patch can ONLY be applied to an OS/2 2.1
GA-level system module, so it's important that you follow the instructions
provided so that fixes can be applied in the future to both system modules that
have already been fixed and those that haven't. INSTALLF.EXE will "archive" the
system module being fixed to either your disk or a diskette. One of the
parameters you specify when invoking INSTALLF.EXE allows you to choose the drive
where you want the files archived, but whatever you choose, it is absolutely
necessary that you maintain these files as they will be needed each time you
want to apply fixes to your system. For example, if you specified D:, the
modules would be archived in D:\ARCHIVE.

When a fixed system module replaces the corresponding OS/2 2.1 GA-level system
module for the first time, the OS/2 2.1 GA-level system module is saved in the
\ARCHIVE directory of the drive you specified when invoking INSTALLF.EXE. This
is considered the "current" fix. If the same system module needs to be replaced
again, the current fixed system module is backed-up on the same drive you
specified to archive files to, and the new fixed system module is copied to the
directory where the current system module had been. For example, if you
specified D:, the current system module would be saved in D:\BACKUP.

**** NOTE 1 ********************************************************************

Presently, "true" Backout is not supported in INSTALLF.EXE. If you have a need
to return your system to the OS/2 2.1 GA-level (ie. you need to reinstall a fix
due to some failure), you will be required to copy the OS/2 2.1 GA-level module
you need from the \ARCHIVE directory into the directory where the corresponding
system module exists. If you have a need to return your system to a previous fix
level, you will be required to copy the system module you need from the \BACKUP
directory into the directory where the corresponding system module exists.

**** END NOTE 1 ****************************************************************

INSTALLF.EXE maintains a record of all fixes applied to your system in the log
file LOGU001.OS2. This log file is maintained on the same drive where you have
OS/2 2.1 installed, and in the directory \OS2\INSTALL. Another parameter you
specify when invoking INSTALLF.EXE is the drive where OS/2 2.1 is installed. For
example, if OS/2 2.1 is installed on the C: drive, the log file would be
maintained in C:\OS2\INSTALL.

**** NOTE 2 ********************************************************************

IT IS ABSOLUTELY NECESSARY that you maintain the location of the 2 items just
described to you: 1.) the archived OS/2 2.1 GA-level system modules, and 2.) the
log file LOGU001.OS2. The archived system modules and the log file are REQUIRED
each time you want to apply fixes to your system. If you specified the disk
drive on which you want to store the system modules, DO NOT delete the directory
\ARCHIVE, AND, DO NOT delete the directory \OS2\INSTALL where the log file is
stored. If you specified a diskette drive on which you want to store these
files, DO NOT erase the contents or lose the diskettes. If these files are not
available, you will have to re-install the OS/2 2.1 GA-level diskettes if you
want to apply new fixes.

**** END NOTE 2 ****************************************************************



KEY PROCEDURES PERFORMED BY INSTALLF.EXE:
-----------------------------------------

1.) ARCHIVING -- This is the process of storing an OS/2 2.1 GA-level system
module in the directory \ARCHIVE on the specified logical
drive.

2.) BACKING-UP -- This is the process of saving current fixed system modules
that exist from previous fixes in the directory \BACKUP on the
specified logical drive. If there is ever a need to return the
system to a previous fix level, then you can copy the system
module you need from this directory into the directory where
the corresponding system module exists.

3.) SERVICE LOGGING -- INSTALLF.EXE maintains a record of all service activity
performed on your system in the file LOGU001.OS2.
INSTALLF.EXE requires this file to determine if fixes
have ever been applied to your system, and if so, where
to locate the files that have been stored. If you are
installing multiple fixes from a pervasive 'pak',
INSTALLF.EXE will record the service information to the
temporary file LOGU001.BAK. When all fixes have been
applied, LOGU001.BAK will be written to LOGU001.OS2. If
you interrupt INSTALLF.EXE while it is applying fixes, do
not erase LOGU001.BAK. INSTALLF.EXE needs this file to
continue applying fixes when you re-run INSTALLF.EXE.



INSTALLATION INSTRUCTIONS:
--------------------------

**** NOTE 3 ********************************************************************

INSTALLF.EXE will attempt to copy the fixed system module into the path where it
was installed during the installation of OS/2 2.1. If the file does not exist in
the assumed path, you will be prompted for its location. For example, if the
file being replaced is actually located in \OS2\DLL_BAK, you would enter that
path-name when prompted.

**** END NOTE 3 ****************************************************************



1.) If the system module being fixed is being used by the operating system, it
will be necessary to do the following so that a patch can be applied:

a.) Start your system using the OS/2 2.1 Installation Diskette.

b.) When prompted, insert Diskette 1.

c.) When prompted to continue or escape, press the ESC key to get to a
command prompt. Continue to step 2.



2.) To install the fixes, type the following at the command prompt and then
press enter:

INSTALLF source dest arch-back

where:

source is the source drive where the files from the fix diskette can be
found. INSTALLF.EXE can apply the fixes from either your disk
drive or diskette drive. If you choose to apply the fixes from
your disk drive, make sure you copy ALL files from the fix
diskette to the disk drive. For example, if you copied the files
from the fix diskette to C:\FIX, then source would be C:\FIX. If
you want to apply fixes from the diskette drive, then source
would be A:.

dest is the drive letter of the system partition where OS/2 2.1 is
installed. For example, if OS/2 2.1 is installed on C:, then
dest would be C:.

arch-back is the logical drive where you want the OS/2 2.1 GA-level
modules that are being fixed stored, AND, where fixed modules
from previous fixes are backed-up. The directories \ARCHIVE and
\BACKUP will be created. For example, if you want these files
stored on your D: drive, then arch-back would be D:. If you want
these files stored on a diskette in your A: drive, then
arch-back would be A:.

EXAMPLE: If you choose to install the fixes from your A: diskette drive,
and OS/2 2.1 is installed on C:, and you want \ARCHIVE and \BACKUP
on your D: drive, then you would enter the following:

INSTALLF A: C: D:



As soon as INSTALLF.EXE has been started, it is important that you allow it to
finish installing all of the fixes that you have received. The message "Fix
successfully installed" will be displayed when the installation is complete. If
this message does not appear, or INSTALLF.EXE ended for some other reason,
please follow the error message and re-run INSTALLF.EXE if necessary.



3.) The service log maintained in \OS2\INSTALL\LOGU001.OS2 is stored in an
unreadable format. If there is a service requirement to view the service
log, you can view the log file by entering the following:

INSTALLF drive

where:

drive is the drive where OS/2 2.1 is installed.

EXAMPLE: If OS/2 2.1 is installed on the C: drive, you would enter the
following:

INSTALLF C:

If you would like to print the log file, simply redirect the output of the
previous command to a print device attached to your system. For example:

INSTALLF C: > lpt1:

**** NOTE 4 ********************************************************************

We suggest that you store INSTALLF.EXE on your disk drive so that if you ever
need to view the service log, the program is available to do so.

**** END NOTE 4 ****************************************************************


 December 27, 2017  Add comments

Leave a Reply