Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0).

Recently he upgraded Fiancee1.0 to Wife1.0, and it’s a memory hogger! It has taken all his space; and Wife1.0 must be running before he can do anything. Although he didn’t ask for them, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. These too slow down the system and cause a slow drain on the resources and well-being of the computer.

Some features I’d like to see in the upcoming GirlFriend4.0:

1. A “Don’t remind me again” button.

2. Minimize button.

3. Shutdown feature – An install shield feature so that Girlfriend4.0 can be completely uninstalled if so desired (so you don’t lose cache and other objects).

I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed; they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0, but it didn’t have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory.

Another thing that sucks–in all versions of Girlfriend that I’ve used is that it is totally “object orientated” and only supports hardware with gold plated contacts.

Bug warning
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

If you receive an e-mail with a subject line of “Badtimes,” delete it immediately WITHOUT reading it. This is the most dangerous Email virus yet.

It will re-write your hard drive. Not only that, but it will scramble any disks that are even close to your computer. It will recalibrate your refrigerator’s coolness setting so all your ice cream melts and milk curdles . It will demagnetize the strips on all your credit cards, reprogram your ATM access code, screw up the tracking on your VCR and use subspace field harmonics to scratch any CDs you try to play.

It will give your ex-boy/girlfriend your new phone number. It will mix antifreeze into your fish tank. It will drink all your beer and leave its dirty socks on the coffee table when there’s company coming over.

It will hide your car keys when you are late for work and interfere with your car radio so that you hear only static while stuck in traffic.

Badtimes will make you fall in love with a hardened pedophile. It will give you nightmares about circus midgets. It will replace your shampoo with Nair and your Nair with Rogaine, all while dating your current boy/girlfriend behind your back and billing their hotel rendezvous to your Visa card.

It will seduce your grandmother. It does not matter if she is dead, such is the power of Badtimes, it reaches out beyond the grave to sully those things we hold most dear.

Badtimes will give you Dutch Elm disease. It will leave the toilet seat up and leave the hairdryer plugged in dangerously close to a full bathtub. It will wantonly remove the forbidden tags from your mattresses and pillows, and refill your skim milk with whole. It is insidious and subtle. It is dangerous and terrifying to behold. It is also a rather interesting shade of mauve.

You get a tattoo that reads “This body best viewed with Netscape Navigator 3 or higher.”

You name your children Eudora, Mozilla and Dotcom.

You turn off your modem and get this awful empty feeling, like you just pulled the plug on a loved one.

You spend half of the plane trip with your laptop on your lap…and your child in the overhead compartment.

You decide to stay in college for an additional year or two, just for the free Internet access.

You laugh at people with 28,800 modems.

You start using smiley’s in your snail mail.

Your hard drive crashes.

You haven’t logged in for two hours. You start to twitch.

You pick up the phone and manually dial your ISP’s access number.

You try to hum to communicate with the modem. And you succeed.

Diskettes should be cleaned and waxed once a week. Microscopic metal particles may be removed by waving a powerful magnet over the surface of the disk. Any stubborn metal shavings can be removed with scouring powder and steel wool. When waxing a diskette, make sure the surface is even. This will allow the diskette to spin faster, resulting in better access time.

Do not fold diskettes unless they do not fit into the drive. “Big” Diskettes may be folded and used in “Little” drives.

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.

Diskettes cannot be backed up by running them through a photo copy machine. If your data is going to need to be backed up, simply insert TWO diskettes into your drive. Whenever you update a document, the data will be written onto both disks. A handy tip for more legible backup copies: Keep a container of iron filings at your desk. When you need to make two copies, sprinkle iron filings liberally between the diskettes before inserting them into the drive.

Diskettes should not be removed or inserted from the drive while the red light is on or 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 to access the slot.

If your diskette is full and needs more storage space, remove the disk from the drive and shake vigorously for two minutes. This will pack the data enough (data compression) to allow for more storage. Be sure to cover all openings with scotch tape to prevent loss of data.

Data access time may be greatly improved by cutting more holes in the diskette jacket. This will provide more simultaneous access points to the disk.

Periodically spray diskettes with insecticide to prevent system bugs from spreading.

TASK: Shoot yourself in the foot.

C: You shoot yourself in the foot.

C++: You accidentally create a dozen instances of yourself and shoot them all in the foot. Providing emergency medical assistance is impossible since you can’t tell which are bitwise copies and which are just pointing at others and saying, “That’s me, over there.”

FORTRAN: You shoot yourself in each toe, iteratively, until you run out of toes, then you read in the next foot and repeat. If you run out of bullets, you continue with the attempts to shoot yourself anyways because you have no exception-handling capability.

Pascal: The compiler won’t let you shoot yourself in the foot.

Ada: After correctly packing your foot, you attempt to concurrently load the gun, pull the trigger, scream, and shoot yourself in the foot. When you try, however, you discover you can’t because your foot is of the wrong type.

COBOL: Using a COLT 45 HANDGUN, AIM gun at LEG.FOOT, THEN place ARM.HAND.FINGER on HANDGUN.TRIGGER and SQUEEZE. THEN return HANDGUN to HOLSTER. CHECK whether shoelace needs to be re-tied.

LISP: You shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds the gun with which you shoot yourself in the appendage which holds…

FORTH: Foot in yourself shoot.

Prolog: You tell your program that you want to be shot in the foot. The program figures out how to do it, but the syntax doesn’t permit it to explain it to you.

BASIC: Shoot yourself in the foot with a water pistol. On large systems, continue until entire lower body is waterlogged.

Visual Basic: You’ll really only appear to have shot yourself in the foot, but you’ll have had so much fun doing it that you won’t care.

HyperTalk: Put the first bullet of gun into foot left of leg of you. Answer the result.

Motif: You spend days writing a UIL description of your foot, the bullet, its trajectory, and the intricate scrollwork on the ivory handles of the gun. When you finally get around to pulling the trigger, the gun jams.

APL: You shoot yourself in the foot, then spend all day figuring out how to do it in fewer characters.

SNOBOL: If you succeed, shoot yourself in the left foot. If you fail, shoot yourself in the right foot.

Unix:

% ls
foot.c foot.h foot.o toe.c toe.o
% rm * .o
rm:.o no such file or directory
% ls
%

Concurrent Euclid: You shoot yourself in somebody else’s foot.

370 JCL: You send your foot down to MIS and include a 400-page document explaining exactly how you want it to be shot. Three years later, your foot comes back deep-fried.

Paradox: Not only can you shoot yourself in the foot, your users can, too.

Access: You try to point the gun at your foot, but it shoots holes in all your Borland distribution diskettes instead.

Revelation: You’re sure you’re going to be able to shoot yourself in the foot, just as soon as you figure out what all these nifty little bullet-thingies are for.

Assembler: You try to shoot yourself in the foot, only to discover you must first invent the gun, the bullet, the trigger, and your foot.

Modula2: After realizing that you can’t actually accomplish anything in this language, you shoot yourself in the head.

2. Viruses don’t take up most of your hard drive.

3. Viruses don’t need 80 megs of RAM.

4. Viruses don’t have major bugs.

5. Viruses don’t have three different sets of documentation.

6. Viruses don’t leak info to the press about the upcoming Jerusalem 95, to keep people from switching to Michelangelo/2 Warp.

7. Viruses aren’t on every computer.

8. Nobody cares if a virus turns out to be 16 bit, even though it is advertised as 32…

9. Viruses install themselves !