What happens to the machine when the human abandons it?
Behold, the personal computer. A Packard Bell desktop, to be precise, with all the whiz-bangs the end of the 20th century allotted: 100 megahertz Intel processor, 1 gigabyte SCSI drive, a floppy and a CD drive, and, the creme-de-la-creme, a 28.8 bits per second dial up modem!
The programmer who owned this box passed away in 2011, and it, like many of his material things, just sat where he last left it. Now the CPU, keyboard, and start-up flops are in my house, and I’m attaching my 50″ flat screen to serve as its monitor.
Quite the whimsical juxtaposition of What Once Was with What Now Is.
Back in the IT days, we referred to an abandoned system as a ‘dead man’s locker.’ The typical service call was someone not information technology inclined asking me to figure out what Billy Bob did to make the pooter run before he croaked. The task at the user level was difficult; every system administrator has peculiar habits – a certain naming convention that doesn’t make literal sense, the redirect of master files from the default directory to a special access directory (and the guys who do this still: STOP IT YOU’RE BEING A DOUCHEBAG) and the lovely discriminate limitations to certain users to start business-specific applications.
Every ‘box’, including the one you’re using to read this, has its required components but all are completely customizeable to the whim of the box’s owner/operator. We all have a certain signature applied to every program we run, and, for us of the IT world, we go so far as to change the way the machine thinks, encouraging dominion.
So how did this fellow exact dominion over machine? He was a COBOL programmer, so was I. If his operating system was DOS-based, then he ran MicroFocus COBOL, which means, he likely signed all his subroutines a certain way.
Yes, all programmers sign their subroutines. 🙂
The task was made simple: see if you can boot it up and if so, see if there’s any files worth saving.
Geez. I gotta make that call? It’s good I’m the neutral party in this arrangement!
The box came up and went through its basic start sequence. I listened for the tell-tale spin of the hard disk and the immediate hunt of the arms. I didn’t hear the distinct song.
The Jumbotron displayed ‘i/o error remove disk then hit <Enter> to continue’. With nothing in the other drives, the i/o error had to be anything along the SCSI controller.
Tool bag out, cover is off.
Everything looked…OLD. Even when I was supporting systems eons ago, this was considered an old box! Checked the bands, the relays, the connection…looks like he never touched it. I did attempt to open the case fully, but alas, the final screws were smaller than the heads I have in my toolkit.
This is the point of system analysis when you gotta ask: is it worth pursuing further?
I thought back to the original request. This was HIS computer; no one else even knows how to code. The only auxiliary access was via fax machine, which they didn’t own anymore. They already have a current-century box working fine in the household. Even if I was to get the arms moving and the drive spun up, the only person who would understand his codes was gonna be me, the neutral party, and nobody in the world is looking for home-spun programs written in MicroFocus COBOL.
Then I think to myself, this would be a fun short story to write. 🙂
I go about trying to find anything that could fit these screws, but I’m just shearing the heads at this point. While I wanted to resolve this and discover he was indeed a talented programmer in his heydey, my curiosity was quelled by limited access to the technology.
In plain words…the needle-nose screwdriver I require costs more than this entire box, code included.