Standard 101 Keyboard Driver Download
Gisberto Ries
Why does the Windows device manager show my laptop keyboard as a Standard PS/2 Keyboard on one laptop and as a HID Keyboard Device on the other, even though I already know that it is only connected via a ribbon cable directly to the motherboard and none of the doesn't it use the interfaces mentioned above? Is this perhaps a mistake?
There is no reason for them to use those connectors within a laptop, but there are definitely convenience reasons to use the communications protocol such as the electrical signalling and communications methods within a device. There may be an off-the-shelf keyboard (or one that they have already designed) that uses one protocol or another. They may already have drivers that they know works for one device or another within the laptop that can talk to whatever keyboard they have.
Just because there is a ribbon cable does not mandate any given protocol or connector type either. All you need to do is be aware of the general design rules and signal integrity requirements for that electrical signal. I've personally designed ribbon cables that run USB, Ethernet and and other signals and never used a "standard" USB or RJ-45 socket.
The keyboard needs to work out of the box in almost all situations, because without a working keyboard it's rather hard to complete the installation of an operating syste or to fix the problem of not having a working keyboard. This applies both when the firmware/bios is in control of the hardware, and after the operating system takes over control of the hardware. The same applies to some extent without a working mouse, but if you know what you are doing it was usually easier to deal with a keyboard and no mouse than a mouse and no keyboard.
The result is that the standard interface for keyboards on PCs stayed much the same from the introduction of the PC/AT in 1985 to the switch to USB in the 2000s. The IBM PS/2 changed the connector and the new connector was eventually adopted by clones, though there was a long period when both were in use, but as far as I know both the electrical interface and the logical interface stayed the same. The PS/2 also added a mouse interface that was electrically similar to the keyboard interface.
Laptops had a more complex keyboard and mouse situation, they would have an internal keyboard, an internal pointing device (touchpad, trackball or trackpoint) and count often support an external keyboard, an external mouse or both on a splitter, but they still needed to look sufficiently like standard keyboards and mice that someone could boot and install an operating system suceefully. Combining internal and external signals, and detecting what was plugged into the combo PS/2 port would have to be handled by firmware in the laptop's keyboard controller.
USB was first introduced in 1996 but it took a while to find it's feet. There was a version of windows 95 with USB support, but in my experiance it was viritually unusable due to lack of perphiheral drivers.
Windows 98 was better but still problematic, I remember plugging USB keyboards and mice into windows 98 boxes, and they worked fine once you got past the "found new hardware" wizard but without a working keyboard or mouse there was no way to get past the found new hardware wizard. Also bios's from that era generally did not understand USB keyboards or mice, so you couldn't use them at the BIOS or bootloader screens.
So that brings us to where we are today, if you as a hardware designer want to make a keyboard that will work out of the box almost everywhere, the safe options are to either make it look like a traditional PC keyboard, or make it look like a USB HID keyboard.
One of the similarities when looking at crash dumps with other people with the same problem is a driver dwvkbd64.sys, dated April 11 2007. THats a few years old, so just wondering if this could possibly be the cause of the BSOD's. I'm looking for a driver update for this file that is higher than version 1.0.0.1 and newer than 2007. Is there one? I just pushed version 10 to my laptop to check, but went into devmgmt.msc and it still shows the 2007 era driver.
Though I don't believe this driver was causing the BSOD's we were experiencing. That seems to be resolved from deleting the FNTCACHE.DAT file which may have been corrupted by having Office 2010 installed but Lync 2013 installed on top.
The driver is installed in my host, and does hook into the standard keyboard driver chain. This does sound a little scary to me, knowing Microsoft's habit to change Windows internals at will and not caring too much wether competing products are broken or not. So if the driver doesn't do any good for me, I'd rather not install it.
The docs do say, thet the driver does "somehow" do "something" good for foreign language keyboards. Well, I have a foreign language keyboard (German), in fact I have plenty of them (very basic ones as well as "Multimedia" keyboards with tons of special keys, mainly made by Microsoft and Logitech, but also other brands), and I have never noticed any difference between hosts with and without the Enhanced Keyboard Driver.
This may be caused by the fact that I hardly ever use any "Enhanced" functionality inside a VM, but I notice that many special keys like volume controls, Windows key, Alt-Gr key work regardless of whether I install teh Enhanced Keboard driver or not.
> and what kind of malfunction I will experience if I don't install it?
I do not install the "enhanced keyboard driver" since it was added. This driver requires a reboot after install and I also do not know what it really is good for.
I recommend not to install it - if you ever come across a function that requires this driver you can install it later.
In other words - dont worry - do nothing !
Ulli
Because it processes raw keyboard input as soon as possible, the enhanced virtual keyboard feature also offers security improvements by bypassing Windows keystroke processing and any malware that is not already at a lower layer. When you use the enhanced virtual keyboard feature, only the guest operating system acts when you press Ctrl+Alt+Delete
This full-size keyboard with integrated number pad makes data entry, calculations and navigation a breeze. The curved space bar along with easy-to-read keys provide a comfortable and familiar typing experience.
Spill-resistant designTested under limited conditions (maximum of 60 ml liquid spillage). Do not immerse the keyboard in liquid., durable keys and sturdy tilt legs with adjustable height, this keyboard is built to last.
Adding a full-size keyboard with one-touch functions and a number keypad to a Chromebook or laptop lets students type on a familiar platform for maximum efficiency. The result? Students can focus on what matters most - their schoolwork.
Silicone cover envelopes entire keyboard, forming a seal around each key to support frequent cleaning while retaining a positive typing experience; designed & tested to withstand disinfecting after each use, supporting safe, long-term, shared use.Tested to withstand 2,700 wipe cycles with alcohol; equal to 5 classroom sessions per day, 180 classroom days per year over 3 years.
With more than 22 years experience designing high-quality keyboards, we carefully design, develop, prototype, and study all the essential components of our keyboards, from the core technologies to the comfort and ergonomics of their design.
So why this driver : "Hewlett-Packard Development Company, L.P. - Keyboard - Standard 101/102-Key or Microsoft Neutral PS/2 Keyboard for HP Hotkey Support" keeps showing up if it is already installed? We cant tell the agents to ignore it since their remote desktop detects the driver update and it wont allow them to open it.
I'm also waiting for that patch that will provide permanent resolution on this one. It was funny that when I assisted an agent and she was with HP support doing a remote session with her laptop, they cant figure out what causing the drivers not to installed on the devices, and they already reset the laptop.
We found a workaround (cause we need to get them on the phone), we just suggested the agents to use a USB keyboard and keep on deleting the PS/2 driver on Device Manager (it keeps on coming back after the restart though), but c'mon, we need a permanent fix on this one.
Things are getting worse because for the past days, we have been receiving reports from the agents that another HP driver (Hewlett-Packard - Enterprise WSD Multi-Function Printer, Multi-Function Printer, Other hardware - HP Printer (BIDI)) is having an issue installing (aside from the Keyboard driver) that hinders them from logging in to their remote desktop. Good thing that we found a temporary fix to get rid off of those updates, but it was a tedious workaround.
I searched for a solution online and after have tried many things I eventually uninstalled the standard ps/2 driver to get it automatically installed on reboot. At least so I thought. After the restart, the driver wasn't installed though and I can't find how to install the driver again.
NOTE: Some VAIO notebooks include a feature which allows the touchpad and touchpad buttons to be disabled using the Fn+F1 keys on the built-in keyboard. Try holding down the Fn key and press the F1 key to see if the touchpad and touchpad buttons are re-enabled.
Edit: Solved the problem. All I had to do was change the keyboard driver to Standard PS/2 from ELAN in Device Manager and in registry change the UpperFilter value to kbdclass instead of ETD kbdclass.
Just out of nowhere the keyboard on my laptop stopped working. I checked in device manager and it said "Windows cannot start this device because its configuration information (in the registry) is incomplete or damaged. (Code 19)". Like any other newby, I googled Code 19 error trying to fix the problem. Came across multiple articles saying that deleting UpperFilter and LowerFilter values in registry will solve the problem. Without thinking or backing up, I went ahead and deleted the UpperFilter value and fucked up. Now even an external USB keyboard won't work.
dd2b598166