Windows potpourri

I’ll give some random Windows tips tonight, since it’s getting late and I don’t really want to think. So here’s some stuff I’ve been putting off. So let’s talk utilities and troubleshooting.
Utilities first. Utilities are more fun. So let’s talk about a pair of reader submissions, from Bryan Welch.

Proxomitron. Bryan wondered if I’d ever heard of it because I’d never mentioned it. I’m sure I mentioned it on my page at editthispage.com because I ran Proxomitron for a couple of years. Proxomitron is a freeware proxy server that blocks ads, Javascript, cookies, and just about anything else undesirable. I’ve found that these days I get everything I need from Mozilla–it blocks popups just fine, and I can right-click and pick “Block images from this server” when I run across an objectionable ad, and of course I have GIF animation turned off and Flash not installed. That works for me, and it saves me memory and CPU time.

But if you want more than Mozilla gives you off the shelf, Proxomitron will give it to you. I used to recommend it wholeheartedly. I haven’t looked at a recent version of it but I’d be shocked if it’s changed much. If any of that interests you, I’m sure you’ve already run off to download it. It runs on any version of Windows from Win95 on.

98lite. Most of my readers run Windows 2000 or XP at this point, but about 20% of you are still running Win98 or WinMe. If you want to get a little extra speed, download and run 98lite to remove Internet Explorer and other not-quite-optional-but-mostly-useless cruft. It’s been pretty well established that Windows 9x runs 20-25% faster with IE gone. That’s more improvement than you’ll get from overclocking your CPU. Or from any single hardware upgrade, in most cases.

If you need IE, 98lite can still help you–it can break the desktop integration and speed things up for you, just not as much.

If you’re still running 98, I highly recommend it. How much so? When I was writing Optimizing Windows, Shane Brooks probably would have given me a copy of it, on the theory that its mention in a book would cause at least sales he wouldn’t get otherwise. I mentioned it (I think I dedicated half a chapter to it), but I didn’t ask him for one. I registered the thing. If I liked it enough to pay for it when I probably didn’t have to, that ought to say something.

Troubleshooting. Let’s talk about troubleshooting Windows 2000 and XP.

Weird BSODs in Premiere under Windows 2000. I haven’t completely figured out the pattern yet, but my video editing computer gets really unstable when the disk gets jammed. A power play at church forced me to “fork” my new video–my church gets its edited, censored, changed-for-the-sake-of-change version (pick one) while everyone else gets the slightly longer how-the-guy-with-the-journalism-degree-intended-it version. Re-saving a second project filled up nearly all available disk space and the machine started bluescreening left and right. After I’d done some cleanup last week and freed up over a gig on all my drives, and then defragmented, it had been rock solid.

So if you run Premiere and it seems less than stable, try freeing up some disk space and defragmenting. It seems to be a whole lot more picky than any other app I’ve ever seen. I suspect it’s Premiere that’s picky about disk space and one or more of the video codecs that’s picky about fragmentation. But if you’re like me, you don’t really care which of them is causing the BSODs, you just want it to stop.

Spontaneous, continuous Explorer crashes in Windows 2000. Yeah, the same machine was doing that too. I finally traced the problem to a corrupt file on my desktop. I don’t know which file. I found a mysterious file called settings.ini or something similar. I don’t know if deleting that was what got me going again or if it was some other file. But if Explorer keeps killing itself off on you and restarting and you can’t figure out why, try opening a command prompt, CD’ing to your desktop, and deleting everything you find. (I found I had the same problem if I opened the desktop directory window in Explorer while logged on as a different user, which was how I stumbled across the command line trick.)

I can’t say I’ve ever seen this kind of behavior before. First I thought I had a virus. Then I thought I had a corrupt system file somewhere. I’m glad the problem turned out to have a simple cure, but I wish I’d found that out before I did that reinstall and that lengthy virus scan…

