Sysadmin crashed computer recording data from active space probe

‘I’m the reason we missed seeing aliens’, jokes nervous reader

By Simon Sharwood, APAC Editor

Posted in Business, 29th January 2018 06:54 GMT

Who, me? Welcome again to Who, Me? The Register’s new column* in which readers confess to times they performed sub-optimally and broke important stuff.

This week, meet “Fred”, who begged us “Oh God, please don't use my real name or contact info.”

Fred’s desire for anonymity stems from the fact that in the late 1970s he worked for a Very, Very Famous Space Agency on two Very, Very High Profile Space Probes.

And he broke one for a few minutes.

“My primary job was repairing the computers controlling the spacecraft,” Fred explained. One of the missions he worked on “was winding down a bit so I was asked to remove some equipment from one of the rooms where its peripherals were stored.” Once the old stuff had been chucked, Fred would put in the new stuff for the more active mission

“The last thing to remove was an IBM 1403 printer. However, I was not familiar with its connectivity to the IBM 360 mainframe … but I proceeded to remove the two large cables attached at the bottom anyway and moved the printer out into the hallway.”

'The capacitors exploded, showering the lab in flaming confetti'


“Not a minute later one of my co-workers ran into the room yelling ‘WHAT ARE YOU DOING!?’”

At this point in proceedings, Fred was unaware of any issues so explained what he’d been told to do.

He quickly received the news that whatever his instructions, implementing them had taken down the mission and it had missed three minutes of data from the spacecraft.

“When I repeat the story to some close friends, I usually end with ‘And that was the three minutes when the spacecraft found life on another planet."

Whatever knowledge humanity missed out on, Fred learned that “with IBM mainframe peripherals, you had to stop the computer and terminate the Bus and Tag cables before restarting, otherwise the system comes to a screeching halt.”

What have you brought to a screeching halt, and what happened afterwards? Click here to share your story with Who, me? and we might just be able to slot you in here on a future Monday morning. ®

* Who, me? is a companion piece to On-Call, our weekly story of tech support trauma caused by silly users, bilious bosses or incompetent colleagues. In Who, me? the joke’s on you, for having messed things up all by yourself.

Sign up to our NewsletterGet IT in your inbox daily


More from The Register

Trump to NASA: Fly me (or some other guys) to the Moon

POTUS also wants to Make Mars Great Again

Sysadmin finds insecure printer, remotely prints 'Fix Me!' notice

ON-CALL Once you're through the web interface the email-to-printer address is easy to find

Sysadmin jeered in staff cafeteria as he climbed ladder to fix PC

On-Call Life lesson: don't display messages on screens if you don't know who'll see it!

User filed fake trouble tickets to take helpful sysadmin to lunches

On-Call Reg reader was shouted at for a problem the customer created, but won his respect and apologies

Bombastic boss gave insane instructions to sensible sysadmin, with client on speakerphone

On-Call When data disappeared, everyone knew exactly where to point the finger

Sysadmin tells user CSI-style password guessing never w– wait WTF?! It's 'PASSWORD1'!

On-Call Sysadmin hated making it look so easy, but didn't mind being a hero for saving a payroll run

'Do not tell Elon': Ex-SpaceX man claims firm cut corners on NASA part tests

Firm: Not what he was saying before we sacked him

Sea-Me-We 3 cable down, again, Oz-Asia traffic slows down

Packets will route around the damage until January

Sysadmin 'fixed' PC by hiding it on a bookshelf for a few weeks

On-call User who though he knew everything was satisfied by doing precisely nothing

Indian call centre scammers are targeting BT customers

In some cases fraudsters knew their mark's personal details