There is a DEVCON script here, for tearing down the USB stack.
http://www.robvanderwoude.com/devcon.php
RenewUSB.bat Remove all USB devices and then rescan for new ones
But I can't tell from your description, whether you have enough control over the
machine right now, to do anything to it.
Another option, might be to attempt the usage of a Restore Point from
System Restore, from Safe Mode. Perhaps that will put things right.
System Restore keeps copies of the registry, so you might go backward
in time 24 hours, and see if it works any better.
http://bertk.mvps.org/html/safemode.html
"System Restore can be run the same as in normal mode. The only difference
is an UNDO restore point will not be automatically created."
I know what your situation feels like, because when I installed my new motherboard
(without a complete set of PS/2 interfaces), I was stuck for the first few minutes
with no working input either. Fortunately, the built-in WinXP drivers rescued
me, before I pitched the box out the window :-)
HTH,
Paul
You can navigate most windows (including Device Manager) using the
keyboard. In general, use the Tab key to move from item to item; use the
cursor (arrow) keys to move up and down; use the "+" key to expand a
category, and use the Enter key to open things--for example, when you're
located on your device in Device Manager, hit Enter and the dialog for
it will come up.
Barry_M wrote:
> Windows XP Pro. SP3
> My mouse stopped working for no apparent reason. Device Manager -> PS/2
> Compatible Mouse Properties -> General [tab] -> Device Status says, "Windows
> cannot start this hardware device because its configuration information in
> the registry is incomplete or damaged. (Code 19)
> Click Troubleshoot to start the troubleshooter for this device."
> Troubleshooter says, "Uninstall and then reinstall your device." To do this
> I must right-click the device in Device Manager and then click Uninstall ->
> Confirm Device Removal -> OK. However, I cannot right-click anything without
> a functioning mouse
It's the context menu key found between the Right hand CTRL and Windows
keys.
"Paul" wrote:
> .
>
Thanks for your reply, Paul.
System Restore has invariably failed without explanation on my computer
since I first started using Windows XP Pro., despite numerous OS
reinstallations and several system hardware changes during that period. I
have given up on it.
Since my posting I found that I am able to uninstall the mouse through
Device Manager, so I do not need DevCon.exe to do that. However, my problem
is not solved because when I uninstall the mouse, restart my computer and
check Device Manager, I find that it shows up again and Device Status gives
the same message.
Barry_M wrote:
>>.
>>
>
> Thanks, Etaoin. I found a page on the microsoft sitecalled "Windows keyboard
> shortcuts overview", and I am getting used to navigating windows without a
> mouse, but it is still a slow and arduous proooocess, and there are still
> many things that apparently cannot be done.
Very few, you will need to use "Mouse Keys" to access the Notification
area Icon.
Bob I wrote:
Whoops, wrong, don't need them there either.
"Bob I" wrote:
> .
>
Thanks Bob; I have learned through the Internet that I can indeed gain
access to the notification area by Windows + B. No doubt I could gradually
learn to do many other things by keyboard if I spent enough time researching
the topic, but this is really a side issue. My primary aim is to get my mouse
working again. Thus far I have found that uninstalling the mouse and
restarting takes me back to square one. The only thing I can think of doing
now is a registry search, since the error message indicates registry
corruption. Is this a good idea? If so, then what should I search for and are
there any areas that I should leave alone?
The first question that comes to mind is do you have the correct driver
for the mouse? The "keyboard" sidetrack evolved in response to "how do
I...?" Now that you can in fact navigate via the keyboard, try removing
mouse and installing the correct drivers for it. You may "Scan for
hardware changes" by pressing the "context menu key" when the computer
name is selected in Device manager (at the top of the list).
"Bob I" wrote:
> .
>
There are three drivers:
C:\WINDOWS\System32\DRIVERS\i8042prt.sys
C:\WINDOWS\System32\drivers\klmouflt.sys
C:\WINDOWS\System32\DRIVERS\mouclass.sys
I do not know whether these are the correct drivers for the mouse.
I'd uninstall the mouse then install msmouse.inf from:
C:\windows\inf
Also I have mouse.drv in C:\WINDOWS\System32\DRIVERS\.
The inf should rewrite your registry keys but you may need to get mouse.drv
from your CD if you don't have it. HTH
Since "My mouse stopped working for no apparent reason.", perhaps you
allowed some "hardware driver update" to be installed automatically? Try
looking in Device Manager at the mouse Properties, Driver, and select
"Roll Back Driver".
"T Shadow" wrote:
> .
>
"T Shadow" wrote:
> .
>
Are you running Windows XP Pro. SP3? I do not have mouse.drv in
C:\WINDOWS\System32\DRIVERS\
"Bob I" wrote:
> .
>
I selected "Roll Back Driver" and received the following message:
---------------------------
No driver files have been backed up for this device.
If you are having problems with this device you should view the
Troubleshooter information. Would you like to launch the Troubleshooter?
---------------------------
Yes No
---------------------------
I ran the Troubleshooter and after I uninstalled and reinstalled the device
it stated:
This Troubleshooter is unable to solve your problem.
In Device Manager, under View, Select Show Hidden Devices, does a second
mouse show up? If so remove both. And then scan for hardware.
I'm using Home but the mouse drivers are the same.
> Are you running Windows XP Pro. SP3? I do not have mouse.drv in
> C:\WINDOWS\System32\DRIVERS\
On my machine here with WinXP SP3, the USB mouse is installed with:
mouclass.sys
mouhid.sys
and my mouse entry says "HID-compliant mouse". I have a Logitech that supports
both PS/2 and USB protocols, and right now it is installed in a USB jack.
No Logitech software is installed, and the drivers are whatever was provided
by Windows.
Sometimes, input devices can be disabled by removing an UpperFilter
or LowerFilter entry for the device by mistake. That typically happens
when a person is trying to get their CD/DVD drive working, they're
searching in the registry for UpperFilter or LowerFilter entries, and
they erase an input device one by mistake. I'm not sure exactly
how that gets put back.
For example, I can see one here. As far as I know, filters are used
as "shims" in a protocol stack, when software wants to intercept something
between layers of the stack. I have no idea, how you tell whether you're
looking at exactly the right one or not. "Mouclass" is suggestive, but
for all I know, it could be from one of my previous mice.
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}
UpperFilters Mouclass
HTH,
Paul