So maybe you're like me and you're administering a system that fell off its Windows domain, and the system was built by your predecessor's predecessor, the local administrator account was renamed, and nobody has any clue what the account name or password is.

And you try ERD Commander because it worked in the past, but not this time...

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.

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.

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 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.

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.

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?

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?

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...

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.