Jokes · Public discussion

Why Computers Sometimes Crash! by Dr. Seuss.

Started by Cipher · · Last activity · 5 posts · 5,213 views

This thread is locked and is currently read-only.

Thread details

What we know about this thread

Original section
Jokes
Published
31 January 2004
Last activity
19 December 2005
Original author
Cipher
Posts
5
Discussion status
Public discussion
Total views
5,213
Views / 30 days
0

The navigation and discussion metadata provide context. Posts remain in their original chronological order.

Showing posts 1–5 of 5
Posts remain in their original chronological order.

Text size
  1. 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 is causing unnecessary risk, then you'll have to flash the memory and you'll want to RAM your ROM, and then quickly turn off the computer and be sure to tell your Mom!

    Well, that certainly clears things up for me.

  2. Personally I hear Maryn Poppins singing that song...

  3. Quoted post said:

    Originally posted by Cipher
    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 is causing unnecessary risk, then you'll have to flash the memory and you'll want to RAM your ROM, and then quickly turn off the computer and be sure to tell your Mom!

    Well, that certainly clears things up for me.

    ROFLMAO!!!

  4. Also roflmao!

  5. Cipher said:

    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 is causing unnecessary risk, then you'll have to flash the memory and you'll want to RAM your ROM, and then quickly turn off the computer and be sure to tell your Mom!

    Well, that certainly clears things up for me.


    Awesome.... Been through that many times.... :eek:

Active in the last 60 minutes

Active in this thread

0 users · 0 guests ·0 bots ·0 total

No signed-in users are active right now.

No known search crawlers active right now.