Microsoft Wireless KB/Mouse 700 Should Not Need Drivers But XP Asks for a Driver

Microsoft Wireless KB/Mouse 700 should not need drivers but XP asks for driver that does not exist. I have a Wireless Optical Keyboard 700 v2.0 which did not come with any driver CD, and worked fine on an old XP Pro desktop before I got rid of that computer. I believe I also used to use it on the XP Pro (32-bit) laptop that is giving me problems now, but am not sure. However, I tested it on the Win7 laptop I normally use, and it works fine.

When I plug the receiver into either port of the trouble laptop, the New Hardware Wizard launches. It recognizes the device properly, but wants a driver. After HOURS of searching I have confirmed that the device neither HAS nor NEEDS a driver; it even specifies that on the Technical Data Sheet. But the XP on this laptop will NOT install the device without a driver that does not exist.

I planned to sell this in a garage sale tomorrow, but I do not want to saddle a buyer with the headaches I am having now. Can you tell me how to tell the NHW program "we don't need no stinkin' drivers" so it will understand?

m> Microsoft Wireless KB/Mouse 700 should not need drivers but XP asks
m> for driver that does not exist.

All hardware requires drivers but the drivers for this are usually
built into WinXP so the first time the device is plugged in it can
find what it needs. Something is evidently missing in WinXP so that's
why it asks for a driver. Try putting a WinXP CD in the drive and when
it asks for the driver point it to the CD drive - might pick up
automatically or you may need to navigate to the i386 folder.

That's why you can't find them to download, they are supposed to be
already there :-)

I had the same issue with a kingston wireless keyboard/mouse about a year
ago --- never found a solution - please let us know if any of the
suggestions work --- i would love to go back and 'impress' the frustrated
client

Simple Charles, the problem is with your XP installation. (See Barry's post). You do not need to reinstall if this the only issue; when the Wizard asks for the driver (which all hardware does need), put the XP CD in your optical drive and direct the Wizard to the drive when it asks for the driver.

What SP is your XP Pro ?
I have 3 wireless keyboard/mouse units, and they never have asked for drivers.
I have SP3 in all of my PCs, and the PCs (and neighbor's Laptops) just work, when I plug them in.
Buy a Logitech Wireless keyboard/mouse MK260
$23 in Australia, so would be cheaper in US (everything is)
If it works, demonstrate it to the buyer, and then remove it for yourself (I love them).

I suggest you go to "Windows Update", find selection which asks if you want to download non-OS updates

There is a check box which will allow Update to download drivers for keyboard, mouse, NIC cards, applications. If you are still running original XP, without the latest SP (SP3) was the released quite a while ago. It is the last (Microsoft claims they are serious this time). He mouse you are using was no even in production or invent when XP was first released.

If I am not mistaken, this is a symptom of not performing a "complete" install. Many people, when installing Windows, choose to load only those drivers that are needed at the time the install is performed. While a complete install ensures that all the drivers that come with the Windows are saved onto the hard drive and are available when hardware changes and the drivers for this different hardware are needed. Otherwise, the Windows disk is needed to find the drivers that were not loaded on the hard drive. I guess people think that not loading all of the drivers is saving them space, when in reality, they are worrying about grains of sand on the beach.

Thanks for the Windows CD suggestion. Although I do not have one for this computer, and can no longer create one due to the C:\i386 folder having been deleted (probably by some "cleanup" program I ran in the past couple of years!), I was able to borrow one from a friend, but the New Hardware Wizard did not find any files there either. Fortunately, I do not plan to keep the device for my own use, I only needed to prove it works on XP and Win7, and my friend connected it to HIS XP laptop and it worked fine. So I can tell the buyer it should install automatically, and if not I can take it back. We have another yard sale date coming up in 4 weeks, and if I manage to stumble around and get it working before then fine, if not the question is academic.

BTW, one reason it didn't work is that the original Windows device manager on this machine has a category for keyboards and one for "mice and other pointing devices", with the built-in hardware listed for each; but neither device manager nor the device type list that comes up in NHW has the correct category "human interface devices", and I suspect that rather than allowing the device to be installed in keyboards and mice separately, it can only install in the hybrid category.

If anyone has any additional ideas, I may test them when lots of time is available, but there is no pressure. The main benefit to me now is "learning" more about Windows internals.

m> I believe "Human Interface Devices" deals with such things as touch
m> screen, and devices for the disabled.

It also is the generic term for anything that you plug into a port and
use to provide input to the system so mouse and keyboard are included
in that definition. The key here appears to be the missing i386 folder
and that's going to have all sorts of ramifications when anything at
all changes in WinXP as this is where it will look for the relevant
DLL's etc to cope with the change.

Without a WinXP CD of the same version ( i.e. Home or Professional )
to copy the i386 folder from then this system is going to have many
problems in the long run and eventually it will need this CD to keep
it running. Some day it will hit up against a missing file and come
crashing down :-(

Thanks, didn't know that. I was guessing, I guess, as to why those categories didn't include his needs.
But we both know that you are right when it comes to his needing the relevant CD.
Any changes with the OS, including on his part (such as new Hardware, etc.).
I myself find it difficult to understand why or how a Cleanup program could remove the i386 folder.
Got it,
Barry.

m> I myself find it difficult to understand why or how a Cleanup
m> program could remove the i386 folder.

No program that I know of would do that, but there's nothing to stop
the determined used from doing it - and it's a tempting target if the
aim is to gain free space on a full HD though the real problem is too
small a drive for the needs of the user. Best fix for that is a larger
drive but not everyone has the funds to do that so deleting large and
'unused' folders is tempting !

Barry, I wish I remembered the name ... I do remember a Windows2000-era disk cleanup / tweaking program that gave the option to delete the \i386 folder under the 'disk space' option. I don't know of any released since that do it, but it may also be a lesson regarding using legacy utilities.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.