I rebuilt a Dell Dimension 4100 last night

So, I rebuilt a Dell Dimension 4100 last night. I didn’t make any hardware changes other than replacing the Western Digital hard drive inside, which was on its last legs.

Along the way, I learned a few things.I won’t say much about the WD drive except to say it’s the most recent in a long line of bad experiences I’ve had with the brand. I don’t know anything about current WD drives. But this one was loud and shrill, Windows bluescreened when I tried to install to it, and when I tried to run SpinRite on it, it said it would take 140 hours to test. A drive that size (20GB) should take 8-10.

In its defense, that drive was five years old. But I replaced it with a Maxtor drive that’s almost eight years old. SpinRite processed that Maxtor in 3 hours and found nothing worth commenting about. (Just because SpinRite didn’t say anything doesn’t necessarily mean it didn’t do anything.)

The Dell Dimension 4100 does have a proprietary power supply (although it looks like an ATX). If you work on Dells, I suggest bookmarking PC Power and Cooling’s Dell cheatsheet. PCP&C power supplies are expensive, but they are reliable, and their prices are comparable to what Dell would charge for a replacement and they are higher quality than what you would get from Dell–assuming Dell will even sell you the part (they’re in the business of selling computers, not parts). I believe newer Dells use standard power supplies.

If you buy a Micron, you can punch in a serial number and get drivers for the machine. With a Dell, you just get guesses based on the options that were available for the machine.

Download the chipset drivers and other low-level stuff from Dell’s support site. Windows 2000 didn’t completely recognize the system’s Intel i815 chipset and I get better performance afterward.

Nlite offers a lot of promise–automating the Windows install, removing components, etc.–but I had trouble getting it to work with the OS recovery CDs I had. I didn’t have enough time (or blank CDs) to figure out how to get it to work for me. I’m sure it works better with a plain old Windows 2000 Workstation CD, but of course I can’t find mine. But if you have a CD that works with it, it’s nice even if you don’t remove the stuff Microsoft doesn’t let you remove, since it provides a nice interface for slipstreaming service packs and hotfixes and removing all of the prompts during installation.

The tricks in Windows 2000 with 32MB of RAM work pretty nicely, even when you have more than 32 megs. Of course, if you’re ruthless with Nlite and can get it to work for you, you probably don’t need that bag of tricks.

I didn’t try to install it without Internet Explorer. I’d love to try that sometime but I didn’t have time for that. At least disabling Active Desktop (see the link in the paragraph above) gives most of the benefit you would get from smiting IE.

The quality of the Dell hardware is reasonable. It didn’t floor me, but I didn’t see anything that made me cry either.

I found what looks like a useful Windows scripting language

Windows 3.1 used to have the ability to record macros, a capability that never made it to later versions. There are a lot of things batch files can’t do. But I spotted a reference to AutoIt on Digg, and that looks useful.Basically it will script keystrokes and mouse movements, as well as giving you BASIC-like program logic. It’s not something you need often, but when you need it, you’ll need it badly.

Windows 2000 without Internet Explorer

Those of you who bought my book (both of you) know that the biggest secret to speeding up Windows 95 and 98 was removing the extra junk nobody used–especially the stuff Microsoft deliberately made impossible to remove via normal means.

In Windows 95, all it took was modifying INF files with a text editor to remove MSN, IE, and the other obsolete software it shipped with from the get-go. Win98 got a bit more complicated. But with 2000, Microsoft started getting nasty–putting encrypted data in multiple places, so even if you hacked the INFs, it didn’t do any good.

But several people still figured out how to do it.I really like Fred Vorck‘s site, because he’s careful to document everything. He also found out the same thing I did by writing my book–there are lots of people who will whine that your instructions are too complicated, they’ll whine that when they follow the directions and make a mistake it doesn’t work, or they just repeat the Microsoft party line that the software can’t be removed, and your mouse will stop working, your computer will generate horrific RF interference, and gas prices will soar if you remove IE from Windows. (The last part is probably true, of course, but none of the rest is.)

What really happens when you remove IE from Windows 2000 is similar to what happened when you removed it from Win95 and 98: Your memory usage drops (by about 20 megs, in this case) and your boot time is cut in half.

