keyboard failure that doesn't seem to be hardware

[Ed Greshko]

On 10/20/2012 01:50 PM, Paul Allen Newell wrote:
>> On Mon, 15 Oct 2012 16:20:35 -0700
>> Paul Allen Newell <pnewell at cs.cmu.edu> wrote:
>>
>>
>
> This is getting to be way too much "fun" ...
>
> A different keyboard (the one that came with the HP beast) does not have any failure problems after a couple of days of testing. The original keyboard (a MicroSoft Natural from @2001 ... I am under the impression that it has changed since then?) and the HP keyboard show no failure on a F16 machine.
>
> Looks like I get to bring that F16 machine onto F17 and see if the Microsoft Natural suddenly starts having problems.
>
> Obviously, I am beginning to think that a bug has been introduced into F17 that only shows up on my Microsoft Natural keyboard (mind you, I am not assuming that the only two keyboards in the universe are an HP keyboard and an old Microsoft Natural (smile)).
>
> I only post this "status update" in case anyone can see something new (and I am thinking the old Microsoft Natural keyboard ...)
>
>

I've not been paying to much attention to this thread recently.....

Time to put the "failing" keyboard back on the F17 system to verify the problem still exists?


-- 
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled