O.T. Missing Folder/files
Robert in CA wrote:
Understood
I assume my scans were OK then, otherwise you
would of mentioned something.
I sure hope the keyboard resolves the problem otherwise
I think the only other option open to us at this point is to
buy another non-Microsoft keyboard as I mentioned earlier.
Perhaps I should of done that in the first place?
Robert
Without knowing the root cause of the Backspace problem,
I can't guess what the cure will be. The controller chip
inside keyboards is not made by Microsoft, and more than
one brand of keyboard could be using the same controller.
They program the PNP identifier to "brand" the product,
but the behavior is determined by the chip, independent of
the identifier used.
Certain failure modes will point at a hardware-based cause.
The keyboards generally always use a scanning matrix. The
row wires and column wires don't follow a "pure rectangular"
pattern. Like I could wire 1-Q-A-Z as a column wire, but
maybe I need more items on the wire than that. Maybe the
matrix is 7x17. If suddenly 1-Q-A-Z stopped working, you'd
say "oh, that's a column wire".
The Backspace probably has "friends" too, but unless you notice
a very weird pattern of seven keys that stopped working
or seventeen keys that stopped working, that's probably not it.
An individual key could fail of course, if some debris got
inside it. But not both keyboards on both machines. That
tells us you have a common utility you use on both of
them, which is doing this. I've had a few keyboards here,
and I don't recollect any "correlated" failures. Each keyboard
will develop its own bad habits, if it's a hardware cause.
*******
Your hard drives don't show anything to be alarmed about.
You can use the Health tab, and note whether the "Reallocated"
Raw Data column still has a value of zero, as that's a good
indicator of health too.
Paul
|