If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Keyboard mystery
On an IBM 8113 (M52) desktop I swapped out the keyboard
to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) The old Logitech Access MB ran well under Logitech software (so long as one remembers to hit the F lock key to enable it). Clean replacements tried were HP KB-1306 and IBM KB-0225. Neither was recognized even when I removed the old KB from Hardware/Device Manager. I had to replace the dirty old Logitech KB to get going again (and System Restore to last week because I had uninstalled the Logitech software.) Now booting OK -- except for nonfunctional error report PXE 0161 + BEEP delaying startup. Any clues? I'd thought WinXP (SP3) was supposed to recognize as new any KB connected at bootup. -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
Ads |
#2
|
|||
|
|||
Keyboard mystery
Don Phillipson wrote:
On an IBM 8113 (M52) desktop I swapped out the keyboard to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) Are you sure you have the mouse and keyboard plugged in their correct jacks? The old Logitech Access MB ran well under Logitech software (so long as one remembers to hit the F lock key to enable it). Clean replacements tried were HP KB-1306 and IBM KB-0225. Neither was recognized even when I removed the old KB from Hardware/Device Manager. I had to replace the dirty old Logitech KB to get going again (and System Restore to last week because I had uninstalled the Logitech software.) Now booting OK -- except for nonfunctional error report PXE 0161 + BEEP delaying startup. Any clues? I'd thought WinXP (SP3) was supposed to recognize as new any KB connected at bootup. |
#3
|
|||
|
|||
Keyboard mystery
Don Phillipson wrote:
On an IBM 8113 (M52) desktop I swapped out the keyboard to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) "Ken" wrote in message ... Are you sure you have the mouse and keyboard plugged in their correct jacks? Being colour-coded, correct PS/2 jacks are easily verified (KB purple, mouse green, but mine is actually a USB mouse.) M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? -- Don Phillipson Carlsbad Springs (Ottawa, Canada) The old Logitech Access MB ran well under Logitech software (so long as one remembers to hit the F lock key to enable it). Clean replacements tried were HP KB-1306 and IBM KB-0225. Neither was recognized even when I removed the old KB from Hardware/Device Manager. I had to replace the dirty old Logitech KB to get going again (and System Restore to last week because I had uninstalled the Logitech software.) Now booting OK -- except for nonfunctional error report PXE 0161 + BEEP delaying startup. Any clues? I'd thought WinXP (SP3) was supposed to recognize as new any KB connected at bootup. |
#4
|
|||
|
|||
Keyboard mystery
"Don Phillipson" wrote in message
... On an IBM 8113 (M52) desktop I swapped out the keyboard to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) Does it get as far as starting Windows? This sounds more like a BIOS error. Which would imply that either the keyboard has been broken while cleaning it or (as Ken has suggested) the keyboard and mouse have been swapped. Hope you get it sorted. -- Brian Cryer www.cryer.co.uk/brian |
#5
|
|||
|
|||
Keyboard mystery
Don Phillipson wrote:
Don Phillipson wrote: On an IBM 8113 (M52) desktop I swapped out the keyboard to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) wrote in message ... Are you sure you have the mouse and keyboard plugged in their correct jacks? Being colour-coded, correct PS/2 jacks are easily verified (KB purple, mouse green, but mine is actually a USB mouse.) M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size This error message sounds like a setting in CMOS is incorrect. Enter CMOS right after turning power on. There is normally a message on the screen telling you how to do this. Normally it requires hitting a key such as DELETE, ESC, or one of the function keys. Once in there save the settings and exit. It might solve your problem. Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? |
#6
|
|||
|
|||
Keyboard mystery
On 10/31/2011 07:20 AM, Don Phillipson wrote:
Don Phillipson wrote: On an IBM 8113 (M52) desktop I swapped out the keyboard to clean it and then got terrible boot problems, both KB and mouse inoperative, KB error 012 and PXE 061 (Media test failu check cable.) wrote in message ... Are you sure you have the mouse and keyboard plugged in their correct jacks? Being colour-coded, correct PS/2 jacks are easily verified (KB purple, mouse green, but mine is actually a USB mouse.) M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? For the memory error you need to OK and save the memory size change for the PXE error, in the bios you need to remove the network boot option or else place it lower in your boot device priority |
#7
|
|||
|
|||
Keyboard mystery
"philo" wrote in message
... M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? For the memory error you need to OK and save the memory size change for the PXE error, in the bios you need to remove the network boot option or else place it lower in your boot device priority Both now done, thank you, OK. Both IBM M52s with WinXP SP3 now boot with no error signals, both from SATA drives. The main physical difference is that Upstairs has a single 1.5 Tb drive (partitioned so C:\ = 75 Gb) while downstairs boots from a 75 Gb C:\ and has a 300 Gb PATA drive. Upstairs has always booted in 45 seconds, not measured today but less than 60 sec. Downstairs requires 115 seconds to boot (55 sec. to desktop background.) Both are configured to load at boot only wireless network connections and Mailwasher email filter. I should like to tweak faster boot (and prevent unneeded CTFMON from recurring.) What web sites seem practical? -- Don Phillipson Carlsbad Springs (Ottawa, Canada) |
#8
|
|||
|
|||
Keyboard mystery
On 01/11/2011 12:41, Don Phillipson wrote:
"philo" wrote in message ... M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? For the memory error you need to OK and save the memory size change for the PXE error, in the bios you need to remove the network boot option or else place it lower in your boot device priority Both now done, thank you, OK. Both IBM M52s with WinXP SP3 now boot with no error signals, both from SATA drives. The main physical difference is that Upstairs has a single 1.5 Tb drive (partitioned so C:\ = 75 Gb) while downstairs boots from a 75 Gb C:\ and has a 300 Gb PATA drive. Upstairs has always booted in 45 seconds, not measured today but less than 60 sec. Downstairs requires 115 seconds to boot (55 sec. to desktop background.) Both are configured to load at boot only wireless network connections and Mailwasher email filter. I should like to tweak faster boot (and prevent unneeded CTFMON from recurring.) What web sites seem practical? Those are quick boot times. I wouldn't mess with sites which offer tweaks which claim to reduce boot times - far too many are infested with malware these days, or contain advice which may trash your system. Two reletively safe ways to reduce boot times are defragmentation of the boot hard drive and by disabling any wired ethernet ports (in the BIOS if possible or by using Device Manager if not), if these wired ports are not being used. An unused ethernet port can add 30s to the time it takes to boot. HTH -- Rob |
#9
|
|||
|
|||
Keyboard mystery
On 11/01/2011 07:41 AM, Don Phillipson wrote:
wrote in message ... M52 now boots OK with extra RAM (total 3 Gb) but with two delays: Error 0164 memory size Error .61 Media test failure; check cable. and then boots OK. Can I bypass these by some BIOS adjustment? For the memory error you need to OK and save the memory size change for the PXE error, in the bios you need to remove the network boot option or else place it lower in your boot device priority Both now done, thank you, OK. Glad you got it Both IBM M52s with WinXP SP3 now boot with no error signals, both from SATA drives. The main physical difference is that Upstairs has a single 1.5 Tb drive (partitioned so C:\ = 75 Gb) while downstairs boots from a 75 Gb C:\ and has a 300 Gb PATA drive. Upstairs has always booted in 45 seconds, not measured today but less than 60 sec. Downstairs requires 115 seconds to boot (55 sec. to desktop background.) Both are configured to load at boot only wireless network connections and Mailwasher email filter. I should like to tweak faster boot (and prevent unneeded CTFMON from recurring.) What web sites seem practical? I would really not too much worry about a 115 sec bootup maybe you can double check and run msconfig and see if there are more apps in startup than you think? |
Thread Tools | |
Display Modes | |
|
|