[Lex Computer & Tech Group/LCTG] A recent talk reminded me of this

jjrudy1 at comcast.net jjrudy1 at comcast.net
Sun Dec 1 13:29:45 PST 2019


Why Computers Sometimes Crash! by "Dr. Seuss" (I have no idea who the real
author was).  It is probably 10 years old.

You have to read it out loud, slowly.

If a packet hits a pocket on a socket on 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 packets want 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 gauss, so your icons
in the window are as wavy as a souse;
then you may as well reboot and go out with a bang, 'cuz sure as I'm a poet,
the sucker's gonna hang.

When the copy on your floppy's getting sloppy in the disk, and the macro
code instructions cause unwanted risk,
then you'll have to flash the BIOS and you'll want to RAM your ROM, just
quickly turn the darn thing off and run to tell your Mom!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.toku.us/private.cgi/lctg-toku.us/attachments/20191201/6c73f6a8/attachment.html>


More information about the LCTG mailing list