In case you haven’t heard about it elsewhere, there are some 2001-2003-era motherboards having problems with leaky capacitors.
Beware the leaky capacitors
Sam’s Club offers $299 Red Hat Linux boxes
I just read today that Sam’s Club is about to start offering 1.1 GHz Duron PCs running Red Hat Linux for $299.
The machines are beefier than Wal-Mart’s $199 Microtel PCs running Lindows and Lycoris. The machines don’t exactly compete with one another; the 800 MHz Microtel boxes are good enough for word processing and e-mail, and Lindows and Lycoris target users with simple needs. Red Hat targets people with a little more familiarity with PCs, as does AMD. Sam’s is also offering a $399 version with a 2 GHz AMD Athlon XP.
The machines are built by a Kansas outfit called CPUbuilders. The systems utilize a SiS chipset with integrated video. They use PC133 memory and not the newer, faster DDR memory. The 1.1 GHz model comes with 128 megs of RAM and a 20-gig drive; the 2 GHz model has 256 megs and a 60-gig drive. Both have standard amenities like Ethernet, modem, sound, and a CD-ROM drive. The budget model lacks a floppy drive, while the more expensive model has one.
They both appear to be solid, but basic, configurations. It’ll be interesting to see how successful they are in the marketplace.
Ah, so there will be a Railroad Tycoon III
I was playing Railroad Tycoon II on my girlfriend’s brother’s computer (had to test it out after rebuilding it, y’know), and I thought to check something. And I see that Take 2 has announced Railroad Tycoon III will be out the second half of this year.
No word about features or anything else. Aside from the sometimes-weak AI and the annoying inability to build tunnels–who puts railroad tracks up a mountain?–RT2 was awfully close to perfect.
The day after the Columbia
Please indulge me while I reminisce about the U.S. space program in the wake of the Columbia disaster.
We just lost the Columbia
Turn on your TV if it’s off. About 17 years after the loss of the Challenger, the Columbia broke up on re-entry this morning.
We lost the first teacher in space on the Challenger, and the first Israeli in space on the Columbia.
I’ll probably reflect on it more later. But it occurs to me that there aren’t many commercial airliners the age of the Columbia in use. I’m no aerospace engineer, but I’d love to hear the opinion of one on what the operational life of one of these craft ought to be. This is one of those where-were-you-when-you-heard? moments in history, like the Challenger and the WTC disaster.
Confessions of a SQL 7 junkie
My name is Dave, and I’m a Microsoft junkie. So are the people I hang out with every day at work. We’re all junkies. We’re addicted to the glamor drug of Microsoft SQL Server 7.
I’m still trying to recover from the nightmare that is Microsoft SQL Server.
You see, I have a problem. My employer and most of its clients rely heavily on SQL Server. SQL Server is a touchy beast. We have some servers running completely unpatched SQL Server 7, for fear of breaking a client’s application. No, I absolutely will not tell you who my employer is or who those clients are.
That makes us, in Microsoft’s eyes, socialism-loving pinko Commies, since we won’t migrate to SQL 2000. Unfortunately, SQL 2000 isn’t completely compatible with SQL 7. So we’re forced into being pinko Commies.
Part of the reason SQL Slammer hit was because of the touchiness of the service packs and hotfixes, and part of it was the difficulty in installing them. The hotfix that would prevent SQL Slammer requires you to manually copy over 20 files, mercifully spread out over only two directories. But it takes time and it’s easy to make a mistake. So Microsoft released a SQL 2000 patch with a nice, graphical installer. But the pinko Commies like me who still use SQL 7 have to manually copy files.
Now, SQL 7 isn’t vulnerable to SQL Slammer, but it has plenty of security flaws of its own. And there’s one thing that history has taught us about viruses. Every time a new virus hits, a game of one-upmanship ensues. Similar viruses incorporating new twists appear quickly. And eventually a virus combining a multitude of techniques using known exploits appears. A SQL Slammer derivative that hits SQL 7 in one way or another is only a question of time.
Someone asked me why we can’t just leave everything unpatched and beef up security. The problem is that while our firewall is fine and it protects us from the outside, it doesn’t do anything for us on the inside. So the instant some vendor or contractor comes in and plugs an infected laptop into our network–and it’s a question of when, not if–we’re sunk. Can we take measures to keep anyone from plugging outside machines into our network? Yes. We can maintain a list of MAC addresses for inside equipment and configure our servers not to give IP addresses to anything else. But that’s obstructive. The accounting department is already supremely annoyed with us because we have a firewall at all. Getting more oppressive when there’s even just one other option isn’t a good move. People in the United States love freedom and they get annoyed when it’s taken away, even in cases that are completely justifiable like an employer blocking access to porn sites. But in a society where sysadmins have to explain that an employer’s property rights trump any given individual’s right to use work equipment for the purpose of seeing Pamela Anderson naked, one must be picky about what battles one chooses to fight.
In a moment of frustration, after unsuccessfully patching one server and breaking it to the point where SQL wouldn’t run at all anymore, I pointed out how one can apply any and every security patch available for Debian Linux at any instant it comes out with two commands and the total downtime could be measured in seconds, if not fractions of a second. And the likelihood of breaking something is very slight because the Debian security people are anal-retentive about backward compatibility. The person listening didn’t like that statement. There’s a lot more software available for Windows, he said. I wondered aloud, later, what the benefit of building an enterprise on something so fragile would be. Jesus’ parable of building a house on rock rather than on sand came to mind. I didn’t bring it up. I wasn’t sure it would be welcome.
But I think I’ll keep on fighting that battle. Keeping up on Microsoft security patches is becoming a full-time job. I don’t know if we can afford a full-time employee who does nothing but read Microsoft security bulletins and regression-test patches to make sure they can be safely deployed. I also don’t know who would want that job. But we are quickly reaching the point where we are powerless and our lives are becoming unmanageable.
Such is the life of the sysadmin. It’s a little bit of a rush to come into crisis situations, and a lot of my clients know that when they see me, there’s something major going on because they only see me a couple of times a year. In the relatively glamor-less life of a sysadmin, those times are about as glamorous as it gets. And for a time, it can be fun. But when the hours get long and not everyone’s eager to cooperate, it gets pretty draining.
More Wikipedia adventures
The Wikipedia marked its 100,000th article this past week. It celebrated by getting Slashdotted. And when I checked this morning, its count stood at 101,999.
I visited this evening to try to find some information about Studebaker. In typical Internet fashion, I didn’t find what I was looking for. And then, somehow, I found myself researching for and writing Wikipedia articles about AMC, its Rambler nameplate, and its successor, Eagle.
How’d I end up going from Studebaker to the maker of the Jeep and the Rambler? Well, that brings up the useless trivia question of the day: What four U.S. automakers intended to merge in 1954 to form American Motors Corp.?* And the bonus question: Which of those two companies fell through?**
So now I’ve written about baseball players and New Wave bands (both too numerous to mention), computers and CPUs (I made a number of revisions to some of the articles pertaining to the 8-bit computers of my youth), tycoons (Mark Hanna and a hastily written biography of Cornelius Vanderbilt, who interestingly, despite founding a university, himself dropped out of school at age 11), my dad’s occupation and his religion, and now, cars.
* Nash, Hudson, Studebaker, and Packard.
** Studebaker and Packard, who merged with each other. Packard would supply engines and transmissions to AMC for a time, but the combined company ceased building Packards in 1958. The combined company merged with a number of other companies and ceased making automobiles in 1966.
Windows 98 CD-ROM drive not working? Try this
Occasionally, a PC’s CD or DVD-ROM drive will stop responding for no known good reason. Sometimes the problem is hardware–a CD-ROM drive, being a mechanical component, can fail–but as often as not, it seems, the problem is software rather than hardware. Here’s what to do with a Windows 95 or Windows 98 CD-ROM drive not working when the same drive works just fine in another OS.
If Windows has both 16- and 32-bit CD-ROM drivers, it can get confused and disable the drive to protect itself. The solution is to remove the 16-bit driver, then delete the obscure NoIDE registry key to re-enable the 32-bit driver.
Microsoft’s Slammer pain is good for everybody
SQL Slammer hit where it counts, including HP–historically, one of the biggest Microsoft supporters around–and Microsoft itself.
This is good. Really good.
Microsoft is one of its own biggest customers. Part of this is due to one of the worst cases of not-invented-here syndrome in the industry, and part of it is marketing. If Microsoft can run its enterprise on mostly its software, its argument that you ought to be able to run all of yours on it is much stronger.
When Microsoft feels our pain, that’s good. Problems generally get fixed. Not necessarily the way we want them fixed, but fixed. When Microsoft for whatever reason doesn’t feel our pain, things languish. Witness the development of Windows 9x late in its lifecycle, after Microsoft was able to run everything internally, including laptops, on Windows 2000. While Windows 98SE was fairly good, all things considered, Windows Me was so horrid that one of my magazine editors wrote me and asked me the least painful way to escape it. Windows Me was fast, but it was less stable than 98SE.
What happened? The patches were difficult to install, poorly tested, poorly documented, and it was extremely difficult to know when you needed them. Microsoft’s inability to keep its own servers sufficiently patched illustrates this.
Several things are likely to happen now. People will take non-Microsoft solutions more seriously and, in some cases, deploy them. A not-as-homogenous Internet is good for everybody. Meanwhile, Microsoft will be cleaning up its act, making it easier to ensure that their patches actually work and can be deployed with reasonable ease.
I still think we’ll have disasters like SQL Slammer again. But this is a good step in the right direction.
Update Expert is something for your NT power toolbelt
Now that most of the fun of SQL Slammer has died down, let me present you a tool that might have prevented it: Update Expert.
Basically what it does is query all the NT/2K/XP machines on your network, then query its own database, and tell you what Microsoft patches are available to you. Then it’ll help you download them and push them out. It even figures out the order to install the patches (important) and knows which ones can be installed together to minimize the number of reboots. It’s a lot better than running Windows Update on every PC on your LAN.
I have no connection with St. Bernard Software. My former boss used it and swore by it; when I changed jobs, I introduced it to my new boss. I recommend it because I use it myself.