Last updated: October 25, 2016
As you know, IBM made changes to DOSCALL1.DLL and KBDBASE.SYS in FP13 that broke the PC installer and the PC enhanced keyboard driver. These changes have carried forward to ArcaOS and the Merlin Convenience Pak (MCP) so the same failures continue to occur and the same workarounds continue to apply.
The workarounds allow you to install Process Commander (PC) and use most of its original functionality. You lose the ability to trap the Ctrl-Alt-Del key and to use the other keyboard hooks that depend on the enhanced driver. However, all the kill methods and monitoring features still work as before.
Get C. W. Rose's EXEPATCH. You need EXEPATCH to create the patched DOSCALL1.DLL. The name EXEPATCH is a bit misleading. EXEPATCH is not a general purpose utility. It is a replacement for a broken part of the PC installers. What EXEPATCH does is make a copy of DOSCALL1.DLL and patches the copy exactly as the PC installers would have done, if they still worked.
Make sure EXEPATCH is easy to access. You probably should put it in a directory in the PATH. Once you have PC installed, you might wish to keep a copy in the \pc\bin directory.
If you don't already have Stardock Process Commander FixKit #1, get it now. It is also available at Process Commander FixKit #1 from Hobbes.
If you have PC installed, you must uninstall it before applying any updates to base OS/2 components. This has been true since PC was first released and applies to any update that might replace base OS/2 components. This includes OS/2 Fix Pak's and Device Driver Fix Pak's. If you don't do this, the FixPak install might unexpectedly archive and replace PC's version of the base driver or DLL rather than Warp's.
If you don't have FixKit#1 installed, install it now with the command:
FIX01This will enable you to use PCINSDLL and correct some latent Process Commander defects. The Fix Kit installer may complain that it can't patch DOSCALL1.DLL. Ignore this. DOSCALL1.DLL will get patched later.
Uninstall PC with the command:
PCINSDLL /UNINSTALL_ALL
This removes all references to PC from CONFIG.SYS and the WPS without deleting the installed PC application code.
If you already had PCKBD.SYS installed, PCINSDLL will report this. If so, edit CONFIG.SYS and find the line that reads:
DEVICE=x:\PC\TMP\PCKBD.SYSwhere x: is the PC install drive and REM it out.
Once PC is uninstalled, apply the planned OS/2 updates. When you are ready to reinstall PC, continue from here.
CD \OS2\BOOT COPY KBDBASE.SYS KBDBASE.SAV
INSTPCInstpc may complain that it cannot create the patched DOSCALL1.DLL. Ignore the message. Do not reboot yet.
FIX01FIX01 may complain that it cannot create the patched DOSCALL1.DLL. Ignore the message. Do not reboot yet.
EXEPATCH \OS2\DLL\DOSCALL1.DLL \OS2\PCDLL\DOSCALL1.DLL
CD \OS2\BOOT COPY KBDBASE.SYS KBDBASE.PC COPY KBDBASE.SAV KBDBASE.SYS DEL KBDBASE.TXT
RUN=x:\PC\BIN\PC.EXE DEVICE=x:\PC\PC.SYS /SAFETY DEVICE=x:\PC\BIN\VPC.SYS RUN=x:\PC\BIN\ACTVCOLL.EXE REM DEVICE=x:\PC\TMP\PCKBD.SYSwhere x: is the PC install drive.
DEVICE=x:\PC\TMP\PCKBD.SYS KEYB:CA-F12where x: is the PC install drive. The KEYB setting tells PC to use Ctrl-Alt-F12 as the hotkey to pop up the PC fullscreen.
CD \OS2\BOOT COPY KBDBASE.SYS KBDBASE.SAV
PCINSDLLPCINSDLL will complain that it cannot create the patched DOSCALL1.DLL. Ignore the message.
If you forgot to REM out the PCKBD.SYS line earlier, PCINSDLL will complain that PCKBD.SYS is already installed. Ignore this message too.
EXEPATCH \OS2\DLL\DOSCALL1.DLL \OS2\PCDLL\DOSCALL1.DLL
CD \OS2\BOOT COPY KBDBASE.SYS KBDBASE.PC COPY KBDBASE.SAV KBDBASE.SYS DEL KBDBASE.TXT
RUN=x:\PC\BIN\PC.EXE DEVICE=x:\PC\PC.SYS /SAFETY DEVICE=x:\PC\BIN\VPC.SYS RUN=x:\PC\BIN\ACTVCOLL.EXE REM DEVICE=x:\PC\TMP\PCKBD.SYSwhere x: is the PC install drive.
DEVICE=x:\PC\TMP\PCKBD.SYS KEYB:CA-F12This setting tells PC to use Ctrl-Alt-F12 as the hotkey to pop up the PC fullscreen.
If you want to use some a key combination other than Ctrl-Alt-F12, modify the KEYB: value and try it. Most values other than Ctrl-Alt-Del will work.
When you are done, most of the original PC features will work. The known exceptions, which all depend on the enhanced keyboard driver, include:
Page last changed Tue Sep 20 10:08:52 2011