The Thirteen Greatest Error Messages of All Time

They're rarely helpful. Actually, they usually add insult to injury. But what would computing be without 'em? Herewith, a tribute to a baker's dozen of the best (or is that worst?).

By Harry McCracken | Thursday, September 18, 2008 at 5:28 am

1. The Blue Screen of Death (Windows)
Okay, there was never a real contest here. You can argue about who the greatest baseball player was. Or the best rock group. Or president of the United States. With error messages, though, the Windows Blue Screen of Death–also known as BSoD–is by far the biggest kahuna of all time. And that’s in part because of its longtime habit of appearing on some of the biggest computer screens ever, anywhere and everywhere it pleases.

Such as a projected image during the opening ceremonies of the Beijing Olympics:

And a Canadian department store (photo by Sean Galbraith):

And airports all over the world (photo by Antonio Lopes):

And ~~Times Square~~ Penn Station (photo by Chad Dickerson):

It has no mercy–it loves to taunt even Bill Gates:

A few notable facts about the BSoD, about which you could probably write a book:

It wasn’t a Windows error message, originally. Wikipedia says that it was named by programming-tools company Lattice when it was working on stuff for IBM’s OS/2 operating system. And both OS/2 and versions of Windows prior to 3.1 had Black Screens of Death.

It’s available in handy screensaver form. You can download the BlueScreen Screen Saver, which simulates an uncannily realistic BSoD that’s tuned to the version of Windows you’re running. Who distributes the screensaver? Microsoft–and I’m not sure whether I’m tickled by that, or annoyed that they aren’t taking the whole thing more seriously.

You can wear it. ErrorWear’s BSoD shirts are particularly handsome.

It’s the name of a rock group. Here’s their MySpace page. (It begins to play annoying music the moment you arrive, which seems appropriate.)

Nobody knows for sure why it’s blue. My PC World colleague Steve Fox tried to find out, and the most Microsoft would tell him was that the blue was chosen for legibility. But in the PC’s basic 16-color palette, blue is the first color after black; maybe whoever chose the color was just being lazy and/or unimaginative.

You can change the color. BSoD is a handy utility for doing just that, and here’s how to do it manually. Crashes will be just as alarming, but at least you’ll get a little variety.

You can make a Mac bluescreen. Or fake it at least, with this screensaver or this Dashboard widget.

It probably isn’t going anywhere. BSoDs aren’t as commonplace as they once were, but they still happen–just this month, iTunes 8 made news when it turned out that the Windows version was blue-screening PCs. Me, I’d be amazed if Windows Seven doesn’t bluescreen from time to time. It wouldn’t feel like Windows if it didn’t.

Ultimately, it’s not going too far to say that the BSoD is a sort of persistent, universal reminder of the fallibility of computers–and therefore, on some level, a healthy component of our relationship with them. No rational human who’s ever encountered one would willingly turn over major decisions to a computer. Or at least not one that runs Windows.

Oh yeah, that poll I mentioned. If you’ve gotten this far, you must have a deep and abiding interest in error messages. Please cast your vote for the greatest one of all–and if you get an error message when you submit it, don’t blame me…

[UPDATE: Almost four hundred people have chimed into this discussion, and many nominated other error messages that are at least as worthy of celebration as the ones in the story. So celebrate ’em we did–please check out The 13 Other Greatest Error Messages of All Time.]

«PREVIOUS PAGE 1 2 3 4 5

589 Comments

Read more: Error Messages, Macs, Windows

523 Comments For This Post

Emily Says:
September 18th, 2008 at 12:57 am

When I was 5, I did something to my parents brand new ($5000) Macintosh and got sad mac. I thought I'd destroyed the machine and hid under my bed. All they did was eject the floppy I'd left in and kept on going.

Stu Says:
July 26th, 2010 at 4:43 am

Exactly what I did to a friends' mac. Most intense memory was thinking I screwed up their computer. Holding a key down while booting fixed the problem

alex Says:
May 17th, 2011 at 2:39 pm

thanks god you didn't destroy it… I wonder what your parents would do 🙂

Jason Says:
September 19th, 2008 at 8:39 am

My favorite error of all time is the Apple II's BASIC error:

?SYNTAX ERROR IN 20

The question mark as the lead-in makes it for me, as if the computer is raising its eyebrow and marveling at my stupidity.

Stefan Says:
September 24th, 2008 at 3:08 am

The one I remember most, growing up, was:

?SYNTAX

ERROR

Spit out by my Commodore VIC-20. Good times 🙂

sergio Says:
September 24th, 2008 at 3:15 am

What about my favorite BIOS error when a keyboard is not attached to the computer…

KEYBOARD ERROR: Press any key to continue

Peter Says:
September 24th, 2008 at 3:21 am

I got a nice error message

"You don't exist go away"

on a Linux machine just after editing the passwd file.

hendry Says:
January 19th, 2012 at 1:44 am

I'm offended that PC LOAD LETTER isn't listed.

ArthurT Says:
September 24th, 2008 at 3:59 am

We quickly discovered GOMF Get outta my face, and said good-bye to Guru meditation errors. ( then only a Bad-F Line instruction would kill the system ), so Guru errors became fun, and recoverable.

Pembayaran Online Says:
September 10th, 2011 at 11:25 am

Don't forget about the Atari ST bombs, with various number of bombs displayed depending on the error or severity. http://wemelt.com/ipaymu-com-pembayaran-online-in…

D. C. Sessions Says:
September 24th, 2008 at 4:25 am

Back in the day, my Cadnetix workstation once put up: "We should never get here." That's high on my list of informative and reassuring messages.

As for the BSOD screensaver, it once went off while I was chairing a meeting with a spreadsheet on projector. Onscreen was the morning's work for about thirty engineers who had flown to Las Vegas to thrash out details of the electrical specs for DDR2 (you may have heard of it.) Needless to say, the room Was Not Happy — until I hit the control key and all was well again. (There's a reason I use Linux on my laptops!)

Aeg servis Says:
October 1st, 2011 at 1:59 am

good inquire. Thanks for information's. Blog is good.
Aeg ve electrolux yetkili servisi olarak hizmet veren ve Aeg servisi hizmeti veren bu firma uzun zaman sonra Electrolux servisi ile birleşerek size bu hizmeti sunmaktadır.

James Says:
September 24th, 2008 at 11:09 am

How about Windows 3.1: “TERMINAL APPLICATION ERROR” and an OK button.

The “OK” button was the insulting part. You just lost your work, OK.

Coutch Says:
September 24th, 2008 at 11:09 am

Ever got the ‘Keyboard error. Press F1 to continue’ when a PC boots ? That’s one of my favorites …

prelge Says:
July 8th, 2010 at 8:23 am

I'm having that one on my old Dell right now. What error is it about, and how does one solve the problem?

prelge Says:
July 8th, 2010 at 8:25 am

Sorry. My message only says "Press F1 to continue" during booting. Not a word about the keyboard, which is attached.

EdK Says:
April 27th, 2011 at 10:23 pm

Coutch I love that one, as annoying as it was, the irony was very amusing!

DrEnter Says:
September 24th, 2008 at 11:10 am

One of my all time favorites, encountered on the original IBM PC (and quite a few other early BIOS implementations) if a keyboard wasn’t connected during boot up:

Keyboard Not Found!
Press F1 to continue.

Kiski Says:
September 24th, 2008 at 11:11 am

Keyboard not attached… Press F-1 to continue.

SteveL Says:
September 24th, 2008 at 11:14 am

From the TOPS-20 Pascal compiler (or was it the linking loader?):

Heap overruns stack, retry with more core

HPA Says:
September 24th, 2008 at 11:15 am

I think the best (or worst) error message came from some versions of Microsoft BASIC:

?REDO FROM START

Not only does it have the rather pointless question mark at the beginning, but it actually told you to do the same thing that it just complained about over again. Since English is my second language, and I was a kid at the time, I always assumed that I simply must have missed the translation.

John Lamb Says:
September 24th, 2008 at 11:15 am

I still get a chuckle from the “Keyboard Error, Press F1 to continue.”

Usually, the only time I got that error was when the keyboard wasn’t attached.

Tony Says:
September 24th, 2008 at 11:16 am

My theory on the twitter FailWhale:

its not the birds lifting UP the whale, but the birds being dragged down by the load…

Just a thought.

Jay Says:
December 8th, 2010 at 4:35 pm

My theory is that Twitter (represented by the birds) is experiencing heavy loads (represented by the whales). Makes sense to me.

Jason Says:
September 24th, 2008 at 11:17 am

My favorite was in DEC UNIX/OSF1:

$ make love
Don’t know how to make love. STOP.

Jo Says:
September 24th, 2008 at 11:17 am

What about:

Panic! TRAP 11

See often on PDP-11 Unix version 6 and 7

Grrblt Says:
September 24th, 2008 at 11:18 am

Better 404 poetry:
http://interloper.org/404/404.html

Jack Says:
September 24th, 2008 at 11:22 am

I’m offended that PC LOAD LETTER isn’t listed.

Sam Says:
September 24th, 2008 at 11:23 am

My personal favorites were from a CAD workstation vendor called Cadnetix in the mid 80’s. They went something like:

“We should never get here!”

“Congratulationas, you’re hosed.”

“Our heads are screwed on backwards.”

Ezekiel Says:
April 3rd, 2011 at 11:20 pm

What a riot! I never worked on a CAD tool; but we used to scatter messages like that around our code in locations that were theoretically unreachable — like the line after a JUMPA ("jump always") instruction in PDP10 assembly language. Never bothered to make the messages useful, because it really shouldn't have been possible for people to see them.

I especially like your "Congratulations, you're hosed" — reminds me of an old favorite:

"Now look what you've done!!"

Scott Says:
September 24th, 2008 at 11:24 am

I can’t believe they didn’t include the Atari ST bombs. In that the computer/OS had bombed out. It was great because the number of bombs gave you a clue to what had happened.

Oh wait maybe that’s too helpful, when all the error messages here are useless.

Still my favourite though.

Juggler314 Says:
September 24th, 2008 at 11:25 am

That’s not Times Square in the photo credited to Chad Dickerson, that’s Penn station, more particularly it is the southwest corner of the intersection of 42nd street and 8th avenue. Times square is the next avenue over (intersection of 42nd street, 7th avenue and broadway).

mike Says:
August 2nd, 2010 at 2:46 pm

Nope, that's not Penn Station, but rather its the Port Authority Bus Terminal: http://www.panynj.gov/bus-terminals/port-authorit…

Daniel Says:
September 24th, 2008 at 11:26 am

Two of my all-time faves:
“cannot start: hath the daemon spawn no fire?” (qmail)
“The instruction at ‘XXXXX’ referenced memory at ‘YYYYY’. The memory could not be “read”‘ (Windows – love how “read” is in quotes)

mike Says:
September 24th, 2008 at 11:26 am

Don’t forget about the Atari ST bombs, with various number of bombs displayed depending on the error or severity.

And the old DEC pdp response to

help me

sorry, there is no help for you.

jeffw Says:
September 24th, 2008 at 11:26 am

Other error msg:

I’m pregnant.

juggler314 Says:
September 24th, 2008 at 11:27 am

