Lem wrote:
> Teriel9 wrote:
>> Hi Bernd,
>> Many thanks for your prompt response, I found a log file which showed
>> which files were loaded, unfortunately it does not tell me the
>> originating process, only whether or not the files were loaded, so I
>> cannot find out which process originates it.
>> Thanks again
>> Teriel9
>>
>>
>> "Bernd" <fake@gmx.de> wrote in message
>> newspPH41Z1KHA.264@TK2MSFTNGP04.phx.gbl...
>>>
>>> -------- Original-Nachricht --------
>>>
>>>> Is there a LOG file which I can access or can I make WinXP Home
>>>> generate one.
>>>> This is further to the lkbdhlpr problem already listed, I would like
>>>> to see which part calls for the loading of this file as it appears
>>>> first in every startup in the Event Viewer.
>>>> I am hoping that by finding out I may be able to prevent it from
>>>> calling for the "lkbdhlpr" process.
>>>> Thanks
>>>> Teriel9
>>>>
>>>>
>>> http://www.windowsreference.com/general/how-to-create-a-bootlog-in-windows-2000xp-and-later/
>>>
>>>
>>> Bernd
>>
>>
>
> Try AutoRuns: http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx
>
> AutoRuns shows virtually every location where a file is loaded at
> startup. If you don't see "lkbdhlpr" in any of the entries shown by
> AutoRuns, then the file probably is being called for by a Logitech
> application that is started automatically.
>
> I suspect that your keyboard should work without the specific Logitech
> software, although its "extra" functionality will not work. Try
> completely uninstalling all of the Logictech software (e.g. iTouch).
> Then reboot and see if the problem occurs. If not, and you want to have
> the additional functionality, download a fresh copy of the software,
> disconnect from the Internet and turn off your antivirus. Then install
> the software. That's essentially what the only post in the Logitech
> support forums has to say:
> http://forums.logitech.com/t5/Keybo...tart-lkbdhlpr-driver-failed-to/m-p/18211#M707
>
As an alternative to uninstalling all of your Logitech s/w, you could
try using AutoRuns to disable (uncheck the box) every entry related to
Logitech. When you reboot, presumably you won't get the lkbdhlpr error.
Then re-enable the Logitech entries one by one until the lkbdhlpr error
returns. This procedure is both tedious (lots of reboots) and not
guaranteed to work, because enabling some but not all Logitech startup
entries may cause other problems.
To be absolutely safe, make a disk image (or disk clone) before you
start messing around. That way, if things go completely south, you will
be able to restore to a working system (even if it does generate the
lkbdhlpr error).
--
Lem
Apollo 11 - 40 years ago:
http://www.nasa.gov/mission_pages/apollo/40th/index.html