Category : OS/2 Files
Archive   : OS2KRNL.ZIP
Filename : README.1ST

Output of file : README.1ST contained in archive : OS2KRNL.ZIP


Filename Size Date Time
OS2KRNL 716884 6-17-92 10:27a

This KERNEL file contains fixes for these following problems:

APAR PJ03686 / PTR B736191
PROBLEM SUMMARY: OS/2 2.0 Swapper.dat file does not shrink.

APAR PJ03733 / PTR B752328
PROBLEM SUMMARY: When two or more processes perform DOSDELETE function
to the same server while using UNC file path names OS/2
system will deadlock. The processes deadlocked include
any DOS file I/O which require access to the same drives.

APAR PJ04081 / PTR B735516
PROBLEM SUMMARY: IPE occurs at location 150:4912 which is a "rep stosd"
inside the BlastSFT. (AUTOCAD problem)

PTR AA04936
PROBLEM SUMMARY: System creates a data block for the unsucessful attemps
to open a file.

PTR AA05235
PROBLEM SUMMARY: MEM.qlqresident and MEM.qlqfree constantly increase and
never decrease.

APAR JR05522 / PTR B736359
PROBLEM SUMMARY: When the server system is upgraded to LAN service 2.0,
the system TRAP D intermittenly at CSLIM:C27E, CS:230 and

APAR PJ04635 / PTR B736621
PROBLEM SUMMARY: DOSRENAME not deleting source file (Cross link files problem).

PTR B736650
PROBLEM SUMMARY: Increase DosRmDir integrity.


Note: The current OS2KRNL will be renamed to OS2KRNL.OLD.

This fix requires the KERNEL FILE to be replaced in the 2.0 system.
To replace the kernel file follow these steps:

1. Change drive and directory to where fixes are located.

2. Enter FIXKRNL X: Y:
X: is the drive where the OS/2 2.0 is installed
Y: is the drive where the fixes are located
(Specify the subdirectory name if fixes are
located in a subdirectory).
Ex: FIXKRNL C: A: or

3. Reboot your system.

  3 Responses to “Category : OS/2 Files
Archive   : OS2KRNL.ZIP
Filename : README.1ST

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: