Re: rows of car batteries baking in the 48° heat
My friend had a Skoda umpteen years ago. The handbook recommended turning on the headlights for a few minutes before trying to start the engine when temperatures were below -10C
249 publicly visible posts • joined 12 Jan 2016
I'd been using MS Word for some time when I complained to my colleague that words that I had correctly spelled were being underlined as spelling errors. It was only then that I discovered that spelling errors and grammar errors are underlined with different colours - the perils of being red/green colour blind!
My very first OU course in 1977 was "Computing & Computers". The real-life company that was used as a case study ("Koch-Light chemicals") utilised the very latest "visible record computer" but I can't remember which model. Part of the course involved writing out BASIC code on squared paper and posting it (Royal Mail) to the OU who typed it up and ran it through their computer. This worked well as I was living in Brora (Sutherland) with no access other than a 75 baud time-share printer link at Thurso tech, a long drive away. The OU staff ran my first job through and annotated it showing where I'd gone wrong; after that they ran the job and returned the results, warts & all, without comment. The latter part of the course involved storing some data on the OU computer and then using that data in subsequent modules. After submitting one job that needed data which had been stored I received a note from the OU computer people asking (in rather stronger terms) "where is your data!". It took some time to discover that the OU had two separate computer sites at Milton Keynes & (I think) Sunderland, my jobs would be sent to either site, depending on the relative workloads. Alas, the data storage for the two computer sites was not shared thus causing the anguished cry of "where is your data!"
Back in the 1990s (Windows 3.1 or Windows NT?) I discovered that accessing or storing anything on drive letter "F" slowed down the whole system. It took a bit of digging to find out why but it appeared that Microsoft had reserved drive letter F as an analytical drive on which all sorts of debugging clutter could be hung and utilised.
In the mid 1980s I was working at a Government facility in Scarborough (N Yorks) and we had a new PDP 11/23 Plus on which to develop new "C" software. It must have been a "Friday build" because it frequently died on us and wouldn't re-boot. This meant phoning the office in Leeds who would despatch an engineer. We were charged £50 an hour from the time the engineer left Leeds until he eventually got back to Leeds.
My first posting in the RAF after basic & trade training in 1961 was RAF Driffield (Yorkshire) which was a Thor missile base. The stores section, run by RAF & USAF personnel, had IBM 80 column card punches, verifiers and data transceivers. One day the data transceiver received a batch of cards which punched OK but the print at the top of the card was missing. The procedure for faults was to contact RAF Alconbury who then sent out an IBM technician. The chap drove all the way up to Driffield, walked into the office, flipped the "print" switch from "off" to "on" then got back into his car and drove back to Alconbury.
My cousin was promoted within the UK Inland Revenue department. In his new office was a locked steel 6 foot cabinet with no key available. Locksmiths opened the cabinet and it was found to be crammed full of envelopes and those gummed re-use labels all marked "On His Majesty's Service". As this was in the 1970s my cousin decided it probably wasn't worth hanging on to them "just in case"...
My cousin also discovered that those gummed re-use labels actually cost more than 2 or 3 envelopes
A friend of mine worked in a large government department and had designed a piece of electronic security equipment that was to be used by the Army, Navy & Air Force. It survived all the usual extremely tough field tests with flying colours but he had great difficulty with the final part of the design - how to quickly destroy it in case of an emergency
Same thing at a large RAF base in Cyprus in the 1960s. Major storm knocked out power for a couple of days. The telephone exchange had an enormous battery which should have provided power for at least 36 hours but died after about 30 minutes. It transpired that a sergeant in the Royal Corps of Signals (who looked after all RAF telephones overseas) was responsible for ensuring that the electrolyte was topped up and regular voltage tests were carried out; he hadn't checked for ages and there was hardly any electrolyte in any of the cells.
After that same storm and flooding there was a signaller (private) in the Royal Corps of Signals who was using a canvas bucket to bail out a cable pit that was full of water. An officer in the Royal Corps of Signals drove up in his LandRover and asked the signaller how he was getting on. When the lad replied "Not very well, sir" he was told to put his back into it and bail more quickly. Shortly after that the SNCO from the Royal Corps of Signals arranged for an RAF fire engine to pump out the cable pit - a job that took about 4 hours because all the cable ducts were acting as drains and feeding into the cable pit.
Latest:
11/19
Issues connecting to Azure resources in Europe, Asia and the Americas regions using Multi-Factor Authentication
Summary of impact: Between 04:39 UTC and approximately 21:30 on 19 Nov 2018, customers in Europe, Asia-Pacific, and the American regions may have experienced difficulties signing into Azure resources, such as Azure Active Directory, when Multi-Factor Authentication (MFA) is required by policy.
Preliminary root cause: Requests from MFA servers to Redis Cache in Europe reached operational threshold causing latency and timeouts. After attempting to fail over traffic to North America this caused a secondary issue where servers became unhealthy and traffic was throttled to handle increased demand.
Mitigation: Engineers deployed a hotfix which eliminated the connection between Azure Identity Multi-Factor Authentication Service and a backend service. Secondly engineers cycled impacted servers which allowed authentication requests to succeed.
Next steps: Engineers will continue to investigate to establish the full root cause and prevent future occurrences. A full Root Cause Analysis will be published in approximately 72 hours. To stay informed on any issues, maintenance events, or advisories, https://www.aka.ms/ash-alerts and you will be notified via your preferred communication channel(s): email, SMS, webhook, etc.
Back in the 1980s I worked for a large Government department in Gloucestershire. The local tech college (not Gloucester) ran a course on "C" programming so our boss signed us up for it. The "notes" looked as though they'd been written in the pub the night before and the machines were on a flaky network where you had to quit the editor in the "proper" way otherwise the whole network crashed. We reported this to our boss who managed to get the course fees returned to his acount.
Hitchin BID manager Tom Hardy tweeted Lord Sugar this lunchtime to say: “Your Amstrad computer has been printing our Hitchin Festival tickets for 25 years! Still going strong with 50,000 tickets printed over the years. Is this a record?”
http://www.thecomet.net/news/business/lord-sugar-salutes-amstrad-pc-still-printing-hitchin-festival-tickets-after-25-years-1-5630168
This is a true story because I was living in Scarborough at the time (1980s) and received one of the publicity leaflets from BT praising their new domestic fire detection system which would sense a fire and automatically alert the fire brigade. I received the leaflet a few weeks before a catastrophic fire destroyed Scarborough's main telephone exchange which was only manned during office hours and did not have one of their wonderful new fire detection systems. The local paper had great fun with that story
Apocryphal story from the 1960s when a brand-new high-tech factory opened with great ceremony. The MD was boasting of his state-of-the-art fire alarm system which dialled the XXX fire station which was a couple of miles away and a tape loop continually broadcast a message "There is a fire at Bloggs & Co factory". This was, allegedly, to avoid delays inherent in the 999 system and get the fire brigade to the scene more quickly.
One night there was a fire at Bloggs & Co factory and it burned to the ground before the fire brigade arrived. The subsequent investigation discovered that the fire alarm system had worked perfectly. However, when the automated "There is a fire at Bloggs & Co Factory" was being sent over & over again the local telephone exchange's automated system broadcast a taped response "The telephone number for XXX fire station has changed to 01234 567890, please replace your receiver and re-dial"
About 25 years ago it seems that Microsoft decided that drive F: was special and could be used for all sorts of fancy debugging procedures. The result was that any drive allocated the letter F ran extremely slowly. I can't remember how I discovered this information but it quickly became well-known in the large Government where I worked (and had just scrapped OS/2 in favour of MS Windows).
And more recently as in the case of the SS France in 2003.
"Boiler No. 23, located on the starboard side of the boiler room, had ruptured. The boiler contained about 20 tons of water operating at a temperature of about 528º F under a pressure of about 60 bar (870 pounds per square inch [psi]). In the normal atmospheric pressure of the aft boiler room (14.7 psi), the pressurized hot water rapidly expanded in volume about 1,260 times into steam"
https://www.ntsb.gov/investigations/AccidentReports/Reports/MAB0703.pdf
There was one of those large toasters with a vertical conveyer belt in the airmen's mess at RAF Driffield (1961 or so). Apart from the arguments about whose slice it was that had just dropped into the collection tray there was the excitement of a piece of bread that became trapped in the mechanism and proceded to cremate itself. Huge quantities of smoke tended to put you off your breakfast but the cooks just took as normal behaviour and carried on as usual. We often wondered what would happen if there was a real fire in the mess!
I got an email from my bank (Santander) at 9pm on Friday 27 April to say that the new debit card that I had ordered was on its way. I was suspicious as I'd not ordered a new debit card. The email was addressed to me personally but the 4 digit number that was supposed to be the last 4 digits of my debit card was incorrect. I phoned Santander and after a lengthy wait spoke to a fairly helpful chap in the UK. He explained that my old debit card had been compromised and they were sending a new one; as to the last 4 digits quoted on the email - they were the last 4 digits of the new debit card which was in the post. He said (in so many words) that the email was a bit of boilerplate that they could not change.
It was only the next day that I realised that I'd been in Kirkwall on Tuesday 24 April and, needing some cash, had used the nearest ATM. Alas, it was the TSB and my card was rejected so I went to the next ATM and was successful. Presumably just using the TSB's ATM and getting my card rejected was enough to get my debit card considered as compromised.
The new card arrived on Tuesday 1 May and has worked OK
The Commodore PET had a loudspeaker which had its own memory address. You could peek/poke it and create sounds of various pitches and volumes. I created a 6502 machine code routine which produced the sound of a police car siren or a WW2 air raid siren - very dramatic and very loud! I cannot remember whether the first IBM PCs had the same facility or not
My first OU course was PM957 "Computing & computers" in 1977. I lived in Brora, Sutherland and all my coding (OU BASIC) was handwritten and sent off to the OU computer centre where it was keyed in and run, the results (warts & all) was then posted (Royal Mail) back to me. Later I did another OU course in computing which had HEKTOR, a small machine akin to the VIC-20 which fed an analogue TV. Great course, began hand assembly before progressing to a "proper" assembler and finally a version of BASIC).
Later in 1984 I worked in R&D for a large government department which bought a few Commodore PETs. With the invaluable help of Raeto West's hefty handbook I taught myself 6502 assembler and produced some useful programs; some of which included speed-up tricks which avoided floating point operations such as multiplying by 10 by shifting left 3 times and then adding the original number twice. I remember that all the IEEE488 (GPIB) routines were hard coded into ROM and that there were a couple of spare sockets for "home-brewed" EPROMS.
Then we got the first IBM PCs and shifted to "C" using the Aztec compiler. Still good fun though
This happened to an Open University researcher who stored several years worth of data on a local machine and had no backup that was remote from his/her office, a fire destroyed most of the equipment but the manufacturer managed to recover most (but not all) of the data from the fire-damaged disk - an expensive recovery process. Alas, I cannot find any record of this event online
Oh yes! I'm red/green colour blind and it was a long time (several years!) before I knew that Microsoft Word had different coloured underlining to distinguish between grammatical and spelling errors. I was a programmer for a large Civil Service department based in Cheltenham and there was a rule that colour should never be used to distinguish between items/icons on a computer screen
I was born in 1943 and first encountered a computer in 1985 when working for a large Government department with HQ in Cheltenham. The computer was a Commodore Pet which, together with Raeto West's invaluable handbook, enabled 2 or 3 of us to produce some useful programs in 6502 assembler - despite all the Scientific Officers looking down their noses as they produced similar programs in high level language on their PDP machines. A year or so later we got the first IBM PC and an Aztec "C" compiler and never looked back!
My late wife took a course "I.T. for the terrified" which ran for six two-hour Saturday morning sessions. The first session was purely about games (including Solitaire) which gave everyone a basic grounding (and confidence) in the use of a mouse. The final session was an introduction to The Internet with dire warnings of what could appear on the computer screen if you made just a simple spelling mistake in your search - using "Ask Jeeves" or similar.