Many of you know that I no longer use Facebook for my personal stuff. However, there are still work things to do, although I’ve noticed Facebook pages get more and more useless by the day. Here are the stats for my Facebook page:
And now, you can no longer post links to YouTube videos on to pages. Facebook just gets stuck, trying to ‘import’ the link. I’ve tried this from different accounts and had to give up, opting to upload directly into Facebook, which is probably their (unannounced) plan anyway.
YouTube’s uploading took ages, too. Or, rather, it took ages to find an uploading link. Dailymotion and Vimeo have, by far, superior interfaces.
Yet, ladies and gentlemen, these are among the top three websites in the world. You truly have to wonder why, in the face of overwhelming evidence of tracking in one case, and privacy breaches in another. Facebook had been pretty hopeless as a traffic referrer anyway, and I wouldn’t be surprised if others woke up to the fact it is worsening as a business platform.
There was an Epson bag hanging from the back of my bedroom door, hidden by larger bags. I opened it up to discover brochures from my visit to a computer fair in 1989 (imaginatively titled Computing ā89), and that the bag must have been untouched for decades.
I’ve no reason to keep its contents (if you want it, message me before Thursday, as the recycling comes the morning after), but I wanted to make some scans of the exhibitors’ catalogue for nostalgia.
Let’s start with the cover. It’s sponsored by Bits & Bytes. Kiwis over a certain age will remember this as the computer magazine in this country.
You can tell this is a product of the 1980s by the typesetting: someone couldn’t be bothered buying the condensed version of ITC Avant Garde Gothic, so they made do with electronically condensing Computers and Communications. In fact, they’re a bit light on condensed fonts, full stop, as they’ve done the same with the lines set in Futura.
While the practice is still around, the typeface choices mark this one out as a product of its time.
Inside is a fascinating article on the newfangled CD-ROM being a storage medium. Those cuts of Helvetica and Serifa are very 1980s, pre-desktop publishing. It should be noted that Dr Jerry McFaul remained with the USGS, where he had been since 1974, till his retirement. The fashions are interesting here, as is ITC Fenice letting us know that he’s speaking at the Terrace Regency Hotel, a hotel I have no recollection of whatsoever. I can only tell you that it must have been on the Terrace.
The other tech speakers have a similar look to the visiting American scientist, all donning suitsāsomething their counterparts in 2018 probably wouldn’t today. In fact, the suit seems to be a thing of the past for a lot of events, and I often feel I’m the oldster when I wear mine.
The article itself makes a strong case for CD-ROM storage, being more space-saving and better for the environment: it’s interesting to know that the ‘depletion of the ozone layer’ was a concern then, though 30 years later we have been pretty appalling at doing anything about it.
The second article in the catalogue of any note was on PCGlobe, supplied to the magazine on 5Ā¼-inch diskette. Bits & Bytes would have run the catalogue as part of the main magazine, and did a larger run of these inner pages, back in the day when printing was less flexible.
It’s a fascinating look back at how far we’ve come (on the tech) and how far we haven’t come (on the environment). Next year, we’ll be talking about 1989 as ā30 years ago,’ yet we live in an age where we’re arguing over Kylie Jenner’s wealth. Progress?
I taught 180 people at tertiary level in 1999ā2000.
Gutted that a second has passed away.
Most of them were kids when I taught them. Lost one to a brain bleed in 2015, just lost another to cancer.
Look after yourselves out there, and live life to the full. Tell those whom you love that you do.
Everybody wants PS2. Still from The Professionals episode ‘Servant of Two Masters’.
I readĀ this article inĀ The Guardian, thinking: surely, after Microsoft rolled out some terrible updates, it wouldnāt be so stupid as to do one that bricks customersā computers again? Especially after the bug was reported a month ago.
The April update worked reasonably well, though I lost my wallpaper. But everything else was there, and I was using Vivaldi, which is a Chromium-based browser.
Then I rebooted.
That was it: my computer was bricked. The first boot, a very tiny rotating circle eventually appeared, but I couldnāt do anything except move the circle with my mouse. Subsequent reboots just resulted in a black screenāsomething, I must say, I had already encountered with an earlier Windows update that saw my having to take the PC back to the shop.
I rebooted the computer three times to force it into recovery mode, but then there was another problem: neither mouse nor keyboard worked. It was as though USB was dead.
Out of sheer luck I had a PS/2 keyboard that was unused, and after more forced reboots, I was able to use the old keyboard to look at various recovery options. Remember: no input device on USB works, and this was a bug that had surfaced with the last update in February.
Forget system restore: the April update is a fresh OS, so there are no restore points.
I had no choice but to roll back to the previous version I had installed.
And here I am, back again, an hour wasted. It would probably be longer if I didnāt have an SSD.
Microsoft, get your QC sorted, because this current model youāve employed over the last few years simply does not work. I have spent more hours on these updates than with any OS you have ever rolled out, and that includes XP Service Pack 3 on a comparatively ancient system.
And if you get stuck like I do, and like all those inĀ The Guardianās article did, I hope you still have a way of plugging in a PS/2 device and have an old-school keyboard lying around.
Above:Autocade can be hard workāand sometimes you have to put up less exciting vehicles, like the 2001ā7 Chrysler Town & Country, for it to be a useful resource.
March 8, 2018 marks 10 years of Autocade.
Iāve told the story before on this blog and elsewhere, about how the site came to beāannoyed by the inaccuracies and fictions of Wikipedia (who said the masses would be smart enough to get rid of the mistakes?), I took a leaf out of the late Michael Sedgwickās book and created a wiki that had brief summaries of each model, the same way Sedgwick had structured his guides. I received an emailed threat from a well known British publisher (Iām looking at you, Haymarket, and as predicted in my reply, your thoughts proved to be totally baseless) when we started, and 12Ā½ million page views later, weāre on 3,628 models (I think we finished the first day on 12), with our page on the Ford Fiesta Mk VII leading the count (other than the home page). Autocade began as a wiki but with so many bots trying to sign up, I closed off those registrations. There have really been about six contributors to the site, all told: myself and Keith Adams for the entries, Peter Jobes and Nigel Dunn for the tech, and two members of the public who offered copy; one fed it in directly back in the day when we were still allowing wiki modifications. I thank everyone for their contributions.
A few years ago, I began running into people online who used Autocade but didnāt know I was behind it; it was very pleasing to see that it had become helpful to others. It also pleased me tremendously to see it referenced in Wikipedia, not always 100 per cent correctly, but as Autocade is the more accurate site on cars, this is the right way round.
When a New Zealand magazine reviewed us, the editor noted that there were omissions, including his own car, a Mitsubishi Galant. Back then we were probably on 1,000 models, maybe fewer. All the Galants are now up, but Autocade remains a work in progress. The pace of adding pages has declined as life gets busierāeach one takes, on average, 20 minutes to research and write. You wouldnāt think so from the brevity, but I want it to be accurate. Iām not perfect, which is why the pages get changed and updated: the stats say weāre running on 3Ā·1 edits per page.
But it looks like weāre covering enough for Autocade to be a reasonably useful resource for the internet public, especially some of the more obscure side notes in motoring history. China has proved a challenge because of the need to translate a lot of texts, and donāt think that my ethnicity is a great help. The US, believe it or not, has been difficult, because of the need to calculate cubic capacities accurately in metric (I opted to get it right to the cubic centimetre, not litres). However, it is an exciting time to be charting the course of automotive history, and because there are still so many gaps from the past that need to be filled, I have the chance to compare old and new and see how things have moved on even in my four-and-a-half decades on Earth.
Since Sedgwick had done guides up to 1970, and paper references have been excellent taking us through the modern motor carās history, I arbitrarily decided that Autocade would focus on 1970 and on. There are some exceptions, especially when model lines go back before 1970 and it would be a disservice to omit the earlier marks. But I wanted it to coincide roughly with my lifetime, so I could at least provide some commentary about how the vehicle was perceived at the time of launch. And the ā70s were a fascinating time to be watching the motor industry: those nations that were confident through most of the 20th century with the largest players (the US and UK) found themselves struggling, wondering how the Japanese, making scooters and motorcycles just decades before, were beating them with better quality and reliability. That decadeās Japanese cars are fascinating to study, and in Japan itself there is plenty of nostalgia for them now; you can see their evolution into more internationally styled product, rather than pastiches of othersā, come the 1980s and on. The rise of Korea, Spain, China, India, Turkey, México and other countries as car-exporting nations has also been fascinating to watch. When Autocade started, Australia still had a domestic mass-produced car industry, Chrysler was still owned by Americans, and GM still had a portfolio of brands that included Pontiac and Saturn.
I even used to go to one of the image galleries and, as many cars are listed by year, let the mouse scroll down the page. You can see periods grouped by certain colours, a sign of how cars both follow and establish fashion. There are stylistic trends: the garishness of smog-era US cars and the more logical efficiency of European ones at the same time; smoother designs of the 1980s and 1990s; a creeping fussiness and a concentration on showing the brandās identity in the 2000s and 2010s. As some of the most noticeable consumer goods on the planet, cars make up a big part of the marketing profession.
The site is large enough that I wouldnāt mind seeing an academic look at industry using the data gathered there; and I always thought it could be a useful book as well, bearing in mind that the images would need to be replaced with much higher-resolution fare.
For now, Iām going to keep on plodding as we commence Autocadeās second decade. The Salon de Genève has brought forth some exciting débutantes, but then I should get more of the Chrysler Town & Country vans up ā¦
I came across a thread at Tedium where Christopher Marlow mentions Pandora Mail as an email client that took Eudora as a starting-point, and moved the game forward (e.g. building in Unicode support).
As some of you know, Iāve been searching for an email client to use instead of Eudora (here’s something I wrote six years ago, almost to the day), but worked with the demands of the 2010s. I had feared that Eudora would be totally obsolete by now, in 2018, but for the most part itās held up; I remember having to upgrade in 2008 from a 1999 version and wondering if I only had about nine years with the new one. Fortunately, itās survived longer than that.
Brana BujenoviÄās Pandora Mail easily imported everything from Eudora, including the labels I had for the tables of contents, and the personalities I had, but itās not 100 per cent perfect, e.g. I canāt resize type in my signature file. However, finally Iāve found an email client that does one thing that no other client does: I can resize the inbox and outbox to my liking, and have them next to each other. In the mid-1990s, this was one of Eudoraās default layouts, and it amazed me that this very efficient way of displaying emails never caught on. I was also heartened to learn from Tedium that Eudora was Apple co-founder Steve Wozniakās email client of choice (āThe most important thing I use is Eudora, and that’s discontinued’). Iām in good company.
However, this got me thinking how most users tolerate things, without regard, in my opinion, to whatās best for them. Itās the path of least resistance, except going down this path makes life harder for them.
The three-panel layout is de rigueur for email clients todayāall the ones Iāve downloaded and even paid good money for have followed this. Thunderbird, Mailbird, the oddly capitalized eM. All have had wonderful reviews and praise, but none allow you to configure the in- and outbox sizes. Hiriās CEO says thatās something theyāre looking at but right now, theyāre not there, either. Twenty-plus years since I began using Eudora and no one has thought of doing this, and putting the power of customization with the user.
But when did this three-panel layout become the standard? I can trace this back to Outlook Express, bundled with Windows in the late 1990s, and, if Iām not mistaken, with Macs as well. I remember working with Macs and Outlook was standard. I found the layout limiting because you could only see a few emails in the table of contents at any given time, and I usually have hundreds of messages come in. I didnāt want to scroll, and in the pre-mouse-wheel environment of the 1990s, neither would you. Yet most people put up with this, and everyone seems to have followed Outlook Expressās layout since. Itās a standard, but only one foisted on people who couldnāt be bothered thinking about their real requirements. It wasnāt efficient, but it was free (or, I should say, the licence fee was included in the purchase of the OS or the computer).
āIt was freeā is also the reason Microsoft Word overtook WordPerfect as the standard word processor of the 1990s, and rivals that followed, such as Libre Office and Open Office, had to make sure that they included Word converters. I could never understand Word and again, my (basic) needs were simple. I wanted a word processor where the fonts and margins would stay as they were set till I told it otherwise. Word could never handle that, and, from what I can tell, still canāt. Yet people tolerated Wordās quirks, its random decisions to change font and margins on you. I shudder to think how many hours were wasted on people editing their documentsāWord canāt even handle columns very easily (the trick was usually to type things in a single column, then reformatāso much for a WYSIWYG environment then). I remember using WordPerfect as a layout programme, using its Reveal Codes featureāit was that powerful, even in DOS. Footnoting remains a breeze with WordPerfect. But Word overtook WordPerfect, which went from number one to a tiny, niche player, supported by a few diehards like myself who care about ease of use and efficiency. Computers, to me, are tools that should be practical, and of course the UI should look good, because that aids practicality. Neither Outlook nor Word are efficient. On a similar note I always found Quattro Pro superior to Excel. With Mac OS X going to 64-bit programs and ending support for 32-bit there isnāt much choice out there; Iāve encountered Mac Eudora users who are running out of options; and WordPerfect hasnāt been updated for Mac users for years. To a large degree this answers why the Windows environment remains my choice for office work, with Mac and Linux supporting OSs. Someone who comes up with a Unicode-supporting word processor that has the ease of use of WordPerfect could be on to something.
Then you begin thinking what else we put up with. I find people readily forget or forgive the bugs on Facebook, for example. I remember one Twitter conversation where a netizen claimed I encountered more Facebook bugs than anyone else. I highly doubt that, because her statement is down to short or unreliable memories. I seem to recall she claimed she had never experienced an outageāwhen in fact everyone on the planet did, and it was widely reported in the media at the time. My regular complaints about Facebook are to do with how the website fails to get the basics right after so many years. Few, Iām willing to bet, will remember that no oneās wall updated on January 1, 2012 if you lived east of the US Pacific time zone, because the staff at Facebook hadnāt figured out that different time zones existed. So we already know people put up with websites commonly that fail them; and we also know that privacy invasions donāt concern hundreds of millions, maybe even thousands of millions, of people, and the default settings are “good enough”.
Keyboards wider than 40 cm are bad for you as you reach unnecessarily far for the mouse, yet most people tolerate 46 cm unless theyāre using their laptops. Does this also explain the prevalence of Toyota Camrys, which one friend suggested was the car you bought if you wanted to ātell everyone you had given up on lifeā? It probably does explain the prevalence of automatic-transmission vehicles out there: when I polled my friends, the automaticāmanual divide was 50ā50, with many in the manual camp saying, āBut I own an automatic, because I had no choice.ā If I didnāt have the luxury of a āspare carā, then I may well have wound up with something less than satisfactoryābut I wasnāt going to part with tens of thousands of dollars and be pissed off each time I got behind the wheel. We donāt demand, or we donāt make our voices heard, so we get what vendors decide we want.
Equally, you can ask why many media buyers always buy with the same magazines, not because it did their clients any good, but because they were safe bets that wouldnāt get them into trouble with conservative bosses. Maybe the path of least resistance might also explain why in many democracies, we wind up with two main parties that attract the most votersāspurred by convention which even some media buy into. (This also plays into mayoral elections!)
Often we have ourselves to blame when we put up with inferior products, because we havenāt demanded anything better, or we donāt know anything better exists, or simply told people what weād be happiest with. Or that the search for that product costs us in time and effort. Pandora has had, as far as I can fathom, no press coverage (partly, Brana tells me, by design, as they donāt want to deal with the traffic just yet; itās understandable since there are hosting costs involved, and heād have to pay for it should it get very popular).
About the only place where we have been discerning seems to be television consumption. So many people subscribe to cable, satellite, Amazon Prime, or Netflix, and in so doing, support some excellent programming. Perhaps that is ultimately our priority as a species. Weāre happy to be entertainedāand that explains those of us who invest time in social networking, too. Anything for that hit of positivity, or that escapism as we let our minds drift.
Iām fascinated by theĀ 1970Ā½ Ford FalconĀ for a number of reasons. The first is the obvious one: rarity. This car was built for only half a model year, from January to August 1970. If you think it looks like a contemporary Torino, youāre right: itās basically a very stripped-down Torino. Yet you could spec it with any of the engines from the Torino, including the 429 inĀ³ V8 (and some did). Which brings me to the second reason: why would anyone really bother with it, if you could get a Torino for a bit more? (That answers why this car only lasted half a model year.) And that leads me to the third reason: what was going through Fordās mind at the time? Thatās where it gets interesting.
At this time, Ford was undergoing managerial changes, with Henry Ford II firing Bunkie Knudsen (who had been lured away from GM). That happened in September 1969, by which time the decision to go ahead with the Falcon had already been made. This is, in other words, a Knudsen initiative.
Federal regulations made the 1966ā70 Falcon obsolete because it had a dash-mounted starterāthe rule was that they had to be in the column. However, itās curious that Ford made this call to put the Falcon nameplate on a mid-sizer, considering it had made its name as an āeconomyā car (by US standards). If you read the brochure, youāll find that this was all about size. Ford bragged that the car was 2 ft longer. Yet for this half-model year, it was still marketed as an āeconomyā car.
I imagine as the US headed into the 1970s, there was no sign of the fuel crisis on the horizon, so there was nothing wrong about size. Why not spoil the average Falcon buyer, used to a smaller car, with something much larger? Hadnāt upsizing already happened on every other model line out thereāby this point the Mustang was about to grow into a monstrosity with massive C-pillars and terrible rear visibility?
Ford (and the other Big Four makers) had been known to blow one model line up, then start another little one, and the Maverick had already been launched for 1970, and was now doing the compact work. By that logic, Falcon could grow more, even though other solutions might have been to either replace the Falcon with the Maverick or simply shift the Falcon nameplate to the Maverickābut both would have involved ādownsizingā, and in 1970 that was not in the US car industryās vocab. The panic hadnāt set in yet.
Fourthly, this is a beautiful shape. Unnecessarily big (till you consider it had to accommodate the 429), but a beautiful shape. The 1970s hadnāt really started in earnest, so we hadnāt seen some of the really garish shapes that were to come. This has that 1960s classicism coupled with 1970s uncertainty. Thereās still some optimism with jet-age inspiration, but the lack of practicality foreshadowed the style-first, single-digit mpg āroad-hugging weightā cars that were round the corner, cars which no one truly needed but Detroit, in its optimism (or blindness), believed Americans did. Thereās still something very honest about the last US Falcon. After this, only the Australians and Argentinians kept things alive, but those are other stories.
Itās a little disappointing to note that Autocade has taken slightly longer to reach 12 million page views: it ticked over to its new milestone earlier today. I really had hoped that weād get there before 2017 was out, but it was not to be.
Part of it might have been the slower rate of models being put upālifeās been busy, and a site that earns a fairly small amount of money compared to our other businesses doesnāt warrant as much time. But 100 models have gone up since June 2017, when Autocade reached its 11 million milestone, with the 3,600th model the Nissan Rasheen (and no, I didnāt plan this oneāitās quite an oddball vehicle).
So hereās the running tally as Iāve been keeping on this blog, for really no reason other than pedantry.
March 2008: launch
April 2011: 1,000,000 (three years for first million)
March 2012: 2,000,000 (11 months for second million)
May 2013: 3,000,000 (14 months for third million)
January 2014: 4,000,000 (eight months for fourth million)
September 2014: 5,000,000 (eight months for fifth million)
May 2015: 6,000,000 (eight months for sixth million)
October 2015: 7,000,000 (five months for seventh million)
March 2016: 8,000,000 (five months for eighth million)
August 2016: 9,000,000 (five months for ninth million)
February 2017: 10,000,000 (six months for tenth million)
June 2017: 11,000,000 (four months for eleventh million)
January 2018: 12,000,000 (seven months for twelfth million)
Itās a shame that the four-month time-frame needed to reach 11 million could be an anomaly rather than part of a trend.
I also wonder whether the odd PHP errorāwe have had quite a few since we began hosting at AWSāhas impacted on search-engine rankings. However, server management has become far, far more complex over the last couple of decades, and the controls I see at AWS mean nothing to me as someone outside the computing industry. The help pages may as well be in Serbian. The notion that software gets easier to use and the expectation that this level of computing would become democratized have not come to pass, certainly not over the last 10 years. It seems the industry wants to sew things up for itself, and the last thing needed are amateurs like me getting into the nuts and bolts. Iām not Facebook or Google: I canāt afford heaps of employees to look after this stuff. (Or, in Googleās case, maybe a couple here and there.)
Incidentally, I may begin removing the sharing links under each headline soon. Iām concerned about the standard Facebook ‘like’ button tracking readers, and there are Po.st links under āShare this pageā to the top left of this page (if browsing via desktop) if you want to show Facebook friends something from here. Po.st does have its own cookies (linked to a company called Radium One), but itās far easier to opt out of those through their site. I’m unconvinced that anyone can opt out of Facebook’s data collection.
Amazingly, Microsoft Windows 10 Creators fall update arrived last week on my desktop PC, and it took all of 25 minutes to do (running a Crucial 525 Gbyte SSD). (Add an extra 35 minutes for me to put my customizations back in.) This is in contrast to the Anniversary update, which took 11 attempts over many months, including one that bricked my desktop PC and necessitated repairs back at PB Technologies.
However, I began getting regular BSODs, with the error message ‘Driver_IRQL_not_less_or_equal’ (all in caps), saying that tcpip.sys was the system file affected. An analysis of the minidump file using Windmp revealed that the cause was netio.sys (add āNetio!StreamInjectRequestsToStack+239ā if you want the full line).
There were few people with a similar issue, though I can always count on people in the industry who helpāusually itās folks like Cyrus McEnnis, whom I have known since we were in the third form at Rongotai College, or Aaron Taylor, or, in this case, Hayden Kirk of Layer3, who pointed me in the right direction (that it was either hardware or drivers).
First up, Windows Update isnāt any help, so letās not waste any time there.
Secondly, Device Manager was no help, either. Getting Windows to find updated drivers doesnāt necessarily result in the latest ones being downloaded. If the file that was crashing was tcpip.sys, then it does hint at something afoot with the TCP/IP, i.e. the networking.
I couldnāt solve it through a virus scan, since a full one would never complete before I got another BSOD. (In fact, one BSOD knocked out Avira, and it had to be reinstalled.)
It wasnāt Nvidia Control Panel, which was a regular culprit that people pointed to. I did remove and reinstall, just to be on the safe side, but that didnāt fix the problems.
I had used the āUpdate driverā option in the Device Manager for my network adapter, the Realtek PCIe GBE Family Controller #2, and while it did update, it wound up on version 1.
Without much to lose, I decided to feed in the full name of the adapter to look for drivers. Realtekās website took me here, where I selected the Win10 Auto Installation Program.
This installed a driver that was version 10, and last updated on December 1, 2017, according to Realtekās website (the driver is dated October 3, 2017).
So far Iāve been BSOD-free, and things appear to have settled down.
If youāre interested, I filed a bug report at Bleeping Computer, and my dump files are there.
Also remarkable is that my Lenovo laptop, which had attempted to install various Windows 10 updates for over a year, and failing each time (I estimate over 40 attempts, as usually I let it run most times I turn that laptop on; as of April 18 it was at 31 attempts). That laptop was on near-factory settings, so the fact no Windows update would work on it was ridiculous. (Iāve even seen this at shops, where display laptops have Windows update errors.)
Again, thereās plenty of advice out there, including the removal of Avira as the antivirus program. I tried that a few times over the first 31 attempts. It made no difference.
I am happy to report that over the weekend, the spring Creators Update actually worked, using the Update tool, and the only alteration I made to Avira was the removal of its System Speedup program.
And as of this morning, the same computer wound up with the newer fall update.
There havenāt been BSODs there but to me it confirms that Microsoftās earlier updates were incredibly buggy, and after two years theyāve managed to see to them.
I can report that the advice on the Microsoft forums didnāt work and I never needed to result to using the ISO update methods. The cure seemed to be patience and allowing multiple attempts. Since Windows 10 behaves differently each time you boot it up anyway, one of those times might have been compatible with the update patches.
Hopefully the above helps those who have been struggling with getting their Windows 10s to update. Iād advise against attempting some of the more extreme solutions, especially if your gut or your logic tells you that you shouldnāt need to go to those lengths just to update, when easier solutions worked perfectly fine when you were on Windows XP or Windows 7.
PS., December 12: After a day without crashes post-driver-update, they returned the following day. Investigations are ongoing ā¦ I’ve updated the Bleeping Computer link page.
P.PS.: Updated a remote-access program as well as Java (which hadn’t updated despite it having been set to automatic updates). During the former, I had another BSOD as it tried to shut down various network services. Wish I wrote down what they were. However, it does point at a networking issue. Also I saw some hackers in Latvia and the Netherlands try to get in to the system and blocked their IPs. Coincidentally, they had not attempted anything yesterday, which was the day I didn’t have BSODs.
P.P.PS.: Event Viewer revealed those hackers were really going for it. Hayden says it was a ‘port exhaustion hack’, which does, logically, affect TCP/IP. I’ve replaced the remote desktop program, though Java 8 wound back on the desktop because of another program I run. The PC has stayed on since the afternoon, so hopefully that is that. It does mean a day wasted on ITāand it does seem worrying that Windows 10 Creators fall has potentially more holes by default, or somehow falls over more easily when attacked. Those attacks had always come, but they never resulted in BSODs. It was, overall, more robust in updating but it may have some other problems, if the last few days are any indication.
The external HD was also moved to another USB port. There could be a connection to USBs, as it crashed once after my partner unplugged her phone, and on another occasion I distinctly heard the external HD activate just before a BSOD.
P.P.P.PS.: The above never solved it, but one month on, this might have done the trick.
