Tales of tech support tomfoolery

Back when I worked for a hosting company, we were moving between data center buildings. They were doing this via box truck, and there were about 4,000 servers to move. So, it was more than one evening of work. One of the nights we were in the middle of the transfer but weren’t actively moving servers, the CTO bravely volunteered to be the overnight NOC tech at the new location. I was the overnight sysadmin+NOC tech at the old location, and if she had any problems, she knew to call me.

So, around 2AM she called to tell me that one of our more important customer’s servers was down, and she couldn’t figure out why. She’d known enough to connect a crash cart ( portable monitor, keyboard and mouse) to the machine, but couldn’t get any response from it. I asked if she could get response from the num lock key, and she replied that she couldn’t.

“Is it powered on?” I asked. A moment later, she answered “Nope”. She pressed the power button, the server came up, and it was good for the next two days. That night it did the same thing, but I was on shift at that location. I diagnosed that the power supply was failing and replaced it.


When I was working dial-up support around the release of Windows 98, the provider I supported didn’t yet support Windows 98. It generally worked, but we weren’t allowed to support it. Everyone on the floor had gotten more than one call from a customer asking us to support their Windows 98 problem, and the customers generally took it gracefully.

I had a friend who got a call where the person on the other end opened the call with “Look, I have a Windows 98 system, and I know you don’t support Windows 98, but we know it’s still the same system. Can we pretend?”

My friend responded. “Yes, we can pretend. Can you go ahead and click on the apple in the upper left hand corner and click on ‘About this Macintosh’?”

“What? Wait, this isn’t an Apple machine, this is a Windows machine!”

“Yes, I understand that, but let’s pretend.”

“Oh. I understand. Thank you.”


I don’t remember the exact details, but my wife was attempting to help a fellow graphic designer with a bizarre display issue on her Mac. After walking over to watch her co-worker reproduce the problem, she observed that her co-worker’s boob was mashing the Apple command key. Repositioning the keyboard resolved the issue.

We got a call about weird display issues on a CRT monitor, images waving about and all sorts. As soon as I arrive there I see a negative ion generator pointed straight at the monitor, apparently the user thought it would negate some sort of bad vibes coming from the screen. No, dear user, it was causing them!

I loved that blog!

I’ve never worked in tech support, but for a period of time years ago among a certain selection of people, I was the guy who knew more about computers than the average person (and therefore a “computer whiz” [rolls eyes]). A friend of a friend, catching a whiff of this, asked me to help him with some computer stuff. Eh, okay. I don’t mind. And I was able to get him fixed up.

He called me a few more times, once when he was all worked up into a dither because he had found a file named VIRUS. I was immediately doubtful that it was anything harmful, because who would design a virus that operates by leaving a file on the mark’s computer called VIRUS? A couple of questions, and it came down to this: He was an aspiring fiction writer. (I saw some of his work; think of Tommy Wiseau trying to imitate Lovecraft.) This questionable file was a short story he had written about a virus doing some kind of catastrophic thing. He had forgotten about it.

As a side note, I eventually got tired of his calls. “You know,” I told him, “if you’d put some effort into learning this stuff, you could take care of it yourself.” His answer was “Why should I learn it when I can call you?” Well, I had let all that support stuff go on far too long already; sometimes I’m just too damn nice for my own good. But that was when I cut him off.

Heh, I’ve dealt with plenty of PEBKAC issues in my time, but that one’s a doozy.

That’s a funny story that I understand doesn’t actually have to do with computer viruses, but speaking of, I have a couple computer virus stories. When I was first made sysadmin at a company in 2000, it was a newly created position that previously had been handled part-time by the Accounting manager, who was, to say the least, not well equipped for the task. The desktop computers had spotty, if any, virus protection at first, before I worked to install antivirus software on every computer and educated users on practices to avoid viruses. But before that, there were viruses. Fortunately, back in the early 2000s the viruses were less ‘Russian hackers trying to steal your identity and life savings’ and more ‘teenage hackers in their parents’ basement writing viruses for fun’.

One time a salesman called me with a computer problem. Turned out that he had picked up a virus that seemed mostly harmless except, whenever you tried to click on a shortcut icon on the desktop, it would move away from the cursor. Kind of amusing, actually.

Another time a woman in Accounting called me in a panic. I observed that she had a virus that had triggered hundreds of overlapping pop-up windows advertising porn and gambling sites, completely covering the screen. She said “I swear to God, I didn’t do anything to cause this!” I knew it wasn’t her. She had recently received a hand-me-down computer from this guy, who had gotten himself a new computer:

Yeah that tracks, I’m thankful every day to no longer have to do that.

Here’s an email I woke up to. Not a particularly funny story, just aggravating.

To: echoreply
From: luser
Subject: Re: Patterson file access

How do I get the Patterson files?

To: everyone
From: echoreply
Subject: Patterson file access

The Patterson files are at the following website
https://example.com/patterson

An email asking me where to find some files that was sent in reply to, and quoted, an email explaining where to find those files.

Before getting snarky on the user, let’s make sure there aren’t any problems. Can I find the files at the website, are the files correct, are there any issues with access from the user’s location? Nope, that is all fine. Does the user not know how to click on a link in an email, do they not know how to download the files, do they not know what to do with them once they’re downloaded? Could be any of that, but I can’t tell if those are the questions they’re asking.

After wasting 15 minutes making sure everything on my end is correct, I send this in response:

To: luser
From: echoreply
Subject Re: Patterson file access

The Patterson files are available at the website in the email quoted below. Let me know if you’re having any trouble with them.

To: echoreply
From: luser
Subject: Re: Patterson file access

