News: 1702279748

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Enterprising techie took the bumpy road to replacing vintage hardware

(2023/12/11)


Who, Me? Heavens to Betsy, dear reader, are you back again? It feels like only a week since we last met in the corner of The Register we call Who, Me? to share the schadenfreude of a fellow Regizen's misfortune.

Let’s get on with it again, shall we? This week meet a fellow reader we'll Regomize as "Loudon" who, back in the early 1990s, landed a job as a field engineer for a major aerospace corporation.

Now, you might expect that an aerospace corporation would want to be at the pointy end of technological innovation – and you'd be right. But that extended only to what the biz made, not the tools it used. The computer equipment Loudon had to work with was all very old – some of it from the 1970s – and he was getting pretty tired of it.

[1]

In particular he had grown weary of maintaining a bunch of DEC RM03s – huge free-standing cabinets with five disk platters inside, weighing 195kg (430 pounds) but contributing storage capacity of only 67MB. Loudon campaigned to have them replaced.

[2]

[3]

He finally had some success, as one department agreed to replace their old failing VAX with a spanking new MicroVAX 3100 Model 10. The MicroVAX 3100 Model 10, you no doubt recall, had a SCSI port for external storage – so the old RM03 attached to the VAX could also go, and be replaced with modern (for the time) storage.

It would be faster, it would be more capacious, it would be easier to maintain – everyone was happy.

[4]

Loudon's plan was to take the old RM03 cabinets and strip them down for parts to keep the rest of the fleet running until he could persuade other departments that SCSI was the future they needed, now. He didn't imagine that would take long once the one MicroVAX started operating.

Unfortunately, other departments had different ideas about what should become of the surplus disks. One department, which had three RM03s already, expressed a desire to add another five to its system. They saw the prospect of a mind-blowing 536MB of storage at their disposal, while Loudon saw a room full of antiques he would have to spend his days tweaking just to keep them alive.

So when it came time to decommission the old disk cabinets, "we decided to move the RM03s to our site office by pushing them over the (very bumpy) road and path to our office," Loudon recalls. Furthermore, "we were not gentle, and each RM03 had a rough journey."

[5]Sysadmin's favorite collection of infallible utilities failed … foully

[6]IT sent the intern to sort out the nasty VP who was too important to bother with backups

[7]Why have just one firewall when you can fire all the walls?

[8]Bright spark techie knew the drill and used it to install a power line, but couldn't outsmart an odd electrician

Indeed the journey was sufficiently rough that, when the department that wanted the disks asked how much it would cost to get them moved and set up, Loudon could honestly say it was not economical to repair them. "We had done some work on one drive and costed up the parts and labor to get it back into full working order," he wrote, and "the costs were far higher than doing what their colleagues had done."

So it was that another MicroVAX found itself a new home.

[9]

Loudon admits that similar tactics were employed in the following years to get rid of a lot of the vintage gear – but some departments were just that determined to hang onto their old systems. Even after he left that employer, he would still get phone calls years later from "some fresh-faced field engineer who was presented with a 40-plus year old antique" who needed advice on how to troubleshoot.

This seems like a fairly extreme way to persuade an employer to shell out for an upgrade, but we suspect Loudon is not alone. If you've ever encouraged a failing system to a well-timed accident, let us know about it in [10]an email to Who, Me? and we'll share your story while protecting your secret. ®

Get our [11]Tech Resources