Defragging jammed drives in Windows 2000 and XP. If you don’t have 15% free space available to Defrag (and how it defines “available” seems to be one of the great mysteries of the 21st century), it’ll complain and not do as good of a job as it should. In a pinch, run it anyway. Then run it again. Often, the available free space will climb slightly. You’ll probably never get the drive completely defragmented but you should be able to improve it at least slightly.

The low-end server

Here’s a good question: What should a small operation do when it gets fed up with its network and is tempted to just chuck it all and start over?
Well, my advice is to start over. But I don’t agree that starting over requires one to chuck everything.

We’ll start with the server. Chances are, these days, you need one. If you’re doing Web and e-mail, you absolutely need one. But to a lot of people, servers are a mystical black box that costs more money than a desktop PC but runs a similar operating system. And that’s all they know.

Here’s what you need to know: A corporate server is built to stricter tolerances than a desktop PC and sometimes uses higher-quality parts (common examples are ServerWorks chipsets instead of Intel chipsets, SCSI instead of IDE, and error-correcting memory instead of the cheap nonparity stuff). You also often get niceties like hot-swap drive cages, which allow you to add or replace hard drives without powering down or opening the case.

They’re generally also better tested, and you can get a support contract on them. If you’re running an enterprise with hundreds or thousands of people relying on your server, you should buy server-grade stuff, and building your own server or repurposing a desktop PC as a server ought to be grounds for dismissal. The money you save isn’t worth it–you’ll pay more in downtime.

But a dozen people won’t hit a server very hard. This Web site runs on a Dell OptiPlex Pentium II/450 workstation. A workstation is a notch above a desktop PC but a notch below a server, in the pecking order. The biggest difference between my Optiplex and the PC that was probably sitting on your desk at work a year or two ago is that my Optiplex has a SCSI hard drive in it and it has a 3Com NIC onboard.

A small office can very safely and comfortably take a reasonably powerful name-brand PC that’s no longer optimal for someone’s desk (due to an aging CPU) and turn it into a server. A Pentium II-350 or faster, outfitted with 256 MB of RAM, a SCSI host adapter and a nice SCSI hard drive, and a 3Com or Intel 100-megabit Ethernet card will make a fine server for a couple of dozen people. (My employer still has a handful of 200 MHz Pentium Pro servers on its network, serving a couple hundred people in some cases.)

This server gets hit about as hard as a typical small business or church office server would. So far this month I’ve been getting between 500 and 550 visitors per day. I’ve served about 600 megabytes’ worth of data. My average CPU usage over that time period is in the single digits. The biggest bottleneck in this server is its 7200-rpm SCSI disk. A second disk dedicated to its database could potentially speed it up. But it’s tolerable.

Hot swappable hard drives are nice to have, but with an office of a dozen people, the 5-10 minutes it takes to power down, open the case, swap drives, and close the case back up and boot again probably doesn’t justify the cost.

A business or church office that wanted to be overly cautious could buy the very least expensive sever it can find from a reputable manufacturer (HP/Compaq, Dell, IBM). But when you do that, you’re paying for a lot of power that’s going to sit there unused most of the time. The 450 MHz CPU in this box is really more than I need.

Jeremy Hendrickson e-mailed me asking about whether his church should buy a new server, and whether it really needed two or three servers, since he was talking about setting up a Samba server for file serving, Apache for Web serving, and a mail server. Running file and Web services on the same box won’t be much of a problem. A dozen people just won’t hit the server that hard. You just make sure you buy a lot of disk space, but most of that disk space will go to file serving. The database that holds all of the content on this site is only a few megabytes in size. Compressed, it fits on a floppy disk with lots of room to spare. Yes, I could realistically do nightly backups of my Web server on floppies. If floppies were at all reliable, that is.

I flip-flop on whether e-mail belongs on the same server. The security vulnerabilities of Web servers and mail servers are a bit different and it would be nice to isolate them. But I’m a lot more comfortable about a Linux box running both being exposed on the ‘Net than I am a Windows box running one or the other. If I had two boxes, and could afford to be paranoid, I’d use two.

