 |
A project to make businesses more aware of their customer experience, and how to fix it. By Mark Hurst. |
| About Mark Hurst | Mark's Gel Conference | New York Times Story on This Is Broken | Newsletter: Subscribe | RSS Feed |
Search this site:
Categories:
- Advertising
- Current Affairs
- Customer Service
- Fixed
- Food and Drink
- Just for Fun
- Misc
- Not broken
- Place
- Product Design
- Signs
- Travel
- Web/Tech
Previous: New York Aquarium website | Main | Next: Hotel map
August 25, 2006 12:04 AM
Broken: Dell keyboard-failure error
A reader points out a keyboard-failure error that instructs the user to type F1.
Uhh, striking a key doesn't work. That's why it's called a keyboard failure!
Oh man. I've seen these errors in jokes, but I never thought anyone would be stupid enough to actually make a system that would show them...
B to the R to the Oken.
Usually you'll see this error when a keyboard is disconnected. Just reconnect the keyboard and hit F1. Every microsoft os based computer in the world does this. It's not just Dell or HP or insert brand here.
I used to get that every once in a while. I never thought about reconnecting the keyboard, but it'd be hard when it's a laptop. ;)
Sometimes a stuck key will cause this to occur. Besides, if you can press F1, then there isn't really a problem.
"Usually you'll see this error when a keyboard is disconnected. Just reconnect the keyboard and hit F1. Every microsoft os based computer in the world does this. It's not just Dell or HP or insert brand here."
Oh, well, in that case...
It's still kind of broken, though. Why doesn't the error ask you to check to see if your keyboard's unplugged then?
This really isn't anything specific to Microsoft. That error is generated by the system BIOS right as it is first booting up (before any OS, Microsoft or otherwise, has started to load). In this example, it's the Phoenix BIOS that's generating that message.
In my experience, this is most often seen when, as Nick mentioned, a key is stuck, or it can also happen if you try purposely pressing some keys on the keyboard before a certain point during bootup.
I remember getting that a lot when trying to get into the BIOS utility, usually by needing to press a certain key, and you press it so many times (16 I think it is), the computer starts beeping at you that it has filled the keystroke buffer. You then get the error message.
It is fairly poorly written, I'll admit, but then again, we are dealing with the limitations of BIOS firmware coding.
I guess another way to look at it is that it's showing a series of things that are happening, but instead of blanking out the previous line, once the process gets to another point, the next line/prompt is printed below it.
...hmmmm, I'm going with the not so broken group on this one...
Acutaly the Default BIOS settings will give u that message. Depending on what BOIS u use, u can disable the keyboard messages, unplug mouse, monitor, and speakers, and boot. My roommate did this for remote access. just a network cable and power. In theory you should be able to use a wireless network but...
Naw, not broken. Every IBM-based PC since the PS/2 has done that. They could tell you to press F1, when it's only a temporary problem like you had something on the keyboard while the computer was booting, you hit F1 to continue. That's always how it works when the BIOS encounters any error while there's still a display device, RAM, and a CPU attached. Otherwise it just gives you beeps. If the clock/CMOS battery runs out and it says 'Invalid System Configuration - Please run SETUP program' it will display that same prompt line under it.
There isn't any better way to write the error. How about 'Take a few paperclips and pull DB0 through DB7 to ground on your parallel port while cold-booting the computer' -- No one would do that.
By the way, they have to fit everything onto one little EPROM or EEPROM chip - it doesn't have any substantial storage space available in it.
So, when you encounter a keyboard failure, you plug in another working keyboard, and press F1. Pretty easy to understand. Some BIOS'es (like the ones used in older IBMs) will figure out the difference between a keyboard failure and a missing keyboard. Most don't. Hey, a keyboard's an external device, so it's pretty easy to check / replace compared to an internal device.
Of course, if it really bothers you or you're trying to make a headless server using a serial console, sometimes you can disable device checking on boot.
Not broken, except to the extent that these (usually older) PC systems required/assumed that a keyboard was necessary for the system to do anything useful. This is just a way for the BIOS to point out that the keyboard is missing/broken, and that you'll need to rectify that problem before it'll go any further. Newer systems either can be configured to ignore this error condition, or don't make the assumption at all and let the system boot anyway.
"Usually you'll see this error when a keyboard is disconnected. Just reconnect the keyboard and hit F1. Every microsoft os based computer in the world does this. It's not just Dell or HP or insert brand here."
Oh, well, in that case...
It's still kind of broken, though. Why doesn't the error ask you to check to see if your keyboard's unplugged then?
posted by: The Pondermatic
--------------------------
If asked you then if the keyboard is broken or unplugged, you wouldn't be able to do anything! Although if them it didn't do anything I think you could assume something is wrong with the keyboard.
just a note... this isn't really that old of a computer... the screen shows it as being a Dell Dimension 8200. If I remember correctly, that's problaby about 5 years old, if that? Someone correct me if I'm wrong.
And while I know that 5 years seems like a lifetime in the computer world, it really isn't that old. Its not like we are looking at a PC from the early 1990's or late 1980's.
BIOS chips are not limited by space, many bios chips today can actually save upto 5 different BIOS profiles and also display 256color 640x480 pictures on boot, i wouldn't call that limited space
"BIOS chips are not limited by space, many bios chips today can actually save upto 5 different BIOS profiles and also display 256color 640x480 pictures on boot, i wouldn't call that limited space"
True, but BIOS manufacturers haven't updated the actual system configuration handling and setup in quite some time - only added extra features which are seperate from the real purpose of a BIOS.
Dell seems to have made their own BIOS firmware in their more modern products. (Modern as in made later than 1997)
The 8200 is relatively recent, even if it's 4-5 years old.
broken, way to often there report out their on Dell recalling their supplier and equipment, problem of malfunction of perifirals like keyboards and monitors, cd rom are figure in percentage already, Dell is broken to often
Comments on this entry are closed
Previous: New York Aquarium website | Main | Next: Hotel map
I've gotten similiar errors to that. "Keyboard error: press any key to continue" on an HP desktop's BIOS, and the computers at my school library have said "This computer is in maintance mode. The keyboard and mouse have been disabled." with the (unclickable) option of OK on the dialog. Brilliant.
The idea is not broken - you can push the button when you reconnect the keyboard (ok, even the idea is broken - what if I want to run a headless server?). In any case, still funny.
Posted by: Daniel Bathgate at August 25, 2006 12:46 AM