The decline and fall of system administration

Infoworld’s Paul Venizia stirred up a controversy, asking what happened to sysadmins who can fix things, as opposed to just rebuilding machines any time something went wrong.

The definition changed, mostly. At least that’s what I think.

Read more

On troubleshooting

My Windows 7 upgrade was supposed to be a one-hour project on a Saturday afternoon. It dragged on until Wednesday. I’m at the point now where I probably have an hour’s work left on the machine–it’s Thursday now–but it’s late and I’m not sure I feel like it.

The answers–loading the BIOS defaults and changing the parallel port settings–seem obvious. Now. But when I look for my keys, where I finally find them seems obvious too, even though it sometimes takes a long time to find them.

Read more

What the 2011 CES may mean

This week was CES, where companies make a big splash and try to show what’s going to happen in the consumer electronics space in the coming year.

In the coverage of CES, I saw three things that seem interesting, but only one of those three was a surprise.
Read more

Um, no, software shouldn’t have kill switches or time bombs in it

So,  ZDNet is advocating that Microsoft use a kill switch to render existing Windows XP computers non-functional. Then he relented and said maybe an expiration date would be sufficient.

John C Dvorak is attacking the idea, with good reason. Dvorak is right.
Read more

It must be that system idle process…

One day, I came back to my desk after lunch and my boss cornered me. “You know about these things. What’s Half-Life?”

I hesitated for a minute. “I’m pretty sure it’s a computer game.”

It wasn’t a game I’d played. If it isn’t Railroad Tycoon, I’m probably not interested. Read more

Tribute to the Asus SP97-V

Tribute to the Asus SP97-V

In need of an obsolete but reliable PC for a project, I searched a dark corner of my basement, a last stop for castoff PCs before being sent off for recycling. I found one. Predictably, it had an Asus motherboard in it. Specifically, it had an Asus SP97-V in it, a budget Socket 7 board from the late 1990s sporting a SiS chipset with integrated video that worked well with Cyrix and AMD CPUs.

Read more

Barfy.

I started my professional career doing network administration at the University of Missouri. (I generally don’t count my stint selling low-quality PCs at the last surviving national consumer electronics chain towards my professional experience anymore.)

Read more

Why I generally buy AMD

I was talking to a new coworker today and of course the topic of our first PCs came up. It was Cyrix-based. I didn’t mention my first PC (it seems I’m about four years older–it was an Am486SX2/66).

With only a couple of exceptions, I’ve always bought non-Intel PCs. Most of the Intel PCs I have bought have been used. One boss once went so far as to call me anti-corporate.

I’m not so much anti-corporate as I am pro-competition.

Read more

Run the right version of Windows for your PC

I said I was done writing about system optimization. I changed my mind. I have one more thing, and it seems appropriate, now that Vista upgrades are available.

Be very wary about upgrading your version of Windows.There are a few Vista-only titles out there, and there will be some more, but the majority of titles aren’t. Walk into a software aisle and you’ll still find a lot of software that will run on Windows 95 (or possibly 98), assuming the computer meets the hardware requirements.

I’m typing this on an 800 MHz HP Pavilion 6835. Sure, it’s outmoded–for around $125, I could swap in an Athlon 64 motherboard that would give me 4-5x the CPU power and that would be considered a low-end PC by today’s standards–but this one’s peppy. I run Windows ME on it. Windows 2000 would be more stable but I’m lazy. I wouldn’t try XP on it. When XP came out, this system was already old.

Technically, XP will install on a 133 MHz Pentium if it has enough RAM. I’ve seen it done, and I’ve seen it try to run on one. It’s not pretty. I really wouldn’t try running XP on anything less than a 1 GHz PC with 256 megs of RAM, because that was the standard PC at the time of XP’s release. But believe it or not, if you install Windows 95 and Office 95 on that Pentium-133, it’s a reasonably nice machine–because that was a high-end box in 1995 when Windows 95 and Office 95 came out.