Since some software does break, because some software does use the IE engine, you might not want to do this on every PC you own. But if, say, you want to run Windows 2000 on an old laptop with limited memory so you can run a handful of useful Windows applications, this is perfect. If you want a stable, lightweight (by modern standards) OS for any Pentium II-class machine that might be sitting in the closet, this makes it a viable option too. A lot of computers are sitting in closets today not because they’re no longer useful, but because there’s no practical or affordable way to boost them up to the half-gig of memory that you need for Windows XP to be practical to use on them.

Read Vorck’s site some more, and dig around, and you’ll find that minimal Windows installs have created something of a subculture. I don’t know if anyone’s squeezed XP down to the level I got Win95 down to (the original Windows 95, released on Aug. 24, 1995, can be hacked down to an installation footprint of 17 megabytes without much hassle), but some people have done some pretty amazing things.

Yes, when I get time someday, I’ll be messing around with this. I wish I’d discovered it sooner.

And in case anyone cares, I found this because some know-it-all at work said you can’t uninstall Outlook Express from Windows 2000. I vaguely remembered having seen a piece of software that goes so far as to remove IE, so I said, “You can remove IE from Windows 2000 if you’re willing to work hard enough at it, let alone Outlook Express.” So I did some more searching, just to satisfy my curiosity.

If and when I end up building a minimal Win2000 box, I may just have to bring it in one day to show the know-it-all. But as longtime readers of this site know, I’ve dealt with that type before. So it’s probably not worth the effort to carry it out to the car.

Windows 2000 in 32 megs of RAM

I can’t remember if I linked this before or not, so here’s Windows 2000 on 32 MB of RAM.

Of course I find this interesting. And his advice is pretty good. My first choice for an OS in 32 megs of RAM would be Windows 95, and probably Windows 95a at that (and gee, some idiot wrote a book about that), but if you need better reliability and stability, Windows 2000 is a good second choice.

One piece of advice worth mentioning that he didn’t mention: If there’s a modem on the system, lose it, especially if it’s a Winmodem. That’ll save lots of precious RAM and CPU cycles.

Windows for Morons

Microsoft is considering a numeric ratings system for PCs for the upcoming version of Windows–The Operating System Formerly Known As Longhorn, that is. I believe it’s going to be called Windows LH.

I smell marketing.Basically the idea is that a PC will be assigned an arbitrary numeric rating between 1 and 5, based on how much CPU power, memory, and potentially how powerful the video card is. Then a piece of hardware will have a number on it, and software will have the same number. If a piece of software has a "5" on it, don’t expect it to run well on a $399 Emachine with a rating of "1".

The problem with this idea is that capabilities change. This year’s "5" PC is 2006’s "1" PC. Granted, PC capabilities aren’t growing by leaps and bounds the way they have for the past few years, and maybe this is an admission that CPU power has leveled off, but memory requirements aren’t going to level off, and hard disk speeds are doing anything but standing still. So this is still a system with built-in obsolesence. And it doesn’t even take into consideration the speed of the disk drives, which to me is still the most underrated component of system performance. If you’re not a gamer, you’re much better off with the cheapest PC you can buy, hot-rodded with the fastest hard drive you can find and some extra memory, than you are with a system with a fire-breathing CPU and the hottest new video card. Or just put the same drive and memory into your old one and keep it for another three years.

Old-fashioned system requirements are still the way to go, I believe.

But I suppose if this rating system goes through–which really should be conducted by an objective third party and not by the collusion of Microsoft and Intel–it’ll give me a chance to write a new book. So I guess I should be happy, eh?

The Microsoft Killer

Yet another story about what’s going to kill Microsoft popped up on Slashdot today. This time it’s cheap solid-state computers running open-source software. I didn’t bother reading it.

Here’s what I think the Microsoft killer will be: Windows.

Say what?Yeah, Windows.

Computers are cheap enough now that the majority of people who want one have one. Even those who can’t afford to buy new can turn to the used market–used 1 GHz systems are now selling in the $100-$150 range without an operating system.

The biggest problem with a computer these days is keeping it running. People throw away VCRs and DVD players because it’s cheaper to buy a new one than to have one repaired. And had I charged fair market value for the last computer repair I did, it probably would have exceeded the cost of a $399 Emachine.

But there’s a problem. When a VCR or DVD player dies, you unplug the old one, plug in the new one, and get on with life. You’re looking at three or four cable connections. It takes most people less than 10 minutes, usually much less. When you go to swap out a computer, you have to worry about all your data and the programs you installed.

