|
That's cute. Reminds me of one from a cryptic UNIX GUI in the 1990s:
+----------------------+
| Error 0 |
+----------------------+
| |
| No error text for "" |
| |
+----------------------+
|
|
|
|
|
DEC's RT-11 OS (I'm showing my age) also had a text-based Help system. You typed: 'Help [Command Name]' at the command line, and you got a screen of text, usually with things like command line options. If [Command Name] was not recognised, you got back the single line: 'There is no Help for [Command Name]'. The programmer had a sense of humor. If you typed: 'Help Me', you got back: 'There is no Help for you'!
|
|
|
|
|
I remember that! They also had error number 69 - no path to partner in their RSX system. Early networking.
|
|
|
|
|
I prefer the old BIOS message "Keyboard not found. Press any key to continue"
|
|
|
|
|
Yes!
This happened on booting old IBM XTs. If I recall it said
Keyboard error
Press F1 to continue
Maybe it was some laid back engineer's sense of humour?
Why make life more difficult than it is?
|
|
|
|
|
This one actually makes sense, it makes sure you fixed the error (by plugging in a keyboard) before continuing.
|
|
|
|
|
MS-DOS also had a "Screen not found" error message, which no one ever saw because it was meant to be displayed on the screen
|
|
|
|
|
Yeah, but Windows took that one just one step further... I recall seeing the BSOD on my friend's computer, and I think it was Win95. It just read:
"It seems you have not plugged in a monitor. Please plug in a monitor and press a key to continue."
In fact, pressing a key wouldn't have done anything, but what has been troubling me for all this years now: HOW did the programmer meant this message - if it's conditions were really met - would be transported to the user? Magic Crystal Ball?
Needless to say, _we_ saw the message because there _was_ a monitor plugged in.
That seems to be a PEBKAC problem, Sir. Why don't you go and fetch a coffee while I handle the operation?
|
|
|
|
|
haha I just got the following error while trying to load the link to this forum. LOL it totally took me off guard. I thought it was a joke and then I realized... "This is the worst error message ever." Worst Error Ever
|
|
|
|
|
Really thats very funny..Ever Never heard like this dude !!!!
"Worship God But First Respect Human"
|
|
|
|
|
On Windows 98 while doing a very dangerous operations (something regarding the file system, so very destructive  ), an empty message box appeared with a question icon and two button: Yes No... this is the worst error message! You know something bad has happened, you don't know what the remedy was proposed by W98 
|
|
|
|
|
From TeX, the geeky typesetting program:
Sorry, Pandora. (You sneaky devil)
Pretend you are Hercule Poirot: examine all the clues.
|
|
|
|
|
The worst I ever came across was from Quadbase (a 90's database system).
Should never get here.
At that point we knew we had really f-ed up the database.
|
|
|
|
|
At least the message told you something relating to the error.
Years back I had a program that wrote data to Microsoft Access database tables. One day it quit working and gave this error message: "Invalid arguments." I scratched my head for a while trying to figure out what that meant. Finally I noticed that the size of the Access file is dangerously high (2GB). That was when I changed my app to use MySql.
|
|
|
|
|
Delphi 5: "Catastrophic error." in a single message box with a ok button. Simple! Amazing!  )
|
|
|
|
|
Might as well have replaced the "ok" with "panic"...
|
|
|
|
|
The worst message for me is no message at all: one time i got a error meeeage box with empty text, just error icon and "Error" caption with OK button. I don't remember where i got it, it was a log time ago, but this was the worst "error message i seen
|
|
|
|
|
|
Oracle 7
Bad END statement
The problem was, "Label not found," I guess since it found the END statement before finding the label, it was the END statement's fault.
I used to wallpaper my cube with bad error messages from Oracle and a note saying what they really meant.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
Watermark, a late 90's content management product, had an error message that read... "Thank You Sir, may I have another?"
|
|
|
|
|
A few years ago I was developing a financial app. I asked my boss what the program should do if a particular condition arose. He replied that it couldn't happen so, don't worry about it. I put the following message in the program: "If you get this message, call my bosses name and home phone number". He received middle of the night calls for years.
|
|
|
|
|
One of my favorite error messages comes from the mainframe world in the Natural environment from Software AG. Natural makes the attempt to not only tell you what's wrong, but what you may be able to do to fix the problem. I don't remember the exact text of the message but it was something along the lines of "an error has occurred". The memorable part is the suggested fix: "Check program and correct".
|
|
|
|
|
My first computer book ever was call "Sad Macs, Bombs, and Other Disasters". I had inherited a powermac 6100 with system 7.5. I really enjoyed all the bomb icons complete with an error number...how informative!
"Go forth into the source" - Neal Morse
|
|
|
|
|
kmoorevs wrote: My first computer book ever was call "Sad Macs, Bombs, and Other Disasters". I
had inherited a powermac 6100 with system 7.5. I really enjoyed all the bomb
icons complete with an error number...how informative!
My favourite error was a pre-OS X Mac bomb-type message
"An unexpected error has occurred because an error has occurred".
Genius 
|
|
|
|
|
I put in an error message during a late night debug session: "Oops, the XXX filter is corrupted. You must now sacrifice a black goat over the keyboard at midnight to restore settings". Then I forgot about it thinking it will never happen. This was my first real job as an embedded systems programmer and I was sure this would never hit. Right.
Somehow, the code made it to production. We got a call from tech support about 6 months later who did not find it amusing. My boss remembered it to the day I left the company.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