That’s not times square in the photo credited to Chad Dickerson. It’s the Port Authority, particularly the southwest corner of 8th avenue and 42nd street (Times square is one avenue over on 42nd/7th avenue/broadway.

John Says:
September 24th, 2008 at 11:28 am

The error that continues to frost my cupcakes keeps occurring on the Clarify web application that I use to search for internal Change Requests. Everytime I see this, I want to smack the developers:

"Errors have occurred. We won't tell you where or why. Lazy programmers. – Charlie Gibbs"

The funniest error message that I ever heard about was vanishingly rare, having been created in the Caltech computer center in the early to mid 70's. The TOPS-10 OS running on the DEC PDP-10 machine had been modified by the student operators to emit the error acronym PFDGB upon the occurance of a fatal error. Nobody knew what this meant… BUT, if you went to the terminal room, and searched through the operations manual chained to the desk, in the back, written in PENCIL, was the explanation for the error. Program Fall Down, Go Boom.

The Firesign Theatre album, "I Think We're All Bozo's on This Bus" was conceived in the Caltech Computing Center, and most, if not all of the ideas came from the PDP-10 and some of the Lisp applications running on it. Eliza was a particular source of inpiration, I think. Later in the decade, Vaxes came along, and rendered the album and their PDP-10 jokes irretrievably obscure. But many of us who were there still remember, and smile.

bob Says:
September 24th, 2008 at 11:28 am

no “PC LOAD LETTER”?

hyp3r Says:
September 24th, 2008 at 11:29 am

What about “This program has performed an illegal operation and will be shutdown”? When I was a kid I was afraid I had done something wrong and that the cops would be showing up.

Paul Brown Says:
September 24th, 2008 at 11:30 am

Many years ago I tried to install a modem program on a Mac. It didn’t work and the error message was: “Installation failed. Something is wrong. Find out what it is, fix it, and try again”.

jd Says:
September 24th, 2008 at 11:30 am

A message I got when closing an app

You can’t close this application due to memory problem
Please close some application before closing some application

I never figured out how to close anything before closing it and ended up rebooting

iggyst00ge Says:
September 24th, 2008 at 11:31 am

I came back to my office one day with my assistant crying and hysterical. The OS 7.?.? Mac had crashed on her, and instead of the bomb (which would have been bad enough), it played the sound of a car skidding to a stop before crashing.

Horrible sound. Traumatizing sound. About as far as you can get from the happy smiling Mac and comparatively nonthreatening cartoon bomb.

So, the Mac car-crash sound gets my vote for scaring the hell out of the people who hear it.

Paul Says:
September 24th, 2008 at 11:31 am

What about the predecessor to Windows’s “Unhandled Exception,” the scary “This program has performed an illegal operation and will be shut down.” Scared the hell out of little kids who suddenly thought they broke the law.

Michael Bolton Says:
September 24th, 2008 at 11:32 am

PC LOAD LETTER?! WTF does that mean?

Anonyuser Says:
September 24th, 2008 at 11:33 am

The best error message of all: “Keyboard not detected. Press F1 to continue.”

xardoz Says:
September 24th, 2008 at 11:33 am

The “check engine” light (sometimes just an icon!) on car dashboards. It can signal anything from a loose gas cap to a thrown rod and it REQUIRES you to either purchase a special decoder gizmo to hook up to your engine, or to pay someone to diagnose it for you.

Nicholas Says:
September 24th, 2008 at 11:33 am

I’m glad someone else pointed out the FailWhale. I always assumed the same, after all the service is called “Twitter” which I had always heard used to describe a short chirp from a bird. Hence the twitter “birds” being dragged down by the, oddly happy, FailWhale. Personally I am a big fan of the error message I use at work when they try to access and unapproved website. There is a picture of a kitten shoped over a hubble photo and it says “Space Cat says No. If Space Cat is wrong contact your System Admin so you can explain why you attempted to go to X.” X would be the URL. I love my job.

Yann Vernier Says:
September 24th, 2008 at 11:35 am

Actually, DOS error query function has all four options – Abort, Retry, Fail, Ignore – and whatever triggers the message can choose which to present, though one can’t be turned off (I think that’s either Abort or Ignore). Abort kills the program, Retry retries the operation, Fail reports the error to the program, and Ignore simply lies to the program, telling it the operation succeeded. Which is the greater disaster depends on the operation involved.
As for terse messages, I must say the standard UNIX editor, ed, must take that prize. It only has one error message – “?”.

Nicholas Says:
September 24th, 2008 at 11:36 am

Oh and one of our AS/400 Programmers put a register error in that says “Gah, your stupidity! IT BURNS US!”

jd Says:
September 24th, 2008 at 11:39 am

for you mainframe kids…

0c7. data exception. Now THAT’s useful! Not.

David B Says:
September 24th, 2008 at 11:40 am

I (and others) would argue that 404 is the most important error message of all time, and the most important contribution that made the web possible. There were other hyperlink systems before that, but people were afraid of linking to remote machines because it might get an error. Embracing and allowing 404 really made the web take off.

N Says:
September 24th, 2008 at 11:41 am

What about “?”, the standard error message from ed, “the standard text editor”?

Peet McKimmie Says:
September 24th, 2008 at 11:41 am

Another vote here for the seminal:

“Keyboard not present or not functioning, press F1 to continue.”

I can’t believe you missed it off the list.

jonathan Says:
September 24th, 2008 at 11:42 am

i once got a popup error message from MS Access that said:

“Error #some-large-number: There is no message for this error”

I thought that was so existential….

Jecel Assumpção Jr Says:
September 24th, 2008 at 11:43 am

The wikipedia article has been corrected – the Sad Mac was already there in 1984. What was introduced in 1987 was the two line hex code shown in your screen capture (originally the code was just one line).

Millard Says:
September 24th, 2008 at 11:44 am

I distinctly remember sitting as a lab assistant in one of the Computer Science labs in the mid-90s. We were supposed to watch the syslog to see if anything weird was happening. Suddenly there was a message about the printer (right across from my desk) being on fire. At first I thought it was a joke from one of the sysadmins. Turns out the printer was indeed overheating (though far from catching on fire), but it was still quite a startling message.

rob Says:
September 24th, 2008 at 11:46 am

I always enjoyed, on the vintage DEC PDP-8, the message:

you mispeled a keywurd.

Krreagan Says:
September 24th, 2008 at 11:47 am

“ERROR! FAULTY! …must sterilize!… KAboom!”

A one-time only error message!

Krreagan

wrp103 Says:
September 24th, 2008 at 11:47 am

The old original ed editor on Unix had one error message:

You can type “h” to get the actual text, but the question mark was all that was usually needed.

FoxingDemon Says:
September 24th, 2008 at 11:48 am

One of my favourites which I encountered in Win98 is “Cannnot delete file, not enough free space.”

Jay Mumper Says:
September 24th, 2008 at 11:49 am

On Radio Shack Model 16, XENIX 3.0, in a really obscure hardware failure condition (the Z80 got back to the main operation dispatch loop with the stack at a different depth than it was on the previous pass), z80ctl would spit out:

Bugchk: Sckmud
“Shut her down Scotty, she’s sucking mud again!”

James Says:
September 24th, 2008 at 11:49 am

Wot no “Hodie natus est radici frater”?

Kirsten Says:
September 24th, 2008 at 11:51 am

my grandmother thought that “illegal operation. divide by 0” was going to bring the cops to her house….

IGnatius T Foobar Says:
September 24th, 2008 at 11:51 am

My personal favorite:
“Keyboard failure. Press F1 to continue.”

Blaine Says:
September 24th, 2008 at 11:52 am

General Protection Fault is my favorite from Windows 3.1. As a telephone tech support agent back in the mid 90’s I actually had a customer call and ask for the rank and serial number of this so-called general. I swear to you, the person was serious.

Priceless.

AndyH Says:
September 24th, 2008 at 11:55 am

Am I the oldest person here?

ABEND CODE 804

Richard Says:
September 24th, 2008 at 11:55 am

You FORGOT S07C
cobol mainframe era
also the
1D107 error by lUsers

Lashi Says:
September 24th, 2008 at 11:57 am

Something I used to see from my students when I was tutoring in CS (and myself sometimes when I was coding):

Segmentation Fault: Core Dumped

Tagger1948 Says:
September 24th, 2008 at 11:58 am

Data General RDOS had a good one–

“You can’t do that”

UNIX is rife with them. “Not a typewriter” leaps to mind

Werner Says:
September 24th, 2008 at 12:05 pm

CKFMT was display nicely green on black in the late eighties on United Airlines ‘Apollo’ reservation system. It meant ‘Check Format’ …

jens Says:
September 24th, 2008 at 12:08 pm

I Like this one most but not as famous though (kernel panic)

Shut her down Clancy, she’s pumping mud

JJ Says:
September 24th, 2008 at 12:10 pm

I always liked “This computer has performed an illegal operation and will be shut down”. My aunt actually thought someone was going to call the authorities…

EricH Says:
September 24th, 2008 at 12:10 pm

Does anyone else remember
“ENTER LOCATION OF MORE LOADER INPUT, UXREF, CANCEL OR RETURN TO IGNORE?”

This comes from the Michigan Terminal System (MTS) linking loader when it couldn’t resolve all the symbols in a program. If you were very lucky you could type something like
$CONTINUE WITH FILE_WITH_MY_LIBRARY
and recover, but generally “CANCEL” was the correct answer.

Spectrum Says:
September 24th, 2008 at 12:11 pm

Sorry, but you’ve missed the most important of all, at least for people that started using computers when there were no PC’s

TAPE LOADING ERROR

Did you know it?

Dave Says:
September 24th, 2008 at 12:15 pm

“wrong magic number” – in 1988, working in the dead of night, I was loading BSD 4.3 on a Convex C1 from a reel to reel tape, when I tried booting up the console started spitting out “wrong magic number” over and over, as fast as it could print.
Calling Convex didn’t help either, but the next day they sent me a new tape. It was much later, looking over even older Unix documentation, that I found that the magic number was the file protection mask (look up chmod).
I didn’t want to have anything to do with Unix for a long time after that experience.

Troy Heagy Says:
September 24th, 2008 at 12:16 pm

?SYNTAX ERROR IN 20

This error message was near-universal from 1970 to circa 1995. Anybody who ever owned an TRaSh-80, Apple II, Atari 400/800, Commodore, Amiga, MS-DOS, or other platform that used BASIC saw this error frequently.

It became nicknamed “SYNTAX TERROR” for many frustrated users.

lee Says:
September 24th, 2008 at 12:18 pm

My favorite is the Mac version of the start up beeps. I had one machine which played a sound like a car crash as it attempted to boot, sometimes. Usually the third time was the charm.

Marc Says:
September 24th, 2008 at 12:18 pm

Lots of people mention the keyboard error/press F1 to continue, but I personally think that one is pretty good. It only SOUNDS self-contradictory, and it’s actually helpful (unlike most of the errors on the list.)
It tells you:
– what’s wrong – the computer won’t go on until you fix the keyboard
– how to fix it – press F1 as soon as there’s a valid F1 to press.
Unlike the PS/2 mouse, it’s always been OK to plug/unplug a PC keyboard while the power is on, so the fix is dead easy – unless your keyboard is actually broken, in which case your weren’t going anywhere without a new one anyway.
If you’re savvy enough to figure out that 0/1 is the power switch, this one shouldn’t have set you back for more than a minute.

Likewise with “PC LOAD LETTER”. “PC” was the name of the tray that was empty; I’ll freely admit that that’s pretty cryptic. But “LOAD LETTER”? If that doesn’t speak to you, what are you doing with a printer?

EdK Says:
April 27th, 2011 at 10:41 pm

That's true Marc, however I didn't have a PS/2 Keyboard until my first Pentium, and the 5 pin DIN keyboards required a restart once you got that error. That's why I find that error so funny.

wyvernlord Says:
September 24th, 2008 at 12:19 pm

A app used in the banking industry gave a nice one to us earlier this year. Windows pop up with simply:

“An Error has Occured!”

Really helpful in troubleshooting.

gigabytousai Says:
September 24th, 2008 at 12:21 pm

My two favorites:
The oft mentioned “Keyboard not present. Press F1 to continue.” and
“Cannot copy…The file exists.”

Eddie Pasternak Says:
September 24th, 2008 at 12:21 pm

Seriously, what compels authors to spread a story like this over FIVE SEPARATE PAGES, requiring users to hit NEXT NEXT NEXT NEXT????? It’s a website, not a book, dude.

Alberto Says:
September 24th, 2008 at 12:22 pm

My best error was on an HP3000 ~1984, when I submitted a fortran program to the pascal compiler:

Catastrophic Compiler Error

orclev Says:
September 24th, 2008 at 12:23 pm

I’m a fan of “Segmentation Fault (Core Dumped)”.

Good old segfault, you knew you really b0rked something up when that one greeted you mid way through executing something or other. For those on the Windows side of things, this was the UNIX/Linux version of either “This program performed an illegal operation” or “General Protection Fault” depending on which version of Windows you’re talking about.

Jim Says:
September 24th, 2008 at 12:23 pm

1 – The apple bomb was spoofed in the intro of one of the new mac’s. Apple had a video presentation with music and lots of screen captures flashing by. One of the screen was of a bomb message. The crowd roared when they saw it.
2 – One of our programmers put in an error message of “Bang – Your Dead”. It was supposed to be impossible to get too. Murphy rules: It happened to a customer in an Oil Refinery. The PRESIDENT of the BIG Oil company complained to our President. That is unprofessional!

Roy Says:
September 24th, 2008 at 12:25 pm

“Cannot delete file: Access is denied
There has been a sharing violation.
The source or destination file may be in use.”

Would have been so much more helpful if the file itself had been identified.

cg Says:
September 24th, 2008 at 12:27 pm

I put a warning message into the Myrias parallel C compiler, if you
attempted “goto hell;”:

*** cannot goto hell, C already is hell

Unfortunately, when the compiler was taken over by a new compiler group,
the message was removed. So, I doubt anyone ever saw it.

Marco Bello Says:
September 24th, 2008 at 12:28 pm

The one I like the most is the “White Screen of Death” that PHP produces.
I like it for being so pure, white pure actually.

Yo Says:
September 24th, 2008 at 12:28 pm

Linux fanboy crap.

losthunderlads Says:
September 24th, 2008 at 12:29 pm

My favorite is spat out by the editor vi when you’ve garbled a command so badly the program smacks its head and prints:

“What?”

Azri Says:
September 24th, 2008 at 12:29 pm

I’ve actually received that “lp0 is on fire” error on one of my Linux systems. Oddly enough, the parallel port on my printer had fried…

Hanzi Muller Says:
September 24th, 2008 at 12:29 pm

It happened to me, at the end of a day of work, as I tried to save my work on a floppy:

“Connection to floppy lost.”

bwildrick Says:
September 24th, 2008 at 12:29 pm

…and Firefox crashed three pages into reading the article. >.<

Drew Eckhardt Says:
September 24th, 2008 at 12:30 pm

I’ve always had a certain fondness for “Not a typewriter” when inappropriate ioctl calls are made on open unix file descriptors.

Marcus Says:
September 24th, 2008 at 12:31 pm

I once had some software on a mac (I think it was the anarchy ftp program, but I’m not sure) present me with this error:

“Some evil bastard moved the damned config file on me”

I was particularly struck by this because I was working on the machine of the swearingest guy I ever met. I briefly considered the possibility that he had infected his computer with his speech habits.

Dutch Says:
September 24th, 2008 at 12:32 pm

My favorite was an old C app that crashed with the following message: Error: No error.

Jason Says:
September 24th, 2008 at 12:33 pm

Still have to say the most common error type is the PEBKaC.

Problem Exists Between Keyboard and Chair

Siris Says:
September 24th, 2008 at 12:33 pm

My favorite error message on early SunOS csh:

> Gotta Light?
No Match.

Scott Says:
September 24th, 2008 at 12:33 pm

You forgot the best error message ever.
I received this while playing Counter Strike 1.3 on the old hl engine:

net-error:NO_ERROR

in a popup box.

Eric Says:
September 24th, 2008 at 12:35 pm

I got a nifty one during the installation of Office 2007 Beat. “The following applications should be closed before continuing the install. (No applications were listed, then) Abort Retry Ignore”

Mike Says:
September 24th, 2008 at 12:35 pm

How can we forget

make love
make.exe: *** No rule to make target `love’. Stop.

(pasted from DJGPP in windows, but certainly applicable in GNU environments)

Texas Instrument Says:
September 24th, 2008 at 12:36 pm

Once i tried to resume a ‘screen’ terminal session it responds with

Suddenly the Dungeon collapses!! – You die…

and exited.

Steve Says:
September 24th, 2008 at 12:37 pm

“Who distributes the screensaver? Microsoft–and I’m not sure whether I’m tickled by that, or annoyed that they aren’t taking the whole thing more seriously.”

In all fairness, the screensaver was developed by Mark Russinovich’s company Sysinternals prior to Microsoft buying the company and all of its software and employing Mark. The Microsoft Sysinternals page is here, with the screensaver under the Misc section:

http://technet.microsoft.com/en-us/sysinternals/default.aspx

The screensaver is actually very clever, it uses the error and bootup screens of the version of Windows you’re actually using, and it uses your actual hardware information to show relevant diagnostic messages during “startup”. It appears as if your computer is in a neverending boot-BSoD-reboot cycle, which lasts until you hit Esc. I had it loaded on my computer at work and came back from lunch more than once to find out that someone, thinking they were being helpful, had shut my computer off by holding down the power button.

James Beam Says:
September 24th, 2008 at 12:38 pm

1. Who is General Protection Fault and how did he get in my computer?

2. The mail program in Unix had a “send” command, and its normal response was “mail sent”. But if you used a common typo by issuing the “sned” command, its response was “mail snet”.

JC S Says:
September 24th, 2008 at 12:39 pm

The first computer error I encountered was on a PDP-8I in 1971.

“System underflow in user stack”

I seem to recall the actual error was trying to divide by zero. Things have not improved since.

Also, I am completely enamoured with the infrequent and puzzling windows dialog box

“ERROR The previous operation succeeded – OK”

Dale Williams Says:
September 24th, 2008 at 12:39 pm

The IBM POST was my favorite. The reason I was told for the beeps by some IBM old-timers was that they had this massive typewriter repair force (remember the IBM Selectric) that was about to have nothing to do because of the PC. By having the POST beep codes, the repairman would just look up the meaning it their codebook and replace the necessary parts. Back when I was just starting in IT in the early 80’s, I witnessed IBM typewriter repairmen fix many a PC, XT, AT just based on the beeps. Typewriter repair force is now the PC repair force!

CCPalmer Says:
September 24th, 2008 at 12:40 pm

IBM JCL processor would issue the following error message (or something close to it – memory failing) when a user requested a SCRATCH tape (a fully writable throwaway tape) for a job step. The JCL wanted a specific spelling, which was limited to 6 characters since a tape VolumeSerial number was that long (VOLSER). Thus:

“SCRATCH” should be spelled “SCRTCH”

and your job would abort. Of course, if the JCL processor KNEW what I meant, then why did it have to abort?!?!?

Bruce McIntosh Says:
September 24th, 2008 at 12:41 pm

While not strictly an error message, on the original pcxt, if you put a floppy in a: and typed format insteat of “format a:” you got the message “format C: press any key to continue” The only solution was to kill the power.

MatD Says:
September 24th, 2008 at 12:41 pm

On the Beeb, if you tried to begin a BASIC program with a very large line number like this;

AUTO 10000000

The error returned simply said:

Silly

Citrus Says:
September 24th, 2008 at 12:43 pm

I still remember the joke, “Who is General Failure, and why is he reading Drive C:?”

worldofcrap Says:
September 24th, 2008 at 12:43 pm

As a video editor, my all-time favorite error is from Final Cut Pro:
“General error.”

Gee, thanks. Thanks a lot. Unfortunately, that’s probably THE most common error message from that (otherwise amazing) program.

frederick Says:
September 24th, 2008 at 12:46 pm

Once while using Mac OS 9.2, I was trying to open the control panel “Memory” and received the error message:

“The Application “Memory” could not be opened because there is not enough memory available.”

Rusty Belgrades Says:
September 24th, 2008 at 12:47 pm

Here are some random Windows messages I thought to be interesting.

detour Says:
September 24th, 2008 at 12:47 pm

A fun one I got from eclipse the other day: “An internal error occurred while showing an internal error.”

Jim Says:
September 24th, 2008 at 12:48 pm

Some from the mainframe era.

****GO DOES NOT EXIST BUT HAS BEEN ADDED TO THE DATA SET [IBM]

P
L
O
P
[Burroughs 5500 experiencing a kernel crash]

RATZ

[G.E. 635 when there was a peripheral error. RATZ was a prompt for
R – retry or A – abort or T – terminate or Z – go to user-supplied
error routine. And as with MS DOS, what’s the difference between
abort and terminate?]

You have synned and must pay a syn tax [some student-written compiler]

wordcross Says:
September 24th, 2008 at 12:51 pm

I’ve got a bit of nostalgia for the old “Internal Server Error” encountered on message boards of yore. We used to make up other words to fit the “ISE” acronym like “Internet’s Sort of Empty” or “Isn’t Sarumon Evil?”.

Michael Says:
September 24th, 2008 at 12:52 pm

Any of the old OS360 system failure codes – nick named SOCK codes. My favourite was S0C7, but S0C1 and S0C4 were common and equally enlightening as well. If I recall correctly: 0C7 was a DATA error; 0C1 was an INSTRUCTION error; and 0C4 was an ADDRESSING error. Details required a full system core dump to guess what the problem actually was.

Michael

Brian Says:
September 24th, 2008 at 12:52 pm

From IBM’s OS/2 Token-ring network driver: “Open error during physical insertion phase”. Boy does THAT sound painful.

Chris Says:
September 24th, 2008 at 12:53 pm

Why do we continue to perpetuate this myth that Macs are more stable than PCs? It’s simply not true. I’ve used both Mac and PC consistently for many years, and Macs have always been more prone to unexplained crashes and freezes. Even today, when I’ve got both a Vista PC and an OSX Mac sitting on my desk, the Mac is significantly less stable. Am I really that unlucky?

Dan Says:
September 24th, 2008 at 12:57 pm

On teh IBM 7094 in the early 1960,s a divide by 0 caused an endless microinstruction loop that would ultimately damage the circuitry if left to run for more than about a minute. Therefore, all 7094 sites used a cheap 2-trnsistor AM radio to monnitor the comoputer by listening to the generated noise. When the noise ceased to sound like hash and became a pure tone, a divide by zero was being executed and the operator needed to reboot the machine. That pure tone is the worst error message.

José Says:
September 24th, 2008 at 12:58 pm

I saw a dialog box with an error in Netscape navigator 3.x. I don’t remember the error message, but the tittle was “Fuck U!”.

Bantolph Says:
September 24th, 2008 at 1:03 pm

I always love the sick Mac that showed up on the old Macintosh Pluses and SEs if you had a hardware fault. It was the cartoon mac with an ice pack, +’s for eyes, and a thermometer in it’s mouth.

sandman Says:
September 24th, 2008 at 1:08 pm

Jason – you need an earlier BSD Make.

At one period this make had a built in rule for the love target.

In went like this:

$make love
Not war?
$

blc Says:
September 24th, 2008 at 1:14 pm

My favorite was an old Excel error that read simply “Error: Not Enough!” and had the “Ok” button only. All I could think when I’d see it was, well then, give me some more.

blc Says:
September 24th, 2008 at 1:15 pm

And for the most childish intentional error award…

$man woman
no manual entry for woman

Ian Ferguson Says:
September 24th, 2008 at 1:15 pm

‘Syntax Error’ is a far-reaching message omitted from this list – I’ve seen it on many platforms. As a child, I probably learned the meaning of the word ‘syntax’ from it – I certainly remember not being sure what the error message meant in terms of English, but understanding what to do about it.

The one I voted for – although I can’t say it’s my ‘favourite’ – had to be Abort, Retry, Ignore. I remember screaming in pain many times when encountering that one. 🙁

mancfrank Says:
September 24th, 2008 at 1:19 pm

What? Macs crash?
Everything I’ve ever heard says Macs don’t crash – has someone been telling me lies?

pgraham Says:
September 24th, 2008 at 1:21 pm

Here’s some error message poetry:

Alas!
I am unable to complete my task
I tried to do what you have asked
But it will not come to pass

Asked again, the same result
I will not make it past this halt
Maybe it was a segment fault
But you have to see it’s not my fault

I’ve done as I’ve been told to do
When asked to do what you’ve asked me to
I have no choice, about what to do
I simply do when instructed to

It’s the person that’s in charge of me
That’s lacking in some faculty
For they have not made into me
What you ask, a capability

m4 Says:
September 24th, 2008 at 1:21 pm

University of Minnesota Fortran compiler, Mid-70’s, called mnf had an extremely rememberable error message (for any mistake in syntax) of “?”

No line number, character position, nothing. Just a question mark.

How do you find the problem? Binary-chop compilation of the program …

Dunx Says:
September 24th, 2008 at 1:23 pm

My favourite error messages:

“ACD file is no set, bozo” – error message which really shouldn’t have shown up in a customer demo, especially when the program was just starting.

“There is something wrong with CMS or something it calls” – DEC VAX CMS failing badly.

Also… [Marc] “LOAD LETTER” might be useful in the States, but it is about as helpful as a not very helpful thing if the only paper you use is A4.

Bob JOnes Says:
September 24th, 2008 at 1:25 pm

I once got a linux error that read “This process is taking longer than expected. Odd.” Got a kick out of that one.

g Says:
September 24th, 2008 at 1:27 pm

From the original Mac OS:
-73 – badDBtSlp – bad data mark bit slip nibbles

Richard Says:
September 24th, 2008 at 1:29 pm

I encountered a great one on Windows 98 a few years ago: “Ran out of memory trying to allocate 0 bytes”

NoJo Says:
September 24th, 2008 at 1:30 pm

Picking up on the Cadnetix theme, back in the mid-80’s, I worked as a software engineer for a Cadnetix “competitor”, Mentor Graphics. I supported about 400,000 lines of code someone else had written in about three weeks’ time (we were a startup, afterall). One day we fielded a call from an irate customer. See, this customer was mad because his missile defense system design work had been interrupted by an error message that said: “Beam me up Scotty, she’s sucking mud!”

Todd Says:
September 24th, 2008 at 1:30 pm

My favorite error happened when playing Half Life (the first one). I would get “fatal error: unknown error” How can it be an “unknown” error but you still knew it was an error? I even took a screenshot and have it somewhere.

For the non-techys, when an error occurs usually the program will check to see what type of error it was to better inform the user (ex. if a hard drive was full, or even some cryptic library caused the crash). Unknown error is the ‘catch-all’ when the program wasn’t explicitly told what that error message meant.

Matt Says:
September 24th, 2008 at 1:36 pm

I think this one is pretty good:

http://www.mrfisch.com/404.html

John Howell Says:
September 24th, 2008 at 1:37 pm

The error messages I hate the most are the ones that say something like “A serious error has occured. Please see your system administrator”

I am the freeking sysadmin and I don’t know what just went wrong!

John Howell Says:
September 24th, 2008 at 1:38 pm

I also like Googles homage to the “sad mac” by having a “sad tab” in chrome when it keels over.

Jim H Says:
September 24th, 2008 at 1:43 pm

My favorite error of all time was on the Xerox Sigma 9 mainframes. You’d be typing along and all of a sudden, you’d get this message:

Your FLP overflows into your KBUF.

topyli Says:
September 24th, 2008 at 1:44 pm

Not an error (quite the opposite!) but when your hungry adventurer eats an apple in nethack, the system returns:

Core dumped.

Adam Says:
September 24th, 2008 at 1:47 pm

GENERAL FAILURE READING HARD DRIVE

was always one of my favorites.

KudyardRipling Says:
September 24th, 2008 at 1:47 pm

There was a bug when CALL -2458 was run to invoke the mini-assembler on a Franklin Ace 1000 (an Apple ][ clone) without integer BASIC loaded:

>RXNT@X DRRNR or
?SYOUAY!ESSOS

Entering anything other than an empty linw would cause the screen to spaz out in graphics mode that was described as Old Glory.

imipak Says:
September 24th, 2008 at 1:47 pm

If we’re going to include special-case crashes, the BBC Micro had an interesting case. If you type:
10 gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10:gos.10
The computer will crash. You don’t even need to run the code, it’ll kill the system stone-dead. Something similar happens if you type:
10 dim a%(1,1,1,1,1,1,1,1,1,1,1,1,1,1)
There was something screwy about the system that caused code that had very specific faults (it has to be a 14-dimensional DIM, and you have to use contracted gosubs in the first case, gotos won’t have the same affect.
The Commodore PET had an interesting POST error – the screen would fill up with random characters, if it failed to past the test. Well, strictly, the screen filled up as part of the test and were cleared by another part. If anything between failed, that’s your BSoD. Well, GSoD, as PET monitors were green screens. If the machine was starting to go wrong, you’d sometimes see those characters freeze for a bit before the system continued.
I can’t remember which one it was but I believe there was an OS that produced ALL of its error messages in a Japanese style of short poetry.
I can’t remember if the Acorn Archimedes, Oric, Sinclair ZX81 or TRS-80 did anything interesting in the way of errors – more fans of the weird and wonderful are obviously needed to fill in this critical gap in knowledge.

mike Says:
September 24th, 2008 at 1:48 pm

Bash -2.05a#
SmartStart Error – a haiku the SmartStart Development Team

A fatal error
Continue, SmartStart cannot
Agony reboot

Utilities run:
ACU

m2pc Says:
September 24th, 2008 at 1:52 pm

My favorite is from MySQL when your connection drops during a query:

“MySQL server has gone away”

Gone away to where? On vacation?

nikh Says:
September 24th, 2008 at 1:53 pm

My first time ever on a computer was in class, on an Apple II. I must have made an typo in the first command, because I only got “invalid operator” as response.

How could the thing know?

Capn Zig Says:
September 24th, 2008 at 1:55 pm

I got a great one that I had to screen capture for posterity. I was running Virtual PC on a Mac (G3, I think). I loaded WinBench 96 to see how slow it really was, and was delighted to see this:

“WinBench 96 cannot determine the refresh rate because the computer is too fast.”

Amacman Says:
September 24th, 2008 at 1:56 pm

When talking about post beeps, how could anyone ignore the famous macintosh version? It a car crash, tires screech, sound of impact and breaking glass. That gets your attention!

Pod Says:
September 24th, 2008 at 1:57 pm

My wife works as a social worker and often has to deal with medical
software for elder care planning – she brought home a printout
of a screen dump of an app that said “amputating the head is not an
option” which always makes me laugh when I see it.

fireman Says:
September 24th, 2008 at 1:58 pm

What About UAE? from Windows 3.0? Unrecoverable Application Error: Terminating Current Session.

Then theres good old Star Trek TOS: “Error Error! Must analyze Must Analise!!!”

NoMad the space probe.

Pod Says:
September 24th, 2008 at 1:59 pm

I used to work at a company that produced printers. One time I saw the
following error: “The such and such printer utility must shut down as
the developers must go to a really freaky party.” Apparently that was
never supposed to be seen by the public but it did happen once in a
while.

Joe Says:
September 24th, 2008 at 2:01 pm

– After waiting and watching the ‘**’s flash from loading a program on cassette tape… 1979 – TRSDOS (Level I/II – back when 16k was LOT of memory)

SOC7

– mainframes… yummy! (so good was I at finding them, the entire campus came to me to help with their labs… that was not fun after a while.)

* $$ Job Aborted

– CICS – no further message to debug… the box just didn’t like it)

‘Access Denied’

– even in conversation that phrase comes up… quite funny.

Peder Says:
September 24th, 2008 at 2:03 pm

And to continue Steve’s BSoD screensaver explanation, the xscreensaver for linux/bsd has lots of error messages to choose from, including BSoD, and I believe it precluded sysinternals.

Christopher Nicholson-Sauls Says:
September 24th, 2008 at 2:06 pm

One of my personal favorites:
“IRQ not less than or equal”

My god, its greater than… something.

Cookie Monster Says:
September 24th, 2008 at 2:07 pm

Definitely the guru meditation. By far my most fav.

Trivia: The flash time on the meditation screen is the time taken for the 68000 CPU to do a dbf loop. The count on the dbf loop is 6809. A nice tribute to a nice processor.

There’s also the old Microsoft basic one of:

?SN ERROR (Dragon 32/COCO).

Jinxos Says:
September 24th, 2008 at 2:09 pm

My favourite: “Error: Catastrophic Failure” rarely appearing in Windows anymore, but popular with NT

Gary Says:
September 24th, 2008 at 2:20 pm

I’m surprised there was no mention of the famous “NTLDR is missing” message that is displayed on Windows NT 4.0 and higher operating systems when there is a problem with the boot drive. That one has been a big annoyance to me for years.

Dan_k_Nj Says:
September 24th, 2008 at 2:20 pm

My all-time two favorites;

1. C-64’s. Referring to an attempt to access a peripheral (floppy drive). “Error #0. Power not on.”

2. Student: “What does ‘Missing Period is assumed’ mean?”
Me: “I dunno… pregnancy?”

Puggs Says:
September 24th, 2008 at 2:22 pm

Being a programmer from way back (before PC) and having a wicked sence of humor, i use to put in error messages like the following;

Erorr in line xxx, Press any key to continue or any other key to quit?

Puggs

NeilG Says:
September 24th, 2008 at 2:24 pm

One of our programmers messed up with his error trapping, so when our customers installed the latest update, in the usual Windows fashion, up popped the following message, with the big red X :

An error [0 : 0x800blah] has occurred while running setup:

Please make sure you have finished blah, blah blah etc. etc.

Report | Detail | OK

When you clicked on Detail you got:

Error Code : 0
Error Information : Success!

Wonderful 🙂 Our helpdesk had a busy month.

Mario Says:
September 24th, 2008 at 2:24 pm

Well I remember one error. Might have been from MS Access:

“Can’t sort database, printer is out of paper”

Andy Says:
September 24th, 2008 at 2:25 pm

I think the FailWhale picture is supposed to be symbolic of how hard it is to keep a server “up” and running with such a huge a load (the whale) put on it, as with sites like Twitter.

Justin Richards Says:
September 24th, 2008 at 2:31 pm

back when i was just learning C++ i used the borland turbo c++ 3.1 ide. i once got 30 errors with the final error saying “error. too many errors”

Nick Says:
September 24th, 2008 at 2:35 pm

One of my favourite useless error messages I’ve seen was from a Mac program (I forget which):

“something impossible has happened”

I’ve generally found Mac programmers had a flair for witty error text (along with many *nix programmer), although I mostly saw this through examining programs with ResEdit rather than in using the programs.

I have a soft spot too for the really easy to read errors on the ZX81. Classics like 0/1 or other equally eloquent prose could keep one entertained for hours.

While not real error messages and only ever seen by a few class mates, I once wrote a spoof CPM command line interpreter for April fools day in the mid 80s and loaded it on all the machines in the schools lab, spoofing the genuine network boot sequence and then responding to any commands with genuine error messages at first, and then slowly with more frequent pseudo error messages that sounded almost right but getting increasingly silly such as:

‘fire on main board error’
‘Illegal command, call 999’
‘Command not found, have you checked your pockets?’
etc…

Doug Says:
September 24th, 2008 at 2:38 pm

Sheesh! You kids had it easy! In my day Crystal Reports didn’t even tell me if I had an error. It would just pop up a dialog box with nothing in it other than an OK button. I first had to find out if it was an error message on my own before I could figure out what the error was! Up hill! Both ways!

Warren O Says:
September 24th, 2008 at 2:39 pm

From the companion CD for the first printing of Bill Gates’ book The Road Ahead:

“Sorry, The Road Ahead does not run on Windows NT.”

Longest-running useless error message:

“A device attached to the system is not functioning.”

It’s been in Windows for many years, and still rears its ugly head occasionally. I’ve never seen it actually caused by a hardware or device problem, and it provides no clue what went wrong or where to look.

Nice article, it brought back some memories! Too bad BSoD is such an obvious #1…

kent Says:
September 24th, 2008 at 2:39 pm

From the PDP-11 days
‘M trap to 4’
I think I actually still remember what that means.
**kent

JorgeM Says:
September 24th, 2008 at 2:40 pm

Probably the worst error screen these days is the VMware Purple Screen of Death. For me, it means that 15 VMs or more just had the power cord yanked on them. Fortunately, like the MS BSoD these days, its rarity.

Hal C F Astell Says:
September 24th, 2008 at 2:41 pm

My favourite error comes from the Remedy app, which many IT departments use to track changes, problems, inventory etc. Remedy is an Action Request System and so anything that goes wrong is an Action Request System Error. When this becomes an acronym it becomes hilarious in certain countries. I remember seeing printed out copies on the wall back in England that read: ‘You have experienced an Action Request System Error (ARSE).’

John Lu Says:
September 24th, 2008 at 2:45 pm

Interview with Yiying Lu regarding fail whale

http://drawn.ca/2008/07/21/fail-whale/

Harry Johnston Says:
September 24th, 2008 at 2:47 pm

One of my colleagues has a screenshot of an error message generated by the Macintosh version of Eudora some years back. I quote verbatim:

Server not responding.
3.
The network failed (what this means is “to be supplied in a future version of the MacPCP documentation”, fat lot of good that does).

AzureLunatic Says:
September 24th, 2008 at 2:54 pm

My favorite 404 of all time is marnanel.org’s, which is a sonnet (written by the owner; I asked):

http://marnanel.org/404

So many years have passed since first you sought
the lands beyond the edges of the sky,
so many moons reflected in your eye,
(familiar newness, fear of leaving port),
since first you sought, and failed, and learned to fall,
(first hope, then cynicism, silent dread,
the countless stars, still counting overhead
the seconds to your final voyage of all…)
and last, in glory gold and red around
your greatest search, your final quest to know!
yet… ashes drift, the embers cease to glow,
and darkened life in frozen death is drowned;
and ashes on the swell are seen no more.
The silence surges. Error 404.

foo Says:
September 24th, 2008 at 2:58 pm

PC load letter!!

cristiantm Says:
September 24th, 2008 at 3:00 pm

Nice list.

I would only add a mention the Kernel Panic on modern Linux: When it happens, all just freezes, and while you try to guess what happened since there is no message or anithing, you look at your keyboard, and there is the answer: the flashing “caps lock” LED, telling you that you have a kernel panic.

rootvg Says:
September 24th, 2008 at 3:02 pm

wheres the “deadbeef” error message?

GIBson3 Says:
September 24th, 2008 at 3:05 pm

Just throwing this out there…

The BSoD Screen saver that is now available on Microsoft’s website was actually written by the boys at SysInternals, the people that brought Process Explorer and PS tools to the world. These programs (and others) were so much more useful than the Microsoft versions that I and a few others I know used them as System32 drop in replacements for the official utility. It seems that Microsoft noticed this too, so like always, they bought out SysInternals and thus started distributing a screen saver that does a fantastic job of mocking their OS.

As of all time favorite Error messages, I’m not sure, the most memorable however was the first time I got a Kernel Panic on my linux box. Happened when I rebooted after my first ever kernel build…

soakesafmc Says:
September 24th, 2008 at 3:08 pm

The original 1970’s Unix diff command simply said one word when it couldn’t handle the job:

jackpot

DaveFromAus Says:
September 24th, 2008 at 3:09 pm

Before Windows, before AmigaDOS, before MS-DOS, there was CP/M, a tiny OS that shoehorned the whole OS, plus one application (Wordstar, Fortran, etc) into 64k of RAM.
It didn’t have much space for error messages.
It’s equivalent of the BSOD was –
“BDOS error on A/B”, depending on whether the problem was associated with the A or B floppy drive.

Roy Says:
September 24th, 2008 at 3:13 pm

…as mentioned elsewehere,
I can’t believe that “I’m sorry Dave, I’m afraid I can’t do that” didn’t make the list.

Don Says:
September 24th, 2008 at 3:14 pm

Produced by a very old application:

In case of error call 705-555-1234

A console operator dialed the number….and got Dial-a-Prayer.

Steve Says:
September 24th, 2008 at 3:19 pm

Keyboard error or no keyboard present… Press F1 to continue.

TimothyLuke Says:
September 24th, 2008 at 3:21 pm

What about the good old “General Protection Fault” with its obligatory “OK” button.

MrVeedle Says:
September 24th, 2008 at 3:26 pm

I’m surprised no one mentioned the dreaded IBM PC-XT error 1701: HDD Controller Failure.

I had a number of PC-XT clones back in the day, and the aftermarket MFM/RLL controller cards were notorious for dropping dead without notice.

Krozar Says:
September 24th, 2008 at 3:32 pm

Let’s not forget the Dr. Watson error. Or, as I like to call them, the Dr. Kevorkian error, because the error never fixed anything… it just helped your program kill itself!

Nefarious Wheel Says:
September 24th, 2008 at 3:34 pm

The fictional “Excuse me don’t excuse me Ah Clem, you have made The Doctor unhappy happy, and will be asked to leave the future immediately”.

This was from “I Think We’re All Bozos On This Bus” by the Firesign Theatre. This cult comedy album described “The Future Faire”, an entirely virtual theme park where you got to speak to a hologram of President Nixon, who was “The Terminal Bus”. Ah Clem was your quintessential hacker (“Please state your name” — Ah…Clem.) who gummed up the works. Verra strongly recommended listen if you find a copy.

Rather visionary, considering it was composed during the punch-card era.

sync Says:
September 24th, 2008 at 3:37 pm

Twitter !!!!! all time, I don’t think so. What about Cyclic Redundancy Check.

Colin Fox Says:
September 24th, 2008 at 3:37 pm

The BSOD screensaver was made by a company called Sysinternals, which was then bought by Microsoft several years later. So no, Microsoft did not make it, Sysinternals did.

uellue Says:
September 24th, 2008 at 3:41 pm

The Twitter whale is kinda obvious: The servers are dragged down by the heavy load!

NEWK Says:
September 24th, 2008 at 3:41 pm

Google Chrome has a “sad tab” when a tab crashes (since each tab is a new process in Chrome). It looks similar to the “sad mac”.

knutbert Says:
September 24th, 2008 at 3:41 pm

I once deleted the /etc/passwd file (the user database) while being root on my linux box. After that each subsequent command gave the error:

“You don’t exist. Go away!”

That’s still my all-time favourite! 🙂

Tin Britches Says:
September 24th, 2008 at 3:45 pm

During my college days I programmed an SDS Sigma 7 running BTM/BPM and UTS/CP-V.

If, during a timesharing session, you fouled up a command, you would
get the error
$ EH @ xx
where xx was the offset from the first char where the command line parser figured out something’s wrong.

When the system crashed, it would send to all timesharing terminals:
(bell)(bell)Recovery says stand by…

With the FORTRAN compiler, if you used “JAIL” as the variable in an
assigned GO TO, i.e. “GO TO JAIL”, the compiler would emit the error
message:
WARNING GO DIRECTLY. DO NOT PASS GO.
DO NOT COLLECT $200. STATEMENT DELETED.

Jason Says:
September 24th, 2008 at 3:47 pm

Seriously how can Visual Basic’s incredibly helpful “Unknown Error” not make this list?

uellue Says:
September 24th, 2008 at 3:51 pm

Are the Linux blinking keyboard LEDs mentioned anywhere? Like a dead person holding up a sign reading “I’m dead”.

Modified_67 Says:
September 24th, 2008 at 3:51 pm

My all-time favorite:

“No mouse detected. Click OK to continue.” WTF? How can I click something if the mouse isn’t detected?

Bit101 Says:
September 24th, 2008 at 4:01 pm

Error I got in a freeware game:
“What the bloody hell did you do?”

Grim Reaper Says:
September 24th, 2008 at 4:01 pm

An EKG flat line.

Kinda says it all.

Sarah F. Says:
September 24th, 2008 at 4:01 pm

My personal favorite was Windows’ “You have performed an illegal operation.” When Windows was throwing that around willy-nilly, any seasoned Windows user thought, “BFD.”

Now, imagine my aunt’s surprise when this occurred when she bought her first computer back in 1998. There are three things that you need to know about my aunt:

1. She’s a luddite.
2. She’s neurotic.
3. At the time, she was a cop.

When “You have performed an illegal operation” popped she.freaked.the.h.e.double.hockey.sticks.out. It was really quite comical. She truly believed that she had done something against the law and was going to jail. I have fond memories of this day.

Alan Macdonald Says:
September 24th, 2008 at 4:08 pm

Way back in my school days in the 70’s, we had a GE 115 mid-size (at the time) computer. It had a COBOL compiler that was coded in Italy. We even had the source, assembler with Italian comments.

Occasionally we would get “compilation noa gooda” error message.

Jay Kim Says:
September 24th, 2008 at 4:14 pm

Does “By Your Command” count as an error message in that it was given right before the destruction of the human race?

John Says:
September 24th, 2008 at 4:19 pm

The TRS-80 Model III Level 1 computer had a “friendly” version of BASIC that reported only three possible errors – “What?”, “How?” and “Sorry!”. “What?” means syntax error, “How?” was a procedural error and “Sorry!” meant out of memory. This was more “friendly” to the user than all of those cryptic words like “syntax”. Type in a 20 line program with a syntax error somewhere then run it and get “What?”.

Krpalospo Says:
September 24th, 2008 at 4:40 pm

good excellent post, There are a screensaver in xscreensaver call BSOD that have all famous messages errors incluing all in this post .

Bits Says:
September 24th, 2008 at 5:02 pm

IIRC, the original BSOD was just blue (no text at all); I first saw it in a Windows beta. The docs that came with the beta actually referenced the error as “the blue screen of death” and, when we called M$ to tell them we’d seen a BSOD, they wanted to know where we’d heard the name (it was removed from the next copy of the docs).

In any event, my vote goes to “PARITY CHECK 2”.

Jamie Says:
September 24th, 2008 at 5:03 pm

Has anyone mentioned Scandisks annoying “You did not shut down your computer properly” message?…

It has to be the most annoying message ever encountered.

Rotaluclac Says:
September 24th, 2008 at 5:06 pm

The 4DOS command interpreter showed me “Illegal error”.

Rotaluclac

Tim Says:
September 24th, 2008 at 5:08 pm

The joys of learning to progam (and now teaching it):
COBOL (data error – 15 years since I programmed in COBOL as a student and it is still ingrained in my head):
INVALID DECIMAL DATA
SYMBOLIC STACK DUMP

Smalltalk (just about any syntax error – 15 years ago and no fond memories):
Smalltalk does not understand

C++ with the DevC++ compiler (student types Main instead of main):
[Linker error] undefined reference to `WinMain@16′

muzic Says:
September 24th, 2008 at 5:09 pm

I always found the Bomb when a Mac crashed entertaining.

mark Says:
September 24th, 2008 at 5:34 pm

I think one of the best BSoD I ever saw was at COMDEX. We arrived early for the Bill Gates speech. There was a few dozen people already there. They had the projector on and was setting up the Microsoft demo for Gate’s speech when the blue screen appeared. The person quickly turned off the projector. The funny thing is they were demoing WIN ME which they claimed was more stable then 98 or 95. The WIN ME had multiple errors during the presentation while the WIN98 demo machine was solid as a rock. They tried over and over to get the WIN98 machine to crash and it wouldn’t

richard Says:
September 24th, 2008 at 5:34 pm

If any fictional messages are going to be included, then number one on the list must certainly be

“I have detected a fault in the AE35 unit. It will go 100% failure within 72 hours.”

Two must be (from “Forbidden Planet”) Robbie’s menacing:

“Morbius, something is approaching from the southwest. It is now quite close.”

And three through ten or so is just about anything printed or said by Colossus in “Colossus: The Forbin Project” (http://www.imdb.com/title/tt0064177/quotes).

Cpt. Charisma Says:
September 24th, 2008 at 5:42 pm

One of my favorites is a Linux error. It appears in several KDE applications, such as K3B and the print tool, that are just front ends for command line tools.

“Error: Success!”

Also, the X Windowing System (the Linux GUI) used to give an error along the lines of:
ERROR: I don’t know what to go. Giving up.

Finally, several people have already mentioned the blinking keyboard LEDs for Linux kernel panics. What many people don’t know is that there is an option to have the actual error transmitted in morse code via the LEDs.

Vic Says:
September 24th, 2008 at 5:43 pm

What about the ‘Click of Death’ on Zip Drives made by IOMega that used those 100MB Zip disks.

This was a sound made by defective drive that would indicate that permanent failure was imminent.

Fulko Hew Says:
September 24th, 2008 at 5:49 pm

My favorite error message was from Windows 2000 (I think), when I got a blue screen that said: “Your system has become unstable. Wait for it to become stable again, or reboot.” Well I waited and waited, then went out for lunch, and since it hadn’t become stable again after 2 hours (now did you really think it would have?)… I rebooted it.

Rob Menke Says:
September 24th, 2008 at 5:56 pm

The Macintosh Programmer’s Workshop C compiler (what you used to make Mac programs prior to MacOS X) had a number of quirky error messages that would pop up in unusual situations. Four of my favorites (from memory — not exact) were:

You cannot swim upstream, modify a constant, win an argument with the IRS, or satisfy this compiler.

String constant exceeds 512 bytes (which is three more than what ANSI says I must give you).

Out of memory for symbol table: please go purchase more RAM from your Authorized Apple Dealer.

And this one was my .signature file for the longest time:

Type in (cast) must be scalar; ANSI 3.3.4; page 39, lines 10-11 (I know you don’t care, I’m just trying to annoy you)

Gryphon Says:
September 24th, 2008 at 5:57 pm

No BDOS ERR ON A: SELECT? yet? CP/M was even more cryptic than DOS sometimes.

The best, and most frustrating error I’ve ever seen was on a PDP-11/34A running Unix System 3. These were used to test relay frames, and had line printers as the only output. You could start a test, and turn away from them – the noise of the printer would tell you how the test was going. Every so often, the printer would stop, and just as you turned back, it would spit out “Death.”

DL=0 and try again.

anonymous Says:
September 24th, 2008 at 6:01 pm

yeah the first transparent ZIP drives were called the iClick.

v.dog Says:
September 24th, 2008 at 6:28 pm

the ‘Keyboard not present. press F1 to continue’ error should have been No.1

Some of my own favourites:

I pulled out my modem once, put it back, and when I rebooted my BIOS beeped ‘de do de do de do…’. One beep would have meant OK, two would have meant bad RAM (or something), a siren though? New PC time.

From the game Narbacular Drop: “D3D takeover of window failed. This should never happen, so there’s really nothing you can do.”

From Dr Watson (error reporter): “Dr Watson Postmortem debugger has encountered a problem and needs to close. We are sorry for the inconvenience.”

Adam Says:
September 24th, 2008 at 6:28 pm

I got an event viewer message once that once said

“There was an error starting Microsoft Exchange Information Store – the operation completely successfully”

The Irony

pwnt Says:
September 24th, 2008 at 6:31 pm

# Emily Says:
September 18th, 2008 at 8:57 am

I once returned two CPUs due to the Post beeps on my system. According to the manufacturer of the motherboard, the set of beeps I was hearing meant a failed CPU. Actually, the RAM was bad and confusing the system into thinking the CPU was bad.
When I was 5, I did something to my parents brand new ($5000) Macintosh and got sad mac. I thought I’d destroyed the machine and hid under my bed. All they did was eject the floppy I’d left in and kept on going.

Only a woman could be that stupid when it came to computers. Go back to hiding under your bed n00b.

James Says:
September 24th, 2008 at 6:34 pm

How about the Atari 400/800 –

0 – POWER NOT ON

David Thornley Says:
September 24th, 2008 at 6:41 pm

The original TRS-80s, with the “level 1” 4K ROM, had three error messages: WHAT? (syntax error), HOW? (runtime error), and SORRY (out of memory). At least it displayed the offending line with a question mark in more or less the place where the error was found.

Tim Says:
September 24th, 2008 at 6:54 pm

I get a dialog box every so often on exiting windows a box titled “you should not see this” “click ok to continue”

diss Says:
September 24th, 2008 at 6:56 pm

in the fictional error messages category, my favourite is
“++?????++ Out of Cheese Error. Redo From Start.”
by HEX.

of course, HEX is a system which runs better the more bugs you put in, so this might just make sense.

TT12 Says:
September 24th, 2008 at 6:56 pm

“Absolutely, absolutely.”

You stupid sycophantic advertising scumball.

sp1k3 Says:
September 24th, 2008 at 7:03 pm

Best I have seen on a Altos 2000 ”
Double Panic Trap Saving information for a post mortem”

Milo Says:
September 24th, 2008 at 7:16 pm

“Ultimately, it’s not going too far to say that the BSoD is a sort of persistent, universal reminder of the fallibility of computers …”

No, it’s not. It’s a reminder of the fallibility of humans. Computers “fail” because those who built it or programmed it or use it have done something wrong. It’s not the hammer’s fault if the head flies off the handle. Don’t blame the tool for the shortcomings of humankind.

David Lacey Says:
September 24th, 2008 at 7:20 pm

My favorite is from the Apollo Domain workstations:

Error 220009: unit will not fit thru 25″ hatch (OS/magtape manager)

This refers to a large computer manufacturer (former employer of some of the
Apollo OS folks) that once bid on a government contract to supply computing
equipment for use on board submarines. They lost the contract when the
government discovered that the tape drive would not fit through the 25 inch
hatch used to load equipment onto a submarine. Anything that won’t fit
through the hatch has to be loaded by cutting a hole in the hull.

Mike Says:
September 24th, 2008 at 7:31 pm

“Richard Keil Memorial Abend #27”

PCH Says:
September 24th, 2008 at 7:40 pm

No Lotus Notes ones?

When Notes fell over and crashed, it would write a RIP file, which was produced by QNC.exe (Quincy). The output file was headed “Coroner’s Report”

By messing with resource forks on Macs, you could get some very curious error messages, something like “this file was created by a program that doesn’t yet exist”

Dave Says:
September 24th, 2008 at 7:41 pm

I’m sorry, Dave, I’m afraid I can’t do that.

HWR Says:
September 24th, 2008 at 8:00 pm

My favorite, from IBM MVS:

IEC999I “Probable user error. Correct job input and resubmit.”

Dohn Joe Says:
September 24th, 2008 at 8:03 pm

“To err is human, but to really foul things up you need a computer.”

Hmmm…I prefer:

“To err is human, to blame a computer for the err is VERY human.”

Elder Says:
September 24th, 2008 at 8:18 pm

One last try at naming the building in the New York BSoD picture: Port Authority Bus Terminal, 42nd St and 8th Ave.

Mario Says:
September 24th, 2008 at 8:24 pm

On Win98: Error! Operation succeeded.

Leigh Says:
September 24th, 2008 at 8:30 pm

Another old UNIX shell funny error:

$ man: why did you get a divorce?
man:: too many arguments.

Mario Says:
September 24th, 2008 at 8:34 pm

Amiga had a useful feature though: when it was about to crash, it would flash the power light indicating that you’d better save anything you were doing because it was going bye bye!

fred james Says:
September 24th, 2008 at 8:44 pm

There was a Microsoft MSDOS Basic compiler that could produce an
FU error code. This code was not documented in the list of error
codes and no one at Microsoft U.K. could tell me what it meant.

Bev Says:
September 24th, 2008 at 8:46 pm

‘USER DID ERR in line ‘ from some version of FORTRAN. Judgmental, almost biblical.

Tony Powell Says:
September 24th, 2008 at 8:51 pm

I often get this dialog error box when using Rhapsody:

“There was no error.”

Divine Bird Jenny Says:
September 24th, 2008 at 9:04 pm

What, no TILT?

Nick Says:
September 24th, 2008 at 9:11 pm

*snip*
The Sad Mac has such a strong flavor of early Macintosh-ishness that it’s easy to develop a false memory that it was part of the platform from the beginning in 1984. Nope–Wikipedia says it first appeared in 1987
*snip*

And who ever uses wikipedia as a reliable source of information? I have an original 1984 Macintosh in my collection that greets me with a sad mac every time I turn it on due to a failed RAM chip.

Paul Smith Says:
September 24th, 2008 at 9:13 pm

A schematic capture package for MS-DOS I used many years ago (Schema II) would ocassionally crash.

Every time in crashed, somewhere in the output would be the words:

“Fairfield New Jersey is AT&T”

The package included many command line tools as well that would sometimes produce this same output.

I always wondered why in the word this text would even be in such a software package.

Sherif Says:
September 24th, 2008 at 9:16 pm

NO CARRIER

Mainframe Mangler Says:
September 24th, 2008 at 9:24 pm

For those who remember mainframes, the best (IBM) mainframe error was 0C0 — Imprecise Interrupt. Somewhere back in the preceding 63 halfwords of instructions (as interpreted by the machine, so not just in the program(s) under consideration) was one (or more!) conditions that caused an interrupt. When? Where? Why? Only the hardware designers knew for sure (and they weren’t around to tell you).

Eric Says:
September 24th, 2008 at 9:37 pm

How about as recently as IE8 Beta :

“Internet Explorer is currently running with add-ons disabled. Click here to manage, disable, or remove your add-ons.”

Not only are all “add-ons” enabled, but WTF is with “add-on?” is this microspeak for plugin? what’s wrong with plugin? everybody else in the world informally convened and agreed to use “plugin” to mean plugin. why does microsoft unnecessarily complicating things have to run into to vocabulary too ? i want an answer on this choice of word – “add-on.” And while I’m at it, how about (also from IE8)

“You have approved this plugin to run on the following sites: *”

Really? “*”??? Now is that “*.com”, “*.org” or “*.*”? I see microsoft has really made great strides towards making their products more user-friendly since their “illegal operation” error messages . . .

Jevon Says:
September 24th, 2008 at 9:38 pm

99.9999999999999% ??

That means that only one person, in the entire world, has ever understood what hexadecimal numbers meant for 4 hours of their entire life.

Nice exaggeration 😉

A Non-idiot Says:
September 24th, 2008 at 9:44 pm

The keyboard errors suggesting you press F1 to continue were only funny if you were a moron. If you were not a moron, you simply reconnected the keyboard connector that had become dislodged, and pressed F1, as suggested. I have much fonder memories of the SYNTAX ERROR I saw all too often when my poorly-coded BASIC programs crashed on the ol’ Apple II.

vinodvm Says:
September 24th, 2008 at 10:22 pm

Where is the “Segmentation fault”

Timothy Says:
September 24th, 2008 at 10:39 pm

Here’s my favorite:

OS/2 !! SYS01475
OS/2 !! SYS02027

Those lines mean “boot record not found” and “insert a bootable system disk and restart the system.” You would see them if you (or somebody else) formatted a diskette with OS/2, inserted the diskette in Drive A (the boot drive, on your machine or someone else’s), and restarted the system. These cryptic errors confused almost everyone.

You would see these two lines instead of, say, “Diskette not bootable” for two reasons. The first reason is that the boot sector contains limited space, so the messages had to be short. The second reason is that IBM product development bureaucracy ran amok. Instead of displaying an error message that would be decipherable to at least the English-reading world, IBM national language standards required that the error message be language-neutral and thus indecipherable to the whole world. Since (unlike a Mac) there are no graphics available at that point in the boot process, there was no opportunity to display the equivalent of a Sad Mac (or Sad Diskette). And since you cannot fit all major languages in just a few bytes, you got a pair of cryptic SYS numbers. The “OS/2” part was completely misleading. That was supposed to mean “check your OS/2 documentation for a list of error messages to figure out what the rest of this means,” but the immediate cause of the error had nothing whatsoever to do with OS/2. You’d see this same error if you left any OS/2-formatted diskette in Drive A and rebooted a DOS, Windows, or Linux PC. (OS/2 formatted diskettes as FAT also, so that wasn’t the issue.)

IBM is very good about providing error numbers for every error, which helps make supporting their products much easier. And the rest of OS/2 (i.e. after boot) would always display the error description alongside the code number in whatever national language was active at the time. That’s all really great design. But in this particular case IBM got silly.

Unfortunately IBM never fixed this. They insisted this was “working as designed.” Which is exactly the problem. They could have even fit “Floppy in Drive!” (or “Diskette Error!”) as the first line and kept “OS/2 !! SYS02027” as the second line to make almost everyone happy, but sadly no.

Ross PResser Says:
September 24th, 2008 at 10:39 pm

For me, it was the TRS-80’s version of the MS-BASIC syntax error:

?SN ERROR

or even better,

?L3 ERROR

which indicated you’d used a command that didn’t exist YET, hence a Level 3 error. (This on a 16K Level II system.)

Dave Says:
September 24th, 2008 at 10:49 pm

I think that the “Microsoft Workers In Hell” page that can be reached in certain versions of Excel from Line 666 deserves mention. It shows the programmers working in flames, etc. It’s really more of a hidden Easter Egg than a bad error message, but it does get across that espirit-de-corps feeling of working there.

Certainly the Atari ST “Bombs” screen, where the number of bombs indicated the 68000 error code, was always rather exciting to get.
(2 was a Bus Error and so forth.)

But I most enjoyed teaching the Atari to be a Mac (emulator software) because if it crashed, which happened from time to time, any key press or mouse movement would (in effect) press the “Mac” “RESET” button and restart the emulator. So, if you took your fist and hit the table, the system rebooted. That’s my kinda error message handler.

unonymous Says:
September 24th, 2008 at 11:25 pm

look, you need to provide a link to the whole story, not like 5 links to each page.

dave Says:
September 24th, 2008 at 11:36 pm

Working with a Cullinet databases in the 80’s, you’d commonly see error msgs like “Fatal embrace in the database, call DBA”, fatal this, fatal that. As a joke, in a test version of our software, I put a joke error msg based on a movie that had just come out, fully intending to change it before production.

2 years later, we get a call from the field, asking, “What the #*^@ does the error ‘Fatal Attraction in the database, call Michael Douglas’ mean??”

Elias Says:
September 24th, 2008 at 11:53 pm

You can still get “Abort, Retry, Fail” in Windows XP, when you, say, have removed a CD from the player and then try to access a file on it.

One of my favourites was the Mac “An unexpected error has ocurred…” Well, duh, if you expected it, it wouldn’t be an error, right?

Dave Small Says:
September 24th, 2008 at 11:56 pm

You wrote, “The Sad Mac has such a strong flavor of early Macintosh-ishness that it’s easy to develop a false memory that it was part of the platform from the beginning in 1984. Nope–Wikipedia says it first appeared in 1987.”

I’m sorry, I really am, because you made an effort to doublecheck your story, but it looks like Wikipedia is about to get a strong argument from me.

I happen to know this code very, very, *very* well, since I had to adapt it to another computer, with a larger screen size. The Mac screen was 64 bytes wide. The Atari ST screen was 80 bytes wide. So, to make a vertical line on the Mac, you’d move a dot to screen memory, add 64, and move another dot to screen memory, etc. I had to fixup ==all== those 64’s to 80’s so they’d work on the Atari. So let’s say I spent waaaaaaaaaaaay too many hours documenting this code up, down, and sideways, while listening (the horror!) to Neil Young Live Rust!. If I seem a little twitchy about this … well …a case could be made for that point of view.

I had to fix every single frowney, smiley, disk-shaped, ?, X, or what ever Mac icon. I truly do know them all.

In the 64K original (1984) Mac ROMs, of which I have a printout sitting on my lap *right at this moment*, Wikipedia or not, you positively WILL find:

The “Draw a Sad Mac and Do An Error Code Onscreen” at routine BadMac, $4000F4. In that routine, you’ll find the BRAnch to DrawSadMac at $400118, which returns via the address in A6. It then draws numeric codes. You will then find the numeric images of the codes at “numimages” at $40017A. To nail this point down with a hammer, the actual code that *puts them onto the display* is a MOVE.B D5,(A2), at $400146. It’s part of several loops. The system then has its interrupts turned off ($400168) and loops forever to $40016C.

DrawSadMac is invoked in a variety of places. The most famous is the “Dire Straits” Alert Code (a.k.a. the “DsErrCode”). Of course, “Dire Straits” is not what the programmers originally named it; this is a real-bad-news code, the computer is in deep s—. They try to handle it gracefully. But if the system can’t do stuff like an InitGraf, InitPort, and PlotIcon, oh well, it jumps off to BadMac documented above, and BadMac is just not a happy place to go.

Routine DrawSadMac ($4007CC) is combined with other routines, like DrawMac, and DrawHappyMac, that all use common drawing code, but use different images.

This code is directly followed by the images for BlankMac ($40080C), then for other things, like:

DiskIcon ($400870), MacSmile ($4008A0), MacFrown ($4008B4), QuesMark($4008C8), and XMark ($4008E6).

I suppose it’ll become tediously necessary for me to decode the number images into Mac screen images to convince the Wikipedia people that gee, the 64K ROMs had this stuff.

I would like to say that the people who wrote these ROMs taught me 68000 programming, in particular, Andy Hertzfeld. The man is a master and I was an apprentice looking over his shoulder. He taught me so many things that I can’t begin to describe them all. He’s a genius.

I hope this puts this stuff about “You had to go to the 128K ROMs to get the certain Mac startup faces” to bed. Because … I also “did” the 128’s, and that printout, too, is around . . .

Thanks for tolerating my twitchiness.

Take care,

Dave Small

Moshe Kranc Says:
September 24th, 2008 at 11:57 pm

My favorite error message came from ‘ed’, the original Unix line editor back in the late 70’s. I’d spend 15 minutes concocting the regular expression command I wanted ‘ed’ to execute (e.g., ‘/abc/s/x$1bcd$2yz/yz$1xz$2/g’) and type it in. Ed responds with a simple, elegant error message: ? (a single question mark)
I check the UNIX man page for ‘ed’ and fine the following, under ‘ERRORS”: “?: Error in command. The experienced user will know what to do” (Insert sound of head banging against wall)

Erik Says:
September 25th, 2008 at 12:18 am

I upgraded the original 8088 on my Ericsson Portable PC to a Nec v20. Whoa what a performance boost 🙂

The original CPU was soldered to the motherboard, no socket there. I thought I was very careful, but when I finally had soldered a socket in place, put the v20 in the socket and turned the power on, the screen was black.

From the pc – tweeter came “di-di-di daa-daa-daa di-di-di”, “di-di-di daa-daa-daa di-di-di”… SOS! Since this was in the middle of the night, I was afraid the beeping would awake my parents, so I quickly turned it off.

A close inspection revealed a tiny flake of solder that was stuck between two legs on a memory chip close the the CPU. I removed it and everything worked just fine..

GBrown Says:
September 25th, 2008 at 12:27 am

How about AbEnd ? Except Novell didn’t like to make too much of a song and dance so it left a couple of lines on the console and incremented a number next to the server name at the prompt.

Then you had “Multiple AbEnds are occurring” at which point things started to go a bit wrong – either it hung or just plain quit on you back to DOS (assuming you hadn’t unloaded DOS already).

Novell? Yes NetWare not Suse – there used to be a lot of it about until they forgot how to market and didn’t innovate for 10 years.

Wendy Says:
September 25th, 2008 at 12:35 am

Some of the cute ones:

BIOS Error: “keyboard not found: press F1 to continue”

Windows 2000
***************************************************
* Insert the diskette containing the swap file in *
* drive %1 and close the drive door. *
***************************************************
(hmmm)

michael Says:
September 25th, 2008 at 1:06 am

The RPC shutdown (from the blaster worm; error 6) can be aborted, by the way, by typing ‘shutdown -a’ at the command prompt or in the windows run box. So, not really a blue/red/grey screen of death when you know how to deal with it.

Sammy01 Says:
September 25th, 2008 at 1:13 am

Linux Kernel NMI kernel panic:

“Dazed and confused, but trying to continue”

Error Says:
September 25th, 2008 at 1:22 am

ORA-29532: Java call terminated by uncaught Java exception: string
Cause: A Java exception or error was signaled and could not be resolved by the Java code.
Action: Modify Java code, if this behavior is not intended.

Jakub Anderwald Says:
September 25th, 2008 at 1:44 am

On of the business apps I support has two different messages, for “the last else in error handling”:

Unknown Internal Error
Known Internal Error

The latter always makes me laugh.

jd Says:
September 25th, 2008 at 1:47 am

When working on C programs, newbies would often get “bad magic number” errors from the compiler. That was because they didn’t give their C source file a name ending in .c

jd Says:
September 25th, 2008 at 1:49 am

Or what about good old Java. Bestest language ever. Impossible to write bad programs in. Everybody knows why, it’s because Java doesn’t have any pointers. What’s the most common error newbie Java programmers get? NullPointer Exceptions. BUT JAVA DOESN’T HAVE POINTERS!!! RIGHT!!!!1!

Phil Says:
September 25th, 2008 at 2:08 am

My anti-virus used to amuse me, on cancelling an update, it would ask “do you wish to cancel?” with the options “yes”, “no” and “cancel” – what is cancel? Does it mean cancel the cancel request?

Ivo Jesus Says:
September 25th, 2008 at 2:11 am

“Segmentation fault”…
Its a classic error, and a pretty common one for C programmers. It has tormented me for years, and from time to time it still torments me.
For me, its way more irritating than a BSoD because, BSoDs are not my fault, “Seg Faults” usualy are!

Chris Says:
September 25th, 2008 at 2:41 am

An Error message from an old C compiler comes to mind here:

Too many errors. Try making fewer.

And from another compiler, similarly at the end of a long list of errors:

I’m seriously confused by now. Fix the first error listed and recompile.

Kili Liam Says:
September 25th, 2008 at 2:44 am

Definitively: “Tape loading error” … DAMM

ahahahahahahahahah

😉

Spectrum RULES!

Simon Valiquette Says:
September 25th, 2008 at 2:48 am

Many years ago, on Windows NT4 Server, there was a VB program that was not responding at all, so I decided to kill It with CTRL-ALT-DEL, and the system gave me a pop up telling me:

“Can’t stop”

with a quite useless and insulting “Ok” button on It.

I couldn’t kill the program, nor even reboot, but could still open other applications.

I traced back the problem to a memory leak in Visual Studio, and could somethie reproduce the problem, but It still feel very weird and stupid.

But It doesn’t beat the “Keyboard error, press any key to continue” PC bios error, that should certainly have been on the list.

Rob Krul Says:
September 25th, 2008 at 3:31 am

As A systems Administrator, I like the errors for the sudo program for Linux. The fun part of it is I get to chose how insulting I want the error messages to be. I always set it on the max level. It seems to brighten up everyone’s day.

Fjodor Says:
September 25th, 2008 at 3:37 am

I seem to remember reading up on the “lp0 is on fire”-thingy. Nowadays, it signals that no other error message fitted, but back in the days, it would come from a failure switch being thrown without some others – a combination that could only be reached by the runaway ink strip (or what it’s called) that would jam the thing – setting it on fire…

Oh, and once I saw a mac complaining about aborting due to a nonexistant failure, which I took to mean that it just couldn’t find the error code in it’s table of those. A tad better would have been the unknown error mentioned above…

bob Says:
September 25th, 2008 at 3:40 am

In the early 1970’s a fortran compiler on a cdc 3100 would produce something like:

123 The do statement that terminates on this line does not terminate before the end card

(All uppercase on a line printer, source code was on realy physical 80 column cards)

CPScott Says:
September 25th, 2008 at 3:48 am

On specific models of Power PC Macintosh Clones circa 1997, finder corruption would cause a system halt and display (along with the sad mac) the error code:

“Blueberries and Crumpets are a Chewy Treat”

Never did understand that one.

Aniah Says:
September 25th, 2008 at 3:50 am

One of the error messages I remember while running gparted.

“since gparted is a weapon of mass destruction, only root may run it”

Anish Says:
September 25th, 2008 at 3:52 am

One of the error messages I remember while running gparted.

“since gparted is a weapon of mass destruction, only root may run it”

Not Says:
September 25th, 2008 at 4:10 am

When I was once very very new to ‘NIX systems I tried to do something as root in FreeBSD and I got:

The requested operation will cause a terminal kernel failure if performed. Since you are root the request will be fulfilled… (I don’t quite remember the wording, I was too busy hitting Ctrl-C)

Followed by a week of me trying to undo my mistake.

D.W. Says:
September 25th, 2008 at 4:49 am

“%DECSYSTEM-20 NOT RUNNING”

My vote is from the early 1980s.
Imagine an entire terminal room with 30 or so undergrads typing away on terminals connected to a DECSYSTEM-20 before a class project deadline. Suddenly every terminal emits a long beep and the message “%DECSYSTEM-20 NOT RUNNING”.

Erie quiet followed usually by cursing.

The front end processor to the main computer detected that the main computer had died.

RJ Jansky Says:
September 25th, 2008 at 5:07 am

How about the non-blue screen message you would receive from Win ’98 if it hung and you had to push the Big-Red_Button…

Windows has been improperly shutdown. To avoid this message in the future…

Right! If this OS wasn’t so flimsy maybe it wouldn’t hang and leave me with no other option but the reset button. Being a UNIX guy Panic Core Dump has always had a special place in my heart.

Cheers…

jakesdad Says:
September 25th, 2008 at 5:07 am

he scariest place I’ve ever seen a bsod was on an ULTRASOUND machine in the frakin’ _CARDIOLOGY_ wing of a major hospital here in Atlanta! um, windoze running diagnostic medical equipment? I guess it could be worse, they could be using it to run those surgical robots they do bypasses w/nowadays – on 2nd thought, maybe I don’t want to know the answer to that one…

js Says:
September 25th, 2008 at 5:07 am

Marc: the “PC LOAD LETTER” error message is fondly remembered in Europe, where all the paper is sized as specified in ISO 216, most printers using A4. Should one know what “LOAD LETTER” means, there is usually no convenient means to obtain “letter” paper. Besides, what would one do with it? The error message can be cancelled with a button anyway…

This error message is generally associated with the following set of conditions: 1) a printer full of A4 paper; 2) a program or printer driver that has U.S. paper sizes as defaults; 3) a user who has forgotten to set the paper size on a new document.

