Cleaning the Windows registry is a popular and controversial topic. Many pundits tell you never to do it. When I wrote a book about Windows back in 1999, I dedicated most of one chapter to the topic. But today the pundits have a point. Most registry cleaning utilities do much more harm than good. I don’t recommend you clean your registry, per se, but I do recommend you maintain it.
I don’t want to dismiss the concept completely out of hand. There’s a difference between a bad idea and a bad implementation. Registry cleaning and maintenance is a victim of bad implementation. But that doesn’t mean it was a bad idea. So let’s talk about how to get the benefit while minimizing the drawbacks.
The Amiga had a command line, or CLI. It was a rather powerful CLI, especially for its time. But there are a number of differences between AmigaDOS and other operating systems you may be familiar with. These are the common AmigaDOS commands and their equivalents from other operating systems like DOS, Windows, Unix or Linux.
I’ve never seen a primer that relates or cross-references Amiga commands to Windows and Unix. So I wrote one. I hope it helps you understand your Amiga better. Because Amiga is sometimes like Windows and sometimes it’s like Unix, I think it might. And maybe, just maybe, you’ll learn something you didn’t know about Windows or Unix too.
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.
I got lots of random errors installing Office 2013 when I went to do it, including error code 112-4 and error code 0-4, and some other install errors mostly ending in 4 that aren’t documented on Microsoft’s web site. Although previously undocumented, these errors are fixable. Read more
In my younger days, I administered WSUS on a small (300 servers or so) network. Every once in a while, I ran into an issue where a server just didn’t want to talk to WSUS. These days, some companies prefer to push patches with SCCM but it uses the same mechanism to push patches.
Apparently my old problem still happens from time to time. So I did some research to come up with a solution. This mechanism is still largely a black box, but it’s a lot better documented now than it was in my day. Here’s what I came up with for troubleshooting WSUS or SCCM. Read more
Sometimes in a batch file I find myself needing to perform more than one operation on a server, especially inside a for loop. Rather than do a pair of for loops, which isn’t always desirable, you can use the & operator. Read more
I found some good advice on Lifehacker today about building a professional network. Not just having 500 connections on Linkedin, but having a real professional network made up of people who help one another advance their careers.
I stumbled into this completely by accident. Read more
A former classmate and industry colleague dropped me a line a few weeks ago. He pointed out that memory is dirt cheap, and he bought 16 GB of RAM, just because it cost him around $100 to do, and was wondering what to do with it. A ramdisk, perhaps?
My search logs prove that ramdisks are the best-kept secret in the industry (virtually nobody knows or cares about them), but they’re still the best way to increase the longevity or life expectancy of an SSD and an outstanding way to pep up performance. A ramdisk is 80 times faster than a hard drive, 60 times faster than a RAID array, and 10-20 times faster than an SSD. Read more
Moving the rest of your temporary files to a ramdisk provides a number of performance benefits. Program installations proceed noticeably faster, and fewer files written to your system disk means less fragmentation, less maintenance for an SSD, and, most likely, longer SSD life.
On some web pages offering programs to download, you may have seen something called an MD5 near the program link, consisting of a long, weird code like 6cbfd919baa7c9e03c8471ae4d8f8bb.
You can use that code to make sure the file you downloaded is what the author intended you to get and wasn’t corrupted during the download process or, worse yet, booby-trapped by someone else. Here’s how.