wow, thats useful.

error, the error has made an error occur, please un-error the error

first

Posted by: kiplingh at September 10, 2005 12:34 AM

Reminds me of the sign that says "Warning: This Sign Has Sharp Edges"

Posted by: GMoney at September 10, 2005 02:50 AM

I hope the manual at least explains what error number 311 is. :)

Posted by: Alden Bates at September 10, 2005 06:30 AM

This could not be posted. If this could not be posted, cause this to be posted.

Posted by: Bob at September 10, 2005 07:18 AM

If this could not be posted, remove the cause of the inability to post.

Posted by: Fuzzy at September 10, 2005 09:11 AM

Either people are posting or Bob and Fuzzy are being annoying. If Bob and Fuzzy are being annoying, eliminate the cause of the annoyance.

Posted by: nick'd at September 10, 2005 09:41 AM

stupid macs (hehehe, that will get em going)

Posted by: Jeff at September 10, 2005 10:22 AM

"stupid macs (hehehe, that will get em going)"

why i oughta.....

Posted by: mac at September 10, 2005 10:59 AM

The only way this could be more broken is if they used a set of LEDs in patterns to blink out the code, where each bar represents one numerical unit, and each flashing bar represents two numerical units. The first two columns of bars represent the first digit in the error code, the next two columns represent the second digit, the fifth column represents the third digit, and the sixth column represents the final digit. The first two digits of the error code indicate the failing subsystem, and the final two digits indicate the recovery action.

Posted by: Hoki at September 10, 2005 01:28 PM

"stupid macs"

Yeah, I'm sure the error message in the Windows version is SO much more enlightening.... ~rolling eyes~

In the Linux version the error message is probably a memory dump in hex, and is the most functional of all since most Linux users could probably read it and tell you exactly what's wrong.

Any Mac users remember back in OS7 the mysterious "an error of type 11 has occurred" message? It took third party authors to list the various types of errors, because Apple sure wasn't telling anyone.

I'd much prefer an error message "Your snargleblaster is snagged on the whoofleator, and must be discombobulated before piffleage occurs," because at least then it would be entertaining even while giving me no less information than these stupid numerical codes.

Posted by: Hoki at September 10, 2005 01:35 PM

I remember the HP printer too, Hoki.

http://www.thisisbroken.com/b/2005/08/hp_printer_erro.html#comments

Posted by: Kevin at September 10, 2005 02:50 PM

Somebody needs to find out the names of the guys at Canon and HP who come up with these designs so we can publically mock them.

Posted by: J. Scott at September 10, 2005 06:06 PM

This is one of the few TIB entries that has actually made me laugh out loud. Good one.

Posted by: Faolan at September 10, 2005 06:32 PM

Good idea, J. Scott! Of course, we could always do something better for the common good of UI and exile them or something...

Posted by: Kevin at September 10, 2005 09:40 PM

I think we should fire bomb thwe guy's house. (Ok, maybe not.)

The error message is very helpful here. After all, i couldn't possibly have figured out what i was supposed to do.:P

Posted by: Sido at September 10, 2005 11:48 PM

Hoki,

Feel that gentle tug on the end of your leg. That's Jeff.

BTW, This one made me laugh so hard my wife ran from the other end of the house to see what was so danged funny.

Oh, yeah - BROKEN.

Posted by: Randy at September 11, 2005 09:26 AM

I don't understand all the fuss about hard to understand error messages. I am in charge of one of the printers at work, here is what I do with error messages that are incomprehensible:

1) Is the printer plugged into the wall and the computer (or network)?

2) Is it turned on?

3) Is there paper?

4) Is there a piece of paper stuck in it?

5) Is there ink?

6) Turn off the printer and then turn it on again.

7) Do same with computer.

7) If all fails call a technician.

Steps 1 through 5 will solve 90 percent of the most common errors

Steps 6 through 8 should fix the rest

Posted by: Sean P at September 12, 2005 12:51 PM

Sean: Are you telling me you are happy with the fact that error messages are completely useless, and this is not a problem with the design?

You don't see anything wrong with an error message that basically says "beep" with no additional information?

Posted by: Carlos Gomez at September 12, 2005 01:04 PM

I agree that error messages should be understandable by the user, but Cannon and HP are certainly not alone in that.

My point was only that too many people skip right ahead to step #8) (AKA 2nd #7) ) without even checking steps 1 and 2.

Posted by: Sean P at September 12, 2005 02:07 PM

That was issued by the Department of Redundancy Department.

Posted by: The Illustrated Librarian at September 12, 2005 09:21 PM

The pod bay door could not be opened because the pod bay door is closed. Please open the pod bay door by opening it.

Posted by: HAL-9000 at September 12, 2005 09:55 PM

hey Sean P,,

there is no #8 on ur list,,,

i think mebbe u meant 4 1 of those 7s 2 b an 8

Posted by: Bill at September 12, 2005 10:41 PM

Thanks for the laugh! Hillarious commentary.

Open doors cannot be opened , empty holes hold as much dirt as full holes , hardware/software errors are the only way a computer can say "I Love You! ... Jerk!"

Posted by: Uranus at September 13, 2005 12:18 PM

I vote we make a new rule: All error messages must be in haiku. They don't necessarily have to make sense, since they certainly don't today, but at least this way they will be semi-entertaining!

Posted by: Hoki at September 13, 2005 07:16 PM

I guess it could actually be more broken: if there were no error feedback message at all. Then you'd be left wondering if there even was an error or not. I think I'd prefer at least a cryptic error message to no message at all. That's debatable, of course, which is the reason for my post.

Posted by: EmGeeEm at September 15, 2005 09:53 AM

Sean, you are an elite techno-geek, thinking that since you are able to understand the problems that most likely occur that people are stupid for not understanding a useless error message.

Here's one you won't understand:

ERROR: Your girlfriend is not aroused. If she is aroused, please do not contact her in any way, as she is too busy being aroused. Please remove yourself from the situation, so she may enjoy her arousal. If you happen to present during her arousal, why are you not kicking that guy's butt?

Get over yourself...

Posted by: Ashamed to also be named Sean at September 15, 2005 08:29 PM

Your computer has an internal error, please un-error your computer before continuing to the un-erroring process.

The day we live in...

Posted by: Kristofir at September 18, 2005 06:27 PM

None of you have worked with a Fuji Frontier, have you?

(E-6232) An error message not selected. Select an error message and perform it.

(W-1258) Couldn't perform because the carrier is installed. Remove the carrier and perform it again.

(E-1549) Error occured while deleting the order. The status of the order to be deleted does not become 'Creating.' Change the status on the imaging controller.

(W-1246) Too large grey pixel. Check and clean optical system.

:)

Posted by: Jesse Alonzo at September 19, 2005 05:29 PM

This entry actually made me laugh out loud. Then I read Jesse's post and laughed out loud even longer

Posted by: Bill at September 30, 2005 05:47 AM

error code A6400, can't get it removed

Posted by: jan at April 25, 2006 01:23 PM