Some 90s computer brands are the same as today, but a lot more companies played in the field than now. Profit margins were higher then, so industry consolidation wasn’t the matter of survival that it is now.
Digital Equipment Corporation was perhaps the second most important computer company in history, behind IBM. Its minicomputers challenged IBM, and, indeed, Unix first ran on a DEC PDP-7. DEC’s Alpha CPU was one of the few chips to make Intel nervous for its x86 line. It created the first really good Internet search engine. In a just and perfect world, DEC would still be dominating. Instead, it faded away in the 1990s. What happened to Digital Equipment Corporation, or DEC?
The Compaq Deskpro 386, announced in September 1986, was a landmark IBM PC compatible computer. The first fully 32-bit PC based on the Intel 386, its release took the leadership of the PC ecosystem away from IBM, and Compaq became the leader.
Compaq was no upstart by 1986. Its Compaq Portable was a runaway success earlier in the decade, and Compaq was a darling of the industry. The Deskpro 386 solidified Compaq’s position as an industry innovator.
I hear the question from time to time what the advantages and disadvantages of Windows 3.0 were. Windows 3.0, released in May 1990, is generally considered the first usable version of Windows. The oft-repeated advice to always wait for Microsoft’s version 3 is a direct reference to Windows 3.0 that still gets repeated today, frequently.
Although Windows 3.0 is clumsy by today’s standards, in 1990 it had the right combination of everything to take the world by storm.
Windows 10 is out today. Of course I’ve been getting questions about whether to upgrade from Windows 7 to 10, and I’ve been seeing mixed advice on upgrading, though some of that mixed advice is regarding Microsoft history that isn’t completely relevant today.
My advice is to upgrade immediately if you’re running Windows 8 or 8.1, and to wait, perhaps six months, if you’re running Windows 7, but I still think you should do it. I’ll explain.
I got an innocent question last week. We’d been scanning an AIX server with Nexpose, a vulnerability scanner made by Rapid7, and ran into some issues. The system owner then asked a question: The server is behind a firewall and has no direct connection to the Internet and no data itself, it’s just a front-end to two other servers. Is there any reason to scan a server like that?
In my sysadmin days, I asked a similar question. Nobody could give me an answer that was any better than “because reasons.” So I’ll answer the question and give the reasons.
I was on a conference call discussing the Microsoft product lifecycle with several coworkers and our Microsoft-assigned support engineers when someone asked if a server version of Windows 10 was going to come out.
The Microsoft rep said no comment. Then I chimed in.
“We need to assume they will release a server version, probably about six months after the desktop version, and we need to start testing and preparing to deploy it when it comes out,” I said.
So the other day I got blindsided with a question at work: What are we doing about Winshock. Winshock, I asked? I had to go look it up, and I found that’s what they dubbed what I’ve been calling MS14-066, the vulnerability in Schannel, which is Microsoft’s implementation of SSL/TLS for Windows.
Based on that, I’d argue it has more in common with Heartbleed than Shellshock, but I guess “Winshock” is catchier than “Winbleed.”
Then the lead of another team asked me to brief his team on Winshock. I actually managed to anticipate all but three of the questions they asked, too, which was better than I expected. Some of what I shared with them is probably worth sharing further.