Reply to thread

Message: <blockquote data-quote="Novindu" data-source="post: 12764" data-attributes="member: 718">Why Computers Sometimes Crash!  By Dr. Seuss. <img src="http://img144.imageshack.us/img144/9664/1b64bb49rt5.gif" alt="" class="fr-fic fr-dii fr-draggable " style="" /> ( Read like a rhyme - kids loves it )  (You gotta read this one out loud)   I f a packet hits a pocket on a socket on a port, and the bus is interruptedAt a very last resort, and the access of the memory makes your floppy diskAbort, then the socket packet pocket has an error to report.    If your cursor finds a menu item followed by a dash, and the double-clickingIcon puts your window in the trash, and your data is corrupted cause the indexDoesn'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 isConnected to the button on your mouse, but your packets want to tunnel toAnother 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 iconsIn the window are as wavy as a souse; then you may as well reboot and go outWith 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 codeInstructions are causing unnecessary risk, then you'll have to flash the memoryAnd you'll want to RAM your ROM, and then quickly turn off the computer and beSure to tell your Mom!   Well, that certainly clears things up for me. How about you?</blockquote>

Verification: Payakata winadi keeyak tibeda?

Top Bottom