%@LANGUAGE="JAVASCRIPT" CODEPAGE="1252"%>
|
|
| ™ | DOUBLETAKE MEDIA |
|
™ |
Tech NO Logical Spins NOTE: Many of these were from anonymous email, SO DT DON KNOW source, but please let DT KNOW IF YOU KNOW: CONTACT DT CLICK BELOW TO GO DIRECTLY TO THE INDIVIDUAL JOKES Merry XMOS: 'Twas the Night Before ChristMOS METRIC SCHMETRIC METRIC SCHMETRIC
CLASSICS FROM SNL NEWS ANCHOR NORM MCDONALD General Motors addressed this comment by releasing the statement "Yes, but would you want your car to crash twice a day?" And... 1. Every time they repainted the lines on the road you would have to buy a new car. 2. Occasionally your car would die on the freeway for no reason, and you would just accept this, restart and drive on. 3. Occasionally, executing a maneuver would cause your car to stop and fail and you would have to re-install the engine. For some strange reason, you would accept this too. 4. You could only have one person in the car at a time, unless you bought "Car95" or "CarNT". But, then you would have to buy more seats. 5. Macintosh would make a car that was powered by the sun, was reliable, five times as fast, twice as easy to drive, but would only run on five percent of the roads. 6. The Macintosh car owners would get expensive Microsoft upgrades to their cars, which would make their cars run much slower. 7. The oil, gas and alternator warning lights would be replaced by a single "general car default" warning light. 8. New seats would force everyone to have the same size butt. 9. The airbag system would say "are you sure?" before going off.
UNIX Airways Air DOS Windows Air Windows NT Air Linux Air N...ASS..A GAUGING A HORSE'S ASS Why was that gauge used? Why did the English build them like that? Why did 'they' use that gauge then? Okay! Why did the wagons have that particular odd wheel spacing? So who built those old rutted roads? Specifications and bureaucracies live forever. So, the next time you are handed a specification and wonder which horse's rear came up with it, you may be exactly right. Because the Imperial Roman war chariots were made just wide enough to accommodate the back ends of two war-horses. And now, the twist to the story... There's an interesting extension to the story about railroad gauges and horses' behinds. When we see a Space Shuttle sitting on its launch pad, there are two big booster rockets attached to the sides of the main fuel tank. These are solid rocket boosters, or SRBs. Thiokol makes the SRBs at their factory at Utah. The engineers who designed the SRBs might have preferred to make them a bit fatter, but the SRBs had to be shipped by train from the factory to the launch site. The railroad line from the factory had to run through a tunnel in the mountains. The SRBs had to fit through that tunnel. The tunnel is slightly wider than the railroad track, and the railroad track is about as wide as two horses behinds. So, the major design feature of what is arguably the world's most advanced transportation system was determined by the width of a Horse's ass! SPELLING CHECK Eye strike a key and type a word As soon as a mist ache is maid Eye have run this poem threw it INSTALLING LOVE Customer: I can do that. I'm not very technical, but I think I am ready to install now. What do I do first? CS Rep: The first step is to open your HEART. Have you located your HEART ma'am? Customer: Yes I have, but there are several programs running right now. Is it okay to install while they are running? CS Rep: What programs are running ma'am? Customer: Let me see....I have PASTHURT.EXE, LOWESTEEM.EXE, GRUDGE.EXE, and RESENTMENT.COM running right now. CS Rep: No problem. LOVE will automatically erase PASTHURT.EXE from your current operating system. Customer: I don't know how to turn them off. Can you tell me how? CS Rep: My pleasure. Go to your Start menu and invoke FORGIVENESS.EXE. Do this as many times as necessary until GRUDGE.EXE and RESENTMENT.COM have been completely erased. Customer: Okay, I'm done. LOVE has started installing itself automatically. Is that normal? CS Rep: Yes it is. You should receive a message that says it will reinstall for the life of your HEART. Do you see that message? Customer: Yes I do. Is it completely installed? CS Rep: Yes, but remember that you have only the base program. You need to begin connecting to other HEARTS in order to get the upgrades. Customer: Oops...I have an error message already. What should I do? CS Rep: What does the message say? Customer: It says "ERROR 412 - PROGRAM NOT RUN ON INTERNAL COMPONENTS". What does that mean? CS Rep: Don't worry ma'am, that's a common problem. It means that the LOVE program is set up to run on external HEARTS, but has not yet been run on your HEART. It is one of those complicated programming things, but In non-technical terms it means you have to "LOVE" your own machine before it can "LOVE" others. Customer: So what should I do? CS Rep: Can you find the directory called "SELF-ACCEPTANCE"? Customer: Yes, I have it. CS Rep: Excellent, you are getting good at this. Customer: Thank you. CS Rep: You're welcome. Customer: Got it. Hey! My HEART is filling up with really neat files. SMILE.MPG is playing on my monitor right now and it shows that WARMTH.COM, PEACE.EXE, and CONTENTMENT.COM are copying themselves all over my HEART! CS Rep: Then LOVE is installed and running. You should be able to handle it from here. One more thing before I go... Customer: Yes? CS Rep: LOVE is freeware. Be sure to give it and its various modules to everybody you meet. They will in turn share it with other people and they will return some really neat modules back to you. Customer: I will. Thank you for your help. God bless UPGRADING FROM GIRLFRIEND 1.0 TO WIFE 1.0 I can not seem to purge Wife 1.0 from my system. I am thinking about going back to Girlfriend 1.0, but un-install does not work on this program. Can you help me? - Duh Bull Take ANSWER FROM DT TECH SUPPORT: This is a very common problem men complain about, but is mostly due to a primary misconception. Many people upgrade from Girlfriend 1.0 to Wife 1.0 with the idea that Wife 1.0 is merely a "UTILITIES & ENTERTAINMENT" program. Wife 1.0 is an OPERATING SYSTEM and designed by its creator to run everything. WARNING DO NOT TRY TO: un-install, delete, or purge the program from the system once installed. Trying to un-install Wife 1.0 can be disastrous. Doing so may destroy your hard and/or floppy drive. Trying to un-install or remove Wife 1.0 will destroy valuable system resources. You can not go back to Girlfriend 1.0 because Wife 1.0 is not designed to do this. Some have tried to install Girlfriend 2.0 or Wife 2.0, but end up with more problems than the original system. Look in your manual under Warnings - Alimony/Child Support. Others have tried to run Girlfriend 1.0 in the background, while Wife 1.0 is running. Eventually Wife 1.0 detects Girlfriend 1.0 and a system conflict occurs, this can lead to a non- recoverable system crash. Some users have tried to download similar products such as Fling and 1NiteStand. Often their systems have become infected with a virus. I recommend you keep Wife 1.0 and just deal with the situation. Having Wife 1.0 installed myself, I might also suggest you read the entire section regarding General Protection Faults (GPFs). You must assume all responsibility for faults and problems that might occur. The best course of action will be to push apologize button then reset button as soon as lock-up occurs. System will run smooth as long as you take the blame for all GPFs. Wife 1.0 is a great program but is very high maintenance. Suggestions for improved operation of Wife 1.0 -Monthly use utilities such as TLC and FTD -Frequently use Communicator 5.0 -DT Tech Support 1. In the beginning GOD created the Bit and the Byte. And from those he created the Word. 2. And there were two Bytes in the Word; and nothing else existed. And God separated the One from the Zero; and he saw it was good. 3. And God said - Let the Data be; And so it happened. And God said – Let the Data go to their proper places. And he created floppy disks and hard disks and compact disks. 4. And God said - Let the computers be, so there would be a place to put floppy disks and hard disks and compact disks. Thus God created computers and called them hardware. 5. And there was no Software yet. But God created programs; small and big. . . And told them - Go and multiply yourselves and fill all the Memory. 6. And God said -I will create the Programmer; And the Programmer will make new programs and govern over the computers and programs and Data. 7. And God created the Programmer; and put him at Data Center; And God showed the Programmer the Catalog Tree and said You can use all the volumes and subvolumes but DO NOT USE Windows. 8. And God said - It is not Good for the programmer to be alone. He took a bone from the Programmer's body and created a creature that would look up at the Programmer; and admire the Programmer; and love the things the Programmer does; And God called the creature: the User. 9. And the Programmer and the User were left under the naked DOS and it was Good. 10. But Bill was smarter than all the other creatures of God. And Bill said to the User - Did God really tell you not to run any programs? 11. And the User answered - God told us that we can use every program and every piece of Data but told us not to run Windows or we will die. 12. And Bill said to the User - How can you talk about something you did not even try? The moment you run Windows you will become equal to God. You will be able to create anything you like by a simple click of your mouse. 13. And the User saw that the fruits of the Windows were nicer and easier to use. And the User saw that any knowledge was useless - since Windows could replace it. 14. So the User installed the Windows on his computer; and said to the Programmer that it was good. 15. And the Programmer immediately started to look for new drivers. And God asked him - What are you looking for? And the Programmer answered - I am looking for new drivers because I can not find them in the DOS. And God said - Who told you need drivers? Did you run Windows? And the Programmer said - It was Bill who told us to ! 16. And God said to Bill - Because of what you did you will be hated by all the creatures. And the User will always be unhappy with you. And you will always sell Windows. 17. And God said to the User - Because of what you did, the Windows will disappoint you and eat up all your Resources; and you will have to use lousy programs; and you will always rely on the Programmers help. 18. And God said to the Programmer - Because you listened to the User you will never be happy. All your programs will have errors and you will have to fix them and fix them to the end of time. 19. And God threw them out of the Data Center and locked the door and secured it with a password. 20. GENERAL PROTECTION FAULT Y to K CONVERSION (old but still funny) I hope that I haven't misunderstood your instructions. because to be honest, none of this Y to K problem makes any sense to me. Januark Be prepared! Be sure to stock up on K-Y2K Jelly. It allows you to insert four digits where only two would fit, before. TOP 10 SIGNS THAT IT'S TIME TO JOIN E-MAILERS ANONYMOUS 10. You wake up at 3 a.m. to go to the bathroom, and check your e-mail on the way back to bed. DRUM ROLL PLEASE ... 1. Immediately after reading this list, you e-mail it to someone. New Computer Viruses You Should Know About Little Red Riding Hood At a previous but undetermined timeframe, a single-family domestic domicile was inhabited by a young girl, known as Little Red Riding Hood (LRRH), and her Maternal Parent (MP). The Maternal Parent (MP) had once provided for the fabrication of an article of clothing, a cloak in nature (including a "hood" or protective covering for the head of the wearer), that was RGB code [255,0,0] in hue (aka, "red"). As a result of this action, and the resultant repeated usage of the "hood", the young girl was always known as LRRH in substitution for the name identified on her birth certificate and other identifying documentation. During one 24-hour interval, a request was issued by the MP for LRRH to deliver a package to the MP's Maternal Parent (MPMP) (genealogically identified as the Grandmaternal Unit (GU) with respects to LRRH). This package was to include:
Little Red Riding Hood (LRRH) optioned to accept the Task Order (TO). LRRH further sourced a package delivery vehicle with the proper functionality for the Task Order, selecting a wicker basket. After a thorough and complete market survey, leveraging LRRH's experience with similar Task Orders in the past, cheesecake and fresh butter were acquired from the kitchen, whereas strawberries were acquired from the garden. While the latter item was not, strictly speaking, within the bounds of the Task Order, the marginal cost savings as compared to waiting for strawberries to grow in the kitchen appeared to be of great benefit to the MP in the completion of the Task. With initial outsourcing complete, the journey was commenced by LRRH (see Appendix A: Proposed Map of Route Between the Domiciles of MP and GU). During a brief eleventh-hour meeting, MP issued a contract rider requiring the complete confidentiality of all personnel working the Task Order. LRRH assured MP that there would be no violation of this rider. In the course of executing the Task Order, LRRH was approached by market competitor Old Grey Wolf (OGW). There were inquiries from OGW to LRRH regarding the nature of the Task Order, and in violation of the contract rider, LRRH disclosed sensitive and mission-critical data relating to the Task. Table 1-1 illustrates the nature of the information believed to have been compromised: Table 1-1: Information Compromised by LRRH During Interactions With GW
The identity of LRRH had been predetermined by OGW using standard practices of observation; therefore, that information was not compromised by the actions of LRRH. It was the intent of OGW to compromise the functionality of LRRH, but the potential negative impact on its operations by the nearby presence of an organized unit of fully-functional Wood Cutters (WC) provided for the redirection of its action item to the domicile of GU. Though LRRH had blatantly violated the terms of the contract rider, this violation went unreported to supervisory entities (i.e., MP) by the violator. LRRH continued to action the Task Order despite clear and compelling evidence that the integrity of the process had been disenfranchised by the OGW. While LRRH continued to analyze its processes through the implementation of the Task Order, OGW leveraged its greater cumulative experience and used Best Practices to arrive at the GU client site in a more efficient and expedient manner than LRRH. Therein, the functionality of GU was impacted by the biorhythmic needs of OGW in a negative manner. Upon the dissemination of information related to the pending closure of the Task Order assigned to LRRH, OGW engaged in an enterprise-wide analysis of situational readiness. Determining that there were vulnerabilities in OGW's methodology, OGW elected to redesign the external identifiers of OGW to better emulate those of GU, by means of garbing the nightgown generally associated with GU and altering the vocal patterns of OGW to align with precedents set by GU. After completing the Task Order by delivering the deliverables:
LRRH recorded observations of the host system. These observations included, but were not limited to:
Upon receipt of the host system status analysis, OGW prepared and delivered a response regarding the functionality of the concerned functionalities, to include:
Immediately thereafter, Old Grey Wolf (OGW) executed its asset plan action item and severely compromised the functionality of Little Red Riding Hood (LRRH). An email to the wrong wife (This was supposedly voted as the best e-mail joke in Australia in 2001)After being nearly snowbound for two weeks last winter, a Seattle man departed for his vacation in Miami Beach, where he was to meet his wife the next day at the conclusion of her business trip to Minneapolis. They were looking forward to pleasant weather and a nice time together. Unfortunately, there was some sort of mix up at the boarding gate, and the man was told he would have to wait for a later flight. He tried to appeal to a supervisor but was told the airline was not responsible for the problem and it would do no good to complain. Upon arrival at the hotel the next day, he discovered that Miami Beach was having a heat wave, and its weather was almost as uncomfortably hot as Seattle's was cold. The desk clerk gave him a message that his wife would arrive as planned. He could hardly wait to get to the pool area to cool off, and quickly sent his wife an e-mail, but due to his haste, he made an error in the e-mail address. His message therefore arrived at the home of an elderly preacher's wife whose even older husband had died only the day before. When the grieving widow opened her e-mail, she took one look at the monitor, let out an anguished scream, and fell to the floor dead. Her family rushed to her room where they saw this message on the screen: "Dearest wife, Departed yesterday as you know. Just now got checked in. Some confusion at the gate. Appeal was denied. Received confirmation of your arrival tomorrow. Your loving husband. P.S. Things are not as we thought. You're going to be surprised at how hot it is down here"
|
|---|
S P O N S O R E D L I N K S |