[CTS] Why Computers Crash
- From: "Surfin Suzy" <surfin_suzy@xxxxxxx>
- To: "CTS" <computertalkshop@xxxxxxxxxxxxx>
- Date: Tue, 6 Mar 2007 13:55:32 -0600
If a packet hits a packet 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 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 situuation`s hopeless and your systems 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,
Thats 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 as 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 smartly turn the thing off, and quickly tell someone.
Other related posts:
- » [CTS] Why Computers Crash
