Year 2100 bug
I am surprised that no one has made more of the use of two digit year. That is a year 2100 bug in the waiting, so soon after Y2K. Still 78 years to go so plenty of time to let this fester.
14 publicly visible posts • joined 1 May 2020
Some years ago a local firm brought along a small digger to our kids primary school fate. I got to the front of the queue and the bloke looked at me, no small kid. I said they we off having fun, I wanted a go. He shook my hand a congratulated me for being the first person not embarased to ask, or pretend the kid wanted a go.
Even if it is removable, how many network operators, in the widest sense, are going to want to swap SD cards every four months on every switch in their networks?
In the cases I've come across in the past where it was removable cards that got toasted that still required a software rewrite to slow the rewrites.
And (yet) again. Either software developers don't read the Flash specs, they don't understand the meaning of the lifetime, or they just don't calculate what it means in practice. I remember getting the "What do you mean, compact flash has a limited number of write cycles?" from a programmer over a decade ago, or the "You can destroy hardware by writing to Flash?" from a manager back in the early 90's.
Before the internet, DSL and VPNs swept all before them, companies would often link sites with leased lines. I worked for a comms manufacturer who made a mux that could merge voice and data onto a single kilo-stream link, saving the cost of separate voice lines. The voice links were compressed to save bandwidth and they had a fax relay mode that demodulated the fax locally and just transmitted the digital content to the other end. This was in use in small branch offices and one of these had a problem. If someone was on the phone and the fax was used, the voice call went into fax relay mode.
Each voice channel had its own DSP, so a software fault was ruled out and the finger of blame started pointing at a 1U pizza box that housed the analogue interface between the mux and a standard phone connection. I had never seen one of these before, but that did not stop it becoming my problem as two tech support engineers "demonstrated" by talking to a phone attached to one line while getting me to listen to another. I could not hear anything over the wall of 19" racks of comms equipment in their lab so I took it away for further investigation.
I injected signals and measure cross talk on the adjacent channel, but I had to put in one hell of a loud signal to get anything noticeable. I persisted. The PCB was just two layers so the grounding layout was bad. I added thick wires and managed to reduce what cross talk existed. How I could get such a mod into production without being lynched was a problem for later, so I too the box back to tech support.
Weeks passed and I heard nothing, then I bumped into one of the tech support guys and asked how the modified box worked. He looked a little sheepish. They had taken the field service report at face value, but when he went on site he had noticed that the fax monitor was turned up to full volume. It was basically acoustically coupling to the nearby phone. When they turned down the volume all was well.
Thinking back, I wonder what the BER was like, but now I'll never know.
Once upon a time at a previous employer, I discovered a notepad process without a window on my corporate ID adminsitered laptop. Further probing with process explorer revealed that it was opening a vbs file. This appeared to be part of the login process, but vbs was blocked from executing as a security precaution.