Dr. Seuss explains why computers crash: If a packet hits a pocket on a socket on a port, And the bus is interrupted as a very last resort, And the address 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 because 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 onto another protocol, That's repeatedly rejected by the printer down the hall, And your screen is all distorted by the side effect 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, Cause as sure as I'm a poet, the program's gonna hang! When the copy of your floppy's getting sloppy on the disk, And the microcode instructions cause unnecessary risk, Then you'll have to flash your memory, and you'll want to RAM your ROM, Quickly turn off the computer and be sure to tell your mom!

Thank you! And here I thought it might be from something I was doing wrong. And all the time it's those microcode instructions. Are those like green eggs and ham? W.L.

I'm going to read that to my kids at bedtime tonight. You may have just started a trend on the site here. Did you write that yourself?

No i didnt write it myself, i saw it ages ago and thought i`d share it :) Woof