| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 95531 | 2008-12-09 12:13:00 | PS/2 and USB keyboards not working: OS @ fault? | gza (13233) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 727179 | 2008-12-09 12:13:00 | I'm posting this thread using the USB keyboard through a make -do install of WXP Pro+SP2 on a partition of a slave drive I have made active. All the following refers to the state of affairs before I created the partition I'm using to type this. PS/2 keyboard works in boot-up stage but locks computer when I give it first touch to enter password. I tried another PS/2 keyboard to no avail. I then purchased a DSE USB/PS/2 keyboard which doesn't cause computer to lock-up: however when I use it in the PS/2 mode the 'Num Lock, Caps Lock & Scroll lock are lit up and flickering. I did not push any keys to activate them. Today I got a Tech in to look at the problem and he adjusted a few Registry Keys that got rid of the yellow exclamation beside the Keyboard in Device Manager. But it still wouldn't work. Problem started on saturday 8th dec. When I got the USB k'board yesterday and it didn't freeze the com but wouldn't do any typing. or anything else,: what happened when I pushed the 'Sleep' button' was a message saying " System Standby Failed- The Device Driver for the Terminal Server Keyboard Driver Device is preventing the machine from entering standby: try updating. I did, still no go. went into device manager, saw the exclamation mark, checked properties, received a message that 'This device cannot start, the driver is missing or corrupt', Error Code 39. I tried rollback( there were no drivers backed up message said), Update: 'A better device than the one installed couldn't be found', Uninstall / reinstall did nothing. The driver loaded for the USB k'board is given as 'KeyMaestro P2360 & is Digitally signed by Msft. I get the same info, Can't install driver, missing or corrupt,etc.Error Code 39. I got into Hardware Resources before I got the USB k'brd, and there were conflicts in I/O Port 0x00000060 PS/2 compatible mouse, & 0x00000064 Standard 101/102 Key Ms Natural PS/2 Keyboard. IRQ 01 shows three microchips , the top one, I/O Range 0060-0060, has a red circle around it with a diagonal red bar through it. The one beneath it is the same except the I/O Range is 0064-0064. The one beneath is ok, says IRQ 01. Worst is that I cannot do a System Restore because apparently the 'C' drive got a wee bit full friday night wiped out all restore points. Never knew that one before, but do now. Chilling Silence quipped on that point in my post last week..Hmmm... Long thread again, sorry, what do you think about this prob I now have, The tech couldn't get things running smooth, is the only answer to the prob a complete format / fresh install, again?? Com & keyboard working perfect on the fresh basic set I am using at the moment. I have read a couple of threads on the subject before I posted. Am looking for some more. :confused: Compaq Presario S3010AN WXP Pro + SP2 AMD XP2000+ 1.67GHz 768 MB SD DDR PC2100 RAM |
gza (13233) | ||
| 727180 | 2008-12-10 23:08:00 | I tried to add the problem drive as a slave but com can't find it. As a primary drive I can't get it to open in safe mode to see if keyboard will function there. Tried all I have read on the subject in forums and other places to no avail and I have reached the conclusion that format/ clean install all is only option. Backing up before this an option but might omit that, could be putting the problem back in to the computer, though that is unlikely because whatever the problem is;a missing whatever; its not there to be added in a backup. Whatever, on with a thousand tasks I'd rather not be having to do. :annoyed: |
gza (13233) | ||
| 727181 | 2008-12-10 23:17:00 | So 3 things right? HDD not being detected as slave. Did you have the jumpers/cabling correct? PS2 ports not working - motherboard fault? And lastly problems with the USB keyboard, see this: support.microsoft.com I'd remove all KB drivers. And any Adobe stuff, and disable any power saving/hibernation. And then see what happens......... |
pctek (84) | ||
| 727182 | 2008-12-11 00:26:00 | Thanks pctec, I did have the HDD jumpers set correctly & in doing that trial XP Pro setup/install on the 'Slave' & running it as Master on its own, the PS/2 and USB keyboards worked so I figured that eliminated a Motherboard fault. My reluctance to format etc and a Google of the " Keyboard not working", took me to this page blog.ryantadams.com I followed instructions and am now using the USB K/Brd. And I am in 7th heaven about this. As I said, the tec that I got in to check the computer changed registry keys, removed the yellow exclamation mark in Device Manager, but none of his efforts could solve the problem. The problem no longer exists. I will bookmark the link you supplied, Thanks. |
gza (13233) | ||
| 727183 | 2008-12-11 01:55:00 | I did have the HDD jumpers set correctly & in doing that trial XP Pro setup/install on the 'Slave' & running it as Master on its own, the PS/2 and USB keyboards worked Some stuff up in Windows then. |
pctek (84) | ||
| 727184 | 2008-12-11 04:18:00 | Yeah, or possibly a stuff up of mine. I think perhaps it all was bought about by the 'C' drive running short of space when I was creating an .iso from a folder in the slave 'H' drive and a temporary file for it was created in 'C' Temp. I'm not 100% positive on this but the loss of System Restore points, Event Viewer informs me, points toward the 'crash'. Something changed keys in the Registry and bought about the 'Error Code (39)'. All back to normal now though |
gza (13233) | ||
| 1 | |||||