Religious Tech Support

Ring ring…

God: Hello this is the religion help line, what is your disbelief?

Sinner: I seem to have lost my faith.

God: Was your faith installed by an ordained priest or a Catholic Minister?

Sinner: Ummm… lets see, I have a confirmation, so it must have been a priest.

God: And have you been doing your Faith updates with Weekly Services?

Sinner: Well, no, not all of them, but I did get the big upgrade at Christmas and Easter, and a few other Weekly Services here and there.

God: Have you recently heard any contrary Data that might have corrupted your faith?

Sinner: Not that I can think of…

God: Please remember that corrupting data can come in many forms, from Simple Lies *(Microsoft) or Street Rhetoric (Internet). Have your Ears downloaded anything that might be construed as corrupting?

Sinner: Well I did listen to a bum on the street that said that God was asleep and that anyone who believes was being lulled into the fires of hell.

God: What you have is a paradox, that is the problem with your faith, you see, somehow you have an INI string installed that does not let you Believe in God, but the output of this string is a Goto Hell. Without God there is no hell, thus the paradox.

Sinner: And how do I get this Paradox out of my system?

God: Please re-read the book that came with your faith, The Bible® and recall the passages that deal with heaven and hell, and look to the passages about Judas.ini. You can also find some help in the Psalms 100-120, but those are long and confusing and should only be used with a complete lack of Faith.

Sinner: And what can I do so that my Faith never becomes corrupted again?

God: Well there are several products out there just for that purpose, Lotus Devout®, Microsoft Seminary Plus®, and Google Hereafter Browser®. If you use these products and not download data from know corrupting sources, you should be fine.

Sinner: Well thank you very much God, This should help out a lot, I should be believing in you without a doubt in no time.

God: Go in Peace® my son.

Ring ring…

God: Hello this is the religion help line, what is your disbelief?

Sinner: Hello, I am now Jewish…


One of my friends works in the customer service call center of a national pager company. He deals with the usual complaints about poor pager operation, as well as the occasional crank caller demanding to be paged less often, more often, or by more interesting people.

The best call came from a man who repeatedly complained that he was being paged by “Lucille.” He was instructed that he would have to call her and tell her to stop paging him. “She never leaves a number, so I can’t call her back,” he said. After three such calls, someone thought to ask how he knew it was Lucille if she didn’t leave a number. “She leaves her name,” was the reply. After establishing that the customer had a numeric-only
pager, the light bulb came on. “How does she spell her name?” the service rep asked.

“L-O-W C-E-L-L”

General Motors HelpLine

General Motors doesn’t have a help line for people who don’t know how to drive, because people don’t buy cars like they buy computers, but imagine if they did….

  • HelpLine: “General Motors HelpLine, how can I help you?”
    Customer: “I got in my car and closed the door and nothing happened!”
    HelpLine: “Did you put the key in the ignition slot and turn it?”
    Customer: “What’s an ignition?”
    HelpLine: “It’s a starter motor that draws current from your battery and turns over the engine.”
    Customer: “Ignition? Motor? Battery? Engine? How come I have to know all these technical terms just to use my car?”

  • HelpLine: “General Motors HelpLine, how can I help you?”
    Customer: “My car ran fine for a week and now it won’t go anywhere!”
    HelpLine: “Is the gas tank empty?”
    Customer: “Huh? How do I know?”
    HelpLine: “There’s a little gauge on the front panel with a needle and markings from ‘E’ to ‘F’. Where is the needle pointing?”
    Customer: “It’s pointing to ‘E’. What does that mean?”
    HelpLine: “It means you have to visit a gasoline vendor and purchase some more gasoline. You can install it yourself or pay the vendor to install it for you.”
    Customer: “What? I paid $12,000 for this car! Now you tell me that I have to keep buying more components? I want a car that comes with everything built in!”

  • HelpLine: “General Motors HelpLine, how can I help you?”
    Customer: “Your cars suck!”
    HelpLine: “What’s wrong?”
    Customer: “It crashed, that’s what wrong!”
    HelpLine: “What were you doing?”
    Customer: “I wanted to run faster, so I pushed the accelerator pedal all the way to the floor. It
    worked for a while and then it crashed and it won’t start now!
    HelpLine: “It’s your responsibility if you misuse the product. What do you expect us to do about it?”
    Customer: “I want you to send me one of the latest version that doesn’t crash any more!”

  • HelpLine: “General Motors HelpLine, how can I help you?”
    Customer: “Hi, I just bought my first car, and I chose your car because it has automatic transmission, cruise control, power steering, power brakes, and power door locks.”
    HelpLine: “Thanks for buying our car. How can I help you?”
    Customer: “How do I work it?”
    HelpLine: “Do you know how to drive?”
    Customer: “Do I know how to what?”
    HelpLine: “Do you know how to drive?”
    Customer: “I’m not a technical person. I just want to go places in my car!”