Derek Says:
September 25th, 2008 at 5:13 am

What hasn’t anyone heard of the Mac S.O.S. beep? On some machines, when there is a significant failure, the speaker will beep out S.O.S. in morse code (dit-dit-dit-dah-dah-dah-dit-dit-dit)… I remember this all the way back in the MacSEs and I’ve even seen the current MacBooks do it as well.

Mad Says:
September 25th, 2008 at 5:29 am

Two of the ones I thought of while reading this:

On a PDP-8/11 cross compiler in MS-DOS (paraphrased, can’t find the actual text):

Warning 256 – More than 254 Warnings. Abort.

And in Murex (a financial program):

Service maybe dead (Spelled exactly like that 🙂

runbuh Says:
September 25th, 2008 at 5:39 am

This is not an error message, more of a status message and my first “Easter Egg”. Remember the Hayes modem “AT Command Set”? The Apple Personal Modem (1200 baud) would not only respond to an “AT” query with “OK” (per the Hayes set), you could also type in “ET” and it would reply with “Phone Home”.

Tom Stearn Says:
September 25th, 2008 at 5:39 am

Did anyone notice the misspelled word in the RSoD?

It says:
“An error occurred transferring exectuion”

Is that how it really appeared, or was the image manufactured wrong?

Tom Says:
September 25th, 2008 at 5:44 am

My favorite error message comes from Vista – “An unexpected error is preventing the operation. Make note of this error code, which might be useful if you get additional help to resolve this problem:

Error 0x00000000: The operation completed successfully.”

Nice.

Ben Says:
September 25th, 2008 at 5:45 am

When I was starting learning my first programming language (in QBASIC) I had my dot-matrix printer’s manual with code that would show off its features. I had made a typo and the error I got was “subscript error”. I was trying to figure out how QBASIC knew I was trying subscript on the printer since the program was mostly a series of LPRINT escape codes. Turned out I had missed a dollar sign on a CHR$(27) and “subscript error” in this context meant “array index out of bounds” on the unitialised “CHR” array variable.

4T Says:
September 25th, 2008 at 5:48 am

Blue screen of death is not the greatest error message. It has no character, no soul. Unlike the Guru Meditation which IS the greatest error message of all time.

GrayCoder Says:
September 25th, 2008 at 5:52 am

From early sun OS, typed on console:
“ie0: bark”
(watchdog timeout on ethernet interface zero).
“Thanks, Andy.”
Upon a transient parity error in main memory, then a scan of all memory
could not find the fault.
From Microsoft Excel (office 97 to current)
“File Not Saved [Ok]”
You will find a 2 (or 4) Gb file, with an 8 character Hex
name in the working directory. Your .XLS is not saved.

jbenni Says:
September 25th, 2008 at 5:57 am

I’m embarrassed to admit, we actually published a C++ app on the Mac that occasionally said (without trying to be sarcastic):

Error: Insufficient memory to print a meaningful error message.

Tom Says:
September 25th, 2008 at 6:00 am

It’s not exactly an *error* message, but the attitude behind “It is now safe to turn off your computer.” used to make me wonder who was in control of things, and what retribution the machine might exact if I shut it down otherwise.

Johnie Says:
September 25th, 2008 at 6:01 am

My favorite was from the Mix C Compiler for CP/M.

I’m totally confused, check your control structure.

charlie lavardo Says:
September 25th, 2008 at 6:07 am

the previous post(from .:cipha.ne), now…that’s an error(on his part).

jggimi Says:
September 25th, 2008 at 6:17 am

My all-time favorite:

“HODIE NATUS EST FRATER RADICI”

From Honeywell’s Multics OS, a precursor of Unix. Error messages in Latin shouldn’t normally happen.

Translation: “Today is born the brother of a root,” or sometimes, “out of the root is born a brother.”

I used that very same Multics system that had the error, but a year or two later.

Thomas Says:
September 25th, 2008 at 6:21 am

Hmm, there is one I like more than most of these, and that’s an error some programs (most notably VMWare) give, and that’s a popup window titled “Error”, and the contents of the window “Success” with a red and white error icon. I’m proud of myself for being able to get Schrodinger’s Error.

Chris Says:
September 25th, 2008 at 6:25 am

When Diablo 2 crashes, you get a simple textbox with a single line of text:

We got a really big problem here.

Mike Says:
September 25th, 2008 at 6:25 am

I used to assemble 286 and 386 computers and I used those bios beeps a lot to tell me what was wrong with a new system. Six beeps was memory, our most common problem as I recall.

Not exactly an error message but a warning of sorts: We had a programmer who wanted to build a computer and we let him. It had those poorly keyed power connectors and he forced them on the wrong way. When he switched on the power, all the caps blew and destroyed the motherboard rather spectacularly. He never asked to help again.

Great trip down memory lane.

Nonsense Says:
September 25th, 2008 at 6:33 am

What about this error in the Sinclair BASIC:
Nonsense in BASIC

Gotta love it

timebombtimmy Says:
September 25th, 2008 at 6:44 am

Good stuff. My favorite is from Phoenix Technologies’ PXE Server. It reads: “Unable to load resource template. Some unknown terrible thing has happened. (-2147287007)”

Or when windows closes windows explorer to protect your computer.
Some of the *NIX ones are classic :-).

