Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!killer!dcs!wnp
From: wnp@dcs.UUCP (Wolf N. Paul)
Newsgroups: comp.unix.microport
Subject: Re: Another fine example of support from Microport
Message-ID: <260@dcs.UUCP>
Date: 17 Dec 88 12:50:52 GMT
References: <1702@maccs.McMaster.CA>
Reply-To: wnp@dcs.UUCP (Wolf N. Paul)
Distribution: na
Organization: DCS, Dallas, Texas
Lines: 29

In article <1702@maccs.McMaster.CA> innovus@maccs.UUCP (Innovus Inc.) writes:
>I am one of those people who have this keyboard driver bug. You know the
>one that makes your system go to "control-lock" mode when you type control-S?
>Well, so far all your Tech people have been able to tell me is "Yes, we know
>that is a problem, and we'll take it down as a bug report, but please don't
>ask us when you can expect your machine to be functional again, we don't
>know when we can schedule a fix for this..." Nice example of Customer Support,
>
>Would someone at Microport please tell me:

I'm not with Microport, but maybe this helps (if you have version 2.3 or 2.3.1):

0. Boot from the 2.3 or 2.3.1 kernel.
1. Install the linkkit from 2.3 or 2.3.1
2. Extract modules "kd*.o" from /linkkit/lib2 and move them to a safe place.
3. Delete the 2.3* linkkit.
4. Install the linkkit from 2.4
5. Replace the kd*.o modules in lib2 with the ones you have extracted from 2.3*.
6. Cd into /linkkit/cf and type "make wini".
7. Copy the new kernel to /system5.

And for those folks who do not have the 2.3 or 2.3.1 versions, maybe 
Microport could make these keyboard driver objects available on the BBS?
How about it, John Plocher?

-- 
Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101
UUCP:     killer!dcs!wnp                 ESL: 62832882
DOMAIN:   dcs!wnp@killer.dallas.tx.us    TLX: 910-380-0585 EES PLANO UD