A partial retraction. OK, Southwestern Bell isn’t responsible for all my missing mail. I had a second POP3 client running that I forgot about, which was grabbing some of my mail. But my computer couldn’t find a DHCP server all day, so even though one problem wasn’t their fault, another one was. So I’m still gonna write Casey Kassum with a request and dedication: Todd Rundgren’s “I Hate My Frickin’ ISP,” dedicated to my beloved Southwestern Bell.
Running, uh, no, executing Windows NT 4.0 on a Pentium-75 with 16 MB RAM. Disclaimer: Before you start thinking things that include my name and words like “crack” or “LSD,” let me state emphatically that this was not my idea. I was only following orders. (I’m not on drugs. I’m not nuts–I’m certifiably sane. I’m not even depressed.) All that clear? Good.
That said, the stated minimum hardware requirements for NT 4 are a 486 CPU with 12 MB RAM. And I did once build a print server out of an old IBM PS/2 that had a 486SLC2/50 CPU and 16 megs of RAM. Hey, I was young and I needed the money, OK? Besides, it was a very experimental time and I didn’t think anybody would get hurt…
OK, I’m done turning druggy double entendres.
Needless to say, NT on this machine is anything but pretty. (And I’ll put a marginal machine into service as a server where no one ever interacts with it directly long before I stick one on an end-user’s desk.) The video card in my flagship PC has more memory and processing power. But we’re out of PCs, and this poor girl needs a computer on her desk (though she’s never done anything to deserve this fate), so here’s what I did to try to make life on this machine more tolerable. These tricks work much better on fast machines.
- Pull out all network protocols except TCP/IP. I also double-checked all TCP/IP settings and made sure the closest DNS server was first on the list.
- Use a static IP address. The DHCP service uses memory and CPU cycles, and on machines like this, every byte and cycle counts.
- Remove Office Startup, Find Fast, and LoadWC from Startup. The first two are in the All Users start menu. The last is in the registry. All eat memory and provide no useful functionality.
- Move the swap file to a second physical hard disk. This machine happened to have a second drive, so I put the swap file there for better performance.
- Turn off unnecessary services. The Scheduler service and Computer Browser service normally aren’t needed. If the network never sent out notifications (ours does), I’d also turn off the Messenger service.
- Remove unnecessary fonts. I won’t do this without her present, since I might inadvertently nuke her favorite font. But if she doesn’t use it, it’s gone.
- Keep free space above 100 megs. Windows slows to a crawl when forced to live on a drive that’s as crowded as a mosh pit.
- Defragment! Making matters worse, this drive didn’t seem to have a single file on it that wasn’t fragmented. I ran Diskeeper and there was more red on the screen than at a Cardinals game when Mark McGwire’s chasing home run records.
- When you have two drives, put the OS on the faster of the two. Unfortunately, the OS is on an ancient Seagate 420-meg drive, with a 2.1-gig drive in as the secondary drive. The roles really should be reversed. When in doubt, the bigger drive is usually faster. The newer drive almost always is. I may just Ghost the OS over to the 2.1-gig drive, then switch them.
- Switch to Program Manager. She’s probably not comfortable with the old Windows 3.1 interface (I’ve only ever met one person who liked it) so I probably won’t do this, but that’ll save you a couple megs.
Yes, even with these adjustments, it’s still awful. So I’m gonna see if I can dig up some memory from somewhere. That’ll help more than anything. But as tempting as overclocking may be, I won’t do it.