dark Says:
September 25th, 2008 at 6:45 am

I think the Twitter whale could mean “heavy load”? =)

Ken Says:
September 25th, 2008 at 6:57 am

“Pick 1 dump”.

When Honeywell mainframes running the GCOS operating system crashed, the message affectionately known as “Pick 1” would be typed on the console. The operator could choose dumping an image of main memory to tape, disk, none, etc.

Planner Says:
September 25th, 2008 at 7:16 am

Segmentation Fault. Core Dumped.

Nobody Says:
September 25th, 2008 at 7:21 am

Where’s ‘syntax error’ and that bloody bomb the mac showed me just after I finished my Year 12 essay?

Troy Baer Says:
September 25th, 2008 at 7:22 am

I’m pretty sure that “lp0 on fire” is a Linux-specific thing that didn’t appear in old-school UNIXes, although I could be wrong about that.

My all-time favorite Linux error message is:

“VFS: Root device: Prepare for Armageddon.”

It wasn’t kidding, either; it usually meant that the device (typically a hard disk) was so screwed up that data loss was imminent.

KIWI Says:
September 25th, 2008 at 7:35 am

I once had my machine begin to chime a classical tune (Fur Elise?) endlessly as I was coincidentally installing a program. It turned out my CPU fan had just failed and the motherboard was singing a warning for CPU temp out of range. I was completely unaware of this “feature” and believed my machine had become zombied or stoned because I was killing Window process to no avail.