Jeremy said his church had a P3-733 and a P2-450, both Dells, due for retirement. I’d make the P3 into a file/print/Web server and the P2 into a mail server and spend the money budgeted for a new server or servers to buy lots of disk space and a nice tape backup drive, since they’d get lots of use out of both of those. A new $1200 server would just buy lots of CPU power that’ll sit idle most of the time and you’d still have to buy disks.

As far as concern about the reliability of reusing older systems, the things that tend to wear out on older PCs are the hard drive and the operating system. Windows deterriorates over time. Server operating systems tend not to have this problem, and Linux is even more immune to it than Microsoft server operating systems. So that’s not really a concern.

Hard disks do wear out. I read a suggestion not long ago that IDE hard disks should be replaced every 3 years whether they seem to need it or not. That’s a little extreme, but I’ve found it’s hard to coax much more than four years out of an IDE disk. Dropping a new SCSI disk or two or three into an old workstation before turning it into a server should be considered mandatory. SCSI disks give better performance in multiuser situations, and are generally designed to run for five years. In most cases, the rest of the PC also has several years left in it.

Later this week, we’ll talk about Internet connectivity and workstations.

Eldred loses, and so do the rest of us

It’s obvious from today’s ruling in the Eldred v. Ashcroft case that copyright law will never revert back to what the Founding Fathers had in mind. Corporate interests will be able to continue to buy extensions to copyright law to prevent the overwhelming majority of works made after 1924 from falling into the public domain unless for some odd reason it gets abandoned.
The problem is that when you and I want something, all we have to offer to our congressmen is our vote every two or six years, and maybe a campaign contribution. Disney doesn’t vote, although its employees do, but Disney can give a congressman or a political party more money in a year than I’ll earn in the next decade.

The result is that companies like Disney can profit off the public domain (that’s where they got The Jungle Book–author Rudyard Kipling didn’t make a dime off the Disney movie) without ever putting anything into the pot. Movies like Casablanca, The Wizard of Oz and Gone With the Wind, which would be public domain by now if the Sonny Bono Copyright Act hadn’t passed in 1998, remain locked up.

I doubt the public domain issue is something that’s going to energize the masses enough to force the issue into Congress. At least not in the short term. Most people have no clue what “public domain” means. They just know that around Christmas, suddenly 50 of their cable channels start playing It’s a Wonderful Life 24 hours a day. If any of them ever bother to ask, they find out it’s because the movie is in the public domain and anyone can broadcast it without paying for it. Then they shrug their shoulders and reach for the remote and look for tanks or bulldozers or football.

But this is a battle we have to fight.

Since writing to our Congressmen is futile–I may do it anyway, hoping that maybe my word carries a couple of grams’ worth more weight since I have produced a number of copyrighted works–we’re going to need to resort to something else: Civil disobedience. If a law can’t be counted on to be kept by 70 percent of the populace, it’s not enforcable and the law will chance. The most recent example of this is speed limits.

This doesn’t mean I’m going to run out to Gnutella and Kazaa and download everything in sight. As much as I may disagree with Aimee Mann’s political views, she has more than the right to be paid–she has the need to be paid. She’s not working a steady 40-hour-a-week job so she needs those record royalties to pay her bills. Taking her music without paying for it is no different from withholding my 40-hour-a-week paycheck.

But when the copyright would have rightfully expired by now anyway, I see no moral or ethical problem in taking it.

For example, there’s the Non-US Online Books Page that lists old books that are out of international copyright but not U.S. copyright. Books make you look smart, right? Download them, unwrap them with a text editor like Metapad, and then you can load them into Word and set the font and size to whatever you want. Duplex-print them (or print the odd pages, let the pages cool, then put the pages back in and print the even pages) and comb bind them or put them into cheap $1 3-ring binders, or take up bookbinding as a hobby. Fill up your bookshelves with free books you may not necessarily ever read. Be sure to include legitimate public domain books in your collection as well.

