Fatal error

This is a total waste of time! why don't you just put subjects like this on a sheet of paper instead of making each comment a new page that has to reload for each one. Good by this is a waste of time.

Wish I had screen shots but a couple that come to mind are:
"hit escape to continue"
and
while logged in as administrator "You do not have significant privileges to run that command, contact system administrator"

...it would be even funnier IF you placed them on one, maybe, two pages; like 30 on one page, then 27 the next. I got to 5 and I was bored. Could just scroll down.

Wacky, I know.

Memory Buffer Overflow: Can't remember what to do next!

Not an error message, but the actual text label on some IBM software we received back some years ago. There were 4 such labelled 3 1/2 inch floppy disks in the shipment. We never did figure out why they were included...

On a scale of 0 to 10, I rate Content about a 6, Presentation a -5 or less.

On an IBM Mainframe (MVS/VM) you could code User errors which had a label of "U" followed by a three-digit number, so "U812" was a popular label ...

The "Guru Meditation Error" really is the old Amiga BSOD equivalent, which included a hex number that I think was both error code and memory location, in red text on a blakc background. Being a loyal Amiga user at hime, I once made wallpaper for my Win3.x system at work that mimicked the Amiga error screen. It said "Guru Meditation Error 80000000:00000812" and had two boxes in the Amiga standard colors (blue box, white text, orange borders): "Error: Fatal AmigaDOS Error WindDoze Detected Abort? Yes No" and "Error: Fatal Hardware Error Intel (TM) Processor Detected Abort? Yes No."

Fast-forward now to when we were moved to our new data center, I left that wallpaper on my PC when they moved it. As I was walking out the loading dock one evening during the move, one of the contractors in charge of moving the PCs asked me if I had some special software that needed to be loaded on my PC because the kept getting all these AmigaDos errors. They had some hired 'droids following scripts upgrading our PCs from DOS to Win3 (I already had Win3 on mine), and they kept seeing these "errors" and when they clicked the "Yes" box to abort, nothing happened, but double-clicking it brought up Program Manager (the father of Windows Explorer). I said, "Chris, that was my wallpaper." There was a very loud "crack" as he smacked himself upside the head and said, "Sh*t! Wallpaper!" "Just testing you guys, Chris!"