Leave It To Microsoft

From an ex-field sales/support survivor:

I used to work in a computer store and one day we had a gentleman call in with a smoking power supply. The service rep was having a bit of trouble convincing this guy that he had a hardware problem.

Service Rep: Sir, something has burned within your power supply.

Customer: I bet that there is some command that I can put into the AUTOEXEC.BAT that will take care of this.

Service Rep: There is nothing that software can do to help you with this problem.

Customer: I know that there is something that I can put in… some command… maybe it should go into the CONFIG.SYS.

[After a few minutes of going round and round]

Service Rep: Okay, I am not supposed to tell anyone this but there is a hidden command in some versions of DOS that you can use. I want you to edit your AUTOEXEC.BAT and add the last line as C:DOSNOSMOKE and reboot your computer.

[Customer does this]

Customer: It is still smoking.

Service Rep: I guess you’ll need to call Microsoft and ask them for a patch for the NOSMOKE.EXE.

[The customer then hung up. We thought that we had heard the last of this guy but NO… he calls back four hours later]

Service Rep: Hello Sir, how is your computer?

Customer: I called Microsoft and they said that my power supply is incompatible with their NOSMOKE.EXE and that I need to get a new one. I was wondering when I can have that done and how much it will cost.

If Restaurants Functioned Like Microsoft…

Patron: Waiter!
Waiter: Hi, my name is Bill, and I’ll be your Support.
Waiter. What seems to be the problem?

Patron: There’s a fly in my soup!
Waiter: Try again, maybe the fly won’t be there this time.
Patron: No, it’s still there.
Waiter: Maybe it’s the way you’re using the soup. Try eating it with a fork instead.
Patron: Even when I use the fork, the fly is still there.

Waiter: Maybe the soup is incompatible with the bowl. What kind of bowl are you using?
Patron: A SOUP bowl!

Waiter: Hmmm, that should work. Maybe it’s a configuration problem. How was the bowl set up?
Patron: You brought it to me on a saucer. What has that to do with the fly in my soup?!

Waiter: Can you remember everything you did before you noticed the fly in your soup?
Patron: I sat down and ordered the Soup of the Day!

Waiter: Have you considered upgrading to the latest Soup of the Day?
Patron: You have more than one Soup of the Day each day??
Waiter: Yes, the Soup of the Day is changed every hour.
Patron: Well, what is the Soup of the Day now?
Waiter: The current Soup of the Day is tomato.
Patron: Fine. Bring me the tomato soup, and the check. I’m running late now.

[waiter leaves and returns with another bowl of soup and the check]

Waiter: Here you are, Sir. The soup and your check.
Patron: This is potato soup.
Waiter: Yes, the tomato soup wasn’t ready yet.
Patron: Well, I’m so hungry now, I’ll eat anything.

[waiter leaves.]

Patron: Waiter! There’s a gnat in my soup!

The check:

Soup of the Day . . . . . . . . . . . . . . . . . $5.00
Upgrade to newer Soup of the Day . . $2.50
Access to support . . . . . . . . . . . . . . . . $1.00

Dear Tech Support

Dear Tech Support,

Last year I upgraded from Girlfriend 7.0 to Wife 1.0. I soon noticed that the new program began unexpected child processing that took up a lot of space and valuable resources. No mention of this was included with the product information.

In addition, Wife 1.0 installed itself into all other programs and now launches during system initialization, where it monitors all other system activity. Applications such as Poker Night 10.3, Drunken Boys Night 2.5, Football 5.0, Hunting and Fishing 7.5 and Racing 3.6 no longer run, crashing the system whenever selected.

I can’t seem to keep Wife 1.0 in the background while attempting to run my favorite applications. I’m thinking about going back to Girlfriend 7.0, but the Uninstall doesn’t work on Wife 1.0. Please help!


A Troubled User

Dear Troubled User,