Or, since I know the majority of you won’t do that, amass a huge collection of early ’50s rock’n’roll tunes. The copyrights have expired in Europe. Import cheap European bootlegs, or get them through Gnutella. Share them with friends. Record a shelf full of CDs. If your hobby is music, sample and re-use the living daylights out of them. If you’re a European musician, do us States-siders a favor and use a 1950s-era sample in every song you record so that your colleagues over here start wondering why they can’t do that.

Sometimes civil disobedience is the only way to overthrow oppressive laws.

Finally–GPL antivirus for Linux

Clamav is a free (GPL) virus scanner for Linux and other Unix systems. It seems to work well. The price is right.
There are very few viruses for Linux, so few that most people don’t waste their time with virus scanning. But if the machine is acting as a server for clients that are vulnerable to viruses–cough–Windows–cough–it’s a good idea to have antivirus software on your server, just so you know your clients are safe.

Debian packages are in Sarge and Sid. Source can be downloaded and built from the link above. Once it becomes better known, it should appear in RPM distributions such as Red Hat in time.

It’s just a scanner, but if it finds an infected file, you can clean it manually with free tools you download elsewhere. Clamav will take care of alerting you, the price is right, and the platform’s right. It’s always been hard to find antivirus software for Linux of any sort, so Clamav is a welcome addition to the family.

We’ll talk a lot more about servers in the coming days.

This unusual case wants to house your next PC

The Lope I-Tee computer case is, well, shaped like a T.
When David Huff e-mailed me about it, he called it interesting. I’ll certainly agree with that.

Here’s the idea: You mount the motherboard up against the back plane of the case and put the drives and the power supply up front, yielding a case that’s not as deep as a conventional case and cools better. Allegedly.

I hesitate to write about it because I haven’t worked with one, I haven’t tested one, and I haven’t even seen one. Hmm. I really don’t know anything about it but of course I have an opinion about it. I feel so Slashdotty.

One big advantage of a layout like this is that all the ports are on the side where you can see them and get to them easily. The biggest disadvantage of a layout like this is that all the ports are on the side where you can see them, and depending on the way your desk is set up, they might be on the wrong side.

USB peripherals and front-mount USB ports are the usual cure for fumbling around the back–you can plug your digital camera or other things that move around a lot up there–but plugging your other peripherals in the back hides the cables and prevents things from getting too unsightly. Let’s face it, plugs and cables don’t fit traditional, conventional ideas of a thing of beauty.

On the plus side, cases that disassemble easily are always nice, as are cases that take up less space. But a couple of minutes with my ruler and my ATX cases shows this case isn’t any less deep than most of my mainstream cases, and due to its shape, it is considerably wider. I’d love something that genuinely took up less space on or under my desk, but this case won’t be it.

This case won’t flop on the marketplace though. They claim it improves cooling. Whether that’s true or not doesn’t matter. People buy aluminum cases because they supposedly conduct heat better. The reality is the difference in heat conductivity between expensive aluminum cases and cheap steel cases is nearly zero, and what difference you can measure is more likely due to aiflow than its material. Enthusiast overclockers still buy them anyway, hoping to get an extra 5 MHz out of their overclock. The same kind of people who buy aluminum cases for overclocking will go for the I-Tee, especially if the I-Tee’s cost is close to that of a mainstream case.

I can’t make any recommendations for or against it, based on not seeing it. But I’m willing to go out on a limb and say this–or a design like it–will survive at least as a niche product.

Umm… Don’t water-cool your power supply

I saw a thing on Slashdot this morning about water-cooling your power supply. One word: Don’t.
I’ve worked inside a power supply twice–both times to replace a dead fan. One time I touched a heatsink that picked up a charge from somewhere–either a voltage regulator or a capacitor. Anyway, it really didn’t feel good. Beyond that, it made me jump.

