Re: Event ID 1073 - USER32
- From: Tom Hall <aria1946@xxxxxxxxxxxxxx>
- Date: Thu, 02 Nov 2006 19:19:25 -0700
On Sun, 29 Oct 2006 12:56:36 -0700, Tom Hall <aria1946@xxxxxxxxxxxxxx>
wrote:
In checking back through older logs, I found the first instance of this
event error on Oct. 13
As it so happens, on Oct. 13th I bought a new Logitech G7 cordless mouse
and a new Microsoft natural keyboard.
The Setpoint 3.10 installer apparently disregarded the existence of other
Logitech software, as the Mouseman installation was not touched. The only
visible change was the registry replacement of em_exec.exe with
khalmnpr.exe.
I uninstalled the Setpoint software and re-installed the Mouseman software,
and ran with the old mouse for a few hours. I decided to test out my theory
that the Event ID 1073 may be caused by something gone amok in the mouse
driver. There was no Event ID 1073 or any derangement of the restart
process, so I shut down the computer and swapped back in the G7 mouse.
After restarting the system, I first uninstalled the Mouseman software
(which forced a system restart) and then re-installed the Setpoint package.
I'll muck around for a few hours and then see what happens when I restart
the system.
Interesting footnote: the new Microsoft keyboard apparently does not
support DOS mode, as I discovered when I tried to boot from a DVD I knew to
be bootable. As soon as I put back the older keyboard (also Microsoft, but
with PS2 connection), voila! the DVD booted.
I'll think twice before I go shopping again for computer accessories on
Friday the 13th... :-)
.
- Follow-Ups:
- Re: Event ID 1073 - USER32
- From: Tom Hall
- Re: Event ID 1073 - USER32
- Prev by Date: Re: Find RAM size fast. TIA
- Next by Date: Re: Regedit copy/paste
- Previous by thread: When MSFT stops supporting XP?
- Next by thread: Re: Event ID 1073 - USER32
- Index(es):
Relevant Pages
|