This is a very common problem. Many people upgrade from Girlfriend 7.0 to Wife 1.0 thinking that it is merely an Utilities and Entertainment program. Wife 1.0 is an OPERATING SYSTEM and is designed by its creator to run everything! It is also impossible to delete Wife 1.0 and return to Girlfriend 7.0. Hidden operating system files cause Girlfriend 7.0 to emulate Wife 1.0 so nothing is gained.

It is impossible to uninstall, delete, or purge the program files from the system once installed. You cannot go back to Girlfriend 7.0 because Wife 1.0 is designed to not allow this. Some have tried to install Girlfriend 8.0 or Wife 2.0 but end up with more problems than in the original system. Look in your Wife 1.0 manual under “Warnings: Maintenance/Child Support”.

I recommend that you keep Wife 1.0. I suggest installing the background application program Yes_Dear to alleviate software augmentation. Having installed Wife 1.0 myself, I also suggest that you read the entire section regarding “General Partnership Faults (GPFs)”.

You must assume all responsibility for any faults and problems that occur, regardless of their cause. You will also find that GPFs tend to be somewhat cyclical, occurring approximately 28 days apart. The best course of action is to enter the command C:APOLOGIZE. Avoid excessive use of C:YES_DEAR because ultimately you will have to use the APOLOGIZE command before the system will return to normal anyway.

Remember, the system will run smoothly as long as you take the blame for all GPFs. Wife 1.0 is a great program, but tends to require very high maintenance. Wife 1.0 comes with several support programs such as Clean_and_Sweep 3.0, Cook_It 1.5 (which replaces Burn_It 1.0) and Do_Bills 4.2. You must however be very careful how you use these programs. Improper use will cause the system to launch the program Nag_Nag 9.5. Once this happens, the only way to improve the performance of Wife 1.0 is to purchase additional software. I recommend Flowers 2.1 and Diamonds 5.0 should this happen.

Best of luck,
Tech Support

Can You Help Me?

Actual dialog of a WordPerfect Customer Support employee:

“Ridge Hall computer assistant; may I help you?”
“Yes, well, I’m having trouble with WordPerfect.”
“What sort of trouble?”
“Well, I was just typing along, and all of a sudden the words went away.”
“Went away?”
“They disappeared.”
“Hmm. So what does your screen look like now?”
“It’s blank; it won’t accept anything when I type.”
“Are you still in WordPerfect, or did you get out?”
“How do I tell?”
“Can you see the C: prompt on the screen?”
“What’s a sea-prompt?”
“Never mind. Can you move the cursor around on the screen?”
“There isn’t any cursor: I told you, it won’t accept anything I type.”
“Does your monitor have a power indicator?”
“What’s a monitor?”
“It’s the thing with the screen on it that looks like a TV. Does it have a little light that tells you when it’s on?”
“I don’t know.”
“Well, then look on the back of the monitor and find where the power cord goes into it. Can you see that?”
….”Yes, I think so.”
“Great! Follow the cord to the plug, and tell me if it’s plugged into the wall.”
…….”Yes, it is.”
“When you were behind the monitor, did you notice that there were two cables plugged into the back of it, not just one?”
“Well, there are. I need you to look back there again and find the other cable.”
…….”Okay, here it is.”
“Follow it for me, and tell me if it’s plugged securely into the back of your computer.”
“I can’t reach.”
“Uh huh. Well, can you see if it is?”
“Even if you maybe put your knee on something and lean way over?”
“Oh, it’s not because I don’t have the right angle-it’s because it’s dark.”
“Yes-the office light is off, and the only light I have is coming in from the window.”
“Well, turn on the office light then.”
“I can’t.”
“No? Why not?”
“Because there’s a power outage.”
“A power… A power outage? Aha! Okay, we’ve got it licked now. Do you still have the boxes and manuals and packing stuff your computer came in?”
“Well, yes, I keep them in the closet.”
“Good! Go get them, and unplug your system and pack it up just like it was when you got it. Then take it back to the store you bought it from.”
“Really? Is it that bad?”
“Yes, I’m afraid it is.”
“Well, all right then, I suppose. What do I tell them?”
“Tell them you’re not ready to own a computer.”

5 Things You Don’t Want to Hear from Tech Support

  1. “Duuuuuude! Bummer!”
  2. “In layman’s terms, we call that the Hindenburg Effect.”
  3. “Your problem can be fixed, but you’re going to need a butter knife, a roll of duct tape and a car battery.”
  4. “Press 1 for Support.
    Press 2 if you’re with ‘60 minutes.’
    Press 3 if you’re with the FTC.”
  5. “Hold on a second, please … Mom! Timmy’s hitting me!”

