Windows might have frozen – but at least my feet are toasty

Not quite what we meant by Halt and Catch Fire


Who, Me? The weather outside might be frightful, but the fire is... unexpected. Kick off your week with a tale of fan-tastic idiocy courtesy of The Register's Who, Me? feature.

Today's tale from Register reader "Mark" takes us back a good few decades to his time spent in the IT support barrel. It was a heady time, and the IT team had just completed a rollout of new PCs, connected together via the magic of networking.

The PCs themselves were exciting: not the beige boxes of old, but a new generation of slimline devices that purred with power. We've not named the PC maker because, as will become clear, what transpired wasn't really its fault.

"Although the fans in these were, I thought, fairly small and quiet," said Mark, "one of the managers didn't like the fan noise."

The ungrateful so-and-so noted that the fan was in the side of the case rather than at the back where all the cables were connected. He hit on a bonzer wheeze: "He could quiet the noise by putting the PC on its side next to his desk with the fan downwards so that it was muffled by the carpet it was resting against."

Simple, right?

Not quite. Computer fans are there for a reason and while today's CPUs will throttle themselves back as the heat rises, things weren't quite so straightforward in decades past. Indeed, this hack has not so fond memories of destroying hardware by failing to consider the cooling needed for that ham-fisted attempt at overclocking.

And then there is the power supply and all the ancillary components, none of which would appreciate a fan wheezing on carpet fibres rather than doing the important job of shifting air around.

"Unsurprisingly, his PC eventually caught fire."

Ever witnessed a perfectly good bit of equipment destroyed in a conflagration caused by management muppetry? Or seen smoke seeping from every port because you'd forgotten to connect the fan? We've done at least one of those things. Perhaps you've done worse? Send us your confession to Who, Me? ®

Similar topics

Broader topics


Other stories you might like

  • 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
  • An early crack at network management with an unfortunate logfile
    It's a backronym, right?

    Who, Me? Come with us on a journey back to the glory days of Visual Basic 6, misplaced enthusiasm and an unfortunate naming incident. Welcome to Who, Me?

    Today's tale comes from a reader Regomised as "Stephen", who was working in the IT department of a Royal Air Force base. "My duties were many," he told us, "from running daily backups of an ancient engineering system using (I kid you not) reel-to-reel tapes to swapping out misbehaving printers."

    This being the early 2000s, his boss loaded up our hero with more tasks. He could change printers and tapes, so Visual Basic (and its bedfellow, Access) should present no problem.

    Continue reading

Biting the hand that feeds IT © 1998–2022