Most people don’t know that 99% of their data is in one place, and even fewer people know where that is and how to get to it. These same people are the ones who are most likely to inadvertently end up with their data in weird places.

The result is the cost to replace a computer is much higher, and it’s not necessarily something the majority of people want to undertake themselves.

The result is lost revenue. And an opportunity.

Google, if you’re the one who wants to unseat Microsoft, find a way to help users move their data from one computer to another. Someone else, if you want to beat Google to the punch, find a way to help users move their data and their programs. I know such a program won’t be foolproof, but if it works even 75% of the time, it’ll sell like crazy.

Of course if someone does it and it proves successful, Microsoft will just clone it and assimilate the market.

But if no one does, maybe Steve Jobs will sell a lot more Macs, because this is one task that’s always been easier on a Macintosh.

Fixing Backup Exec with Hisecweb installed

If you run your web servers on Windows under IIS, you’d better install the Hisecweb security template unless you want to find yourself hosting a warez site.

But Hisecweb breaks Backup Exec. So what do you do when upgrading to Apache and Linux isn’t a solution?The problem is that Hisecweb makes the system state (shadow copy components in Windows 2003) and SQL server not show up in the selection list. Not only does it not show up in the selection list, Backup Exec cannot find the resources. So backups fail, and if you have to restore from them, you won’t have the registry or a number of system files, which vastly reduces the value of your backup.

The solution is to tell Backup Exec not to use null sessions on those components, which seem to be one of the many things disabled by Hisecweb. On the server being backed up, go into Services and disable your Backup Exec Remote Agent. Now, fire up Regedit. Navigate to HKLM\Software\Veritas\Backup Exec\Engine\NTFS and locate the key called Restrict Anonymous Support. Set this value to 1. Close the registry editor and restart the Backup Exec Remote Agent service.

SQL Server and the system state or shadow copy components should now show up in the selection list for the server you just changed.

This registry hack can also fix visibility problems when the two machines are on different sides of a firewall.

Vindicated?

This article on Windows installation at Firing Squad preaches all the same things I was preaching nearly six years ago in my Windows 9x book.

Where to find the stuff has almost all changed, and msot of the old utilities don’t work anymore, but these are exactly the same concepts I yammered on and on about. Funny, I’ve been told system optimization is a waste of time…Incidentally, this is the second article on optimization that I’ve seen in less than a month. The other one read an awful lot like a Windows XP translation of an article I published in Computer Shopper UK back in 2000, which in turn was a shortened version of one of the chapters in the same book.

So I guess people don’t just throw their 2-gigahertz computers away and buy new ones when they start to seem slow?

It really makes me wonder what would have happened if, after the book received a gushing review in Canada and was perpetually sold out in stores up north, if those 3,000 copies of the book that languished in a warehouse in Tennessee had made their way into those stores.

That’s OK. That was five years ago, nothing can change it, and I really don’t have any desire to be a computer author anymore. I find the only way to really know a lot about computers is to work with them for 40-60 hours a week in a production environment. Labs don’t cut it–you can never underestimate the effect of 1,000+ users hammering on what you built. Never. And if you spend those hours working, that doesn’t leave enough time to write books and release them in a timely fashion.

So rather than write mediocre computer books or send myself to an early grave by working full time in addition to writing for 30-45 hours a week, I’d rather have a life, make a decent living, and not write computer books.

Troubleshooting Packagefortheweb packages

Under some circumstances when installing an app from a Packagefortheweb archive, such as Sun’s JRE, I get a goofy error message like “Cannot run 16-bit Windows Program” or a message about a failure to find a path with long filenames in it.

It’s a bit of a pain but you can fix it.The trick is to extract the file rather than run it. I found PowerArchiver can do it. Winzip may also be able to. I wish I had a command-line utility to do it but I don’t.

Extract it to a short directory name, then move it to the root drive. Then run your setup.exe. That should be the end of your problems. Clean up afterward to eliminate directory clutter.

Recover your Windows CD key

Do you know your Windows CD key off the top of your head? Didn’t think so. Do you know where it’s written down?

Don’t panic if the answer to that question is also no.There’s a utility called Winkeyfinder that can recover the key for you. Download and run it and print out your key while you’re thinking about it.