A
Alan C. Lawhon
To avoid any confusion, I'll start off by stating that I'm
sending this message from my workplace computer, (NOT my
desktop [home] computer), which is the computer that
actually has the problem.
My desktop computer is running Windows 2000 Pro. I have a
Logitech cordless optical mouse and a Logitech
cordless "iTouch" keyboard for user input. Up until last
night, both the keyboard (and the mouse) had been working
like a champ. However, I started getting some very weird
behaviour from the keyboard last night. (The mouse
continues to work just fine.) There was either
intermittent or no response to keypresses, or weird
responses such as the same character echoing multiple
times, or other "weird" behaviour. This weird
behaviour started rather abruptly, there was no "gradual"
degradation of keyboard funtionality, it happenned rather
suddenly. (Responses were so weird that I initially
thought my computer might be the victim of a virus attack.)
Anyway, this behaviour rapidly got worse until the
keyboard was not responding [to input] at all.
At first I suspected that (maybe) the two "AA" batteries
installed in the keyboard were depleted, so I replaced
them with fresh batteries. This didn't solve the
problem. I clicked on "Keyboard" in Control Panel and
Windows says "... this device is working properly."
Finally, out of desperation, I decided to attempt a fresh
install (reinstall) of the Logitech keyboard software and
device driver from the [Logitech] CD. The reinstallation
appeared to go without a hitch. However, upon rebooting,
the following "Red Circle" error message appears on my
desktop:
EM_EXEC.EXE - Entry Point Not Found
The procedure entry point ?
SetValueData@CRegEntry@@QAEJABVCString@@0@Z
could not be located in the dynamic link library
COMNCTR.dll
OK (button)
NOTE: I unplugged the Logitech keyboard and tried an IBM
PS/2-compatible USB keyboard that I use with my notebook
computer. I got the same "Entry Point Not Found" error
message during bootup.
I don't know what's going on here, but it sounds bad.
Anyway, I can't figure out how to get the keyboard to
respond to input. (I'm restricted to "mouse-only"
operations right now.) I will be very grateful for
any help or suggestions anyone can offer which will get
keyboard response restored. Right now it appears that I'm
dead in the water - as far as keyboard input is concerned.
Alan C. Lawhon
sending this message from my workplace computer, (NOT my
desktop [home] computer), which is the computer that
actually has the problem.
My desktop computer is running Windows 2000 Pro. I have a
Logitech cordless optical mouse and a Logitech
cordless "iTouch" keyboard for user input. Up until last
night, both the keyboard (and the mouse) had been working
like a champ. However, I started getting some very weird
behaviour from the keyboard last night. (The mouse
continues to work just fine.) There was either
intermittent or no response to keypresses, or weird
responses such as the same character echoing multiple
times, or other "weird" behaviour. This weird
behaviour started rather abruptly, there was no "gradual"
degradation of keyboard funtionality, it happenned rather
suddenly. (Responses were so weird that I initially
thought my computer might be the victim of a virus attack.)
Anyway, this behaviour rapidly got worse until the
keyboard was not responding [to input] at all.
At first I suspected that (maybe) the two "AA" batteries
installed in the keyboard were depleted, so I replaced
them with fresh batteries. This didn't solve the
problem. I clicked on "Keyboard" in Control Panel and
Windows says "... this device is working properly."
Finally, out of desperation, I decided to attempt a fresh
install (reinstall) of the Logitech keyboard software and
device driver from the [Logitech] CD. The reinstallation
appeared to go without a hitch. However, upon rebooting,
the following "Red Circle" error message appears on my
desktop:
EM_EXEC.EXE - Entry Point Not Found
The procedure entry point ?
SetValueData@CRegEntry@@QAEJABVCString@@0@Z
could not be located in the dynamic link library
COMNCTR.dll
OK (button)
NOTE: I unplugged the Logitech keyboard and tried an IBM
PS/2-compatible USB keyboard that I use with my notebook
computer. I got the same "Entry Point Not Found" error
message during bootup.
I don't know what's going on here, but it sounds bad.
Anyway, I can't figure out how to get the keyboard to
respond to input. (I'm restricted to "mouse-only"
operations right now.) I will be very grateful for
any help or suggestions anyone can offer which will get
keyboard response restored. Right now it appears that I'm
dead in the water - as far as keyboard input is concerned.
Alan C. Lawhon