[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2ZXbr2kqbFW7CAMqLeDOV4wAAAIk&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZXbr2kqbFW7CAMqLeDOV4wAAAIk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZXbr2kqbFW7CAMqLeDOV4wAAAIk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44ZXbr2kqbFW7CAMqLeDOV4wAAAIk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://www.theregister.com/2023/12/04/who_me/

[6] https://www.theregister.com/2023/11/27/who_me/

[7] https://www.theregister.com/2023/11/20/who_me/

[8] https://www.theregister.com/2023/11/13/who_me/

[9] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_onprem/storage&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33ZXbr2kqbFW7CAMqLeDOV4wAAAIk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[10] mailto:whome@theregister.com

[11] https://whitepapers.theregister.com/



We've all made that call.

Admiral Grace Hopper

"It's not working, I need a new one".

"Is it definitely broken? It might still be repairable"

"I'll just check"

* pushing/sliding/falling/hard landing/breaking noises *

"No, it's definitely broken beyond repair".

Re: We've all made that call.

Michael H.F. Wilkinson

It's the terminal form of percussive maintenance/a.k.a. put old kit out of our misery

Re: We've all made that call.

Chloe Cresswell

I used to carry in my toolkit a white headed rubber mallet for HDs that weren't quite failed _yet_...

Michael H.F. Wilkinson

Well played by Loudon! A bumpy road is clearly a good replacement for the BOFH's panel-beating hammer of [1]yore .

Somehow I am thinking of a dead skunk in the middle of the road now. Wonder why

[1] http://bofharchive.com/1998/bastard98-21.html

Peripherals

GlenP

Not quite IT but inevitably under our remit...

Previous company had two paper shredders, an elderly strip shredder and a much newer, and more secure, cross cut one.

Payslips were still produced on a matrix printer as a printed top sheet with the actual secure NCR slip underneath so the top sheet was split off. The top sheets were kept as a strip for the required period then a year's worth would be shredded in one go, which was where the argument started. Firstly the newer shredder would only take one sheet of paper at a time and frequently jammed - that was easily sorted by actually lubricating the thing which I discovered hadn't been done in several years. The second complaint was it would only run continuously for a few hours a day - well it was only a 50% duty cycle!

Because of these issues they absolutely insisted they would use the old shredder for the job. It was pointed out that it was insecure, and the Company would be liable under the (relatively new) Data Protection Act* since it was easy to piece the paper back together again, but the payroll people were adamant. The old shredder happened to be in the wrong building though and needed moving about 100 yards so a couple of the shop floor were enlisted for the job. Now I'm not saying they did drop it deliberately, and I'm not saying they didn't, but the end result was some bent components and loud graunching sounds when it was turned on - result achieved!

*A company had recently been fined due to a lack of an adequate shredding policy when an employee "happened" to find a copy of his payslip in a black rubbish bag. Everyone was certain it was a stitch-up but it cost a few thousand pounds.

Re: Peripherals

lglethal

So do you know who slipped the Shop Floor guys a couple of notes to perform the impromptu permanent deactivation?

Re: Peripherals

DailyLlama

Yes, but the notes were shredded for security purposes.

You don't really even need to break it

DS999

Just put forth less effort to fix it everytime it goes down. Something breaks, tell them "I will need to go onto the internet to research this problem" and take advantage of the quiet time that will afford you to catch up on your email or other paperwork. Then you go ahead and fix it, but warn them that information about troubleshooting and fixing such obsolete hardware is becoming more and more difficult to find so it will probably take longer and longer for you to fix it each time it breaks.

If they don't learn their lesson after a few times doing this, next time just fully work on the other responsibilities of your job and totally ignore their ancient equipment. Tell them "I'm waiting for a call back from a retired engineer who is the only guy I've found who has said he's seen this problem and may know what to do". After being down for half a week, you can fix it and tell them how lucky they are that guy finally contacted him because you never would have been able to solve it without his help. Maybe subtly remind them that if you were hit by a bus and they have to hire a replacement finding someone who has even what little experience with that obsolete hardware you do will be very expensive since they are all either retired or moved on to more lucrative fields.

We were not gentle, and each RM03 had a rough journey

abend0c4

Having regularly had to take them in flight cases on transatlantic journeys, the disk packs themselves were remarkably robust - not entirely surprising given the rather low information density.

I'm sure the sheer weight of the actual drives being manoeuvred over rough ground (assuming you could summon up the necessary effort) would quickly throw the heads out of alignment, but they were otherwise quite [1]solidly built [The box with the switches is a CDC TB216 Field Test Unit, not a Digital computer, the basic drives were supplied by CDC].

[1] https://www.youtube.com/watch?v=ttelBz4Td_E

Re: We were not gentle, and each RM03 had a rough journey

Phil O'Sophical

That was my first thought. A lot of those old drives could have been pushed down a flight of stairs and would have been fine after a polish and head alignment.

The 256MB packs (RM05s?) were relabelled CDC kit, was the RM03?

Re: We were not gentle, and each RM03 had a rough journey

Anonymous Coward

There was a point where the maintenance costs associated with this type of equipment and even just the cost of re-commissioning would be more than potentially moving to newer equipment, heck even the electrical consumptions costs could probably make a business case!

Re: We were not gentle, and each RM03 had a rough journey

abend0c4

electrical consumptions costs could probably make a business case

RM03s had power sequencing cables to ensure that only one would start up at a time - the surge currents were pretty substantial (22A @240V) until the motors came up to speed. In standby, they consumed 3.5A @240V and while active around 7A. For 67MB.

Re: We were not gentle, and each RM03 had a rough journey

abend0c4

The 256MB packs (RM05s?) were relabelled CDC kit, was the RM03?

You can find the RM02/3 service manual [1]here which cross-references the DEC and CDC part numbers.

I'm sure someone will correct me if I'm wrong, but I think all of the "washing machine" stye drives were from OEMs.

[1] http://www.bitsavers.org/pdf/dec/disc/rm03/EK-RM023-SV-001_RM02_03_Service_Jun78.pdf

Re: We were not gentle, and each RM03 had a rough journey

GlenP

I'm pretty certain all the ones I worked with said DEC on the front and CDC inside!

Bizarre printer failure

Richard Gray 1

We did have one person who didn't want to loose his personal Laser jet printer despite being told that the orders had come from on high.

If he was a better user we might have been slower to respond...

We did a guerrilla run into his office at night. used a strip of black insulation tape over the laser unit /fuser (I can't remember which).

He came down the next day with a printout with one column missing. We took the printer away for "repairs" and was never seen again

Re: Bizarre printer failure

robinsonb5

I'm going to hope it was the laser unit - or the imaging drum. Having spent a happy half hour last year peeling gooey plastic labels off a modern fusing belt, I can only begin to imagine the smell of insulating tape getting smeared around an oldschool fuser!

GroovyLama

Mid-2000's, a colleague had got back from some international travel and had been complaining the hard drive in his laptop was making a lot of dodgy sounds, and laptop was running slow, and that it needed replacing. IT told him it needed to be reviewed before the drive could be swapped, and someone would be round lunchtime to check it over.

He decided to perform his own check. He pulled the drive out of the laptop - this was a Dell laptop. I seem to remember you could unclip the drive out quite easily, just like the batteries. A Latitude model maybe? - He started off by shaking the drive up to his ear, and then proceeded to SLAM it down on the desk a few times. He then held it up and shook it again.

"Yup, it's definitely got a rattle to it. I think it's knackered".

Cue all the surprised faces when IT came to check the laptop and it couldn't boot off the drive. Replacement drive provided post haste!

the pointy end

Anonymous Coward

> you might expect that an aerospace corporation would want to be at the pointy end of technological innovation

Many aircraft have a service life of 20 years or more, so the IT kit at the manufacturer has to be compatible with what the customers have. It's probably the same for industrial or medical systems.

I recall getting a task to create some update floppies (single sided/single density IIRC) for distribution in the days when CDs were the standard. Finding a system with a suitable drive was the hard part. Then working out file formats. Then testing the update mechanism on a multi-million dollar test aircraft (gulp).

Re: the pointy end

lglethal

Yep, basically if there's an aircraft still flying you HAVE to keep all the records, models, drawings, etc. You can attempt to bring them up to a newer standard, but budgets rarely extend that far, and automated systems are a nightmare (as my Firm found out when they decided to transition from CATIA V5 to Siemens NX - basically for anything that's going to be modified in the future, it's easier and quicker just to remodel from scratch in NX, than to try and wrangle the conversion into shape...).

I still remember in my first job many moons ago, when CATIA V5 was the new Airbus standard (mid 2000's), that there were still at least a few people working daily on terminals running an early version of CADDS (cant remember which version but easily mid 80's if not older). At least the old Airbus rule was to stick to one CAD/PLM system for the entire length of the Aircraft project (so A400M was the first to move to CATIA V5, before that it was V4). No idea if that rule is still in place...

Re: the pointy end

Anonymous Coward

When I left a company in that arena 5 years ago, there was still a repair technical who would demonstrate repairing core memories yearly.

I wasn't allowed to know how many she repaired, but I did see her records for the demonstration/practice for the last 30 years.

Rare machines

Chloe Cresswell

I used to be friends with someone who worked with some machines called "Deltas". The company was bought out and they were told all IT work had to be done by the new owner's IT department.

So my friend had one of their guys come out and look at the deltas in their racks. Guy looks at one and asks basically "what the fuck is that?"

"That's a delta."

Guy takes out a form and starts to fill in the details... "does it have a serial number?"

"X00001, the X is for eXperimental"

Guy looks at him, and then asks "How many of these are there?"

"5, X00001 to X00005"

"How many were built?"

"5..."

We should start referring to processes which run in the background by their
correct technical name... paenguins.
-- Kevin M. Bealer, commenting on the penguin Linux logo