Tech Support Diary

A Week in the Life of the Notes Support Person from Hell

User called to say they forgot password. Told them to use password retrieval utility called FDISK. Blissfully ignorant, they thank me and hang up. God, we let the people vote and drive, too?

Accounting called to say they couldn’t access expense reports database. Gave them Standard Sys Admin Answer #112, “Well, it works for me.” Let them rant and rave while I unplugged my coffeemaker from the UPS and plugged their server back in. Suggested they try it again. One more happy customer…

8:14 am
User from 8:05 call said they received error message “Error accessing Drive 0.” Told them it was an OS problem. Transferred them to microsupport.

11:00 am
Relatively quiet for last few hours. Decide to plug support phone back in so I can call my girlfriend. Says parents are coming into town this weekend. Put her on hold and transferred her to janitorial closet down in basement. What is she thinking? The “Myst” and “Doom” nationals are
this weekend!

11:34 am
Another user calls (do they ever learn?). Says they want ACL changed on HR performance review database so that nobody but HR can access database. Tell them no problem. Hang up. Change ACL. Add @MailSend so performance reviews are sent to */US.

12:00 pm

3:30 pm
Return from lunch.

3:55 pm
Wake up from nap. Bad dream makes me cranky. Bounce servers for no reason. Return to napping.

4:23 pm
Yet another user calls. Wants to know how to change fonts on form. Ask them what chip set they’re using. Tell them to call back when they find out.

4:55 pm
Decide to run “Create Save/Replication Conflicts” macro so next shift has something to do.

8:30 am
Finish reading support log from last night. Sounded busy. Terrible time with Save/Replication conflicts.

9:00 am
Support manager arrives. Wants to discuss my attitude. Click on PhoneNotes SmartIcon. “Love to, but kinda busy. Put something in the calendar database!” I yell as I grab for the support lines, which have (mysteriously) lit up. Walks away grumbling.

9:35 pm
Team leader from R&D needs ID for new employee. Tell them they need form J-19R=9C9\DARRK1. Say they never heard of such a form. Tell them it’s in the SPECIAL FORMS database. Say they never heard of such a database. Transfer them to janitorial closet in basement.

10:00 am
Perky sounding intern from R&D calls and says she needs new ID. Tell her I need employee number, department name, manager name, and marital status. Run @DbLookup against state parole board database, Centers for Disease Control database, and my Oprah Winfrey database. No hits. Tell her ID will be ready tonight. Drawing from the lessons learned in last week’s “Reengineering for Customer Partnership,” I offer to personally deliver ID to her apartment.

10:07 am
Janitor stops by to say he keeps getting strange calls in basement. Offer to train him on Notes. Begin now. Let him watch console while I grab a smoke.

1:00 pm
Return from smoking break. Janitor says phones kept ringing, so he transferred them to cafeteria lady. I like this guy.

1:05 pm
Big commotion! Support manager falls in hole left where I pulled floor tiles outside his office door. Stress to him importance of not running in computer room, even if I do yell “Omigod — Fire!”

1:15 pm
Development Standards Committee calls and complains about umlauts in form names. Apologizing for the inconvenience, I tell them I will fix it. Hang up and run global search/replace using gaks.

1:20 pm
Mary Hairnet from cafeteria calls. Says she keeps getting calls for “Notice Loads” or “NoLoad Goats,” she’s not sure, couldn’t here over industrial-grade blender. Tell her it was probably “Lettuce Nodes.” Maybe the food distributor with a new product? She thinks about it and hangs up.

2:00 pm
Legal secretary calls and says she lost password. Ask her to check in her purse, floor of car, and on bathroom counter. Tell her it probably fell out of back of machine. Suggest she put duct tape over all the airvents she can find on the PC. Grudgingly offer to create new ID for her while she does that.

2:49 pm
Janitor comes back. Wants more lessons. I take off rest of day.

8:30 am
Irate user calls to say chipset has nothing to do with fonts on form. Tell them Of course, they should have been checking “Bitset,” not “chipset.” Sheepish user apologizes and hangs up.

Support manager, with foot in cast, returns to office. Schedules 10:00am meeting with me. User calls and wants to talk to support manager about terrible help at support desk. Tell them manager about to go into meeting. Sometimes life hands you material…

