Overload: A one-way ticket to a madman's situation

In which our hero does some accidental load testing

Who, Me? Take your mind off Monday with a look back nearly 30 years to the era of OS/2 and chips ending in "DX". It's The Register's weekly delve into the Who, Me? mailbag.

This week's confession comes from "Jon" and takes us back to around 1992, just as the Windows juggernaut of Microsoft was readying itself to crush IBM's OS/2 under screens of purest blue.

"Email was an interesting new 'thing' on the internet," Jon recalled. To stitch together the network that we all take for granted, many email hubs used good old-fashioned dial-up technology to call each other up and perform an email transfer.

Jon's Canada-based firm had purchased some software from an outfit in Boston, Massachusetts, to do the transfer. The service would be used to regularly collect and send internet email.

"Testing went remarkably well," he said modestly. An Intel 386/40-based machine running OS/2 was used for the production installation and again, everything went swimmingly.

For those of a certain age, the arrival of the Intel 80386 microprocessor series was somewhat of a watershed moment at the end of the last century. Mostly compatible with the 16-bit era, the 32-bit i386 architecture continues to linger, despite the best efforts of modern software manufacturers to kill it off. The DX variant was the height of luxury back in the day, particularly when compared to the poverty of the cut-down SX incarnation.

Delighted to see hardware, software and operating system working in perfect harmony, Jon fired up a test script. The correct diagnostic messages duly popped up and, flushed with success, he deleted them.

"The last step," he said, "was to program our new email hub to dial the master in Boston, at 5 in the morning on cheap telephone rates, in order to pick up the day's email."

Sinking in paper

Ooo, a mystery bit of script! Seems legit. Let's see what happens when we run it


It was shortly after 5am that Jon received a panicked phone call from the Boston-based supplier.

"Our mail hub had connected correctly," he told us, "with several hundred thousand diagnostic messages in the queue..."

That was more than enough to crash their hub, and the team at Boston would be ever so pleased if Jon could possibly fix the problem. Right now.

Realising his error, he dashed to the office and shut down the diagnostic script which he'd forgotten all about and was still cheerfully generating test messages, Sorcerer's Apprentice-style. Oops. The program was hurriedly shut down and the remainder of the queue wiped.

Steam ceased to be emitted by the Boston hub.

Being an honest fellow, Jon confessed his sin.

"To my surprise the response from both the business partners and our supplier was amazement – that OS/2 had managed several hundred thousand email messages without error."

Thanks to Jon's inadvertent load testing, it was confirmed that – yes – the company was ready for business in the email department.

Oh, and please – no further testing, OK?

Ever inadvertently set the network on fire (physically or digitally) but managed to pass it off as testing? You have? Now is the time to confess all and share what really happened with an email to Who, Me? ®

Similar topics

Broader topics

Other stories you might like

  • September 16, 1992, was not a good day to be overly enthusiastic about your job
    If I get in early and work hard, everyone will notice, right?

    Who, Me? "The early bird trashes the business" is a saying that we've just made up, but could easily apply to the Register reader behind a currency calamity in today's episode of Who, Me?

    Our hero, Regomized as "Mike", was working as a "data entry operative" for a tourism company in 1992. The company ran bus tours to the then brand-new EuroDisney, parent company of Disneyland Paris (now the most visited theme park in Europe), which had opened earlier that year.

    Mike was an eager beaver, his youthful naivete having convinced him that if he worked extra hard, came in extra early, and kept the in-tray clear, then his efforts would be both noticed and rewarded with promotion and a bump in pay.

    Continue reading
  • An international incident or just some finger trouble at the console?
    All routers are equal, but some are more equal than others

    Who, Me? Welcome to an edition of Who, Me? where some configuration confusion left an entire nation cast adrift.

    Today's story is set in the early 2000s and comes from a reader Regomized as "Mikael" who was gainfully employed at a European ISP. The company had customers in multiple countries and Mikael's team was responsible for the international backbone.

    "Us senior network engineers were widely regarded as consummate professionals," he told us, before adding, "at least amongst ourselves."

    Continue reading
  • A discounting disaster averted at the expense of one's own employment
    I know what this process needs: Microsoft Access!

    Who, Me? A tale of discounts and process improvement via the magic of Excel, Access and a fair bit of electronic duct tape we imagine. Welcome to Who, Me?

    "James" is the Regomized reader of record today, and continues the theme of running the risk of doing a job just that little bit too well with an ancedote from the end of the last century involving his first job out of university, at a certain telecommunications giant.

    The job involved a process of calculating the discount received by big customers (the ones with multiple branches). "For the life of me I can't remember what the main DB was called," he told us, "but it was the old style green writing on a black screen that took forever to download the necessary data."

    Continue reading
  • In IT, no good deed ever goes unpunished
    When being helpful can mean being shown the door

    Who, Me? Going above and beyond in IT can sometimes lead to also going directly out of the door, as one Register reader found when discovering that sometimes efficiencies can be less than rewarding.

    A reader Regomised as "Will" told of us his days working at a now-defunct company that produced large telephone switches. In those days whenever a major software revision occurred, customers were expected to send in their configurations and Will's group would merge them into the latest and greatest. A new load would then be returned to the customers.

    It was not a fun process, not least because of constant hardware and software failures during the merge process. "When I first started, there was a constant grumble about how unreliable the machine used for the merging was," Will told us.

    Continue reading

Biting the hand that feeds IT © 1998–2022