Technology

1. Cannot find REALITY.SYS. Universe halted.
2. COFFEE.EXE Missing - Insert Cup and Press Any Key.
3. Buy a Pentium 586/90 so you can reboot faster.
4. 2 + 2 = 5 for extremely large values of 2.
5. Computers make very fast, very accurate mistakes.
6. Computers are not intelligent. They only think they are.
7. My software never has bugs. It just develops random features.
8. C:\WINDOWS C:\WINDOWS\GO C:\PC\CRAWL
9. C:\DOS C:\DOS\RUN RUN\DOS\RUN
10. <--- The information went data way --->
11. Best file compression around: 'DEL *.*' = 100% compression.
12. The Definition of an Upgrade: Take old bugs out, put new ones in.
13. BREAKFAST.COM Halted...Cereal Port Not Responding.
14. The name is Baud, James Baud.
15. BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!
16. Access denied--nah nah na nah nah!
17. C:\> Bad command or file name! Go stand in the corner!
18. Bad command. Bad, bad command! Sit! Stay! Staaay..
19. Why doesn't DOS ever say 'EXCELLENT command or filename!'
20. As a computer, I find your faith in technology amusing.
21. Southern DOS: Y'all reckon? (Yep/Nope)
22. Backups? We don' NEED no steenking backups.
23. E Pluribus Modem
24. >... File not found. Should I fake it? (Y/N)
25. Ethernet (n): something used to catch the Etherbunny.
26. A mainframe: The biggest PC peripheral available.
27. An error? Impossible! My modem is error correcting.
28. CONGRESS.SYS Corrupted: Re-boot Washington D.C. (Y/N)?
29. Does fuzzy logic tickle?
30. A computer's attention span is as long as it's power cord.
31. 11th commandment-Thou shalt not covet thy neighbor's Pentium.
32. 24 hours in a day...24 beers in a case...coincidence?
33. Disinformation is not as good as datinformation.
34. Windows: Just another pane in the glass.
35. SENILE.COM found . . . Out Of Memory . . .
36. Who's General Failure & why is he reading my disk?
37. Ultimate office automation: networked coffee.
38. RAM disk is not an installation procedure.
39. Shell to DOS...Come in DOS, do you copy? Shell to DOS...
40. All computers wait at the same speed.
41. Computer: A device designed to speed and automate errors.
42. Go ahead, make my data!
43. Smash forehead on keyboard to continue.....
44. Enter any 11-digit prime number to continue...
45. ASCII stupid question, get a stupid ANSI!
46. E-mail returned to sender -- insufficient voltage.
47. Help! I'm modeming... and I can't hang up!!!
48. All wiyht. Rho sritched mg kegtops awound?
49. Error: Keyboard not attached. Press F1 to continue.
50. '640K ought to be enough for anybody.' - Bill Gates, 1981
51. DOS Tip #17: Add DEVICE=FNGRCROS.SYS to CONFIG.SYS
52. Hidden DOS secret: add BUGS=OFF to your CONFIG.SYS
53. Press any key to continue or any other key to quit...
54. Press any key...... no, No, NO!! Not THAT one!
55. Press -- to continue...

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 Golf program, often trying to abort Golf 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 shutdown for a while.

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 senses the presence of any other version of GirlFriend and communicates with it 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 in some obscure language that 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. And I've never liked how GirlFriend was totally 'object-oriented.'

A year ago, a friend of mine upgraded his version of GirlFriend to GirlFriendPlus 1.0, which is a Terminate and Stay Resident version of GirlFriend. He discovered that GirlFriendPlus 1.0 expires within a year if you don't upgrade to Fiancee 1.0. So he did, but soon after that, he had to upgrade 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. One of the primary reasons he decided to go with Wife 1.0 was because it came bundled with FreeSexPlus. Well, it turns out the resource allocation module of Wife 1.0 sometimes prohibits access to FreeSexPlus, particularly the new Plug-Ins he wanted to try. On top of that, Wife 1.0 must be running on a well warmed-up system before he can do anything. Although he did not ask for it, Wife 1.0 came with MotherInLaw, which has an automatic pop-up feature he can't turn off.

I told him to try installing Mistress 1.0, but he said he heard if you try to run it without first uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.0 won't install anyway because of insufficient resources.

There was once a young man who, in his youth, professed a desire to become a "great" writer.

When asked to define "great" he said "I want to write stuff that the whole world will read, stuff that people will react to on a truly emotional level, stuff that will make them scream, cry, wail, howl in pain, desperation, and anger!"