10:00 am
Call Louie in janitorial services to cover for me. Go to support manager’s office. He says he can’t dismiss me but can suggest several lateral career moves. Most involve farm implements in third-world countries with moderate to heavy political turmoil. By and by, I ask if he’s aware of new bug which takes full-text indexed random e-mail databases and puts all references to furry handcuffs and Bambi Boomer in Marketing on the corporate Web page. Meeting is adjourned as he reaches for keyboard, Web browser, and Tums.

10:30 am
Tell Louie he’s doing great job. Offer to show him mainframe corporate PBX system sometime.

11:00 am

4:55 pm
Return from lunch.

5:00 pm
Shift change; Going home.

8:00 am
New guy (“Marvin”) started today. “Nice plaids” I offer. Show him server room, wiring closet, and technical library. Set him up with IBM PC-XT. Tell him to quit whining, Notes runs the same in both monochrome and color.

8:45 am
New guy’s PC finishes booting up. Tell him I’ll create new ID for him. Set minimum password length to 64. Go grab smoke.

9:30 am
Introduce Louie the custodian to Marvin. “Nice plaids” Louie comments. Is this guy great or what?!

11:00 am
Beat Louie in dominos game. Louie leaves. Fish spare dominos out of sleeves (“Always have backups”). User calls, says Accounting server is down. Untie Ethernet cable from radio antenna (better reception) and plug back into hub. Tell user to try again. Another happy customer!

11:55 am
Brief Marvin on Corporate Policy 98.022.01:

“Whereas all new employee beginning on days ending in ‘Y’ shall enjoy all proper aspects with said corporation, said employee is obligated to provide sustenance and relief to senior technical analyst on shift.”

Marvin doubts. I point to “Corporate Policy” database (a fine piece of work, if I say so myself!). “Remember, that’s DOUBLE pepperoni and NO peppers!” I yell to Marvin as he steps over open floor tile to get to exit door.

1:00 pm
Oooooh! Pizza makes me so sleepy…

4:30 pm
Wake from refreshing nap. Catch Marvin scanning want ads.

5:00 pm
Shift change. Flick HR’s server off and on several times (just testing the On/Off button…). See ya tomorrow.

8:00 am
Night shift still trying to replace power supply in HR server. Told them it worked fine before I left.

9:00 am
Marvin still not here. Decide I might start answering these calls myself. Unforward phones from Mailroom.

9:02 am
Yep. A user call. Users in Des Moines can’t replicate. Me and the Oiuji board determine it’s sunspots. Tell them to call Telecommunications.

9:30 am
Good God, another user! They’re like ants. Says he’s in San Diego and can’t replicate with Des Moines. Tell him it’s sunspots, but with a two-hour difference. Suggest he reset the time on the server back two hours.

10:17 am
Pensacola calls. Says they can’t route mail to San Diego. Tell them to set server ahead three hours.

11:00 am
E-mail from corporate says for everybody to quit resetting the time on their servers. I change the date stamp and forward it to Milwaukee.

11:20 am
Finish @CoffeeMake macro. Put phone back on hook.

11:23 am
Milwaukee calls, asks what day it is.

11:25 am
Support manager stops by to say Marvin called in to quit. “So hard to get good help…” I respond. Support manager says he has appointment with orthopedic doctor this afternoon, and asks if I mind sitting in on the weekly department head meeting for him. “No problem!”

11:30 am
Call Louie and tell him opportunity knocks and he’s invited to a meeting this afternoon. “Yeah, sure. You can bring your snuff” I tell him.

12:00 am

1:00 pm
Start full backups on UNIX server. Route them to device NULL to make them fast.

1:03 pm
Full weekly backups done. Man, I love modern technology!

2:30 pm
Look in support manager’s contact management database. Cancel 2:45pm appointment for him. He really should be at home resting, you know.

2:39 pm
New user calls. Says want to learn how to create a connection document. Tell them to run connection document utility CTRL-ALT-DEL. Says PC rebooted. Tell them to call microsupport.

2:50 pm
Support manager calls to say mixup at doctor’s office means appointment cancelled. Says he’s just going to go on home. Ask him if he’s seen corporate Web page lately.

3:00 pm
Another (novice) user calls. Says periodic macro not working. Suggest they place @DeleteDocument at end of formula. Promise to send them document addendum which says so.

4:00 pm
Finish changing foreground color in all documents to white. Also set point size to “2” in help databases.

4:30 pm
User calls to say they can’t see anything in documents. Tell them to go to view, do a “Edit — Select All”, hit delete key, and then refresh. Promise to send them document addendum which says so.