How do I get the Patterson files?

To: everyone
From: echoreply
Subject: Patterson file access

The Patterson files are at the following website
https://example.com/patterson

A couple decades ago I worked for a small humane society that also ran the municipal animal control department, and by default I fell into the role of technical instructor. Skills…varied widely.

My favorite was the brand-new animal control dispatch operator, responsible for initial input of cases into our database. This was in 2003 or so, and she wasn’t exactly a tech wiz. I asked her if she’d used a computer before. She said she had, but on prying I found out she meant she’d used a cash register.

I kept simplifying and simplifying my instructions, until I realized she’d never used a computer mouse. So I taught her to do that. She moved the mouse agonizingly slowly, and as she moved it let out a tense gutteral groan, as if she were constipated and straining. Every time.

I was so, so glad to complete her training.

Back in the early 90s I ran a company where we did inbound customer service as a B2B service. Customers called in and we took their orders, created customer accounts, answered basic questions like “When will I get my [whatever]?”. Our IT setup was state of the art for small biz at the time: The workers each had a 386sx PC running MS/DOS and connected to a Novell Netware server. Woot! :zany_face:

Most of our workers hadn’t used a computer before either. And yes, many had only been cashiers or waitresses before. Whole lotta ground to cover. At least we didn’t have mice.

Most took to it OK, given the amount of handholding the software did for them. But we hired a few that proved simply untrainable even to that limited level and were duly sent on their way.

When we first converted to PCs from mainframe TSO terminals, my cubie mate had never used a mouse before. She was smart, but had a lot of trouble mastering the double-click. Either too slow or too fast. I remember it taking weeks for her to consistently be able to double-click successfully. Very weird.

Similar to the mouse issue, but a decade or two newer. I have people that can’t operate touch screens. I can see they’re doing it wrong, but I’m not entirely sure how to fix the behavior.

Tap it; don’t stab it. What I’m doing is tapping and what you’re doing is stabbing. See how I can always interact with the icons on the phone, and you don’t? No, I don’t mean hit it harder; that’s exactly the opposite of what I mean!

I ran into someone like that too back in the day.

A gotcha with doubleclick is that even if you do the two clicks at the correct pace, you can’t move the mouse more than a couple pixels between the clicks. Or else the OS will treat it as 2 single clicks near one another.

My person could not single-click without the mouse moving 1/8" in some random direction. Doubleclick? Fugeddaboudit.

Took me quite awhile to notice what they were doing.

Some employers complained about people wasting time playing Solitaire in Microsoft Windows but it was really useful for learning mouse skills.

I had a teachable moment in my calculus class today, and I hope it took hold with the students. I was showing the students how to do a particular problem on the online homework, typed in the answer, and hit Enter… and it didn’t give credit for it. OK, always a bit embarrassing when that happens to the teacher… but I read the popup, and it didn’t say “that’s wrong”. It said “Your answer has the correct value, but it’s formatted incorrectly”. I pointed it out to my students, and told them that often error messages contained useful information, so always take a look at them before just reflexively clicking on the X: In this case, the note I had overlooked to enter the answers as a fraction, not a decimal.

When I first started at the bank from which I eventually retired, one of my first jobs was to install computers which replaced the dumb greenscreen mainframe terminals. The computers ran Windows 3.1, and we purposely left Solitaire on the machines for the very reason you suggest.

The computers had no hard drives; they booted from a floppy and loaded a Netware client. After login, the PC loaded Win3.1 from the Novell server to which the user attached. There was essentially one copy of Windows on each server, which all users loaded into RAM. When it was determined that solitaire was no longer needed, I used a software utility called ‘Winbatch’ to create a small program which popped up a message that essentially said ‘Get Back To Work!’. I named the program sol.exe and replaced the sol.exe within Windows 3.1 on all the Netware servers.

One of the first people to use my new program was, of course, the owner of the bank. When he encountered the message, he called my boss and congratulated him on a clever idea. My boss told him that I was the author of the program, which earned me a small bit of esteem.

It’s been eons, but IIRC there was a way to dispense w the floppy, where the network card could in effect act as a Bios-level conduit to a boot image on the Netware server. (Very) thin clients FTW.

Now we use handheld uber supercomputers as thin clients. Progress!

We never progressed that far! The next round of PCs that we installed had their very own internal hard drives.

Turns out I was half right.

There wasn’t a way to do that with Netware which in that era required IPX as a networking protocol. But once TCP / IP came in, there was Bootstrap Protocol - Wikipedia AKA BOOTP which would let a DOS or *nix box with a suitable network card load a boot image from a suitable server. Netware eventually embraced TCP/IP, but long after their fate was sealed.

As to hard drives in general, from when I started in the mid 1970s on mainframes the then-current fad has gone back and forth and back and forth on clients with or without local storage. If the clients have no hard drives or floppy drives or RS-232 ports or USB ports, it was real hard for the workers to steal data. Or to have mission critical stuff stored only on their workstation with no backups.

Seems like nowadays the flavor du jour is cloud storage primary and local storage is essentially just a teeny weeny multi hundred GB :zany_face: cache for performance reasons.

Yep, I built a menu based install system for servers using PXE boot at a previous job. It was pretty great, you didn’t even have to take the server out of the rack, just plug a cable into the port configured for the PXE boot VLAN and reboot it. Through the miracle of IPMI, the NOC tech could reinstall the system right from their desk, other than swapping the cable back and forth. The techs who were knowledgeable enough to configure a switch port with a VLAN didn’t even need to monkey with the cables.

Why do businesses feel the need to do that kind of thing? let people unwind with a bit of solitaire between tasks for Eru’s sake.