What went wrong with Windows Vista? If you were around when it launched, you probably wouldn’t argue with me if I said the things that went right were easier to count than the things that went wrong. Windows XP lived nearly forever because Vista was so bad.
If you still use Windows XP, I wish you’d stop. Seriously, for your safety and the safety of others, I wish you’d stop. The good news is you have some options, and you’ll probably be happier with one of them.
It’s been a long time since I’ve seen someone explain the benefits of defragmenting your computer hard drive. I do see a lot of misconceptions out there. I explained defragmenting in my 1999 book, so I’ll explain it again.
Part of the misconception is that things have changed. The tools have changed, yes. But the need hasn’t.
I can’t say I’ve ever seen the Windows registry explained well. It helps to think of the registry as a database. Microsoft loves databases, and they’ve been trying for decades to stuff as much database technology into Windows as they can. The registry was one of the earliest and most successful of those efforts.
Although it was controversial in the 1990s, the registry solved a very real problem. Windows 3.1 and earlier stored all of its settings in huge plaintext files called ini files. They were a tangled mess, and the more you used your computer, the slower it became. The registry made it a lot faster for the computer to find each setting it needed.
If your start button disappeared, I have the fastest possible fix for you. It works with Windows 7, Windows 8, and Windows 10, and server versions, in addition to versions of Windows you shouldn’t be running anymore.
The symptom: If you install more than 512 MB of RAM in a system running Windows 9x (that’s any version of Windows 95, 98, 98SE, or ME), you get weird out of memory errors.
The culprit is a bug in Windows 9x’s disk cache. The solution is to limit the cache to use 512MB of memory, or less, which is a good thing to do anyway. Here’s how.
It’s important to check SSD alignment in Windows. If your SSD isn’t aligned, you reduce its performance and its life expectancy. Fortunately in many cases, your SSD will be properly aligned, but it only takes a minute to check.
Here’s a good question. Should you migrate Windows 7 to SSD or install fresh? And what about Windows 10? This is likely to be controversial and everyone has an opinion. I’ll weigh the pros and cons of each, as a guy who knows a little about optimizing Windows, and who has been using SSDs since 2009.
I got an HP Elitebook 8440p because I wanted something a little newer and faster than my old Dell E1505. It was certainly newer and faster, but it had a problem. Every morning it greeted me with a BSOD. That E1505 was getting older and it had its own quirks, but I don’t remember it ever bluescreening on me. Here’s how I fixed the bluescreens I got with the HP Elitebook 8440p and Windows 10.
Not only did it bluescreen, but the behavior seemed pretty consistent. Two days in a row, I woke the laptop up from hibernation, and about nine minutes later, it bluescreened.
Part of being a system administrator is copying large quantities of files around, for any number of reasons. The traditional tools for this, Copy and Xcopy, have some limitations. For this reason, two companies extended Xcopy: Microsoft, with Robocopy, and Pixelab, with Xxcopy. Let’s compare Xxcopy vs Robocopy.
Microsoft includes Robocopy with recent versions of Windows. Even when it wasn’t included, you could get it as part of the Windows Resource Kit. Xxcopy is commercial software.
Xxcopy’s advantages are its similarity to Xcopy and its simpicity. I most frequently used its /clone switch, like this: xxcopy /clone source destination
So if you’ve just installed a new hard drive and want to move your old one to the new one, do this:
xxcopy /clone e:\ f:\
And then you can swap the drives.
The /backup switch is safer than /clone, as it doesn’t delete any files. Since I normally used it for one-time copies to blank media, there was no perceptible difference between the two.
It really just is an extended Xcopy. Sub in something more powerful for /s and off you go.
I stopped using Xxcopy when it stopped being free for commercial use several years ago. But it worked just fine then, and presumably still works just fine now, if you’re willing to pay for it or qualify for a free license.
Some organizations won’t approve third-party software without jumping through a lot of hoops, or at all. It may very well be easier to learn Robocopy than to install Xxcopy.
Robocopy is just there, if you’re running a fairly modern version of Windows. It’s part of the operating system, so you won’t need any approvals, and there’s nothing to download or install. That’s a huge political advantage in most companies.
I also think Robocopy’s restart capabilities with the /z switch are a bit better if the copy gets interrupted. That was the reason I started using it.
I have no idea why Microsoft changed the syntax. It’s robocopy source destination files. Well, I kind of understand. Perhaps it’s more powerful this way. But it’s a lot more confusing. It’s almost as bad as the infamous PIP command.
It’s very easy to delete files you don’t mean to delete, and to copy a bunch of stuff where you don’t intend to.
If Xcopy is a hand saw, Robocopy is a power saw with no safety features on it. If you’re a little bit afraid of it, that’s good. It means your brain works. To continue the analogy, Xxcopy is a power saw with some safety features.
That said, you can put safety features on it. The problem is you have to put the safety features on yourself.