4:45 pm
Another user calls. Says they can’t read help documents. Tell them I’ll fix it. Hang up. Change font to Wingdings.

4:58 pm
Plug coffee maker into Ethernet hub to see what happens. Not (too) much.

5:00 pm
Night shift shows up. Tell that the hub is acting funny and to have a good weekend.

Shift Keys FAQ

  • Q. My shift keys have little arrows on them. Does that mean the *real* shift keys are located above them, and these keys are just little signs to point them out?

    A. Nope, they’re the Real McCoy. The little arrows mean “up”, as in “look up at the screen”. Your keyboard is telling you to learn to touch type and quit staring at your fingers.

  • Q. What happens if I press both shift keys?

    A. Even bigger letters may show up on your screen. You should not use this feature, however, because these letters are also brighter, and may cause Screen Burn-In, which would be particularly embarrassing if you were typing something naughty at the time. You might consider obtaining the author’s Shift Key Burn-In Protector program for only $139.95. Or you might not, it’s your computer, but don’t say I didn’t warn you.

  • Q. my religion prohibits the use of shift keys. how can i type capital letters and punctuation

    A. Discuss alternatives to the shift key with your spiritual advisor. Perhaps your deity would not be angered by repeated use of the Caps Lock key, or maybe you can retain a consultant to depress the shift for you.

    You might also consider replacing punctuation marks that require the use of shift keys with lower case expressions; replace ? with “huh” and ! with “zowie”.


    A. Do small children with a fondness for peanut butter use your keyboard frequently? If so, you may want to clean it off for more reliable operation. First, disconnect your keyboard by gripping each of its ends firmly and pulling as hard as you can. Next, immerse the keyboard in warm water and scrub thoroughly with your favorite lemon-scented detergent and lots of steel wool. Finally, you need to dry the keyboard. Either dry it to touch with a handheld blowdryer, or place it in the dryer for not less than 60 minutes. Be sure to clean the lint screen when you are finished.

  • Q. Why are there are no “shift” keys on my keyboard, but there are two keys labelled “hif”?

    A. Again, you may want to consider cleaning your keyboard, and washing your hands more frequently for that matter.

  • Q. Are there shift keys on my Macintosh?

    A. Yes, although instead of the notation “shift”, the key may be labelled with an excited Mac face, something like :O . Press this key to use shift, and be thankful you’re using a friendly Mac instead of a mean old PC with all them confusin’ words ‘n stuff on it.

  • Q. I’m sick of pushing the shift key every single time I want big letters. Is there any other way to do this?

    A. This is the Modern Age of Convenience, and you may be able to activate the shift key merely with the power of your voice! Check to see whether your computer is equipped with speech-recognition equipment by saying the word “shift” very clearly and slowly into its speaker. Then watch the keyboard closely to see if the Shift key moves down. Note that you may have to repeat this action several times to “train” the computer to recognise your voice before the feature works reliably.

  • Q. There are two shift keys, which should I use?

    A. Avoid unnecessary wear on either shift key by alternating between the two. Keep track of your usage of each key so that you press them in equal amounts. Your keyboard may be equipped with a small notepad; you should use this to make little tally marks in two columns for each time you shift. Remember, it’s better to go to a little trouble than wind up with a broken shift key.

  • Q. Why are the shift keys bigger than the other keys?

    A. They aren’t. This is simply an optical illusion. Just as the moon appears much larger when it is close to the horizon, your shift keys look larger because of their proximity to other keys. To verify this, go out in a large field at night with your keyboard, place it in an upright position, and view it from a distance of 200 yards. Sure enough, the keys all look the same size!

  • Q. If I press the shift key at the wrong time, or too many times, will my computer explode?

    A. No. Well, generally no. Not unless you are using a NEC laptop. Or vt100 terminal emulation. But even then, hardly ever. Really, don’t worry about it. Forget I mentioned it. Just type softly. Move along, next question.

  • Q. No matter what I do, the shift key just doesn’t seem to work. What’s wrong?

    A. Have you ever considered that the problem may not be your keyboard, the problem may be YOU? Perhaps God Himself has suspended the operation of these keys to send you a Message that you have strayed from the path of righteousness. Use this as an opportunity to reflect on your life. Before rushing blindly ahead with a lot of shifting, consult the spiritual advisor of your choice for help in dealing with any unresolved issues in your relationship with the Almighty.