Not a project you want to undertake if you don’t know what you’re doing. And if you do know what you’re doing, you probably already know it isn’t something you want to do be doing. Anyone who uses the word “electric” to describe something pleasant has obviously never experienced anything electric flowing through them.

I’ll pass, thanks.

Vaguely productive Saturday

When I gained consciousness Saturday morning, I was on the phone.
I don’t remember it ringing. I don’t remember the caller identifying himself. All I remember is a coworker describing a problem with a tape backup. I had to ask him at least three times which server it was, and it took me a few minutes to figure out where that server was and what it did.

That was about 5:15 this morning. By about 6, I’d figured out what went wrong with the backup, gotten it running, and crawled back into bed.

Such is the life of the professional sysadmin. The 1-AM road trips to Miami Street in south St. Louis or to Highway 40 and Mason Ridge in Town & Country are nearly as delightful. But having a regular paycheck really is delightful.

The phone rang again about 9. I’d told the world I’d be up by then. But I hadn’t counted on being roused from a deep sleep when I was half done. I was slightly more coherent this time–I remember the phone ringing, I remember clumsily knocking the phone and the base off my nightstand, and I remember picking it up and saying hello. I didn’t remember I’d promised to edit video that morning.

So I spent much of the day assembling clips, hunting down stray frames, and generally polishing a pair of just-over-two-minute videos.

During my breaks, I investigated the possibility of upgrading to the latest version of b2 0.61. It works and its feature list is impressive–not far off from offering what Movable Type offers out of the box and in some ways superior–but I couldn’t get all of Steve’s custom code to work with it yet so I haven’t gone live with it.

My girlfriend called around 8 pm. I told her I was tired. She called me an old man. I was too tired to protest. She told me she replaced her Vin Diesel wallpaper on her computer with a picture of the two of us.

I’m moving up in the world.

Or maybe I dreamt that last part.

Rethinking Movable Type and b2

A very interesting discussion today made me re-think the importance of a content management system such as Movable Type or b2.
I was talking with two people whom I expected would be among the last to even consider dropping their long-standing practice of creating their daily writings with FrontPage and moving to a CMS approach. (Saying their names would be name dropping and it’s irrelevant.) Their questions made me really question what the advantages to this system are. That’s good.

Products like Radio Userland and Trellix are really just a step beyond FrontPage, in my estimation. They’re designed for journals, rather than general purpose Web design, which probably makes them faster and easier to use and certainly cheaper. But you still get flat, static files. Radio will allow readers to navigate by date, so they can quickly get to last Tuesday’s entry–assuming that for some reason they already know they want to read last Tuesday’s entry. (Sometimes they will, sometimes they won’t.)

Manila and Blogger move all of Radio Userland’s work to the server and gives you an integrated search engine, which is one more step in the right direction.

But a true content management system takes a reader’s daily entries, stores them in a database, and then when a reader asks for the content, generates HTML to send them. Movable Type does this generation in advance; b2 does it on the fly. There are advantages and disadvantages to both approaches; it’s not worth dwelling on.

What b2 and Movable Type give you over static pages is significant. Maybe you like what I wrote Thursday about video editing and you want to read more stuff like it. Well, I happen to have a category called video. Click on it and you get everything I’ve ever written and put into that category. When I post new content, I just tell the system what category to put it in, and it does the rest of the work for me.

Also, b2 and Movable Type make it significantly easier to gain traffic from search engines like Google. Once an entry falls off the current front page (usually set to show a week’s worth of entries), it gets its own page for time and eternity. One day’s entry is much easier for a visitor to make sense of than seven days’ worth. Individual entries can be titled appropriately, which makes Google rank it higher than pages that aren’t titled. Both of these make a reader more likely to visit.

Since b2 and Movable Type use databases, it’s easy to query the database for similar content. It’s easy to display current content. When someone visits this page, even if they grab a story that’s four years old, they get the same sidebar as my current page, which contains recent stories of note. If one of those stories grabs the visitor’s attention, I’m more likely to turn that visitor into a regular reader.

