windows nt Archives

Home » windows nt

What happened to Digital Equipment Corporation?

Dave Farquhar Retro Computing June 20, 2017October 3, 20181980s, 1990s, altavista, amiga, apple, commodore, compaq, computer security, d-link, DEC, Digital Equipment Corporation, Digital Research, firewall, hp, IBM, intel, lexmark, linksys, macintosh, netgear, PIP, spam, syntax, unix, windows nt, x86

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?

There’s a short answer and a long answer.

Dave Farquhar

David Farquhar is a computer security professional, entrepreneur, and author. He started his career as a part-time computer technician in 1994, worked his way up to system administrator by 1997, and has specialized in vulnerability management since 2013. He invests in real estate on the side and his hobbies include O gauge trains, baseball cards, and retro computers and video games. A University of Missouri graduate, he holds CISSP and Security+ certifications. He lives in St. Louis with his family.

dfarq.homeip.net

Advantages and disadvantages of Windows NT 3.1

Dave Farquhar Retro Computing May 18, 2017November 29, 20181990s, AIX, amiga, apple, best buy, DEC, hp, IBM, intel, linksys, motorola, Orange Book, proprietary unix, unix, windows nt, Windows XP, wrt54g, x86

I’ve talked a lot about the advantages and disadvantages of old milestone operating systems. But what were the advantages and disadvantages of Windows NT 3.1? That’s a fair question.

Dave Farquhar

dfarq.homeip.net

Advantages and disadvantages of Windows 3.0

Dave Farquhar Retro Computing January 19, 2016February 28, 2021AMI, amiga, excel, Microsoft Office, new hardware, Once Windows, radio shack, unix, windows nt, Windows XP

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 Microsoft 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.

Dave Farquhar

dfarq.homeip.net

Windows 10 is out. I say you should upgrade, just not necessarily right now.

Dave Farquhar Uncategorized July 29, 2015July 25, 2015acer, new hardware, Technical Preview, vista, Windows 10, windows 2000, windows 7, windows 8, windows 98, windows nt, Windows Vista, Windows XP

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.

Dave Farquhar

dfarq.homeip.net

Yes, we need to run vulnerability scans inside the firewall

Dave Farquhar security February 18, 2015February 15, 2015AIX, firewall, malware, old windows, unix, vulnerability, windows 2000, windows nt

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.

Dave Farquhar

dfarq.homeip.net

Why every breach is different

Dave Farquhar security February 6, 2015February 5, 2015Adobe Acrobat, Adobe Flash, breach, Microsoft Office, unix, vulnerability, windows nt

I’ve grown used to being asked what unpatched vulnerability was used in the most recent breach, in an effort to make sure some other company is protected.

I appreciate the desire to learn from other companies’ mistakes and not repeat them. But there are several reasons why the answer to that question is complicated, and not necessarily helpful.

Dave Farquhar

dfarq.homeip.net

Don’t wait for Service Pack 1

Dave Farquhar security, Windows January 8, 2015January 5, 2015Windows 10, windows 2000, windows nt, Windows Server, Windows XP

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.

“Shouldn’t we wait for Service Pack 1?”

I went in for the kill. Read more

Dave Farquhar

dfarq.homeip.net

What is Winshock?

Dave Farquhar security, Windows December 3, 2014December 2, 2014antivirus, code execution, excel, IBM, ips, Patch Tuesday, SSL, symantec, TLS, vulnerability, windows 7, windows 8, windows 9x, windows nt, Windows Server, Windows XP

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.

Dave Farquhar

dfarq.homeip.net

Predicting the future, circa 2003

Dave Farquhar security, Windows September 26, 2014March 18, 2020BSD, discipline, podcast, SQL, unix, VPN, WAN, windows nt

In the heat of the moment, I searched my blog this weekend for quotes that could potentially be taken out of context and found something rather prophetic that I wrote in the heat of the moment 11 1/2 years ago:

Keeping up on Microsoft security patches is becoming a full-time job. I don’t know if we can afford a full-time employee who does nothing but read Microsoft security bulletins and regression-test patches to make sure they can be safely deployed. I also don’t know who would want that job.

Who ended up with that job? Me, about a year after I left that gig. It actually turned out I was pretty good at it, once I landed in a shop that realized it needed someone to do that job, and utilized that position as part of an overall IT governance model.

Dave Farquhar

dfarq.homeip.net

Computer, how old are you?

Dave Farquhar Windows July 11, 2014July 5, 2014command prompt, excel, unix, windows nt

Yesterday I wrote about finding old computers. Here’s how I determine how old a computer is.

There’s a registry key called HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\InstallDate that stores the system build time in Unix format (the number of seconds since 1 January 1970) and hexadecimal. With a few mad skilz you can make that data human-readable.

Dave Farquhar

dfarq.homeip.net

← Previous