So when you’re refurbishing an old machine, try to install whatever the current version of Windows was when it was new. The PC will run a lot better. Here’s a guide.

Windows 95: Released August 1995
Typical PC of the time: 486, 66 MHz
Hot PC of the time: Pentium, 133 MHz

Windows NT 4.0: Released July 1996
Typical PC of the time: Pentium, 75 MHz
Hot PC of the time: Pentium Pro, 200 MHz

Windows 98: Released June 1998
Typical PC of the time: Pentium, 233 MHz
Hot PC of the time: Pentium II, 333 MHz

Windows 2000: Released February 2000
Typical PC of the time: Pentium III or Athlon, 600 MHz
Hot PC of the time: Pentium III or Athlon, 1 GHz

Windows XP: Released October 2001
Typical PC of the time: Pentium 4, 1.5 GHz
Hot PC of the time: Pentium 4 or Athlon, 2+ GHz

Windows Vista: Released January 2007
From what I understand, even a hot PC of 2007 has difficulty running it. I haven’t seen Vista yet; my employer is still running XP for everything.

Of course, if you install as much memory as the system will take, you can push your limits, since Windows is often more memory-bound than CPU-bound. I also try to replace the hard drive with the fastest model I can budget for. Don’t worry if the drive has a faster DMA rate than the controller on the board; you’ll still benefit from the faster seek times and better throughput of a newer drive. If the new drive saturates the bus, it could be worse–I guarantee the old one didn’t.

The best defragmenter for Windows NT, 2000, XP and Vista

Want Diskeeper’s features without ponying up 50 bucks?

Sorry, I can’t help you. The combination of My Defrag, Scandefrag, and Pagedefrag is better and it’s free.

Scandefrag defragments your system during the boot process, as early as it can. It works better on NT-based systems like Windows 2000 and XP than it does on 98 or ME. All it does is launch the other tools.

Pagedefrag is, of course, a classic. It’s just convenient to bundle it up with these other tools. This tool defragments your registry and swap file(s) at boot time, which is the only time the system allows it.

My Defrag (actually Jerrod Kessels’ defrag) is, to put it simply, the best general purpose defragmenter for Windows NT, 2000 and XP that I’ve ever seen. Period.

If My Defrag can’t do an ideal job, it does the best it can do. Some defragmenters leave a file alone if they can’t defragment it, but this one will defragment as much as possible and move it as close to the front of the disk as possible, where performance is much better. On full disks, this is important. Since ideal conditions almost never exist (except when a system is first built), a defragmenter’s performance under less than ideal conditions is very important.

The most exciting thing about My Defrag is its ability to sort files. I like Sort alphabetically.

Sorting alphabetically (the -a7 switch) helps because it uses the full pathname. This means all of your files that are part of, say, Mozilla Firefox will be put as close together on the disk as possible, so when you launch Firefox, all of those files are close together and the disk head doesn’t have to move around a lot. The result is an application that launches faster.

So how often should you defragment? Once a year, I would do a boot-time defragmentation with Scandefrag to whip the Registry and swap files into shape. When that finishes, I would run My Defrag in full optimization mode, with file sorting. If you make a major change to your system (say, upgrading your office suite), do a quick defragmentation after the install and a full defragmentation a month or so after.

As part of your routine system maintenance, a faster, automatic defrag with no options specified is a good idea on occasion. The author says to do it no more than once a day and I agree. In my experience, once a week or even once a month is almost always fine. The way My Defrag works, the system shouldn’t get terribly fragmented on a daily basis, even if you use your system heavily. Defragmenting too frequently can shorten a hard disk’s life expectancy, although the occasional defragmentation seems to help it. I defragment a few times a year (and always have), and I generally get five or six years out of a hard disk, which is a year or two longer than most experts say to expect.

Don’t waste your money on any other tools. Download this trio, install it, use it, and watch your system performance climb.