Why Computers Sometimes Crash!
by Dr. Seuss.

I f a packet hits a pocket on a socket of a port, and the bus is interrupted at a very last resort, and the access of the memory makes your floppy disk abort, then the socket packet pocket has an error to report.

If  your cursor finds a menu item followed by a dash, and the double-clicking  icon puts your window in the trash, and your data is corrupted cause the  index doesn't hash, then your situation's hopeless and your system's gonna  crash!

If  the label on the cable on the table at your house, says the network is  connected to the button on your mouse, but your packet wants to tunnel to  another protocol, that's repeatedly rejected by the printer down the hall......

And  your screen is all distorted by the side effects of virus, so your icons in  the window are no bigger than your iris;  there's no point in you rebooting   -  or giving it a bash,   'cuz sure as I'm a poet, the sucker's gonna crash.

When  the copy on your floppy's getting sloppy in the disk, and the macro code instructions are causing unwaranted risk, then you'll have to flash the memory and you'll want to RAM your ROM, and then return the darned computer to the place that it came from!

Well, that certainly clears things up for me. How about  you?