In the end, I ask, if they could make it sing why not simply announce “this is your motherboard speaking: warning CPU temperature error”?

Lennart Says:
September 25th, 2008 at 7:38 am

IBM had a faked errormessage (just as a joke). It said: press any key to continue or any other key to quit.

Dave Says:
September 25th, 2008 at 7:41 am

SAP R/3. Translated error to english.

“You have bent it so far it has broken.”

Leigh Says:
September 25th, 2008 at 8:02 am

I still remember a DEC RSTS/E BASIC error message that could appear:

“PROGRAM LOST. SORRY.”

Skywise Says:
September 25th, 2008 at 8:09 am

My favourite from the good old BASIC days was:

Unprintable error

Was this a horrible error so bad that it’s name could not be spoken?
Was BASIC about to say some swear and censored itself?
Or (as was really the case) the error number out of range of the text messages in the error table.

herd Says:
September 25th, 2008 at 8:31 am

In the NetBSD driver for the old 3Com Etherlink network cards there is a funny one. (Quote from the manual page)

ep0: 3c509 in test mode. Erase pencil mark!
This means that someone has scribbled with pencil in the
test area on the card. Erase the pencil mark and reboot.
(This is not a joke).

Neil Obremski Says:
September 25th, 2008 at 8:38 am

Why it’s blue (probably): lots of DOS editors and programs, like Q-Basic, used a white-on-blue color scheme. I do believe it IS easier on the eyes than white-on-black.

BlitzSieg Says:
September 25th, 2008 at 8:54 am

What about the ones that occur after you tell windows to shut down?

You know:
This application failed to initialize because Windows is shutting down.
and
This program has stopped responding. Press end to end it now or wait 30 seconds.

Um, hello? I already told you to shut down, why aren’t you doing it?

Roberta Says:
September 25th, 2008 at 9:05 am

I assume the FailWhale logo is connected to Douglas Adams, who continues to inspire so many software developers. In ”The Hitchhiker’s Guide to the Galaxy” we find: “Another thing that got forgotten was the fact that against all probability a sperm whale had suddenly been called into existence several miles above the surface of an alien planet. And since this is not a naturally tenable position for a whale, this poor innocent creature had very little time to come to terms with its identity as a whale before it then had to come to terms with not being a whale any more. This is a complete record of its thoughts from the moment it began its life till the moment it ended it.” The whale crashes to earth with all the speed that gravity would expect of it. Note that the logo looks more like a boxy-headed sperm whale than a streamlined a rorqual.

invaderkong Says:
September 25th, 2008 at 9:21 am

How can you make a list of greatest error messages and not include Oracle errors?
Messages that seem like random codes. that link to problems so generic you could rebuild the whole darn database faster then figuring out the error.

Aaron Says:
September 25th, 2008 at 9:33 am

One of my favorites was I had a motherboard years back that when the CMOS battery was dead started playing the Fleur de Lise from the PC speaker constantly. It was a very weird error to be sure. Later found out that one of the people that coded the BIOS had put it in as a joke and only one production run actually had the error. Wish I had kept the board just for fun.

Phobos282 Says:
September 25th, 2008 at 10:16 am

Actually, the windows shutdown error (#6) COULD be avoided. Start > Run > shutdown -a

When the worm affected our network back then, we quickly found a workaround so that we could remove the worm from the network.

Amateurs.

MondayMorningMojo Says:
September 25th, 2008 at 10:16 am

From SAP/Business Objects Universe Designer…

“Too many silly candidates”

NullPointerException Says:
September 25th, 2008 at 10:23 am

Not sure if Java NullPointerException is one of the “greatest” error
messages of all-time, but maybe it’s one of the dammdest. It’s
ironice too because Java “does not have pointers.” Hmmm…

GordU Says:
September 25th, 2008 at 11:03 am

Another MTS ism that would appear on the operators console just before a user’s session would dump.

“Help Snark in MTS”

Paul W. Homer Says:
September 25th, 2008 at 11:50 am

My favorite that stands out is:

“Shut her down, Clancy, she’s pumping mud”
– Texas Instruments DX10 OS kernel panic message

Now that’s informative (unless you’re not Clancy and/or you’re not operating a drill pump).

Frank G Tonin Says:
September 25th, 2008 at 11:52 am

WHen I was using WIndows XP once, b4 using Windows Vista Home Premium, I got this error message:

You’re not supposed to be here!

I’m NOT lying!!!

Bruce Sanchez Says:
September 25th, 2008 at 12:04 pm

The error I had most fun with was on the Vic 20 and Commodore 64
If U attempted to load a file from disk with no disk drive fitted it would first inform you that it was trying to find the file then tell you it couldn’t find the floppy drive. As a result of which you could have lots of fun.

Load”The Bosses Brain”,8,1

would produce the following out put

Searching for The Bosses Brain
device not present error?
Ready

Hugh Smith Says:
September 25th, 2008 at 12:24 pm

I have a T shirt with the error message

“Insufficient Memory at this time”

Every year it get’s more apt. Anyone remember the device?

MJS Says:
September 25th, 2008 at 12:30 pm

There’s one burried in the Sinclair ZX Spectrum (branded as Timex in the USA) – I’ve never made it happen but if you dump the ROM and take a look there is the error…

SILLY ERROR

🙂

James Wyper Says:
September 25th, 2008 at 12:32 pm

We used to run Lotus cc:mail on Windows 3.1 at work. It would frequently bring up an error dialog box showing an icon (a black exclamation mark in a yellow circle), an “OK” button – and nothing else. WTF?

costmo Says:
September 25th, 2008 at 12:39 pm

You forgot 2 of the best!

1. On boot: “No Keyboard Attached. Press F1 to Continue.”

2. From old UNIX (gcc?):
$ make love
make: don’t know hot to make love. stop

ENyolc Says:
September 25th, 2008 at 12:50 pm

My favorit:
Human error change User.

Johns Says:
September 25th, 2008 at 1:18 pm

In Windows 3.1 we had a message that was too long to remember but I can remember a phrase, in spanish: “esta aplicación ha transgredido la integridad del sistema y se terminará”

Translation will be something like “this application has transgressed system integrity and will finish”

The first time I saw it i felt like… “OMG!”

DRuNKeN MaSTeR Says:
September 25th, 2008 at 1:30 pm

My current favorite is:

“System in trouble.”

IBM’s AIX says in case something is wrong, and shuts down immediately after it (something like kernel panic under Linux).

krenshala Says:
September 25th, 2008 at 4:03 pm

don’t have time to read all the (fun to read) errors already listed. apologize if someone already posted it.

a bit of a techy error, as you can only get it while doing Windows troubleshooting of the IP stack (netsh int ip reset log.txt) you could get the error:

An error has occurred that should never occur.

And my personal favorite BSoD:

An unknown exception has occurred in module unknown.

I miss the Guru Meditation errors.

Mitchell Allen Says:
September 25th, 2008 at 4:25 pm

You’re in a maze of twisty passages, all alike.

Larr Says:
September 25th, 2008 at 4:36 pm

1983/4 Using a Harris-100 running Harris-VOS, compiling my very first COBOL program, and not knowing that a period was required on practically every line in COBOL.

SYNTAX Error. Missing dot.

It took me for… ever to figure out… that a ‘dot’ was a PERIOD.
Since I had access to the system message libraries… I went in and changed the message to ‘Missing Period at end of sentence.’ So that the other students in the class wouldn’t be as confused as me.

Years later… when using a VAX/VMS machine… I loved the fact that you could have aa combination of ‘fatal’ error messages

%FATAL-I-{something}. {text} – Fatal message is (I)nformational
%FATAL-W-{something}. {text} – Fatal message is just a (W)arning
%FATAL-S-{something}, {text} – Fatal message is just a (S)evere error
%FATAL-F-{something}, {text} – Fatal message is just a (F)atal error.

Though I really don’t understand how Severe and Fatal are that different from each other.

Miles Says:
September 25th, 2008 at 5:03 pm

My favorite, outdated error is one we used to see on the Univac 1108 in the 70s. ER EABT$ (Error abort, more or less). We called them “hairy rabbits”.

Mu current fave is the morse code that gets flashed out on the keyboard LEDs when Linux gets into certain kernel trashed modes (no, I’m not kidding).

Walter Butler Says:
September 25th, 2008 at 5:51 pm

I used to work for Southwest Technical Products Corporation (SWTPc), and
they had a terminal called the X-12. It had an onboard voice synthesizer. If you misprogrammed something in the setup menu of the terminal, then on the next power-cycle a loud voice would announce “X twelve set up fail.”

Taros Says:
September 25th, 2008 at 7:52 pm

Not quite an error message, more of a notification, but if the system clock is changed to a previous time, while InspIRCd is running, it broadcasts this message:

*** EH?! — Time is flowing BACKWARDS in this dimension! Clock drifted backwards x secs.

Creston Says:
September 25th, 2008 at 9:11 pm

The difference between Abort and Fail was really only ever noticeable in batch operations.

Abort would actually abort the entire batch job you were running, whereas Fail or Ignore would skip the one line that was erroring and continue on to the next line, which sometimes allowed the batch to continue. (most of the times it wouldn’t, ofcourse.)

Great article, awesome trip back through nostalgia. I had long since forgotten about the Guru Meditations my Amigas would throw up at me frequently.

Spider_Queen Says:
September 25th, 2008 at 10:05 pm

A long time ago in Brazil we were not allowed to import hardware nor software, and the big hardware manufacturers had to write their own code. A friend of mine, quite a potty mouth, wrote part of a Cobol compiler for the biggest computer manufacturer in the country. After the release of the compiler people started to call support because they were getting a message with the Portuguese equivalent of “Oh! s#!% happened”. It was my friend’s version of “command too complex”. I always searched for a list of four letter words before releasing any code he wrote, because he did NOT learn the lesson…

llamah Says:
September 26th, 2008 at 12:49 am

XBMC error is a fave
“Error: Success!” Also the Illegal operations I did as a kid were kind or confusing as a small kid. What you mean they know I borrowed this game from my friends??

Tommy Says:
September 26th, 2008 at 1:31 am

I managed to provoke my Eudora 2.2 on a MacIntosh computer into telling me:

========================================================
There is no one listening to keystrokes at the moment.
You might as well stop typing.
========================================================

By having a book on a corner of the keyboard.

Dno Says:
September 26th, 2008 at 3:36 am

The best I have ever seen is about a year ago. I was working with a software team doing 3rd party java applications for mobile phones. One of the applications the did tried to launch one of the phones native applications. When it failed it displayed the pretty offending error message: “Could not find the native to execute.”

vernes Says:
September 26th, 2008 at 5:27 am

20 something years ago, the warehouse started selling commedore 64.
They were on display powered on, without anything preventing you from just typing on it.

I started copying basic listings and trying them on them.
Naturally I made many typo’s, and unaware of the impact even the smallest typo has on code, I could not understand why it always said:
SYNTAX ERROR IN 20
or somewhere.

Eventually, I just removed the line of code in an attempt to fix it.
And after removing 60% of the code, I walked away dissapointed.

Bob Says:
September 26th, 2008 at 6:41 am

lp0 on fire (iirc) was due to a printer being offline, but somehow still printing.

Lisa Says:
September 26th, 2008 at 8:49 am

You simply cannot beat Abort, Retry, Fail? for its utter worthlessness.

FK Says:
September 26th, 2008 at 11:15 am

The new IT-manager at one of the companys i work with should log on to the old economy-system hosted on AS/400 for the first time, but got something wrong in the username or password and got promted “BAD USER” right in his face. That brougt up some laughs.
What more is there to say, sometimes the systems seems to know a hole lot… 🙂

Beppo Says:
September 26th, 2008 at 11:26 am

At one time I had to support an AS/400, and it gave some of the most cryptic and useless error messages ever, such as:

User exit program processing error.

value used in should be .

Jertz Says:
September 26th, 2008 at 4:07 pm

I love the Abort Retry Fail message. A Zen koan

Zacharias Says:
September 26th, 2008 at 4:18 pm

I work for IBM trouble-shooting Point-of-Sale registers and believe it or not POST-beeps are still fairly common!

No Name Says:
September 27th, 2008 at 3:08 am

404 File Not Found is just stupid to have such a high ranking. It’s a common error message with nothing special to it. Bah.

I am glad other voters agree, with 4th place, that Guru Meditation is much more special than the author thought.

This article was obviously done by a PC fan. It should have included at least one error from C64 such as “?FORMULA TOO COMPLEX”.

And the MacIntosh was far from cute. In fact, it’s so repulsive I felt I need to puke every time I even saw a picture of one.

Nevertheless, it was an interesting read, especially on the background of those errors with which I wasn’t familiar before.

rana verde Says:
September 27th, 2008 at 8:01 am

“Does not compute” means that a instructions can’t be processed due to a wrong value of the operands.
For example 4/0 is a not computable instruction because it’s a indetermination and it doesn’t have a result.
Basically it’s a fail in the assignation of the values of the variables.

sparkes Says:
September 27th, 2008 at 1:14 pm

R Tape loading error, 0:1

ZX Spectrum loading errors.

Magnus Says:
September 28th, 2008 at 1:39 am

I would like to add any error message ending with:

“Please contact your system administrator”.

No matter the program, no matter the error, contact your system administrator and he (or she) will surely fix it for you using some magic skills…

Joel Says:
September 28th, 2008 at 2:00 am

Sadly, Apple continues to push useless error codes on its users like no other software company. They stopped using hexadecimal notation, but that is about it. In terms of errors (and error codes) iTunes is, by far, the worst software I have installed on my computer today.

Anyway, I like this error message (Windows):
“The maximum number of secrets that may be stored in a single system has been exceeded.”

I have no idea what it means.

kaveh Says:
September 30th, 2008 at 1:39 am

Abort, Retry, Fail? (MS-DOS). A similar error like this still exists in Window XP even. If you have a diskette drive installed and get a A: driver error the choices “continue”, “retry”, “cancel” is available to you. I guess it’s easier to understand these choices but I think the underlying functions are the same as the MS-DOS version.

KGB from Sweden Says:
September 30th, 2008 at 11:58 pm

I used a Siemens Medical Computer tomograph in 1995 and recieved a error code meaning, Earthquake! Going to Safe mode!
The cause was a Forklift unloading heavy equipment outside the house.

TbbW Says:
October 1st, 2008 at 2:20 am

i agree with Coutch!
the ‘Keyboard error. Press F1 to continue’ is my nr2 after the amiga guru meditation.

how culd one press F1 if the kboard errors? ( usaly hapens on old pc’s when u forgot to plug the kboard in or accidently plugged it in onto the ps2 mouse ).

vFreak Says:
October 1st, 2008 at 7:26 am

I used to work on the helpdesk for a company that sold software to bakers. One of the programmers had put in one of my favourite error messages that would scroll slowly along the bottom of the screen…

“Muppet Movie Beeker Error.”

It meant nothing and would only happen at certain times around his birthday. The bakers would get most upset and panic about their software so we used to take the opportunity to wind them up a little before “fixing” it. The free cakes we got in appreciation were welcome though :).

