ID: 17780
Tech
How dod the person take over the remote?
ID: 15210
Tech
TO: ALL EMPLOYEES
FROM: SYSTEM'S ADMINISTRATOR
SUBJECT: WARNING! C-NILE VIRUS ... MUST READ:
Just learned about this from a reliable source. It seems that there is a computer virus out there called the "C-Nile Virus" that even the most advanced programs from Norton cannot take care of, so be warned. It appears to affect those of us who were born before 1958.
Symptoms of the C-Nile Virus:
1. Causes you to send the same e-mail twice.
2. Causes you to send blank e-mail.
3. Causes you to send e-mail to the wrong person.
4. Causes you to send e-mail back to the person who sent it to you.
5. Causes you to send e-mail to other listed persons who received the e-mail from the person who sent it to you.
6. Causes you to forget to attach the attachment.
7. Causes you to hit "SEND" before you've finished the
ID: 16124
Tech
The Dosfish
Long ago, in the days when all disks flopped in the breeze and the writing of words was on a star, the Blue Giant dug for the people the Pea Sea. But he needed a creature who could sail the waters, and would need for support but few rams.
So the Gateskeeper, who was said to be both micro and soft, caused to be fashioned a Dosfish, who was small and spry, and could swim the narrow sixteen-bit channel. But the Dosfish was not bright, and could be taught but few tricks. His alphabet had no A's, B's, or Q's, but a mere 640 K's, and the size of his file cabinet was limited by his own fat.
At first the people loved the Dosfish, for he was the only one who could swim the Pea Sea. But the people soon grew tired of commanding his line, and complained that he could neither be dragged or dropped. "Forsooth," they cried, "the Dosfish can do only one job at a time, and of names he knows only eight and three." And many of them left the Pea Sea for good, and went off in search of the Magic Apple.
Although many went, far more stayed, because admittance to the Pea Sea was cheap. So the Gateskeeper studied the Magic Apple, and rested awile in the Parc of the Xer Ox. And he made a Window that could ride on the Dosfish, and do its thinking for it. But the Window was slow, and it would break when the Dosfish got confused. So most people contented themselves with the Dosfish.
Now it came to pass that the Blue Giant came upon the Gateskeeper, and spoke thus: "Come, let us make of ourselves something greater than the Dosfish." The Blue Giant seemed like a humbug, so they called the new creature Oz II.
Now Oz II was smarter than the Dosfish, as most things are. It could drag and drop, and could keep files without becoming fat. But the people cared for it not. So the Blue Giant and the Gateskeeper promised another Oz II, to be called Oz II Too, that could swim fast in the new, 32-bit wide Pea Sea.
Then lo, a strange miracle occurred. Although the Window that rode on the Dosfish was slow, it was pretty, and the third window was the prettiest of all. And the people began to like the third window, and to use it. So the Gateskeeper turned to the Blue Giant and said "Fie on thee, for I need thee not. Keep thy Oz II Too, and I shall make of my Window an Entity that will not need the Dosfish, and will swim in the 32-bit Pea Sea."
Years passed, and the workshops of the Gateskeeper and the Blue Giant were many times overrun by insects. And the people went on using their Dosfish with a Window; even though the Dosfish would from time to time become confused and die, it could always be revived with three fingers. Then there came a day when the Blue Giant let forth his Oz II Too onto the world. The Oz II Too was indeed mighty, and awesome, and required a great ram, and the world was changed not a whit. For the people said "It is indeed great, but we see little application for it." And they were doubtful, because the Blue Giant had met with the Magic Apple, and together they were fashioning a Taligent, and the Taligent was made of objects, and was most pink.
Now the Gateskeeper had grown ambitious, and as he had been ambitious before he grew, he was now more ambitious still. So he protected his Window Entity with great security, and made its net work both in serving and with peers. And the Entity would swim, not in the Pea Sea, but also in the Oceans of Great Risk. "Yea," the Gateskeeper declared, "though my Entity will require a greater ram than Oz II Too, it will be more powerful than a world of Eunuchs.
And so the gateskeeper prepared to unleash his Entity to the world, in all but two cities. For he promised that a greater Window, a greater Entity, and even a greater Dosfish would appear one day in Chicago and Cairo, and it too would be built of objects.
Now the Eunuchs who lived in the Oceans of Great Risk, and who scorned the Pea Sea, began to look upon their world with fear. For the Pea Sea had grown and great ships were sailing in it, the Entity was about to invade their Ocenas, and it was rumored that files would be named in letters greater than eight. And the Eunuchs looked upon the Pea Sea, and many of them thought to immigrate.
Within the Oceans of Great Risk were many Sun Worshippers, and they had wanted to excel, and make their words perfect, and do their jobs as easy as one-two-three. And what's more, many of them no longer wanted to pay for the Risk. So the Sun Lord went to the Pea Sea, and got himself eighty-sixed.
And taking the next step was he of the NextStep, who had given up building his boxes of black. And he proclaimed loudly that he could help anyone make wondrous soft wares, then admitted meekly that only those who know him could use those wares, and he was made of objects, and required the biggest ram of all.
And the people looked out upon the Pea Sea, and they were sore amazed. And sore confused. And sore sore. And that is why, to this day, Ozes, Entities, and Eunuchs battle on the shores of the Pea Sea, but the people still travel on the simple Dosfish.
ID: 6785
Tech
Dr. Seuss as Technical Writer
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 '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 on 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,
'cause as sure as I'm a poet, the sucker's gonna hang!
When the copy of your floppy's getting sloppy on the disk,
And the microcode instructions cause unnecessary risc,
Then you have to flash your memory and you'll want to RAM your ROM,
Quicky turn off the computer and be sure to tell your mom!
ID: 13347
Tech
"Everything that can be invented has been invented." - Charles H. Duell, Commissioner, U.S. Office of Patents, 1899.
ID: 9674
Tech
Dear Bob in Tech Support,
I'm currently running the latest version of GirlFriend and I've been having some problems lately. I've been running the same version of DrinkingBuddies 1.0 forever, as my primary application, and all the GirlFriend releases I've
tried have always conflicted with it.
I hear that DrinkingBuddies won't crash if GirlFriend is run in background mode and the sound is turned off, but I'm embarrassed to say I can't find the switch to turn the sound off. I just run them separately, and it works
okay. GirlFriend also seems to have a problem co-existing with my Leisure 3.1 and QuietTime programs, often trying to abort them with some sort of timing incompatibility.
I probably should have stayed with GirlFriend 1.0, but I thought I might see better performance from GirlFriend 2.0. After months of conflicts and other problems, I consulted a friend who has had experience with GirlFriend 2.0. He said I probably didn't have enough cache to run GirlFriend 2.0, and eventually it would require a Token Ring to run properly. He was right - as soon as I purged my cache, it uninstalled itself.
Shortly after that, I installed GirlFriend 3.0 beta. All the bugs were supposed to be gone, but the first time I used it, it gave me a virus anyway. I had to clean out my whole system and shut down for a while to re-check my hardware.
I very cautiously upgraded to GirlFriend 4.0. This time I used a SCSI probe first and also installed a virus protection program. It worked okay for a while, until I discovered that GirlFriend 1.0 was still in my system. I
tried running GirlFriend 1.0 again with GirlFriend 4.0 still installed, but GirlFriend 4.0 has a "feature" I didn't know about that automatically detects the presence of any other version of GirlFriend and communicates with it in the background in some way, which results in the immediate removal of both versions.
The version I have now works pretty well, but there are still some problems. Like all versions of GirlFriend, it is written in some obscure language I can't understand, much less reprogram. Frankly I think there is too much attention paid to the look and feel rather than the desired functionality. Also, to get the best connections with your hardware, you usually have to use gold-plated contacts, which is very expensive. And I've never liked how GirlFriend is totally "object-oriented", as that interface is sometimes cumbersome and even counter-intuitive.
A year ago, a friend of mine upgraded his version of GirlFriend to GirlFriendPlus 1.1, which is a Terminate and Stay Resident version of GirlFriend. To his dismay, however, he discovered that GirlFriendPlus 1.1 expires within a year of the upgrade, if you don't upgrade AGAIN to Fiancee 1.0. So he did, but soon after that, he had to upgrade YET AGAIN to Wife 1.0, which he describes as a HUGE resource hog.
It has taken up all his space, so he can't load anything else. In fact, it has even automatically deleted several of his other programs to make room for itself, not the least of which was DrinkingBuddies 1.0, which used to be one of his favorite applications, as well. This is particularly disturbing to me, as we used to run DrinkingBuddies 1.0 on a network with several of our mutual friends, and now he can't even connect any more!
He told me that one of the primary reasons he decided to go with Wife 1.0 was because it came bundled with FreeSexPlus, which sounded great. Well, it turns out the resource allocation module of Wife 1.0 sometimes inexplicably
prohibits access to FreeSexPlus, particularly when he starts the new Plug-Ins he wanted to try. Also, for no apparent reason, the OralSex 1.0 module that worked fine in his previous versions of GirlFriendPlus and Fiancee, stopped working the instant the upgrade to Wife 1.0 finished
installing.
On top of that, Wife 1.0 must be running on a well warmed-up system before he can do anything with the FreeSexPlus module. This warming up process requires him to run an antiquated version of ForePlay Beta, which has an
agonizingly slow interface, and which has an unfortunate tendency to crash, requiring a cold reboot to his system. The real insult to injury however, is that even though he did not ask for it, Wife 1.0 came embedded with MotherInLaw 2.0, which has an irritating automatic pop-up feature he can't turn off.
I told him to try installing Mistress 1.0 (which I had heard works great in such situations), but he said he heard if you try to run it without first uninstalling Wife 1.0, Wife 1.0 will delete all of your MSMoney files before doing an uninstall of itself; then Mistress 1.0 won't install anyway because of insufficient resources.
Please help me Bob, I don't know what to do. Since the initial release, I have had nothing but problems.
I've heard that I would really like the CoolGirlFriend 1.0 Deluxe Upgrade (which is supposed to come bundled with a completely functioning version of FreeSexDeluxe), but that release is no where to be found - not even the Beta version! That release is also supposed to come with its own resource management module seamlessly layered in, so it won't conflict with any of my other programs (barring previous versions of GirlFriend, which I would happily delete!).
Please advise.
ID: 9866
Tech
Last week my wife and I purchased a new computer. We ran into some difficulties while setting it up so we called the customer support phone number we found in the manual.
I picked up the phone and called the number. A man answered the phone and I explained the problem to him.
He began rattling off computer jargon. This confused us even more.
"Sir," I said politely, "Can you explain what I should do as if I were a small child?"
"Okay," the computer support guy said, "Son, could you please put your mommy on the phone?"
ID: 16127
Tech
What really does happen to MS programmers once they die?
Did you hear about the Microsoft Windows programmer who died? He found himself in front of a committee that decides whether you go to Heaven or Hell.
The committee told the programmer he had some say in the matter and asked him if he wanted to see Heaven and Hell before stating his preference.
"Sure," he said, so an angel took him to a place with a sunny beach, volleyball, and rock and roll, where everyone was having a great time.
"Wow!" he exclaimed. "Heaven is great!" "Wrong," said the angel. "That was Hell. Want to see Heaven?" "Sure!" So the angel took him to another place. Here a bunch of people were sitting in a park playing bingo and feeding dead pigeons.
"This is Heaven?" asked the Windows programmer.
"Yup," said the angel. "Then I'll take Hell." Instantly he found himself plunged up to his neck in red-hot lava, with the hosts of the damned in torment around him. "Where's the beach? The music? The volleyball?" he screamed frantically to the angel.
"That was the demo," she replied as she vanished.
ID: 114
Tech
Tech Support
Just in case you think you are TC (technologically challenged). The following is an excerpt taken from a Wall Street Journal article:
1. Compaq is considering changing the command "Press Any Key" to "Press Return Key" because of the flood of calls asking where the "Any" key is.
2. AST technical support had a caller complaining that her mouse was hard to control with the dust cover on. The cover turned out to be the plastic bag the mouse was packaged in.
3. Another Compaq technician received a call from a man complaining that the system wouldn't read word processing files from his old diskettes. After trouble-shooting for magnets and heat failed to diagnose the problem, it was found that the customer had labeled the diskettes, then rolled them into the typewriter to type the labels.
4. Another AST customer was asked to send a copy of her defective diskettes. A few days later a letter arrived from the customer along with photocopies of the floppies.
5. A Dell technician advised his customer to put his troubled floppy back in the drive and close the door. The customer asked the tech to hold on, and was heard putting the phone down, getting up and crossing the room to close the door to his room.
6. Another Dell customer called to say he couldn't get his computer to fax anything. After 40 minutes of trouble-shooting, the technician discovered the man was trying to fax a piece of paper by holding it in front of the monitor screen and hitting the "send" key.
7. Yet another Dell customer called to complain that his keyboard no longer worked. He had cleaned it by filling up his tub with soap and water and soaking the keyboard for a day, then removing all the keys and washing them individually.
8. A Dell technician received a call from a customer who was enraged because his computer had told him he was "bad and an invalid". The tech explained that the computer's "bad command" and "invalid" responses shouldn't be taken personally.
9. A confused caller to IBM was having troubles printing documents. He told the technician that the computer had said it "couldn't find printer". The user had also tried turning the computer screen to face the printer - but that his computer still couldn't "see" the printer.
10. An exasperated caller to Dell Computer Tech Support couldn't get her new Dell Computer to turn on. After ensuring the computer was plugged in, the technician asked her what happened when she pushed the power button. Her response, "I pushed and pushed on this foot pedal and nothing happens." The "foot pedal" turned out to be the computer's mouse.
11. Another customer called Compaq tech support to say her brand-new computer wouldn't work. She said she unpacked the unit, plugged it in and sat there for 20 minutes waiting for something to happen. When asked what happened when she pressed the power switch, she asked "What power switch?"
12. True story from a Novell NetWire SysOp:
Caller: "Hello, is this Tech Support?"
Tech: "Yes, it is. How may I help you?"
Caller: "The cup holder on my PC is broken and I am within my warranty period. How do I go about getting that fixed?"
Tech: "I'm sorry, but did you say a cup holder?"
Caller: "Yes, it's attached to the front of my computer."
Tech: "Please excuse me if I seem a bit stumped, It's because I am. Did you receive this as part of a promotional, at a trade show? How did you get this cup holder? Does it have any trademark on it?"
Caller: "It came with my computer, I don't know anything about a promotional. It just has '4X' on it." At this point the Tech Rep had to mute the caller, because he couldn't stand it. He was laughing too hard. The caller had been using the load drawer of the CD-ROM drive as a cup holder, and snapped it off the drive!
13. Another IBM customer had troubles installing software and rang for support. "I put in the first disk, and that was OK. It said to put in the second disk, and had some problems with the disk. When it said to put in the third disk - I couldn't even fit it in..." The user hadn't realized that "Insert Disk 2" meant to remove Disk 1 first.
14. In a similar incident, a customer had followed the instructions for installing software. The instructions said to remove the disk from it's cover and insert into the drive. The user had physically removed the casing of the disk and wondered why there were problems.
As Ripley would say, believe it or not!
+10,000 Jokes