Outlook Classic also refused to start for many users - looks like it is trying to check/sync something upon start, and when 365 went down it borked completely
Turning off network completely during start-up of Outlook Classic helped to start it at least
but yeah, it all wants to be connected at all times these days...
I suppose so. It was just part of my job. My boss in my first job said to me something like "PCs are fun, but it's networking where the really interesting stuff is these days."
Compared to 21st century stuff, there was a little more complexity. TCP/IP was not yet standard and most office-level networking didn't talk TCP/IP. It was very expensive, complicated, fiddly, and so 1980s and early 1990s computers. just avoided it. We didn't use it at all.
There's a _lot_ of historical revisionism. Some of the Wikipedia articles are clearly edited by people too young to remember the time when PC networking caught on, and they don't believe the stories from back then and have edited them and changed the facts to fit what "everybody knows" these days.
So, no TCP. I worked in 5 full-time jobs in 2 countries, and set up and worked on hundreds of networks in multiple cities, different equipment, different industries and market sectors. I'd been building LANs and networking up businesses' PCs and Macs for decade before I ever saw TCP/IP.
No TCP/IP at all anywhere. Nobody cared. It was some complicated Unix thing and if you ran business computers they didn't run Unix or if they did they weren't networked so they had no network stack.
Forget the stories of "industry giants" like Sun or whatever. Only universities had them, spending someone else's money on these fantastically expensive American toys.
Before Mac OS X the world's most-successful best-selling commercial Unix was SCO Xenix. They sold millions of units. Xenix did not come with a C compiler, or X11, or a network stack. All of these were separate expensive optional extras so you didn't buy them if you didn't absolutely require them.
In America local telephone calls were free. In the rest of the world, local calls cost money. So, few BBSes, little use of download sites in the modem/dialup era: it was too expensive.
Countless hundreds of thousands of isolated standalone Unix boxes talking only to dumb terminals over RS-232, and backing up to tape drives or floppies. Even more standalone PCs, with the entire network in 1 building and no links to outside.
No comms = no security problems = no patches and no updates.
So, in real corporate life, what network protocol you used depended on whose kit you bought. Use Novell server OSes? Then you ran IPX/SPX. That's what Doom ran on.
Use Microsoft (and IBM) PC server OSes? Including 3Com? Then you ran NetBEUI. Wikipedia is wrong: it's not an API, it was a protocol.
Use Macs? You ran Appletalk (for file/printer sharing) over Appleshare (network protocol, over Localtalk (RS-423 cabling) or, later, Ethernet.
Use DEC VAX servers on the backend? Then you ran DECnet.
Really rich multinational, HQ in America? Maybe Banyan Vines, and you ran XNS. Never saw it in real life.
Use IBM big iron? Then you were rich and didn't use toys like PCs and Macs.
There were smaller ones too, like weird peer-to-peer networks that invented their own cabling, interconnect, protocols, everything. LANtastic. The $25 Network. SAGE MainLAN. Personal Netware. Netware Lite. (The latter 2 different and incompatible.)
Lots of protocols.
Only after Win95 and NT came along were OSes mainstream that could run more than one protocol at a time. In the DOS era, it took too much memory.
Now things are simpler on that one front -- "it's always DNS" just means it's always TCP.
But the OSes were in the tens of MB to maybe 100-200MB in size. The entire OS came on a 2-digit number of floppies holding 1.4MB each so there was a cap on size, and they shipped mostly fairly well debugged. It was common for companies to run version-point-zero products for years, unpatched and unupdated ever, because they worked.
When the OS is that small and relatively simple, with no VMs, no mix-and-match hypervisors, no containers, no stream of dozens of updates a day, it was easy to get to know both ends of the wire inside out and know exactly what they did.
When TCP/IP started to come in, in the late 1990s, over dialup at first, in came waves of malware. At the same time, OSes switched to shipping on huge optical media, and the pressure to keep them small and simple went away, so they got big and bloated fast.
And with that, along came dial-up internet, then from 1999, broadband: half a megabit a second, if you were rich. So, you could update the deployed software in the field. Result: it didn't have to be small and it didn't have to work, so it immediately stopped being small and stopped working at the time it shipped.
Ubuntu is to me one of the newest big Linux distros. It launched in 2004. I switched from SUSE to Ubuntu that year. When Ubuntu launched, it came on CD, and it took so little room -- just 300MB or so -- that Canonical filled the rest of the CD with Windows installers for all the apps bundled in Ubuntu. You could get used to the apps (Firefox, Thunderbird, LibreOffice, Pidgin, VLC, etc.) first, and then replace Windows with Ubuntu once you knew the apps.
Soon it filled the CD. A few years later it switched to DVD. Then it filled the DVD. Now it no longer fits on a DVD.
Apple switched to dual-layer DVDs -- much harder to copy. Microsoft invented various bogus "activation" systems. The pirates, weaned on Amiga games a decade before, just cracked them. So MS stopped updating pirate copies and thereby invented a vast malware industry and sabotaged its own products.
CD-ROMs, modems, and TCP/IP began the Great Enshittification. It applies to FOSS every bit as much.
Now, LLMs will blast apart those vast complex stacks of buggy junk, shooting them full of holes like the shielding bases in Space Invaders.
At the same time...
And the genAI bubble collapses, bankrupting lots of industry giants... but the tech scales down to high-end PCs.
As the same time...
China has its own chips and OSes, and while they aren't very fast, they are good enough. So it can get away with invading Taiwan and destroying the world chip industry.
Meanwhile climate change will destroy many of the chip and component making plants: the biggest El Niño in 1000 years is about to obliterate a lot of Asia.
Meanwhile, America tears itself apart in civil war, and the Gulf Stream collapses and Europe starves while it freezes. Nobody else can make chips or pay to maintain these vast fragile swiss-cheese OS stacks.
At the same time, chips get slower and memory gets much smaller, as the rest of the world has to make small cheap fabs, not the huge nanometre-scale ones that cost hundreds of billions and take decades to being online. Big fast computers get very expensive again, and stay that way.
With any luck, it will become impossible to deploy anything that is more than a few tens of thousands of lines of hand-inspected code, because a bot will prise it open in at most a few days and pwn you.
So we'll be back to double-digit megabytes RAM and megaHertz class CPUs, if we're lucky.
so this post is good I'd say - to at least know about this ! I didn't, so now I'm keen to find out more
reply