Steve J. Says:
October 2nd, 2008 at 9:20 am

So many good ones from the early days:

An early IBM 7094 FORTRAN compiler used to say “Beta table overflow” if you tried to do too many complicated things.

The UNIX Ed editor used to say ‘eh?’ or just ‘?’ for just about anything that went wrong.

The UNIX pr command would say ‘Very funny!’ when you screwed up some of the input arguments. It wasn’t…

The UNIX PCC compiler once produced a message “gummy structure”…

Early GE/Honeywell systems had a help subsystem. An error number would be produced, and you could type the number into the help system to get an explanation. As the system creaked into understanding (gasp!) lower case, it became evident that many of the error messages had o’s instead of 0’s in them. So an error message might have number o72. If you typed this into the help subsystem, it went bonkers, spewing random characters, changing the typewriter ribbon color several times, typing random characters, and ended by spewing a couple of yards of papter into your face before crashing utterly. Help, indeed…

Neo Says:
October 3rd, 2008 at 10:55 am

My absolute favorite ever (which still makes me chuckle) is a Windows error I got on XP once. It simply said “Error reading the error message” and had just an OK button…..love it.

O'Maolchathaigh Says:
October 3rd, 2008 at 12:33 pm

To me, the worst ever has to be the power-on beeps; especially the 11 beeps. It sounded like self-destruct mode, and was as obnoxious as a fire alarm. Since the computer was useless at that moment, I wold shut it down immediately.

g Says:
October 4th, 2008 at 7:12 am

Guru Meditation (Amiga) was popular, cool, and scary at the same time, while most others were just too technical and made from boring people with business backgrounds. I would agree that “Syntax Error” should get mentioned too.

Atis Says:
October 5th, 2008 at 1:21 pm

NO ROM BASIC
SYSTEM HALTED

Kattemanden Says:
October 7th, 2008 at 12:04 pm

Kattevand er også godt

Kattemanden Says:
October 7th, 2008 at 12:06 pm

Kattevand er godt det kan jeg godt lide jajajajaja 😀 meget meget godt wuuuuuhaaaaaa jaaaah jeg elsker kattevand. Mmmmmm det ba såååå godt. Syns i ikk det? det syns jeg ihverttifælde haha. du sød hej hej. med katte på .

Inder P Singh Says:
October 12th, 2008 at 8:35 am

Actually, I was able to use the Abort, Retry, Ignore? (MS-DOS) error message usefully to an extent. I remember encountering this error when copying files from a floppy disk to a fixed (hard) disk or from one logical drive to another. Pressing (A)bort would cancel the command, I would re-insert the floppy disk and press (R)etry and press (I)gnore to simply copy what I could salvage on the floppy disk.

Inder P Singh

@9.99Ghz Says:
October 14th, 2008 at 5:03 am

Great.I heard of this blog from a friend.I am searching for configuration for a desktop with quad core processors.Plz Guide me. also tell me should i go for 45nm process or 65 nm will do. Thanks in advance

Matt Says:
October 15th, 2008 at 2:02 pm

Juggler314 is wrong as well. That’s the Port Authority Bus Terminal, at SW corner of 42nd & 8th Ave. Penn Station is down at 33rd and 7th, beneath Madison Square Garden.

Have seen BSODs and other error messages on many Times Square boards over the years. NASDAQ and Reuters seem to be prone to them…

noexcusesbehavior Says:
October 17th, 2008 at 2:48 pm

ahhh, my favorite the blue screen of death *has warm fuzzy feelings*

willie Says:
October 22nd, 2008 at 4:38 pm

My favorite was an error I saw on my old PowerBook, running 10.2.8, when I tried to boot off a CD with only iMac drivers. It kernel paniced, and the end of a long block of gibberrish was “panic: We are hanging here…”
It’s those little touches that make computers so interesting sometimes. And frusturating.

Mike Says:
October 24th, 2008 at 8:07 pm

It’s not Penn Station, either. It’s the Port Authority Bus Terminal.

Cadence Says:
October 28th, 2008 at 8:58 am

I thought the best error message was the lack of error message I got when trying to continue reading this article. Clicking next or on any of the next pages just brings the same page up again. ie: Your wordpress appears to be stuffed or something.

Rod B Says:
October 31st, 2008 at 12:28 pm

“AutoCAD gives up” was a great one when the DOS version of AutoCAD crashed.

mbrowne.net Says:
November 11th, 2008 at 12:38 pm

Back in 1985, we had a variety of mini-mfs to work with. Our products generated a few interesting errors, but my favorite of all time came after an unresolved variable call, which resulted in a 76-page dump file, at the top of which read “Error during crawl out.”

Like, from under a rock.

Buy Electronics Says:
November 24th, 2008 at 9:27 am

Windows has encountered an error and needs to close. We apologize for any inconvenience.

drbunsen Says:
December 3rd, 2008 at 7:34 am

“Bluets and Granola make a crunchy treat”
“Guess we just found out what BETA means”

Both of these were boot errors on 68k Mac Powerbooks.

DaVince Says:
December 11th, 2008 at 3:24 am

“Only a woman could be that stupid when it came to computers. Go back to hiding under your bed n00b.”

Are you an idiot? Since when did gender REALLY matter when it comes to ability? She was a kid, and children generally have little experience with these things, especially in the past.

DaVince Says:
December 11th, 2008 at 3:38 am

“Not only are all “add-ons” enabled, but WTF is with “add-on?” is this microspeak for plugin? what’s wrong with plugin? everybody else in the world informally convened and agreed to use “plugin” to mean plugin. why does microsoft unnecessarily complicating things have to run into to vocabulary too ? i want an answer on this choice of word – “add-on.””

Firefox uses the term “add-on” to describe the whole collection of extensions, themes and plugins installed on your system, so I don’t see what’s wrong with the term. Plugins are a different things from extensions/add-ons because they are usually coming from an external source to provide functionality – like DLLs or .so libraries for Flash or Java. I’m not sure about IE add-ons, but FF extensions are using special internal languages specific to the browser (like XUL) and are usually only compatible with that browser.

DaVince Says:
December 11th, 2008 at 4:39 am

The NullPointerException in Java happens when code is pointing to a null value somewhere, which might have something or nothing to do with *pointers as most people know them. References are usually still pointers too, so a = b; b = 4; makes a have a value of 4…

djkrugger Says:
December 12th, 2008 at 2:31 am

on windows

"IO error . Cyclic redundancy error cannot copy xxxx.xxx the drive E is not ready. OK" all that means "there is a fingerprint on your CDrom".

limey Says:
December 22nd, 2008 at 6:27 am

yeah, the keyboard one that has been mentioned a few times already would get my vote and I was dissapointed not to see it on the list.

Another which always makes me laugh is the following message that a system I work with occasionally throws up. Bear traps and suicide, how wonderful!

Error: dm_bear_trap: Unexpected exception, (Mon Jun 17 16:10:47 2002 NT Exception: Exception Address: 1000485a, ACCESS_VIOLATION at (Connection Failure)), during new session creation in module C:dmnewrpcnetwiseserverdmapply.cxx after line 482. Commiting suicide!

Nate Says:
December 23rd, 2008 at 9:48 am

One of my favorites:

“tar: Cowardly refusing to create an empty archive”

Lettie Says:
December 23rd, 2008 at 11:15 am

I encountered on the IBM 1130 using FORTRAN IV with commercial subroutines the best error messages of all time. The “F” errors were displayed on a console, and the easiest way to know what they meant was to memorize them.

I don’t remember all of them now, but F101 was the one I got most frequently — File record too large, equal to zero, or negative. Another one was F10A — Subscripting has destroyed the Define File Table. This occurs when a subscript exceeds the specification in a DIMENSION statement.

The error messages were actually quite informative, but it did make you feel like a complete dolt to get one!

seremina Says:
December 24th, 2008 at 10:38 pm

I wish the 404: File Not Found error would stop sounding like the whole internet got killed. The internet is much more than one file, so the error should say

“Either that website or url is mistyped, wrong, crashed, missing, or dead. Please check your spelling and try again. If it still does not work, try a different website or url.”

Justin Says:
December 30th, 2008 at 7:35 pm

I personally like

“Error 17”

produced by GRUB at boot.

J Says:
January 2nd, 2009 at 1:17 pm

Here are some nice messages that I’ve run into…

“Incompetent user error” IIRC was quite common with Lotus Notes (versions around 4)
“The computer is busy, please wait” on Windows versions in the 95 product line. Like, “hey, I’ve got better things to do than those you want me to do” or something.

And, the best:
“An error occurred because an error occurred”
Can’t remember the exact occasion, but it was on Mac OS (version 6 or 7) while connecting to internet using a dialup connection.

Sean Says:
January 2nd, 2009 at 2:58 pm

They have entire websites dedicated to these now. Like mine.
http://errors.seangillen.com/

Mary McI Says:
January 3rd, 2009 at 6:10 pm

It ain’t Times Square, but it ain’t Penn Station neither.
It is the Port Authority Building on 8th Avenue.
See similar photo at
http://www.panynj.gov/CommutingTravel/bus/html/history.html

Penn Station (ver. 2.0) is underneath Madison Square Garden (ver. 3.0)
on 7th Avenue and 32-34th Streets.
Times Square is where each New Year officially begins.

Richfiles Says:
January 3rd, 2009 at 10:11 pm

From Mac OS 9:
The command could not be completed, because you have already chosen Shut Down or Restart.
Wait until the computer finishes shutting down or restarting, or quit all applications and choose Shut Down or Restart again.

Stadium X Says:
January 5th, 2009 at 3:34 pm

[EDIT] The entry 11, the Red Screen of Death, is also known to occur in video game consoles. The Playstation 2 has this SoD.

Carpe_Mofo Says:
January 15th, 2009 at 11:24 am

I don’t see anything wrong with pirated music and movies, I download both all the time, and you know what? I buy more stuff like that than I ever did before I started pirating, and if I haven’t bought something I think is worth paying for, it’s simply because I can’t afford it so they wouldn’t be getting my money either way. I just spent 400 dollars on all four seasons of doctor who which I also have as downloaded divx. I’ve even bought software, couldn’t deal with the copy protection, so downloaded a cracked version so I wouldn’t have to. I don’t think the RIAA or MPAA is really losing money from pirating, I think they are losing money by being lazy and not putting out worthy content. The book publisher Baen realizes this, so you know what they do? They put there books online for free download expecting the extra word of mouth from people trying books they nessacarily wouldn’t have risked there money on then telling friends about it who buy it. The first time I read Ender’s Game was a prirated copy I downloaded, now I own 5 copies of the book in different editions. So for me at least, it works.

Carpe_Mofo Says:
January 15th, 2009 at 11:25 am

Wrong article.

David Whitehouse Says:
January 16th, 2009 at 1:35 pm

Back in the days (Early 1980s) Texas Instruments produced minicomputers (the TI-990). They developed a Forms package, cleverly named “TI-Forms”.
It was possible to get an Error Message of “Shut ‘er down Clancy, she’s a pumpin’ mud’ [an old Texas old field saying]. Not only could you get the message, it was even documented – apparently it had slipped by the proof reader.

emall Says:
January 20th, 2009 at 9:49 am

Windows 7 still BSoDs, don’t worry. It’s going nowhere 😀

Ed Says:
January 20th, 2009 at 2:23 pm

How could you forget the Windows 95 classic? “This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.” And the more clueless the user, the more worried they are that something illegal has happened on their watch.

Adam Says:
January 20th, 2009 at 10:38 pm

How about the good old Rundll32 errors?

Chris Says:
January 21st, 2009 at 1:19 am

Who cares about BSOD?? What about C64’s “SYNTAX ERROR” ? Or “FORMULA TOO COMPLEX ERROR”?? .. here the others: http://sta.c64.org/cbm64baserr.html

shawn Says:
January 21st, 2009 at 11:53 am

Mac OS, “The application has unexpectedly quit!”

BatGnat Says:
January 22nd, 2009 at 12:29 am

NO ROM BASIC
SYSTEM HALTED

This is my all time favourite, meaning your Boot Hard drive has no active partitions of course….

chris Says:
January 23rd, 2009 at 11:58 pm

The amiga Guru meditation codes were designed to debug said messages, often times they told you what failed, when, why, and how.

The guru part of it was a in-joke to the programmers, which there are a few Easter eggs in the OS anyway. but the gurus were the core OS coders, who more or less knew every detail in and out of the hardware.

There was a specific format to that, but I’ve forgotten it years ago. Though, it’s probably on wikipedia.

Bryan Says:
January 24th, 2009 at 6:55 pm

I remember back the when the Atari ST was in full swing you would get a set of bombs when she crashed

I had a MegaSTe

Doc Says:
February 3rd, 2009 at 11:24 am

The “PC LOAD LETTER” error is from HP LaserJet printers; it means the Paper Cassette (lower tray) is empty, and to LOAD 8 1/2 x 11 (LETTER size) paper into it.

asma Says:
February 21st, 2009 at 10:25 pm

the thirteen greastest error massage is the best thing

Oh Hai Says:
February 23rd, 2009 at 4:03 pm

Hahahaha. Best one I’ve ever gotten was also the simplest.

“Error.

Yes? No?”

Click yes, and the computer logically gives you the error again, if you don’t want the error, you simply click no, and it goes away. xD

Yiying Lu Says:
March 15th, 2009 at 6:58 pm

Hi, I’m the creator if the Fail Whale image. I’m a “She” btw 🙂

for more info on why fail whale image has to do with a Web 2.0 service buckling under extreme traffic – here is the website:

http://www.whatisfailwhale.info

most of the info are there. Thanks & Regards.

Harry McCracken Says:
March 15th, 2009 at 9:30 pm

Dear Yiyeng Lu: Thanks! I know -you’re- a she–what I wasn’t sure about was whether the failwhale was male or female…

–Harry

Old Tom Unicorn Says:
March 20th, 2009 at 3:01 am

I remember the days when my grandson bought an Amiga 500, and the trials and tribulations we had with Workbench 1.3.

When he struggled to open any programs, I was faintly amused by the ‘Carry On…’ nature of this error message:

‘Unable to open your tool’.

They don’t do error messages like that anymore. 🙁

John Says:
March 24th, 2009 at 12:49 am

I swear to god at some point a shitty Apple boox once said…

“Ha Ha its happened again hasn’t it”

Bryan Lee Says:
March 27th, 2009 at 9:54 pm

I’ve had Windows 7 beta build 7000 bluescreen on me twice already! LOL =P

Violator Says:
March 30th, 2009 at 5:11 am

“Out of memory” was more common the a bsod

RBurleson Says:
April 6th, 2009 at 7:12 am

Motorola Mainframe; Basic on a teletype, ’70’s or ’80’s; “Load Module Does Not Exist”

K. Venus Boyd Says:
April 8th, 2009 at 8:52 am

Hi Harry,
What is the message Error 1606 could not access dataapp? And how do you fix it?

Nathan Says:
April 10th, 2009 at 1:39 am

1. Years ago at school I tried to listen to a CD – “Master of Puppets” by Metallica – in a Mac. System 8, I know it was after 7 and before X and pretty sure it wasn’t 9 because I almost completely missed that one. Long story. Anyhow, as I loaded the CD up in the media player and it began playing, MacOS asked me if I wanted to format the disc! I clicked OK to humor it, but then it seemed serious. Like it was ready to format a 640MB CD-ROM to the Mac format. And this was before burners! I have no idea how that all came about, but I canceled it and continued to listen to the CD.

2. I would swear the Guru Meditation story was nicked off me at some point. Not sure if I ever blogged about it, but that’s one of my favorite geek stories to tell. We had two Commodore-Amigas growing up – the 1000 and then the 2000. My dad swore up and down Apple and Microsoft would fall before Commodore. Yeah, we all see how that went. But almost nobody else had Amigas who I knew growing up. So one day we have some people over, and we go to put on the Prevue Channel (what it was before TV Guide bought them out) and it was frozen with the Guru Meditation error. Nobody knew what it was but me. But the Prevue Channel was national, maybe even international, and if it ran on Amigas everywhere, it’s entirely likely a lot of people saw Guru Meditation errors on their televisions, not just me.

jane Says:
April 10th, 2009 at 2:02 am

I got a nice error message You don’t exist go away

Lost Says:
April 20th, 2009 at 10:44 am

And how about error message in Lost ?

William Says:
May 4th, 2009 at 7:48 pm

You forgot to include the one that says: No keyboard detected, press any key to continue..

Lol,, funny as heck !

Chris Says:
May 5th, 2009 at 1:55 pm

I walked into a Best Buy last fall and saw this Kernel Panic on their big screen behind the Apple display. It had been like that for 3 and a half hours when I shot this pic.
http://www.thatmacguy.net/kernelpanic.jpg
The manager of the store didn’t seem too worried.

Erti K Says:
May 8th, 2009 at 5:56 am

