SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Sun, 17 Feb 2002 23:47:38 PST7
From:	"Benedict G. Archer" <bgarcher@gte.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: process commander question

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

Steven Levine wrote:
>
> >Following Mr KIA (March 2001) to install PC on a MCP with 10/26 kernel
> >led to a trap d on bootup; couldn't even get to a command line. Booting
>
> This is expected if PC is allowed to install it's keyboard handler.
>
> I checked the SCOUG article and the updated version I maintain at:
>
> http://home.earthlink.net/~steve53/os2tips/ProcessCommander.html
>
> and both appear to match. Did you you use:
>
> PCINSDLL /INSTALL_HOOK /INSTALL_PMSHELL /INSTALL_FS
>
> or
>
> PCINSDLL /INSTALL_PMSHELL /INSTALL_FS

I double clicked the INSTPC.exe icon and selected two of three options
presented, none referred to a keyboard driver.

> Did you run the procedure before attempting to reboot after the install?

Didn't reboot until I had installed PC, installed FIX01, applied the
patch to doscall1 and manually added the suggested line to config.sys.

> >everything, but on bootup PC warns that the alternate keyboard driver
> >isn't installed and issues an emphatic order to install it. But PC seems
>
> Ignore this. I need to update the article to note this will occur.
>
> >on a floppy (I also have fix01 from Stardock on a separate floppy), and
>
> Not quite. Mr. KIA's instructions assume you are updating an existing PC
> install. They do not explicitly cover how to handle a fresh install.
> That said, I can't see why they should not work.

This system never had PC. I will be installing on another new system
soon.
They seem to work. Actually, Mr KIA explains how to install PC when a
full MCP install is done--"Reinstall PC from the CD. Do not install the
alternate keyboard driver."

> >there were no install options related to the keyboard driver. I'm
>
> It's been a while. I thought there was an option to turn it off.
[...]
> to use for a fresh install. I suspect that if you had run the documented
> procedure before rebooting, it would have worked and you would not have
> trapped.

I'm not sure I follow you here. Icouldn't have executed PCINSDLL from a
command line because it was still in a zip file so Idouble clicked the
INSTPC icon. Except for that I did follow your instructions to the
letter. What saved me a lot of trouble was having a saved copy of
kbdbase.sys so I could replace the PC version--your first step was to
copy kbdbase.sys to kbdbase.mcp. However INSTPC also saved kbdbase.sys
as kbdbase.old and left a little text file behind saying that it did
that. If I had replaced kbdbase.sys before rebooting I would have been
OK. I think that's the only thing missing from the instructions. I'm
glad my utility diskettes worked; without them I couldn't get to a
command line.

Ben

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 17 | February | 2002 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.