ID: 1340
Tech
If you messed up your life, you could press "Ctrl, Alt, Delete" and start all over!
To get your daily exercise, just click on "run"!
If you needed a break from life, click on "suspend".
Hit "any key" to continue life when ready.
To get even with the neighbors, turn up the sound blaster.
To "add/remove" someone in your life, click settings and control panel.
To improve your appearance, just adjust the display settings.
If life gets too noisy, turn off the speakers.
When you lose your car keys, click on "find".
"Help" with the chores is just a click away.
You'd use your diskette to recover from a crash.
We could click on "send" and the kids would go to bed immediately.
To feel like a new person, click on "refresh".
Click on "close" to shut up the kids and spouse.
To undo a mistake, click on "back".
Is your wardrobe getting old? Click "update".
If you don't like cleaning the litter box, click on "delete".
ID: 17781
Tech
How did the person take over the remote?
He asked for remote CONTROLS!
ID: 1635
Tech
- Nice Set of Floppies!
- Hey, how 'bout I take off your cover and insert a bigger CPU.
- I'd like to play on your laptop.
- Need me to unzip your files?
- If you were an ISP, I'd dial you all day long!
- I'd like to boot up your PC!
- I'll bet my hard drive is the biggest you've ever seen!
- I've got a 21 inch... (monitor)
- I'd get a T3 to watch your streaming video...
- Your homepage or mine?
ID: 9617
Tech
By following the instructions below, you should have error-free, long-lasting floppy disks.
1. Never leave diskettes in the disk drive, as data can leak out of the disk and corrode the inner mechanics of the drive. Diskettes should be rolled up and stored in pencil holders.
2. Diskettes should be cleaned and waxed once a week. Microscopic metal particles can be removed by waving a powerful magnet over the surface of the disk. Any stubborn metallic shavings can be removed with scouring powder and soap. When waxing the diskettes, make sure the surface is even. This will allow the diskette to spin faster, resulting in better access time.
3. Do not fold diskettes unless they do not fit into the drive. "Big" diskettes may be folded and used in "little" disk drives.
4. Never insert a diskette into the drive upside down. The data can fall off the surface of the disk and jam the intricate mechanics of the drive.
5. Diskettes cannot be backed up by running them through the xerox machine. If your data is going to need to be backed up, simply insert two diskettes into the drive. Whenever you update a document, the data will be written on both diskettes.
6. Diskettes should not be inserted or removed from the drive while the red light is flashing. Doing so could result in smeared or possibly unreadable text. Occasionally the red light remains flashing in what is known as a "hung" or "hooked" state. If your system is "hooking" you will probably need to insert a few coins before being allowed access to the slot.
7. If your diskette is full and you need more storage space, remove the disk from the drive and shake vigorously for 2 minutes. This will pack the data enough (Data Compression) to allow for more storage. Be sure to cover all the openings with scotch tape to prevent loss data.
8. Access time can be greatly improved by cutting more holes in the diskette jacket. This will provide more simultaneous access points to the disk.
9. Diskettes may be used as coasters for beverage glasses, provided that they are properly waxed beforehand. Be sure to wipe the diskettes dry before using. (see item 2 above)
10. Never use scissors and glue to manually edit documents. The data is stored much too small for the naked eye, and you may end up with data from some other document stuck in the middle of your document. Razor blades and scotch tape may be used, however, provided the user is equipped with an electron microscope.
11. Periodically spray diskettes with insecticide to prevent system bugs from spreading.
ID: 8781
Tech
A guy walks into the Microsoft Shop.
Guy: I'd like a cheesecake, please.
Receptionist: Sure.
The receptionist hands him a block of cheese.
Guy: Umm... This is just the cheese. Where's the cake?
Rec: You have to purchase that seperately.
Guy: What the ----? What kind of product are you trying to sell me? Oh well.
Rec: Good. I knew you'd understand.
The Rec hands him the cake.
Guy: So... What do I do with the cheese and the cake?
Rec: You blend it.
Guy: With what?
The Rec hands him a blender.
The guy puts the cheese and the cake into the blender and blends it.
Guy: Now I have a bunch of liquid. What do I do with it?
Rec: Oh ---- you retard, you're supposed to exchange the cake for the batter first.
Guy: For the sake of Pete, what the ----? Fine. Let's start over. So I get the cheese and I get the cake. Then I exchange the cake for the batter, right?
Rec: Yep.
The guy blends it.
Guy: Right... I'm still stuck with a load of liquid.
Rec: You're supposed to cook it.
Guy: With what?
Rec: With this full-sized oven.
Guy: What the ----?
Rec: Yep.
The guy cooks the cheesecake.
Guy: Hey Rec! My cake is hot! Aren't cheesecakes supposed to be frozen?
Rec: Yeah, you need to put it in that freezer behind you for 24 hours. Since you're not an employee, it costs $1 a minute to use it.
Guy: You mean I'm supposed to pay $1440 to freeze my cake?
Rec: Wow! You're good at math! And, yes.
The guy puts his cheesecake in the freezer, pays his over-inflated bill, and leaves.
The next day, he comes back and finds the cake gone.
Guy: What happened to my cheesecake?
Rec: Well, you see, at lunch about an hour ago, there was this guy who was still hungry and saw the cheesecake and ate it.
On a completely unrelated note, the guy's brother bought a computer from Microsoft.
GB: How do I type my work?
Rec: Install Office.
GB: Sure.
GB: Umm... how do I install it?
Rec: You use a CD.
GB: Oh. Whoops, I jammed my cubicle into my case instead. Let's start over. So, I buy the computer and I install Office using a CD. Umm... I don't get how to do it.
Rec: You put the CD in the drive and let it Autorun.
GB: What the ---- is a drive?
Rec: Why don't you leave your computer here and let us do it for you?
GB: Sure.
The guy's brother leaves the computer and goes home.
The next day, he comes back.
GB: Yeah, I left my computer here yesterday?
Rec: No, there's no record of that. There was an extra computer here yesterday, so the shipping people shipped it off to CraCom.
GB: CraCom? As in CrappyCompany? It went bankrupt 2 hours ago!
Rec: Oh, I'm sorry. Would you care to buy a notebook?
GB: I already have one in my pocket, thanks.
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: 12137
Tech
The Web site you seek
cannot be located but
countless others exist
Three things are certain:
Death, taxes, and lost data.
Guess which has occurred.
Everything is gone;
Your life's work has been destroyed.
Squeeze trigger (yes/no)?
Windows NT crashed.
I am the Blue Screen of Death.
No one hears your screams.
Seeing my great fault
Through darkening blue windows
I begin again
The code was willing,
It considered your request,
But the chips were weak.
Printer not ready.
Could be a fatal error.
Have a pen handy?
A file that big?
It might be very useful.
But now it is gone.
Errors have occurred.
We won't tell you where or why.
Lazy programmers.
Server's poor response
Not quick enough for browser.
Timed out, plum blossom.
Chaos reigns within.
Reflect, repent, and reboot.
Order shall return.
Login incorrect.
Only perfect spellers may
enter this system.
This site has been moved.
We'd tell you where, but then we'd
have to delete you.
Wind catches lily
scatt'ring petals to the wind:
segmentation fault
ABORTED effort:
Save and close all that you have.
You ask way too much.
First snow, then silence.
This thousand dollar screen dies
so beautifully.
With searching comes loss
and the presence of absence:
"My Novel" not found.
The Tao that is seen
Is not the true Tao, until
You bring fresh toner.
The Web site you seek
cannot be located but
endless others exist.
Stay the patient course
Of little worth is your ire
The network is down
A crash reduces
your expensive computer
to a simple stone.
ID: 10014
Tech
It's pretty bad if you start typing "lol" as if it were a sentence (Lol.)
Its worse if you start saying, "laugh out loud" in everday conversations.
It's absolutely horrible if you actually say, "l-o-l."
ID: 7669
Tech
Perhaps the Most Truthful: on Microsoft marketing:
"There won't be anything we won't say to people to try and convince them that our way is the way to go."
Not on his mind while developing Win9X..circa 1981...
"640K ought to be enough for anybody."
On the solid code base of Win9X... thanks WPW!
"If you can't make it good, at least make it look good."
from "OS/2 Programmer's Guide" (forward by Bill Gates):
"I believe OS/2 is destined to be the most important operating system, and possibly program, of all time. As the successor to DOS, which has over 10,000,000 systems in use, it creates incredible opportunities for everyone involved with PCs."
Bill Gates, Free Market and the LA Times Thanks GC!
"There are people who don't like capitalism, and people who don't like PCs. But there's no-one who likes the PC who doesn't like Microsoft"
From the back of an old Digitalk Smalltalk/V PM manual, 1990:
"This is the right way to develop applications for OS/2 PM. OS/2 PM is a tremendously rich environment, which makes it inherently complex. Smalltalk/V PM removes that complexity and lets you concentrate on writing great programs. Smalltalk/V PM is the kind of tool that will make OS/2 the successor to MS/DOS".
from "OS/2 Notebook", Microsoft Press, (c) 1990 - an excerpt from an interview with Bill Gates and Jim Cannavino, p. 614:
Developer: Does the announcement [of the OS/2 joint development agreement between IBM and Microsoft] mean that Microsoft is curtailing any plans for future development of Windows?
Gates: Microsoft has not changed any of its plans for Windows. It is obvious that we will not include things like threads and preemptive multitasking in Windows. By the time we added that, you would have OS/2.
There's a reason they threw it away...
from "Programmers at Work" by Microsoft Press, interview with Bill (found on comp.os.os2.advocacy),
Interviewer: Is studying computer science the best way to prepare to be a programmer?
Gates: No, the best way to prepare is to write programs, and to study great programs that other people have written. In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system.
Only the finest Microsoft marketing! (submitted by BarryB):
"If you don't know what you need Windows NT for, you don't need it."
On the Box of Windows 2.11 for 286 (submitted by GLDM)
"New interface closely resembles Presentation Manager, preparing you for the wonders of OS/2!"
On code stability, from Focus Magazine (submitted by Benedikt Heinen Microsoft programs are generally bug-free. If you visit the Microsoft hotline, you'll literally have to wait weeks if not months until someone calls in with a bug in one of our programs. 99.99% of calls turn out to
be user mistakes.
[...]
I know not a single less irrelevant reason for an update than bugfixes. The reasons for updates are to present more new features.
Unconfirmed quotes:
Microsoft's GUI innovations... 1983 (thanks E.R.)
"Imagine the disincentive to software development if after months of work another company could come along and copy your work and market it under its own name...without legal restraints to such copying, companies like Apple could not afford to advance the state of the art."
Even more 1984 predictions (thanks Scott Renyen)
"The next generation of interesting software will be made on a Macintosh, not an IBM PC."
+10,000 Jokes