OLD laptop - no response from keyboard (keyboard taps make "bip" sound)
I'm working on an old HP Omnibook XE3. P3, 600mhz, 64mb ram. (!). Came with win98 / win2k (sticker says), but now has WinXP Pro sp3. I'm fixing it for a friend with no cash.
But when the windows XP desktop appears, EVEN IN SAFE MODE, there's no respose to any keyboard input. When I touch a key, I hear a faint quick little "bip" sound coming from the speakers, almost as if there's a "static" crackle noise that gets interrupted. (Hard to describe). And there's no response. Not even from the arrow keys or the windows key.
However, the touchpad and touchpad buttons work ok.
NOTE - BEFORE the desktop comes up, when I'm logging in the user, I can type in individual password characters, so the keyboard works then. Also in the bios setup, I can move around using the keyboard keys, enter, esc, etc. But once I'm in windows (normal mode, safe with net, or safe ), I can't use the keyboard. Dev Mgr says the keyboard is ok.
One hour of my time is worth more than this old relic, but I'm curious if there might be a quick fix for this keyboard issue.
I thought, maybe a key is being held down (mechanically bad key), and causing this. But then why only after desktop?
But when the windows XP desktop appears, EVEN IN SAFE MODE, there's no respose to any keyboard input. When I touch a key, I hear a faint quick little "bip" sound coming from the speakers, almost as if there's a "static" crackle noise that gets interrupted. (Hard to describe). And there's no response. Not even from the arrow keys or the windows key.
However, the touchpad and touchpad buttons work ok.
NOTE - BEFORE the desktop comes up, when I'm logging in the user, I can type in individual password characters, so the keyboard works then. Also in the bios setup, I can move around using the keyboard keys, enter, esc, etc. But once I'm in windows (normal mode, safe with net, or safe ), I can't use the keyboard. Dev Mgr says the keyboard is ok.
One hour of my time is worth more than this old relic, but I'm curious if there might be a quick fix for this keyboard issue.
I thought, maybe a key is being held down (mechanically bad key), and causing this. But then why only after desktop?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might need to open it up and check the connections. I remember the same thing happening with the exact same model of laptop I have doing the same thing when I put it back together. I believe it was a cable that wasn't fully connected. I also still happen to have it too.
try this (system restore) if it worked before :
http://support.microsoft.com/kb/307545
--------------------------
An easier way is to boot from a Bart PE CD (or UBCD4Win CD) and use the file manager for manipulating files. Here the procedure :
1. rename c:\windows\system32\config
2. Navigate to the System Volume Information folder.
it contains some restore {GUID} folders such as "_restore{87BD3667-3246-47
The restore points are in folders starting with "RPx under this folder.
3. In such a folder, locate a Snapshot subfolder. This is an example of a folder path to the Snapshot folder: C:\System Volume Information\_restore{D8648
4. From the Snapshot folder, copy the following file to the c:\windows\system32\config
_REGISTRY_MACHINE_SYSTEM
5. Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
6. Exit Bart PE, reboot and test
Use a fairly recent restore point from at least a day or two prior to problem occurring .
** you can add the other hives also with this procedure
http://support.microsoft.com/kb/307545
--------------------------
An easier way is to boot from a Bart PE CD (or UBCD4Win CD) and use the file manager for manipulating files. Here the procedure :
1. rename c:\windows\system32\config
2. Navigate to the System Volume Information folder.
it contains some restore {GUID} folders such as "_restore{87BD3667-3246-47
The restore points are in folders starting with "RPx under this folder.
3. In such a folder, locate a Snapshot subfolder. This is an example of a folder path to the Snapshot folder: C:\System Volume Information\_restore{D8648
4. From the Snapshot folder, copy the following file to the c:\windows\system32\config
_REGISTRY_MACHINE_SYSTEM
5. Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
6. Exit Bart PE, reboot and test
Use a fairly recent restore point from at least a day or two prior to problem occurring .
** you can add the other hives also with this procedure
I'd be more inclined to suspect malware of some type.
Grab a Linux Live CD such as Knoppix http://www.knoppix.org/ Boot from it (you won't be installing anything) and play with it and use the keyboard. If it works OK like that which I suspect it will there is something wrong with the software on the computer.
If there is something wrong then consider wiping and reinstalling if there is nothing of value on it.
Grab a Linux Live CD such as Knoppix http://www.knoppix.org/ Boot from it (you won't be installing anything) and play with it and use the keyboard. If it works OK like that which I suspect it will there is something wrong with the software on the computer.
If there is something wrong then consider wiping and reinstalling if there is nothing of value on it.
Is there any chance of adding some RAM (at least temporarily) to the laptop? Although I've seen early versions of XP run with 64MB, I've never tried this when it was at SP3 level. I doubt XP SP3, fully patched will run properly with this small amount of RAM. Maybe it did work until a windowsupdate finally overloaded this thing. With more RAM you should be able to verify this.
Also nobus' suggestion above may work, as this would remove such an update, but as that OS is also based on XP you may run into similar issues there
Also nobus' suggestion above may work, as this would remove such an update, but as that OS is also based on XP you may run into similar issues there
I'm still more inclined on the side that if the keyboard connection was loose and reseated and the problem still occurs, it would be a driver issue then.
So are you going to decide on a solution or not? I'm noticing as of lately it seems to be a trend to not award any points to someone and just leave the topic rot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you tried an external keyboard? I'm going to try and simulate the conditions you have and see if I can replicate them.
..and nada for me..:-(