Are you getting a 0xc1900201 error installing Windows 10? I got both that and 0xc1900200. Here’s how I fixed it.
I upgraded my venerable Dell E1505 to Windows 10 over the weekend. It was harder than it needed to be, but I got it running. It’s an old machine, but the CPU is fast enough to run Windows 10, and if you max out its memory and put an SSD in it, I think it may even run Windows 10 better than it ran Windows 7.
Marx made five different type of couplers between 1934 and 1974. If you’ve never seen Marx couplers explained before, here’s a primer on how to identify them and use them together. And I even have a few repair tips if you need them.
“Daniel” from “Microsoft” called me the other day. The number looked halfway legit so I picked up. He out and out claimed to be from Microsoft and said he was getting alerts from my computer. His voice sounded familiar–I think I’d talked to him before.
Insurance companies are starting to offer discounts if you plug one of their devices, often called a RightTrack or SnapShot, into your car’s ODB2 port.
One of my college buddies asked me about them when his insurance company offered his family a 5% discount to plug these into their cars, and then make them eligible for up to another 25%. Those are compelling numbers. So what are the potential drawbacks?
I was trying to install some software last week and I got an NSIS error. The message certainly suggests corrupt downloads, but corrupt downloads are relatively rare, and when they happen, redownloading it ought to clear that up. Getting two of these failures in a row with different programs is really a freak occurrence, so I started looking for another problem.
CP/M was, as you probably know, the first popular microcomputer operating system. It was good but imperfect, and its cryptic command for copying files, PIP, is often cited as an example. Copy makes sense. Even the Unix equivalent, cp, makes sense–it’s copy without the vowels. But what does PIP mean? What’s the origin of CP/M’s PIP command?