He now works for Microsoft writing error messages.

What if Data Ran Windows98?

WORF: Captain, there are three Romulan warships uncloaking dead ahead.
PICARD: On screen. [The main viewing screen changes to a pattern of horizontal lines, each only a single pixel wide.]
PICARD: Data, what's wrong here?
DATA: Captain, the main viewscreen does not have sufficient video memory to display an image of this size. May I suggest that you select a lower resolution?
PICARD: Make it so. [The screen blanks, and then an image appears, with big, blocky square pixels. Three objects appear in the center, which could be Romulan warbirds, but which actually look more like the aliens in Space Invaders.]
PICARD: Data, open a hailing channel to the Romulans.
DATA: Aye, sir. [Data picks up an hourglass from the floor beside him, turns it over, and places it on the console in front of him. He punches some buttons on the console and sits motionless for several seconds. A flash of light blossoms from one of the Romulan ships on the viewscreen.]
WORF: Incoming plasma torpedo, Captain!
PICARD: Shields up!
DATA: I'm sorry, Captain, but I am still attempting to complete your last instruction. I must ask you to wait until I have finished before you issue your next command.
PICARD: What on earth do you mean? Data, this is *important*! I want those shields up *right now.*
DATA: I'm sorry, Captain, but I am still attempting to complete your last instruction. I must ask you to wait until I have finished before you issue your next command.
LAFORGE: Allow me, captain. [to Data] Control-alt-delete, Data. [Data removes the hourglass from the console, and returns it to the floor.]
DATA: The Romulans are not responding to my hails. Press my nose to cancel and return to Windows. Pull my left ear to close this communications channel which is not responding. You will lose any information sent by the Romulans. [LaForge pulls Data's left ear.]
PICARD: Shields... [There is a tremendous explosion. The bridge shakes violently, and all the crew members are thrown to the floor. A shower of sparks erupts from Wesley Crusher's station at the helm, throwing Wesley back away from the console.]
PICARD: Up, Data!
DATA: Aye, sir.
RIKER: All decks, damage report!
WORF: Captain, Ensign Crusher is injured. He appears to be unconscious. [Data picks up the hourglass again, places it on his console, and punches some more buttons. He waits a few seconds, then puts the hourglass back on the floor.]
DATA: Shields are now up, captain.
PICARD: And not a moment too soon. Worf, lock all phasers on the lead Romulan ship.
WORF: Aye, sir. [He punches buttons on the weapons console.]
PICARD: Mr. Data, take the helm, and prepare for evasive action.
DATA: I am sorry, sir, but I do not have the proper device driver installed for that console.
PICARD: Well, damn it, install the right one.
DATA: Please insert Setup Implant #1 in my right nostril.
PICARD: Number One, where do we keep Data's setup implants?
RIKER: I left them with Geordi.
LAFORGE: What!!? I thought you still had them!
PICARD: Data, don't you have device drivers stored in your internal memory?
DATA: Not found, sir. Please insert Setup Implant #1 in my right nostril.
PICARD: Data, I don't *have* Setup Implant #1.
DATA: Not ready reading right nostril. Abort, Retry, Fail?
PICARD: Abort!
DATA: Not ready reading right nostril. Abort, Retry, Fail?
PICARD: Well, fail, then!
DATA: Current nose is no longer valid. [Data walks over to the helm, and presses several buttons. The ship lurches, the images of the Romulan warships suddenly shift to one side of the viewscreen, and a high-pitched whining noise is heard coming from somewhere else in the ship.]
LAFORGE: [alarmed] Data, what the hell are you doing?
PICARD: Number One, do we have a customer service number for Data?
RIKER: Yes sir, but last time I tried to call them, I got put on hold for two hours before I was able to talk to anyone. And that person wasn't knowledgeable about androids of Data's model. She specialized in industrial control robots. [Suddenly, the lights all go out, the viewscreen goes blank, and all the usual noise of fans, motors, and so on whines to a halt. After a few seconds, the red emergency lights come on. Data is standing by the console, absolutely motionless.]
PICARD: What's going on?
LAFORGE: [checking the helm console] Lieutenant Data has caused a General Protection Violation in the warp engine core.
PICARD: These androids look really sharp, but you can't really do anything with them. [The shimmer of the transporter effect appears, and six Romulans in full battle dress materialize on the bridge. A seventh figure, a Ferengi, appears moments later.]
FERENGI: [with a mercenary grin] Can I interest you in a Macintosh, Captain?