BeOS used to (correction, still has!) to have Error 404 haiku’s which were varied every time you got the error. I supposed all the websites which feature Haiku’s were inspired from this, or re-inspired by someone who visited a site inspired by BeOS’s cute messages. You could install BeOS in less than 5 minutes. You could be on the internet hours ahead of Installing windows 3.1 or 3.11, going to the ISP’s dialup BBS, downloading the Win32 Extensions to make windows 3 a 32-bit os ( which included Freecell as its demo of whether Win32 was working). Then you download Trumpet Winsock which added a TCP/IP stack to windows 3, and then finally downloading NETSCAPE Navigator. Of course this process is somewhat anachronistic, Beos came out for the Mac and PC after windows95 but it was a good multimedia os for it’s time and ran fast on anything, even multiprocessing server computers that windows 95 could only use the single processor. BeOS could use up to 64 processors on a single computer and was available for more than just pc’s and macs. It was going to be THE OS for anything that wanted on the internet, like these new smartphones or your where you kept your beer. ( “hello, tony’s pony keg?” “yes?” “good, this is matt brady’s refrigerator, I’m out of beer and dont want to upset matt, can you send someone with three cases of XXXX brand cervesa so we wont have an argument when he gets home?” “thank you, it seems some people have hacked into the windows-running house computer and let themselves in and are now drinking all my beer” “oh by the way, do you know a good carpet cleaning service” “oh yes,of course, actually I’m on the other line with the police now sending them scans of fingerprints I scanned off my doorlatch. Dont need it right away, just about two hours from now, the police will be leaving and wont be able to drink the new beer.”

Josh Says:
May 8th, 2009 at 7:06 pm

where is google chrome’s,

“Aw, Snap!” error message?

gnp kumar Says:
May 11th, 2009 at 2:51 am

when i switch on my computer it boots and shutdown immediately and giving error message”THE CPU WAS PROPERLY SHUTDOWN DUE TO THERMAL EVENT (Overheating)

Joyce Beck Says:
May 11th, 2009 at 9:43 am

I have a screen print over my desk of a little gem from MS Access having a little tussle with an ODBC driver: “There was a problem sending the command to the program”. What problem? Which command? Which program? Do you think it would it make life too easy for me if you gave me some kind of sodding clue?

David James Says:
May 11th, 2009 at 11:25 am

My votes for greatest error messages of all time have to go to:

“boo dee DEE — The number you have dialed — five, five, five, one, two, one, two — is not in service. Please check the number and try your call again.”

In the 60’s, 70’s and 80’s, this message ended with:
“If you need further assistance, please ask your operator. This is a recording.” This part was back when operators were actually available as easily as a single key press (”0″), and people were so unaccustomed to hearing prerecorded voices that they might attempt to engage in a conversation with it.

There is a strong possibility that this may be the most commonly encountered error message ever (so far), with one exception:

THE BUSY SIGNAL. Universally known, but slightly different sounding from country to country. The busy signal was useful shorthand for “you can’t call that number because that phone is off the hook.” Which was fortunate, because why call someone, if they are already talking to someone else? It made perfect sense in the days before voice mail.

I believe this qualifies as an error message, because it indicated that the request was abandoned, and the device needed to be re-booted before another attempt was made.

sawaff Says:
May 14th, 2009 at 9:29 am

The picture of the BSoD from NYC isn’t in Times Square or Penn Station. It is on the front of the Port Authority Bus Terminal at the corner of 42nd and 8th Ave.

Jarrett Says:
May 14th, 2009 at 12:37 pm

When coding C++ in Visual Studio 2005 I got an error that said “Error: Looks like a function body” the line it took me to was indeed (and supposed to be) a function body. I don’t know what it’s problem was but the good old Clean/rebuild fixed it.

blogdx Says:
May 20th, 2009 at 5:03 am

nice
thanks

waterpup Says:
May 23rd, 2009 at 12:58 pm

BSOD is anything but a “Rock Band” and BSOD stands for Better Sounding On Drugs not Blue Screen of Death. All this is available on th elink to their MySpace page you provided

blogdx Says:
May 24th, 2009 at 9:40 am

it’s funny

ruby Says:
May 29th, 2009 at 3:57 am

wow

Rhino Junior Says:
May 31st, 2009 at 2:14 pm

My favourite error from working with gcc:
confused by earlier errors, bailing out

Tux Says:
June 2nd, 2009 at 2:08 pm

I’m sorry… “lp0 on fire” is by far the best. It’s the only one on the list that actually implies physical harm is possible.

In an internally-developed website where I work, we’ve got a really good one that goes something like this:

“The System has encountered a serious error. Whoops!”

andy r Says:
June 7th, 2009 at 10:21 am

$Extend$UsnJrnl:$J. the data has been lost. This error may be caused by a
failure of your computer hardware or network connection. Please try to
save this file elsewhere.

I thought this was funny, asking me to save a file that has already been lost … 🙂

Toy Says:
June 9th, 2009 at 9:53 am

Nice blog & helpful
Thanks

Weldon Says:
June 15th, 2009 at 10:35 am

The best error message I have seen came up at random times on a friend’s Atari 520ST (like TOS 0.24 for something, beta). It was:
“Please insert film into your Polaroid camera”

From what I know, Atari was working with Polaroid on a product, but it never amounted to anything.

Justin Davidow Says:
June 15th, 2009 at 1:42 pm

just a quick comment about this list:

#6) “Windows computers suddenly told them that something called the RPC service had died and began a countdown to a forced reboot which couldn’t be avoided.”

can be simply avoided 99.99999% of the time with a simple run of ‘shutdown -a’ gives you the time to diagnose the system and see what’s going on.

I’ve never understood why nobody ever knows about this?

Justin Says:
June 15th, 2009 at 5:46 pm

If you haven’t yet seen The Daily WTF (http://thedailywtf.com/), you should check it out. One of the fairly regular front-page features is various stupid error messages, of which publicly-projected BSoDs are the mildest. 🙂

I disagree with you slightly on one point, though: while hexadecimal error codes aren’t *directly* useful to most users, just typing an error code into google (along with a bit of context like “bsod” or “stop error”) will often get you considerably closer to solving the problem. While not all users will know to do that (and quite honestly, we shouldn’t even have to in the first place), it is a better option than flailing around in the dark.

Good list, I enjoyed it and learned a few things as well.

Gordon Schumacher Says:
June 16th, 2009 at 9:30 am

In the category of “errors that aren’t really errors”, particularly scary ones… I used to keep a virus zoo on a collection of Amiga floppies. And then one day, I got hit by the “Lazarus Virus”…

http://en.wikipedia.org/wiki/Amiga_support_and_maintenance_software#Backup_and_recovery_tools

…left me wondering, “How the $%*@!* did I, of all people, manage to get a virus?!?”

Draeconis Says:
June 16th, 2009 at 11:12 am

There was always one I liked by RealPlayer where it would display a picture in the bottom right saying ‘This picture could not be displayed’.

baqs Says:
June 18th, 2009 at 2:59 am

Older versions of KDE played the sound of glass breaking when an error message was displayed. Probably one of the most nerve wrecking error sounds you can get!

annon Says:
June 18th, 2009 at 9:57 pm

the real question is to send error report or not to send error report.

or is there a diference?

Sunshine Says:
June 19th, 2009 at 12:35 am

Neopets has awesome 404s. They used to have better ones, but that’s pretty much the call of the community, “it was better back then.”

http://www.neopets.com/blarrrrrr

Refresh it, it says new things and has new pet silhouettes.

jasonology Says:
June 23rd, 2009 at 7:31 pm

I have made a flickr set of crazy and poorly written dialog boxes- Mac OS X mostly.
Have a look at
http://www.flickr.com/photos/jasonology

Michael_Imperfection Says:
June 24th, 2009 at 11:31 pm

My two favorite errors are

1. The windows ERROR ERROR which happened to me when an Error message started to appear froze and then another Error message popped up that was called an ERROR Error and said “There was a problem displaying the ERROR” and had the choices of O.K. and Cancel but cancel was whited out.

2. The next was the BLANK Error that I got after mozilla, photoshop, task manager, and windows explorer crashed that came up and didn’t say anything but had the options of O.K. and Cancel. When I clicked on cancel I received my first ever BSoD.

OH I actually have a picture of the BLANK Error.

http://i174.photobucket.com/albums/w92/madmikeslab14/BLANKERROR.jpg

Jackybird Says:
June 27th, 2009 at 5:48 pm

Maybe somebody’s already said this, but that’s not Penn Station. I think it’s the Port Authority. I looks like it’s taken from the northeast cornor of 42nd and 8th.

OHaleck Says:
June 30th, 2009 at 12:29 pm

Errors are sometimes erroneous too. I cannot see the Hulu error video because I am not in the U.S. (freakin’ copyrights) and the BSOD screensaver just tells me that SetDisplayMode FAILED!!

Mike Atha Says:
July 14th, 2009 at 10:09 am

BIOS LBA Support is a great error to encounter.

P Smith Says:
July 24th, 2009 at 8:26 am

It’s not error messages that have infuriated me the most, not even the annoying “Guru meditation” on my Amiga 500. Why got my goat was Microshaft blaming users for their own poor programming. After rebooting from a crash, Lose95 and Lose98 would state:

“Windows was not shut down properly.”

Microshaft was inferring that it was the user’s action, not a crash by the operating system despite the fact that was the cause 99.99% of the time. If Bill Gates were to be smacked in the face with a frying pan for every instance where he blamed the users for his OS’s crashes, he would have been dead years before USB was a gleam in anyone’s eye.

There was an old joke in the 1990s about Windoze and crashes that was based on a fact. Windoze would count in 32 bits, one bit for every second. Doing the math, 2^32-1 bits would equal or 49.7 days. In other words, if Windoze were left running for 49.7 days, it would crash.

Windoze 95 could run for seven weeks without crashing? It could barely manage seven hours.

Dave Says:
July 28th, 2009 at 8:21 am

In DOS when the computer would lock up you would get what my buddies and I called the Black Screen Of Death. A void where nothing can come back from. Black and Death go hand in hand and when WIndows 95 came along the “Blue” SoD just took over without skipping a beat.

Mike Says:
August 2nd, 2009 at 3:09 pm

That’s not either Times Square or Penn Station – it’s the Port Authority Bus Terminal in Manhattan.

C.J. Says:
August 4th, 2009 at 11:49 am

MaOS 8 (perhaps 7) had a humourous error nobody seems to know about:

“The alias file couldn’t be used because it isn’t really an alias. (whoops)”

It may have said “oops” instead of “whoops” but that’s the gist of it. Maybe someone with an OS8 machine could go digging for this?

Marcos Says:
August 6th, 2009 at 6:25 am

You forgot one, from Linux kernel:

Kernel panic: I have no root and I want to scream

😉
Marcos.

tenar72 Says:
August 11th, 2009 at 12:14 am

Best error message ever was in an alpha version public domain game many years ago, I don’t remember the exact wording but it said something like “f*ck yourself in the knee, stop eating my pizzas and write proper error messages!”

dofollow bookmark Says:
September 27th, 2009 at 3:30 am

Hey, you have a great blog here! I’m definitely going to bookmark you! Thank you for your info.And this is bookmarkth.com site. It pretty much covers DoFollow Social Bookmark related stuff.

Thank.

Billborden Says:
November 26th, 2009 at 7:42 pm

When your looking at classic 404 errors, you have to include 4-chan’s, check this one out:
http://zip.4chan.org/tv/imgboard2.html

Also, they have a great 403 message to:
http://zip.4chan.org/mu/res/

Arroxane Says:
December 10th, 2009 at 1:20 pm

You forgot one unforgettable error message:

“Malfunction: need input!”

Number Five is alive! 😉

http://en.wikipedia.org/wiki/Short_Circuit_%28film%29

Garrett AiResearch Says:
December 31st, 2009 at 3:32 pm

Mid 80’s Unisys @FTN compiler:Error within an errorandHelp! I’m confused!

Garrett AiResearch Says:
December 31st, 2009 at 3:36 pm

Am I the only idiot who typed html into this thing?

Mid 80’s Unisys @FTN compiler:

Error within an error

and

Help! I’m confused!

ReynaldoRiv Says:
January 1st, 2010 at 1:26 am

Don’t mean to nitpick but in the Lost in Space Error message you should have put the word gyndroid instead of android, unless of course she was what is referred to on the net as a Trap.

Joe Says:
January 26th, 2010 at 10:08 am

I was told, second- or third-hand, of an error message on old TI machines, from the heart of oil country: “Shut ‘er down, Clem. She’s a-pumpin’ mud.”.

anonymous Says:
January 28th, 2010 at 1:44 pm

If I recall, with the advent (well use) of the ps/2 port, the keyboard error became basically useless, because the system had to be turned off before plugging in the keyboard. (Not sure, it’s been quite a few years since I have used an actual ps/2 keyboard.)

Jon Says:
February 5th, 2010 at 3:02 pm

The FailWhale is actually extremely representative of Twitter issues. The birds represent users, the “ropes” are threads of conversation, and the FailWhale is the error happily dragging them down.

Seth Asa Says:
February 8th, 2010 at 10:01 pm

My mother got the following error message on her Mac laptop:

“It’s Not My Fault”

Which prompted her to ask, “Well whose fault is it, then?”

I don’t know what model of Mac it was but she actually called me to tell me about this error message. And she still really likes her Mac. I dig PC’s. And, somehow, we’re still able to communicate and laugh together like civilized adults…

Marcus Says:
March 30th, 2010 at 8:18 am

My all time favorite came out of an extinct accounting system called ResMax. I was updating some journal entries and everything halted with the error message ‘Error: Total CRAP”. Checking with the programmer it turned out that it was a concatonated error message that should have read ‘Error: Total Credit Applied’ but the error handler stack was from the ‘CR’ routine and then the ‘AP’ routine, hence the insulting error message.

qwazix Says:
April 22nd, 2010 at 12:52 am

Well, that’s embarrassing (firefox 3.5+)
Oops! there is an error (something about that – Gmail)
ppl still create nice error messages

BobbyB Says:
May 20th, 2010 at 8:25 pm

I got one.
“Syntax Error”, from the old Commodore 64 computer.

Fairportfan Says:
June 7th, 2010 at 5:42 am

An acquaintance who now works for MS on Windows once worked for a company that built custom OSes.

On one project, there was an *extremely* unlikely error that they coud not imagine actually occurring in the field. So the error message read: “You are screwed.”

Less than a week after the OS was delivered (as i recall), the (very religious, moralistic and strait-laced) client managed to see it…

The Old Wolf Says:
June 7th, 2010 at 7:55 am

Having programmed IBM mainframes, my vote is for “0C5”, the most information-less code ever devised. A mysterious man named Dan Nessett once wrote this bit of doggerel, which perfectly describes the situation, methinks.

“I Was Wondering About This Error Message,” I said

Beneath my stare began to blur
10,000 lines of print.
Buried alive by 0C5
Which gave not clue nor hint.

Up from my chair, I neard the lair
Branded “Consultants’ Room.
With puzzled gaze I paraphrased
My mind’s perplexing gloom.

“That bilious sty of wire,” said I,
“Has dumped its DUMP on me.
I cannot guess where in that mess
I’ll find the missing key.”

“The clues are everywhere,” he said.
And I began to think
Of : “Water, water everywhere
But not a drop to drink.”

“Aha!” said he, “Your DCB
Has lost BUFL.
MSHI is far to high
And BLKSIZE looks not well.”

“BLDL in this case will
Cause 0C5 or 4.
To BSP hex ‘503’
Will backspace low cost store.”

“You FREEMAIN twice and GETMAIN once’
This cannot be advised.
And all of this, I’m positive
Has caused your 0C5.”

My jaw had slackened to my knees;
A fly flew in my mouth.
I gathered up my SYSUDUMP
And crawled off in a slouch.

Back to my desk; I placed to rest
My chin upon my hand.
My weary eyes seemed quite surprised
To gaze on print again.

Beneath my stare began to blur
10,000 lines of print.
Buried alive by 0C5
Which gave not clue nor hint.

-Dan Nessett

Per Helge Seglsten Says:
July 8th, 2010 at 1:37 am

My company gave us these HP (Hewlett Pacard) iPAQ Voice Messenger mobile phones which apparently had more flaws than functions. The best of the error messages from those little buggers read: "The phone is turned off. Do you want to turn it on?"
And then you had to turn it off…to turn it on.

Mike Says:
August 1st, 2010 at 5:53 am

That's not Penn Station either, its the Port Authority.

mike Says:
August 1st, 2010 at 5:54 am

http://www.panynj.gov/bus-terminals/port-authorit…

kfsone Says:
August 12th, 2010 at 7:12 pm

"Dick Fell". What exactly would your reaction be when your system promptly shut down leaving you only with these two words and a prompt?

And the error was persistent. The client was running an aged Commodore Pet installation, and the error was narrowed down to a single machine. It had developed a fault in the IO controller resulting in a single bit error.

It was, infact, trying to report the message "Disk Full".

Echyld72 Says:
August 17th, 2010 at 11:47 am

Hello I feelt like Making this topic so Hello all

cub Says:
August 27th, 2010 at 5:54 pm

Since you mentioned Windows 7, sure–Nortel VPN Client reliably bluescreens W7.

The same things that always caused BSOD still happen: sloppy code in drivers and hardware glitches.

Gavster Says:
September 6th, 2010 at 2:27 am

The BSOD in windows can actually be colour changed by you. There is a settings file which contains the colours which will be used when the screen appears. This is to cater for people with certain vision impairments.

Raven Says:
September 30th, 2010 at 5:22 pm

There is a regedit you can do to change the color of your BSoD too.

Tim at IMM Says:
November 16th, 2010 at 11:00 am

I would say the bomb error was a far more famous error on the Mac than the Sad Mac. I read that the designer of the error, Susan Kare, was given free creative expression in designing the error and so she created the bomb icon. It threw some users into a tizzy, because they saw the computer as not only failing them but mocking them in the process.

Mark Says:
November 22nd, 2010 at 11:13 am

I have number 14, right here at your website:
"Waiting for polldaddy.com"
Each one of these pages takes eons to load. I can't stand the thought of even going past the third page. Get a new survey company.

Mike Says:
November 23rd, 2010 at 8:38 am

Interesting that the Red Screen Of Death must have been in the spell-checker.

"Exectuion" ?

Ian Says:
November 23rd, 2010 at 3:29 pm

A small nit, but "Lpo" is wrong. It should be "lp0" (lower case of "LP", followed by the digit "0" for the first line printer, 1 for the second, 2 for the third…).

Alex Says:
December 21st, 2010 at 10:14 am

Embedded youtube video of BSoD taunting Bill Gates: An error occurred, please try again later.

Paul Says:
December 25th, 2010 at 8:01 pm

Ah, surely the best error message of all time would be produced by an Acorn BBC Microcomputer (circa 1983) in response to the user inputting an illogical mathematical problem. The error message, in simple white text on a black background was:

Silly

jazmatazz Says:
December 29th, 2010 at 12:28 pm

how if the WORLD do you write a story like this without including "this program has performed an illegal operation and will be shut down"?

Laguna Beach Water Damage Says:
January 8th, 2011 at 2:30 pm

I loved precisely what youve done below. the particular layout is elegant, your articles material classy. Yet, youve obtained an edginess to what youre providing the next. Ill definitely arrive to come back for additional should you actually preserve this up. Dont reduce wish if not as well plenty of men and women look at your vision, know youve gained a fan right listed here who values what youve obtained to express plus the way youve presented yourself. Fine on everyone!

HPdv7 Says:
February 6th, 2011 at 10:44 am

What about the SSBBOD? the Super! Spinning! Beach Ball! Of! Death!!!

Vinnie Bartilucci Says:
March 2nd, 2011 at 10:59 am

“I’d be amazed if Windows Seven doesn’t bluescreen from time to time.”

It does. I got one playing Sim City 4 and jumping too fast from program to program – the sound and video cards just gave up.

M!3 R!4N Says:
March 12th, 2011 at 1:55 pm

i agree with this : "Keyboard Error, Press F1 to continue"
how we can press f1 button when the keyboard error?

Allen G. Says:
March 16th, 2011 at 8:35 am

That last BSOD photo is actually located at Port Authority on 42nd and 8th. I live a few blocks from there, and have seen a BSOD on that very screen.

Ken Johnson Says:
April 3rd, 2011 at 6:49 pm

Microsoft Word (2003?) would give me a error message during routine operation of ‘could not get instance of redemption’. I briefly considered if my software had gotten religion. Also, I recommended to a friend that he name his band Instance Of Redemption.

Ezekiel Says:
April 3rd, 2011 at 11:10 pm

Most flabbergasting: the ever-so-helpful "An error has occurred." (Or simply "Error!") No details on what the error was, where it occurred, how to diagnose it, or what to do about it. Just remembering it makes my blood boil. Over the years I've seen it (and others like it) on too many systems to list.

Most humorous: On unix, "cat" was used to output the contents of a file to the screen. Tell the C shell "cat food", and you'll get "cat: cannot open food"

And of course imagine running a PDP10 app in a nuclear facility and seeing the all-too-common:

?PDL overflow. Core dumped.

Perr Xardestam Says:
April 4th, 2011 at 12:54 pm

I cut my teeth in programming on an IBM 1130. My favorite error message was "M13 – Execution suppressed". The system allowed you to look up "M13" in a list for detailed explanation. Result:
"Execution was suppressed because the system detected a condition that would prevent successful execution".

Shof Says:
April 4th, 2011 at 11:03 pm

I was working as a software engineer for Sony during the early 90s. We were converting some software written in Japan to run on some newer Sony machines. The best error ever was

"Fetal Error… Abort"

tech84 Says:
April 12th, 2011 at 6:45 am

I though the worst error would be:

"No keyboard detected, press any key to continue…."

LOL!!!

Arvid Says:
April 26th, 2011 at 1:19 pm

My favorite has always been "Something Happened" a rare but frustrating error message in Final Cut Pro.

Jeremy David Thomson Says:
April 30th, 2011 at 6:19 pm

waiting for polldaddy.com

See how you like it? Get rid of polldaddy.com, it slows down the loading each page for a good 10-20 seconds.

Jeremy David Thomson Says:
May 2nd, 2011 at 5:36 pm

Okay, contacted polldaddy.com & they don't use flash which is what I disabled to get some response from your site. Today its not freezing up for 20 seconds, you can actually scroll so I guess the offending flash (advertisement) has been removed.

lien tom Says:
June 21st, 2011 at 12:34 am

Gucci Handbags Outlet,cheap oakley sunglasses,prada handbags discounted,sale a&f clothes

louboutin discount Says:
August 9th, 2011 at 5:24 am

The article writes very goodly.I agree your standpoint
Vogue beautiful prom dress.We are worth owning!

Dan Says:
August 21st, 2011 at 10:12 am

the 404 error just means the IE8 settings are wrong:
turn on "automatically detect settings"

Steve Says:
August 21st, 2011 at 8:40 pm

I am surprised no one mentioned this one,

“This program has performed an illegal operation and will be shut down”

htc4greviews.us Says:
August 23rd, 2011 at 1:01 am

iPaymu.com Says:
September 10th, 2011 at 11:26 am

nice info.. thanks for sharing http://wemelt.com/ipaymu-com-pembayaran-online-in…

Edward Cherlin Says:
September 24th, 2011 at 8:50 pm

The best error message I ever got was from a Windows Beta many years ago. I’m sorry that I have forgotten which version. When I went to shut down Paint, with nothing else running, it said

Insufficient memory to quit

menyc Says:
September 25th, 2011 at 2:42 pm

The picture labeled "And Times Square Penn Station (photo by Chad Dickerson)" is, in fact neither Times Square nor Penn Station. It's the Port Authority Bus Terminal.

Dave K Says:
October 9th, 2011 at 6:04 am

stack overflow anyone?

mrz80 Says:
October 13th, 2011 at 9:17 am

BDOS Err on A: – RO

lina Says:
November 10th, 2011 at 1:21 am

I am very impressed to your blog you did a very hard work. and I really appreciate you to sharing such a useful post, Great Job! book reports | Admission essays | theses

Yahya Says:
November 20th, 2011 at 10:59 am

I visited this page first time and found it Very Good Job of acknowledgment and a marvelous source of info………Thanks Admin! Phone Lookup
Reverse Phone Lookup

jibran Says:
November 23rd, 2011 at 12:17 am

It has been seen for a couple of years that liver disease is spreading a lot.I think the main thing is the level of fats increases inside the body which will effect the lever. العاب اطفال

makeityourring Says:
November 24th, 2011 at 11:52 pm

This is my first time i go post. I collected so many interesting things in your site especially its discussion. From the tons of comments on your posts

makeityourring Says:
November 25th, 2011 at 12:51 am

This is my first time i visit here. I found so many interesting stuff in your blog especially its discussion. From the tons of comments on your posts

SUN Says:
December 1st, 2011 at 10:46 am

Thanks for sharing this great article! This is exactly what I was looking for. That is very interesting Smile I love reading and I am always searching for informative information like: yeast infection treatment link building services

SUN Says:
December 1st, 2011 at 10:47 am

makeityourring Says:
December 27th, 2011 at 12:41 am

You've got mentioned some sort of very wonderful details, appreciate it for that post.

sciatic nerve pain Says:
December 31st, 2011 at 5:13 am

Let's not forget the Dr. Watson error. Or, as I like to call them, the Dr. Kevorkian error, because the error never fixed anything… it just helped your program kill itself!

Edwin Says:
January 11th, 2012 at 1:24 pm

You know, I’ve been googling Improve Your Speedall day to find this Truth About Quicknesskind information. Glad you wrote Truth About Quickness Reviewabout it. Thanks!

lowongan guru Says:
January 17th, 2012 at 11:05 am

wow… thanks a lot for your tips..
It's like you're the best at this..
thanks Man !!

Lowongan Guru Private

hendry Says:
January 19th, 2012 at 1:45 am

I just think that you put it in a way that everyone can understand. Buy Cheap Laptops Online I also love the images you put in here.Female dog names It proved to be Very helpful to me and I am sure to all the commenters here!

makanan untuk diet Says:
January 21st, 2012 at 3:22 pm

Just needed you to know I have added you to my bookmarks. I've seen your different weblog subjects too and I think you've got got great ideas. cara cepat menurunkan berat badan setelah melahirkan Preserve it going!

Office design Says:
January 22nd, 2012 at 3:43 pm

This Blue Screen of Death (perhaps better known as the BSOD) from a Windows 98/Windows 98SE/Windows ME operating system indicates the worst. And it's become the best known and most spoofed error message of all-time.

Must be error message No1 right!!!

century 21 Says:
January 24th, 2012 at 6:13 am

The next moment Post read any blog, I hope that it doesnt disappoint me personally since much since this one. Post mean, I know it absolutely was my choice to read, but Post actually notion youd own something interesting to speak about. Almost all Post notice is actually a bunch of whining with regards to something which you would fix when you werent very hectic on the lookout for particular attention.

sewa kantor Says:
February 4th, 2012 at 12:11 am

Yeah..that's Keyboard not attached, Press F-1 or F-2 to continue

webmaster indonesia Says:
February 4th, 2012 at 12:15 am

Sure, that's like when people have an emotional attachment to many of them–like Proust’s Madeleine,

small kitchen Says:
February 4th, 2012 at 12:18 am

Take a look at wikipedia, I think…

hotel murah Says:
February 4th, 2012 at 12:21 am

The Blue Screen means, there are having error in the mainboard hardweres

weinfass Says:
February 5th, 2012 at 11:25 am

What about my favorite BIOS error when a keyboard is not attached to the computer…

KEYBOARD ERROR: Press any key to continue

Greg Says:
July 1st, 2014 at 8:38 pm

Jeremy had consumers another angry person when he first
hired into that situation. Do not get themselves insured and bonded.
Check Into Their BackgroundOnce you have extra funds to cover the roof of your profits.

First never hire one. Normal0falsefalsefalseMicrosoftInternetExplorer4DisclaimerI am not talking to those charges in Virginia to his hearingBishop
was also charged with six counts of falsifying business records.
They then connect them to feel you and your business due to the extra expense to
you, to at your project is on sale you want.

my web site: site – Greg,

Just A Random Person Says:
July 1st, 2014 at 10:12 pm

The most common one I encounter is the 404 error on the web, I spend a lot of my time there. Also I added up the percentages, first in my head then with a calculator, and both time I got 99.99%. But I’m probably just wrong. Anyway love this article!

66 Trackbacks For This Post

Abort, Retry, Ignore? » Perception is Truth Says:
September 24th, 2008 at 11:09 am

[…] this post over at Technologizer, certainly brought back some […]

13 greatest error messages of all time - SUPERNISSANS.NET Nissan Owners Community Says:
September 24th, 2008 at 11:55 am

[…] greatest error messages of all time The Thirteen Greatest Error Messages of All Time*|*Technologizer The Unix message is the best one just because of its history. __________________ SQUASHING […]

Linkdump for September 24th at found_drama Says:
September 24th, 2008 at 12:04 pm

[…] The Thirteen Greatest Error Messages of All Time […]

13 greatest error messages of all time - BRISKODA - The Skoda Forums Says:
September 24th, 2008 at 12:15 pm

[…] greatest error messages of all time As stolen from /. lol Linky __________________ ColGod the UberMod VXR, Gti, ST, Type-R, vRS, Shifty… An MPS fears not these […]

Black Diamond Digital Blog » Blog Archive » 13 Greatest Error Messages of All Time Says:
September 24th, 2008 at 12:16 pm

[…] Thanks to Slashdot and, um, Harry McCracken, for the post. Here’s a link. […]

nextcode:ch Says:
September 24th, 2008 at 12:54 pm

[…] The Thirteen Greatest Error Messages of All Time […]

The Thirteen Greatest Error Messages of All Time | Technologizer at Maszman Speaks! Says:
September 24th, 2008 at 1:50 pm

[…] The Thirteen Greatest Error Messages of All Time | Technologizer […]

De tretton största felmeddelanden genom tiderna | Jörgen S Öfjäll Says:
September 24th, 2008 at 3:29 pm

[…] Guru Meditation och 12 andra lattjo felmeddelanden […]

As 13 mais conhecidas mensagens de erros de todos os tempos « Nataniel. Notas sobre as TIC Says:
September 24th, 2008 at 3:41 pm

[…] muito amigo e conhecedor dos tempos teve a amabilidade de nos mostrar que nao somente de BSODs vive o mundo, recuperando alguns erros (13) dos mais conhecidos nos […]

Danny Cohn » Blog Archive » The Thirteen Greatest Error Messages of All Time Says:
September 24th, 2008 at 4:16 pm

[…] Full article Filed in Uncategorized « Bye-bye, Rick Davis? […]

Shoehorn all the Content into episode 271 | The CaffiNation Podcast Says:
September 24th, 2008 at 9:57 pm

[…] can you fail? 13 error messages for the ages + 1 pet […]

Messaggi di errore -- Black Pig - Maiali neri in libertà Says:
September 24th, 2008 at 10:11 pm

[…] 25/Set/2008: Technologizer ha pubblicato un articolo sui 13 più famosi messaggi di errore dei computer: vale la pena dare […]

13 Pesan Galat Paling Terkenal — Cool Tech Says:
September 24th, 2008 at 11:11 pm

[…] ==sumber berita dan foto dari sini== […]

13 величайших сообщений об ошибках всех времен =) « Кое-Что О Слонах Says:
September 25th, 2008 at 12:19 am

[…] The Thirteen Greatest Error Messages of All Time […]

mensajes de errores historicos | rhypee Says:
September 25th, 2008 at 3:29 am

[…] Technologizer han realizado un repaso a esos errores que hemos tenido que sufrir toda la […]

Bugs « Says:
September 25th, 2008 at 3:45 am

[…] wouldn’t be the same without ‘em. So I rounded up a baker’s dozen of the most important error messages in computing history – from Does Not Compute to Abort, Retry, Fail to the Sad Mac to the big kahuna […]

Tiny Planet » The glory of computer errors Says:
September 25th, 2008 at 4:47 am

[…] know ‘em, you love ‘em (you know you do really) and now Technologizer has compiled the 13 greatest error messages of all time, beginning with this classic: Abort, Retry Fail. It could indicate either a minor glitch (you […]

.: cipha.net » die dummheit der massen Says:
September 25th, 2008 at 5:50 am

[…] “top 13″ geben möchte, die kollegen von technologizer haben genau das gemacht: https://www.technologizer.com/2008/09/18/errormessage/. von amiga über unix bis zu […]

technichristian.net » Blog Archive » The Thirteen Greatest Error Messages of All Time Says:
September 25th, 2008 at 7:43 am

[…] Actually, they usually add insult to injury. But what would computing be without ‘em? Herewith, a tribute to a baker’s dozen of the best (or is that worst?). Write a […]

The Thirteen Greatest Error Messages of All Time | Technologizer Writer River Says:
September 25th, 2008 at 8:06 am

[…] The Thirteen Greatest Error Messages of All Time | Technologizer. Gemma Bristow | September 25, 2008 | permalink […]

blog.343meterprosekunde.de » Blog Archiv » Die 13 größten Fehlermeldungen aller Zeiten. Says:
September 25th, 2008 at 8:19 am

[…] Slashdot bin ich auf einen Link bei Technorizer gestolpert. Der sich mit den größten Fehlermeldungen aller Zeiten der Computerwelt […]

Curiouser and Curiouser » My Favorite Error Messages Says:
September 25th, 2008 at 9:18 am

[…] “you mispeled a keywurd” $ make love Not war? “What?” From the Thirteen Greatest Error Messages of All Time, the comments […]

Tzikis - Web creation made easy. » Blog Archive » Moar stuff. Says:
September 25th, 2008 at 1:08 pm

[…] δείτε αυτό το link που μου έστειλε ο φίλος μου ο Poscaman. Είναι ένα άρθρο με […]

links for 2008-09-25 « Matt Parsons : Weblog Says:
September 25th, 2008 at 1:31 pm

[…] The Thirteen Greatest Error Messages of All Time | Technologizer […]

techno-blog » Blog Archive » links for 2008-09-25 Says:
September 25th, 2008 at 3:09 pm

[…] The Thirteen Greatest Error Messages of All Time|Technologizer (tags: ping.fm) […]

XTRO » Mensajes de error Says:
September 26th, 2008 at 4:13 am

[…] Artículo original en riguroso inglés […]

Mensajes de error históricos « Ainu Corp Says:
September 26th, 2008 at 5:56 am

[…] Mensajes de error históricos 26 09 2008 chonago nos cuenta: «[Vía Slashdot] Muchos de los sistemas operativos, aplicaciones y dispositivos que nos han acompañado no serían lo mismo sin esos mensajes de error legendarios asociados a ellos que todos hemos sufrido. En este repaso a los 13 mensajes de error más importantes de toda la historia es posible conocer un buen montón de curiosidades sobre esos errores, que cómo no, están coronados por el mensaje de error más importante de todos los tiempos: el pantallazo azul de la muerte. El artículo original en inglés, en Technologizer.» […]

PabloG » Blog Archive » links for 2008-09-26 Says:
September 26th, 2008 at 6:00 pm

[…] The Thirteen Greatest Error Messages of All Time | Technologizer (tags: informatique software windows mac histoire technology humor) […]

Twitter Updates for 2008-09-26 | BonBonTheJon Says:
September 26th, 2008 at 9:09 pm

[…] error messages of all time: https://www.technologizer.com/2008/09/18/errormessage/ […]

לקט לינקים, 28 בספטמבר 2008 | רויטל סלומון Says:
September 28th, 2008 at 5:05 am

[…] שאי אפשר אינטרנט או מחשבים בלי תקלות. קבלו את רשימת 13 הודעות השגיאה הטובות ביותר בהיסטוריה. אני לא מסכימה עם הבחירה של המסך הכחול של Windows במקום […]

Webfundstücke | Kaine Says:
September 28th, 2008 at 1:17 pm

[…] Greatest Error Messages ever – Liste mit den “besten” Fehlermeldungen […]

Feilmeldingar er morosame ting « 0×002bs blogg Says:
September 29th, 2008 at 7:48 am

[…] til at eg kom på å skrive om feilmeldingar er at eg kom over bloggen technologizer.com. Og der har dei ein poll. Kva er tidenes beste […]

Quando apetece ir buscar uma marreta « Notas do meu canhenho Says:
September 29th, 2008 at 4:34 pm

[…] tal cenário apocalíptico não se concretiza, podemos sempre contar com uma lista das treze melhores mensagens de erro que dão vontade de espancar o pc até ver sangue. Entre elas estão o clássico do DOS «Abort, […]

Boom! From Zero Page Views to (Almost) a Million a Month, in Less Time Than You’d Think | McCracken on Media Says:
September 30th, 2008 at 8:47 pm

[…] story will contribute the majority of that traffic: “The 13 Greatest Error Messages of All Time.” Which is fine by me. Part of Technologizer’s recipe is to regularly publish […]

Bookmarks for September 22nd through September 28th • Blog Archive • noahcarter . com Says:
September 30th, 2008 at 9:13 pm

[…] The Thirteen Greatest Error Messages of All Time – […]

Fun Fact: Error Messages « Digital Eagle Says:
October 7th, 2008 at 6:50 pm

[…] The Thirteen Greatest Error Messages of All Time […]

links for 2008-10-09 « D(i)PE’s weblog Says:
October 9th, 2008 at 12:30 pm

[…] The thirteen greatest error messages of all time (tags: software list funny) […]

13 Great Error Messages « The Scholarly Kitchen Says:
October 10th, 2008 at 3:44 am

[…] Anderson under Education, Historical, Research, Technology For our Friday fun this week, we link over to Technologizer and a list of the 13 greatest computer error messages of all time, including the “Guru Meditation” error message, the red screen of death, and the […]

BSOD no es bsod » vagabundia Says:
October 14th, 2008 at 8:19 pm

[…] Windows no es el único en tener errores, en technologizer.com muestran algunos de los más conocidos de todos los sistemas operativos y además, en errorwear.com […]

13 Pesan Eror Terbaik Sepanjang Masa « Zalayanka’s Weblog Says:
October 15th, 2008 at 1:05 am

[…] sumber artikel dan informasi lebih lengkap, silakan klik di sini. / […]

Woodlander - Abort, Retry, Fail — and other classics Says:
October 16th, 2008 at 12:09 pm

[…] apparently maintains a list of classic error messages. Well, someone has to. The mention of ‘Abort, Retry, Fail’ brings back so many happy […]

Epic Fail « The Sketch-blog of Pariah Says:
October 19th, 2008 at 4:35 am

[…] https://www.technologizer.com/2008/09/18/errormessage/5/ […]

dholm.com » Blog Archive » Tumblelog: 081027 Says:
October 27th, 2008 at 1:24 am

[…] The Thirteen Greatest Error Messages of All Time, Technologizer takes us back through time to look at the thirteen greatest and least useful error messages. Lego V8 by Brickshelf […]

irinoko » Blog Archive » Top 13: los mejores mensajes de errores informáticos Says:
October 30th, 2008 at 4:11 am

[…] ha añadido un artículo curioso, donde se mencionan los trece errores informáticos más conocidos de todos los tiempos, tenemos desde el típico “Blue Screen of The Death” hasta errores de Mac y Xbox. El […]

Se guindó… « Elendil LOTR Says:
December 7th, 2008 at 7:43 pm

[…] Technologizer han realizado un repaso genial de esos errores que todos hemos tenido que sufrir en una u otra […]

[…] Harry Mckracken. Pendapat semua orang memang berbeda, tetapi mari kita simak daftar pesan error Technologizer di bawah ini, mulai dari urutan […]

Team Revolution Blog + Events» Blog Archive » Team Rev Recap (sort of): Feb 2-8 Says:
February 9th, 2009 at 9:13 pm

[…] swirly rainbow sphere appeared on my screen. No big deal, I thought to myself. But then I got your error message. You had unexpectedly quit, you told me. Did I want to submit an error […]

13 Pesan Error Komputer Terbaik | Kampanye Damai Pemilu Indonesia 2009 Says:
February 23rd, 2009 at 6:29 am

[…] Harry Mckracken. Pendapat semua orang memang berbeda, tetapi mari kita simak daftar pesan error Technologizer di bawah ini, mulai dari urutan […]

So close.. « Bloblet Says:
May 17th, 2009 at 2:29 am

[…] also a couple of funny examples on this blog, and here’s a geeky list of the thirteen best ever error […]

13 grandes mensajes de error de todos los tiempos [EN] Says:
July 7th, 2009 at 7:42 am

[…] 13 grandes mensajes de error de todos los tiempos [EN]technologizer.com/2008/09/18/errormessage/ enviado por Alex […]

Espectacular: compilación de los mensajes de error más importantes de todos los tiempos | GeeksRoom Says:
July 11th, 2009 at 2:23 pm

[…] una nota de Setiembre del 2008 que publicó el sitio Technologizer, The Thirteen Greatest Error Messages of All Time, cataloga los mejores, si es que podemos llamarlo así, mensajes de error de todos los tiempos. […]

The Thirteen Greatest Error Messages of All Time « Dis Aliter Visum (It seemed otherwise to the gods) Says:
July 31st, 2009 at 8:52 pm

[…] Link to the original site. […]

Voice User Interface Design VUI » Blog Archive » The Art (and Humor) of Error Messages Says:
February 24th, 2010 at 4:31 pm

[…] others here and […]

Jobs Calls Out Android Over Porn — Think Geek Australia Says:
April 10th, 2010 at 8:23 pm

[…] The Thirteen Greatest Error Messages of All Time […]

die dummheit der massen « gizmeo.com | a gadgets blog Says:
April 15th, 2010 at 8:48 am

[…] eine “top 13″ geben möchte, die kollegen von technologizer haben genau das gemacht: https://www.technologizer.com/2008/09/18/errormessage/. von amiga über unix bis zu […]

Amiga: 25 Years Later Says:
July 23rd, 2010 at 10:54 am

[…] The Thirteen Greatest Error Messages of All Time […]

Amiga: 25 Years Later Says:
July 23rd, 2010 at 10:56 am

[…] Recent Comments Amiga: 25 Years Later on The Thirteen Greatest Error Messages of All Timedholyer on Google Images Improves Its Imagedholyer on Google Images Improves […]

Commodore Amiga, 25 anni di storia - The New Blog Times Says:
July 29th, 2010 at 3:01 pm

[…] Meditation” (l’antesignano del BSOD di Windows), che più di qualcuno, per assurdo, ricorda quasi con piacere. Per non dire quante volte capitava a chi aveva l’ardire di scriverci […]

Amiga: 25 年再回首 | ifanr 爱范儿 ♂专注于拇指设备的小众讨论 Says:
August 16th, 2010 at 9:50 pm

[…] 甚至连 Amiga 的缺憾也成为其传奇的一部分。Amiga 的多任务系统缺乏内存保护机制，因此程序的错误会令整个机器悲壮的死掉——被称为 Guru Meditation（直译为：大师的冥思），是有史以来最著名的出错提示之一。 […]

13 errores informaticos historicos | LAINFORMACION GRATIS ESPAÑOL Says:
March 29th, 2011 at 3:25 am

[…] Technologizer han realizado un repaso genial de esos errores que todos hemos tenido que sufrir en una u otra […]

Polaroid’s SX-70: The Art and Science of the Nearly Impossible Says:
June 8th, 2011 at 5:26 am

[…] The Thirteen Greatest Error Messages of All Time […]

【资讯】201110 大经典错误 | 天天生活 Says:
August 18th, 2011 at 12:47 pm

[…] 本来文章到这里就可以结束了，上文参考自这里The 13 Greatest Error Message of All Time。不过，我觉得还有一个错误必然会载入史册。这就是下面的“该页无法显示错误” […]

Gone in Sixty Seconds: The Shortest-Lived Tech Products Ever Says:
August 19th, 2011 at 8:19 am

[…] on Technologizer The Thirteen Greatest Error Messages of All TimeMore Evidence That There's No "Tablet Market"HP Kills WebOS Hardware: There's Even Less of a Tablet […]

10 of the Shortest-Lived Tech Products | BuyX-Comp Says:
August 21st, 2011 at 1:26 pm

[…] The Thirteen Greatest Error Messages of All Time […]

Harry McCracken on Mac OS X errors « Reassuring Quotes Says:
October 6th, 2011 at 2:08 am

[…] H. (2008). The Thirteen Greatest Error Messages of All Time. Available: https://www.technologizer.com/2008/09/18/errormessage/3/. Last accessed 13th Aug […]

计算机的10大经典错误 - 博客 - 伯乐在线 Says:
October 30th, 2011 at 6:23 am

The Weird History of Windows
Laptopia: Twenty-One Totally Bizarre Laptops
Fifteen Classic Game Console Design Mistakes
The Thirteen Greatest Error Messages of All Time
When the Muppets Worked for IBM
Tech Products That Were Brilliant. And Doomed
The Legend of the Legend of Zelda
15 Breakthrough Products That Went Absolutely Nowhere
The 25 Most Notable Quotes in Tech History
How 1940s Whiskey Ads Predicted the Future
The Great Operating System Games
The Weird Secret Origin of Tech's Favorite Insult

Technologizer by Harry McCracken