Click bait
Nice click bait in the title, was expecting that cat to be a bit closer to the computer ;)
Black Friday Giveaway! We don't want you to think El Reg isn't jumping on the internet bandwagon as the frenzied hunt for "bargains" continues apace. So we're offering you a deal of our own: a BOGOF On Call! That's right, TWO techie tales for the price of ONE, as we bring you a double header from reader "Geraldine" on her …
A simple sticker pointing out how the jam detection had been disabled could have saved the poor lad from the massive tear-down/rebuild, but obviously everyone 'knew' about it so it wasn't necessary, until someone didn't.
But also, how did it get to the point of having the printer stripped to components (i.e. who authorised it?) before having someone point out the work around?
'...and the implicit subtext of "touching it will break something, but nobody's sure how or why"'
And I'm the unmitigated prick who will do precisely that, on a scheduled downtime interval, to ascertain if it's still necessary and if so, precisely why, include it into a manual and log, then test the next damnable taped over switch or remove the tape after testing and change management review.
I worked in a change management lacking environment once. One day, I was happily tooling along with some patches to be manually applied via dos prompt and suddenly, my prompt promptly disappeared.
I turned to the shop supervisor and asked, "I just lost my dos prompt and can't raise it again, what did you do?".
It turned out that there was a change order and we were exempted via that order, so he helpfully tested it upon us, the BOFH mk2's.
"Stop it!" at rather high volume was projected by a voice heard by approximately 1000 men without amplification.
He subsequently rose to management, but retained access rights by chicanery and telephone calls to his office frequently revolved around "Stop it!", raising a rueful laugh in the building.
By that point, I had become in charge of information security, he kept trying to do admin things without warning, creating hell, or havoc, your choice.
Laughably, due to manpower shortages, which were infamous, I retained my network god access and worked some issues alongside the tier 2 and 3 types.
I happened to be working at one point on a modest change in a specific network and noticed that my computer logon script wasn't what I saved and worse, as I slapped a tail program on it, changes were incremental and eventually, a loop was introduced. I reached for my telephone and speed dialed one of the few entries on my speed dial.
"Carl, I'm working on the ZZZZZZZ network logon script and noticed some odd changes."
"Woo-hoo, I was working on that computer logon script, as it's part of a change order and it needs to be done. I accidentally created a loop and I'll fix it once I reboot and log on with my network cable disconnected."
"Carl, you're no longer a tech or administrator, you're a manager. STOP IT AND MANAGE", generating open laughter in the office.
I then advised him that I had the ticket, fixed his foul up and the order is marked compliant, so Stop It!.
Generating sidesplitting hilarity in the office.
Full background, that was a US military installation that is part of a command abroad, in a war theater.
I also was asked, by the installation commander how I was to enforce a SOP (Standard Operating Procedure) mandated and frequently ignored, with problematic results, a weekly mandatory reboot.
Knowing that tasking order, I had a script ready to go, which implemented active directory changes to our OU, a secondary SCCM job to push a script that did the same and a more retro approach, where the DNS and WINS server were queried and what was common and not responded to by SCCM or AD got poked the script, which performed the changes at system level.
I simply said, the network command refuses to enforce the order, so, as computers are your responsibility, what do you want to do?
He said, reboot at seven days.
Went to my office, did so. One push on the enter key was all that was needed, once logged in.
About a month later, he was briefing his General and his computer rebooted in the middle of his presentation and he related his orders.
Which he did, which much open laughter, relate to me.
But also, how did it get to the point of having the printer stripped to components
There was a time when computer equipment was subjected to Preventive Maintenance, usually as part of a service contract. Replacing the drive belt and tensioner in RA8x drives, adjusting vacuum and pressure levels and replacing filters in various tape drives, down to replacing or cleaning out the airflow filters in VAXen and Alphaservers.
Preventive Maintenance on printers would have been in those contracts too, and printers being subject to the unholy alliance of dust, moving mechanical parts and the buildup of gooey ink, they would dearly need it. Which means that at least once a year, but probably more often, a service engineer would show up, dragging a trolley with the PM kit for that printer model, and to a first approximation take the entire printer apart indeed. With any part not deemed up to spec and potentially causing a service call some weeks or months on, let alone broken, replaced. If the customer was lucky the printer would be back in working order at the end of the day, but it might instead be waiting for parts that weren't in the kit, in the engineer's "would be useful to have at hand" stash of parts back in his car, nor in any of his printer-frobbing colleagues' either.
So yes, a printer closely resembling one of those exploded views in the associated service manual, with an ink-smeared person wielding screwdrivers and spanners next to it may well have been a planned activity.
"But also, how did it get to the point of having the printer stripped to components (i.e. who authorised it?) before having someone point out the work around?"
That suggests that stickers were available in that specific era, which is iffy, save toward the end, when printers finally sang their swan song and the "printing" was stored in a log file.
And when PM very often required a manual teardown to remove paper dust and small shreds. And where the masked off contact should have been observed during the tear down, as inspection is a part of the process.
Oops, I think I just gave away my age...
I've always found that rapid, multiple uses of fire tends to get rid of both issues...
(Mine's the one with the asbestos coating and the RFotSoBOFH* logo tastefully embroidered on the left shoulder, thanks. And I've counted the cash too...)
(*Royal Fraternity of the Society of Bastard Operators From Hell)
"You can't train a cat, all you can do is make it more sneaky about doing whatever it wants to do."
Almost true. We trained our cats not to get caught on the kitchen counters.
You see I said "caught". We never see them on the counters. But we do hear a loud thump from the kitchen sometimes. Like a cat just jumped off somewhere higher up. And a bowl magically fell on the floor the other day that had been on the countertop. But we didn't see a cat do it.
I joined Unisys as a fresh faced young graduate in the mid 90s after working on Silicon Graphics workstations throughout my CompSci degree, only to be introduced to the Unisys V-Series, which was obsoleted already but had just been installed for an outsourced payments processing venture. It had a total of 32Megawords, which left me distinctly nonplussed because I'd just upgraded my Amiga to 64MB of memory (via a WarpEngine 040, for the truly geeky reader). The processor was a minor work of art, is I was told it practically ran COBOL instructions natively. It was rather chunky.
The V series occasionally would just fall over in a heap badly, and the engineer decided I'd like to see the inside of it. Cue a tear down...
...only to find a 10 inch long thin flatblade screwdriver, with a 6 inch uninsulated bit, jauntily lying across the motherboard. Presumably randomly making contact with some of the rather massive DILs when airflow changed.
I recommended it be removed. The engineer agreed with the young oik.
Management were amazed at the reliability improvement a few weeks later. I had been sworn to secrecy by the engineer, and was complicit in the "remove, reseat and cleaned" explanation.
This post has been deleted by its author
Whilst working as a fresh-from-school apprentice in a telephone exchange, I was tasked with helping to wire up an additional selector rack in a Strowger exchange.
The rack was already in place and powered by the 50V DC feed through two hefty copper busbars about 4 inches apart. The busbars were plastic clad, apart from the ends near the rack where terminations were made.
The individual wiring to all the selectors was carried on open steel cable trays mounted above and to the side of the busbars, and these cable trays were bolted together by M10 nuts and bolts.
So who do you think it was who managed to drop his 10mm spanner neatly across the bare ends of the live and return busbars then?
The equipment room went strangely quiet, as all the selectors stopped chattering, and the spanner glowed gently, and then brighter, and brighter, and then melted gently in the middle, and all the equipment sprang back into life, followed by the clang of alarm bells and the flashing of warning lights.
I carefully climbed down the ladder from near the ceiling, and went and owned up to the T.O.
I wasn't sacked on the spot, just lectured on the importance of caring for my tools...
So who do you think it was who managed to drop his 10mm spanner neatly across the bare ends of the live and return busbars then?
10mm spanner -> M6 bolt. M10 bolt -> 17mm spanner.
I was told about an incident in the exchange I was assigned to for keeping their VAXes happy: a painter had set a tin of paint down on those bus bars. Across both.
The result was said to have been similar to Mr. Bean's way of painting his living room.
Have not done that. Close, but have never done it.
Best I have done is to melt the blade of a screwdriver.
Before working on a mains circuit (which I believe to have been shut off), I first meter it, then short it with a screwdriver, just to be sure (taking the appropriate safety precautions, of course - safety glasses, etc)
I have drawn a spark more than once.
We had a baby-Burroughs server. A BTOS modular jobby. It consisted of half a dozen modules plugged into each other, stretching across a desk.
I went on holiday and when I came back, I found site services had moved it to a neary-by table because the desk it was on was needed elsewhere... Only they hadn't asked anyone about it, and I was the only one who knew how to shut it down, they had simply picked it up (2 men, one at each end of the long sausage of components stuck together "Lego" style) and moved it to the table, whilst it was still running.
2 of the HDDs were dead, unsuprisingly.
The machine I had was still running BTOS at the time.
BTOS - Burroughs Technology Operating System (it was the Burroughs name for CTOS and it was also marketed under the name Starsys).
I also went on a training course in Milton Keynes at the Unisys campus in Fox Milne.
That was fun. Middle of the course The Blues Brothers was shown on TV. Just about everybody on campus had watched it. Just one boring old fart, who complained about the racket coming from all the neighbouring rooms.
BTOS - Burroughs Technology Operating System (it was the Burroughs name for CTOS and it was also marketed under the name Starsys).
Wasn't CTOS from Convergent Technologies? I rememeber running 68K based MiniFrame and MegaFrame boxen running CTiX. Some MegaFrame I/O processor boards ran CTOS (scaled down obviously). They also came out with 80x86 based NGEN (or Burroughs B25 if you prefer) that ran CTOS. I'm talking about before Unisys bought Convergent Technologies.
I remember those. It was made by Convergent Technologies.
I worked for Unisys in Birmingham in 87/88 and had a few visits to the Milton Keynes training centre. I did work on these.
After that I worked for Bull Information Systems in London and discovered to my horror they rebadged it as well, called it a B20 I think and renamed the operating system to Starsys.
The one I had on my desk had just about every available module and was about three foot long.
https://en.wikipedia.org/wiki/Convergent_Technologies_Operating_System
It was actually quite a clever design. Pity my manuals had been translated from American English to French and then to proper(ish) English. Made for some interesting reading.
... ahh, Unisys @ Fox Milne, that does bring back happy memories - an attractive young lady colleague was on a course there. As I only lived 100 miles away I dropped in for a social visit one evening, nobody questioned why there was an extra person at breakfast. Happy days.
Nostalgia for BTOS & the B20 range too, networked long before the IBM PCs could offer any credible alternative, pity they lost the plot, among other things lagging behind on colour and sticking with their proprietary networking standard.
...only to find a 10 inch long thin flatblade screwdriver, with a 6 inch uninsulated bit, jauntily lying across the motherboard.
A PC is where you can lose a screwdriver in. A mini is where you can lose a toolkit in, and a mainframe is where you can lose the service engineer in.
...my friends and I behaved somewhat irresponsibly with a classic piece of kit.
We had some Tektronix 4051 vector displays. We were left unattended, bored, and near an open toolbox. Hilarious outcome. Reversed polarity on the horizontal deflection circuit and got to watch our teachers pull their hair out figuring what we had 'done to the software'
One surmised quickly what we had done and asked rhetorically whether he should congratulate us for coming up with the mod or punish us for being an annoying bunch of cheeky bastards. He went with "both"
I did that once. I fixed a mainframe's printer in Florida over the phone from Iowa.
OK, "fix" is probably stretching it a bit.
The operators had called me to fix a daily batch job that didn't print out overnight. I had just fixed it a few days earlier because it had crashed due to more data coming in than usual. So it's not to surprising that they called me up again because it "failed" again.
I dialed in and checked the print queue first and saw the file and several more waiting to print. So I called the operators back and asked if the printer was on? They checked and it was on but it had been offline. Seems a tech had worked on it the day before and had left it offline. No one had noticed till they went to get the overnight printouts to distribute to the bosses.
Here to thank El Reg for using a sane acronym. I'm not sure if it's unique to this side of the pond, but I usually see BOGO offers. BOGO as in "Buy One Get One", which is sometimes called out in the ads. Buy One, Get One? No shit, if I buy one and I get none, I'm pressing charges for theft. If its BOGF, now that may be a deal.
I had a customer who had "graduated" from running her lab on a DEC 11/23+ booting of RL02's to the new 8" hard drive! So much faster ... until one day when it would not boot up. We talked about it over the phone and I gave her some diagnostic tasks including listening to the sounds that the machine made when she booted it by hand via MCR.
She called back a couple of days later to say that the problem was solved - she discovered that she couldn't hear the disk spinning so she'd removed the top casing from the 8" hard drive and just gave the disk a little spin with her finger to start it turning - once it booted she put the cover back on with it running and didn't turn it off while backing everything up!
An easy fix for me - I just shipped her a new hard drive.