Path:
eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.o
rg!.POSTED!not-for-mail
From: Paul 
Newsgroups: microsoft.public.windowsxp.general,alt.windows7.general
Subject: Re: Still ... Keyboard problem
Date: Sun, 12 Nov 2017 17:13:01 -0500
Organization: A noiseless patient Spider
Lines: 50
Message-ID: 
References: 
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 12 Nov 2017 22:13:00 -0000 (UTC)
Injection-Info: reader02.eternal-september.org;
posting-host="e0f8c23c4ac5e5fc899797d5779c788e";
 logging-data="23006";
mail-complaints-to="abuse{at}eternal-september.org";
posting-account="U2FsdGVkX18AiUlBUXLgbALmqDXMX9aYJK8eR9VdiqQ="
User-Agent: Ratcatcher/2.0.0.25 (Windows/20130802)
In-Reply-To: 
Cancel-Lock: sha1:EAegUIkumTpl74ypIatewJmKeTM=
Xref: feeder.eternal-september.org microsoft.public.windowsxp.general:134500
alt.windows7.general:163171

FreeMan wrote:
> Lenovo T500
> Win XP Pro  all updated
> mfr drivers.
> 
> One time out of 25 when I cold boot the keyboard is unresponsive Meaning 
> hit a key and nothing happens.
> 
> ReBoot and all is well using the mouse.
> 
> Trouble shooter says nothing wrong.
> Using the standard keyboard driver.
> 
> Things like the mouse and fingerprint scanner work just fine at the time 
> the keyboard is not there.
> 
> Suggestions please.

So the fingerprint scanner is what makes you different
than all the other users here...

Is it a HID device, or some other type of device ?
What does Device Manager show for the fingerprint scanner ?

Some devices use a "filter driver" and if the driver
is poorly written, it could latch onto *all* the HID
devices, with less than predictable results. This
seems to be a problem with the HID ecosystem and
its practice of using aggressive filter drivers.
(The driver writer doesn't use Plug and Play properly.)

It might be the order of discovery when the OS boots,
which gives slightly different results, once in a while.

If the fingerprint scanner has a "disable" in the BIOS,
you could try using that control. But if the error
only shows up, once in every twenty five boots,
it's going to take a hell of a lot of reboots
to determine that made a difference.

If you're using the fingerprint scanner for authentication,
it might not be feasible to immediately disable it. It might
take some futzing, to return the system to regular
authentication or something. Don't be in too much of
a rush to disable that, unless you know how it works,
or whether it is currently being used... and so on.
It's pretty hard for me to guess here, what "traps"
await you :-)

    Paul
--- Platinum Xpress/Win/WINServer v3.1