Archived from groups: alt.sys.pc-clone.gateway2000 (More info?)
I recently attempted to repair a laptop keyboard (Solo 5150) with
partial success. The board was malfunctioning from a spilled beverage.
(1) First I placed the keyboard in a thick, see-thru plastic bag and
then began to remove the plastic "pins." These various layers of the
keyboard are held together by molded pins which are not replaceable.
Once broken, the pins are trash. However, the bag will catch all the
little cups which rest under the keys.
(2) Once disassembled, clean each layer of the keyboard. In my case,
liquid had leaked between the layers of flexible plastic circuit.
(3) Once dry, reassemble the pieces face down, and in their original
order. Don't forget about the small metal clips. Don't worry about the
rubber cups, they will be replaced later. Place something the size and
weight of a stapler in the center of the keyboard and then glue each
missing post with a small, BB sized spot of 5-minute epoxy.
(4) Once the glue has cured, begin the slow process of removing each
key, and placing the rubber cups below each one.
The process takes about an hour. I think the biggest risks are losing
one or more key cups and applying so much 5-minute epoxy that it
squeezes out into the keyboard.
My attempt had only partial success, I was able to fix those keys which
would return multiple letter. However, it appears that the contacts
were also very deteriorated. The laptop had been used for some time in
a very corrosive environment and for some reason it had made the laptop
connections very brittle (although the other contacts appear fine). I've
had to clean the contacts numerous times.
I had ordered a replacement before I even began this rebuild, so it was
only a learning exercise. The smart money is still on a replacement
keyboard. However, I'd be interested if anyone is able to report some
success.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.