It’s also fairly easy to make b2 or Movable Type display links to the last few entries in the same category at the bottom of an entry. (I really need to implement this.) Imagine if someone likes my video editing story, gets to the end, and sees links to five more stories like it? Do you think the reader is more likely to click on one of those links than s/he is to go looking for something else like it? If the reader has to go looking on his or her own, I’m probably out of the picture. It’s easier to go back to Google. But if the reader reads another story or two of mine, I get more chances to get my hook in.

One advantage for me–this was a terrible turn-off for one of the others, as he keeps tight control on other people’s content on his site, and that’s one of the things his readers really like–is the comments system. I like leaving all of my content open to all for comment. I get very little e-mail and sometimes other people answer questions for me. That’s not necessarily a plus. At least it’s easy to turn off the feature entirely.

There are some less-obvious benefits as well. Both b2 and Movable Type offer newsfeeds–small, downloadable XML files that programs can download and use to display headlines off your site, complete with links to the full story. News aggregators are becoming popular among certain segments of the Internet community; already a significant portion of my traffic is newsfeed-related. This allows people to keep my newest stuff on their desktop or display it on their own Web pages–almost like the ill-fated PointCast, only this time likely to succeed just because there isn’t a necessary business model. This feature makes keeping up with my site, or a large number of sites like mine, trivial.

One advantage to me since I spent a weekend or so setting up a CMS for the first time has been that I don’t spend any time editing HTML anymore, short of inserting hyperlinks and inserting emphasis. I write, and that’s it. Some days I can write my entry in 15-20 minutes. On those days, I spend about 15-20 minutes on my site, unless it’s been a heavy comments day, because I just write in my preferred tool of the day, copy and paste it into b2, click a button, and within a few seconds, my new stuff is live.

Another advantage to me is traffic. Having entries small enough for people to link to and small enough to facilitate locating search terms quickly, Google treats me very well. This month, over 26% of my total traffic is coming from Google. (By comparison, 31% of my traffic comes from bookmarks.) And I’m not even doing everything I can–yet–to kiss up to Google. And since there are plenty of links on the sidebar to content that’s either fresh or compelling by some past measure, chances are someone will click on at least one other entry here, which gives me two chances–not just one–to turn that visitor into a regular reader.

If you’re currently using a tool like FrontPage or Trellix or Radio Userland to create your daily journal/blog/whatever you want to call it, you ought to give a full, complete, content management system-type program like Movable Type or b2 a look. Movable Type is easier to set up, but if you have programming ability, b2’s setup will allow you more flexibility on your site output.

Migrating a lot of existing content can be a pain. You can look at doing what I did–operating the sites in parallel, leaving the old content up and running but putting the new content in b2/Movable Type–or you can try to enlist some help in getting the old content moved in. Even if the old content stays put, it remains no less accessible than it is now. The new content just becomes much easier to navigate and cross-reference and mine for the juiciest bits.

But no matter how painful the changeover, I believe the categorization, the dynamic nature of the front page, and the ease in finding older content of interest will only increase your readership. It certainly has for me.

A reminder: 30 Days to a More Accessible Web Site

In a conversation today, I referred to Mark Pilgrim’s excellent 30 Days to a More Accessible Web Site.
This is must-read material. I confess to being guilty of neglecting most of the things in this piece, even though I would have gained substantial benefit from some of it at a recent point in my life, when I wasn’t able to operate a mouse and could barely keyboard.

I implemented the “add titles to links” feature. It required me to hack some PHP and is certainly the most substantial thing I’ve implemented without Steve’s help. It’s not much but it’s nice, even for those who have no disabilities–now, when you mouse over a calendar entry, the title of the entry pops up, like a tooltip. And for those using speech readers, now my calendar starts to make some sense.

As a bonus, some of this stuff will make Google treat you better if you implement it.

Read it. Download a copy and save it to your hard drive. And start implementing it.