Upgrade diary: HP Pavilion a305w

Wow, what a slug. Want me to tell you how I really feel?

Typical Black Friday special from years past. Cheap, but what a limiting future. Here are your handful of options. As far as I can tell, there are about eight of them.

Read more

Are Black Friday computers a good deal?

Black Friday is going to be here before we know it. And historically, that’s been a good day to snag a deal on consumer electronics. But does that hold for computers?

I’ve studied many Black Friday computers–I have two Black Friday specials from years’ past sitting in the basement as I write–and I have to say that when it comes to those, you’re getting what you pay for. Yes, they cost less than computers from September and October. But there’s a good reason for it. Read more

It’s been 15 years, and computer stores haven’t changed much

In the early 1990s, I learned how to fix computers because I got tired of long waits and shoddy repairs from computer stores.

Last month I took a friend to go buy a computer. I didn’t want her to get stuck with retail junk, so I took her to a computer store that I knew sold quality parts. Plus I know the owner. He wrote an O’Reilly book too. I figured it would be a smooth experience, since I knew exactly what to ask for. The salesperson said he’d get back to me within two days with a quote, then it would take about a week to build the system after we gave the OK. Seems pretty smooth and reasonable.

It turned into a nightmare. Or at least a mess. Read more

Tribute to the Asus SP97-V

In need of an obsolete but reliable PC for a project, I searched a dark corner of my basement, a last stop for castoff PCs before being sent off for recycling. I found one. Predictably, it had an Asus motherboard in it. Specifically, it had an Asus SP97-V in it, a budget Socket 7 board from the late 1990s sporting a SiS chipset with integrated video that worked well with Cyrix and AMD CPUs.

Read more

The rise and fall of Shack, and how to fix it

Wired has a nostalgic piece on the not-quite-late, not-quite-great Radio Shack. I think it’s a good article, but it glosses over part of the reason for the store’s decline.

It blames computers.But blaming computers ignores Tandy’s long and successful run in that industry. Most Apple fanatics and other revisionist historians conveniently overlook this, but when Apple launched the Apple II in 1977, Tandy and Commodore were right there with competing offerings. I don’t know about Apple, but Tandy and Commodore were selling their machines faster than they could make them.

Read more

Slimming down Windows XP for SSDs and nettops

I found a very long and comprehensive guide for using Nlite to reduce the size of a Windows installation.

The guide is geared towards an Asus Eee. But it should work well on pretty much anything that has an Intel CPU in it.A couple of tweaks to his settings will make it suitable for AMD-based systems. Just remove anything Intel-specific, and add back in anything specific to AMD, and there you go.

And if you have a multi-core or hyperthreaded CPU, leave multi-processor support in.

I also recommend slipstreaming SP3 and all the hotfixes you can. Then you don’t have to run Windows Update, them, and you don’t have to clean up after it either. I haven’t investigated all of the whys and wherefores, but I’ve noticed that the more you slipstream ahead of time, the smaller your Windows directory ends up being. I have some systems at work that are constantly bursting at the seams on their system partitions. Other systems, which were built later from a copy of Windows with more stuff slipstreamed in, have a lot more breathing room.

Using the i64x.com instructions, you can pretty much count on getting a Windows XP installation under half a gig in size. That makes life with a small SSD much more bearable, since a typical installation tends to take a couple of gigs these days.

I’ll add some tips of my own. Inside the Windows directory, there are some subdirectories named inf, repair, and servicepackfiles. Compress those. That’ll free up some more space–at least a couple dozen megabytes in most cases.

If you’re really cramped, compress the whole Windows directory. Boot time actually decreased by a couple of seconds when I did this (down to 12 seconds from about 14), but software installations slowed considerably. But for everyday operation, you could almost consider NTFS compression a performance trick. It makes sense; an SSD can sometimes saturate the bus it’s connected to, so data compression lets it shove 20-50% more data through that saturated bus.

The downside is that when you install something that lives in the Windows directory, it has to not only copy the data into place, but also compress it. Installing the .NET Framework on a system with a compressed Windows directory takes a while.

A good compromise is to install pretty much everything you think you’ll need on the system, then start compressing.

It’s difficult to make a case for compressing the entire drive, however. Most modern data file formats are compressed–including all modern media formats and Office 2007 documents–so turning on NTFS compression on directories storing that kind of data gives no benefit, while introducing overhead.

The "good enough" PC

PC World has a treatise on “good enough” computing. This isn’t actually a new trend but it’s never stood still for as long as it has now.Jerry Pournelle used to describe cheap CPUs from Cyrix and IDT in the late 1990s as “good enough.” Running at 166 and 200 MHz, they ran Windows 95 and NT4 and Office 97 just fine. They weren’t good gaming CPUs, but for everything else, they were great, and you could build a computer with one of those and save $100 or more over using a comparable Intel CPU.

Trouble was, the mainstream moved. Intel knocked off all the upstarts by starting a megahertz war, and AMD came back from a near-death experience to compete. The requirements to run Windows increased nearly as rapidly, and it wasn’t all that long before 900 MHz was pretty much the bare minimum to run Windows comfortably.

But chips kept getting cheaper, and today you can buy a 2 GHz CPU for pretty close to what a Cyrix or WinChip CPU cost. But you get more than 10 times the power for that money. And Windows XP runs perfectly comfortably on a 2 GHz CPU, whether it’s a new Intel Atom or Celeron or a 5-year-old corporate discard. So does Office 2003, which is the very last version of Office that any sane person would want to use.*

*Besides being the evil spawn of Windows Vista and Microsoft Bob, Office 2007 also crashes more often than Windows 3.0 did. The only way I can go a week without losing work from Office 2007 crashing is to go on vacation.

The PC World author claims that Linux and Open Office running on Intel Atom CPUs will be the undoing of Microsoft. I think that’s a bit of a stretch. Netbooks running Linux got returned to the vendor a lot. I suspect the biggest reason is because they probably couldn’t figure out how to get their USB mobile broadband cards–I’m talking the stuff that cellphone vendors offer for 50 bucks a month–working in Linux. That, and they probably couldn’t get Flash working so they couldn’t see Facebook and other popular sites the way they could on their regular PCs.

Frankly, the two things that keep me from buying a $200 Dell Vostro netbook this weekend are the price of mobile broadband ($50 a month), and my concerns about the reliability of anything sold by Dell in the last 5-6 years. I work with a lot of Dell equipment, and once the warranty goes, their machines do not age gracefully at all. But I think Dell will sell a lot of these units, because the price is absurdly low, they weigh two pounds, and they run anything but 3D games and intensive graphics apps nice and fast. Sure, a dual-core system with its memory maxed out and a solid state disk will outrun it, sometimes even running circles around it, but that system will also cost 10 times as much.

I do think Office 2007 is the best thing that ever happened to Open Office. Open Office’s interface is a lot more familiar and doesn’t hide anything, and while it may not be as fast as Office 2003, it’s certainly faster at most things than Office 2007 is.

Linux has been usable for basic computing for a very long time, but getting it installed and configured remains a challenge at times. A netbook that connects painlessly to the wireless networks in restaurants and to cellphone makers’ mobile broadband cards while running Linux probably stands a chance. Giving some automated, easy means to synchronize application data and web bookmarks between the netbook and a desktop PC would probably help a lot too–something that does the same thing that Activesync does for moving data between Windows PCs and Windows Mobile PDAs. Will these things happen?

But I do think an era of “good enough” is upon us. There was a time when the top-of-the-line PC would be entry level within a year or two, and that’s not really true anymore. The entry-level PC of today is comparable to the mid-range PC of five years ago. For most of my lifetime, basic computing on a five-year-old PC was always painful, no matter how good that PC was when it was new. That’s not the case today.

Graphic designers, video producers, and scientists will always need ever-more powerful systems for their work, so they’ll continue to drive the cutting edge. But everyday computing is stabilizing. I don’t think Intel wants the future of everyday computing to be the cheap Atom CPU, but at this point it may be impossible to avoid it. If Intel decides to quit playing in this space, AMD can design something comparable to replace it in the marketplace. The Geode won’t cut it, but something based on the Athlon XP architecture and built using a modern process certainly would.

And frankly I’m glad about this development. It’s been nice not having to buy a new computer every three years or so.

First impressions: Intel D945GCLF2, aka the dual-core Atom desktop board

I was never able to get my mother in law’s computer to misbehave, but my son was. He’d crawl up to it, press whatever buttons he could find, and invariably it would reboot and give beep codes.

Intel's dual-core Atom boardSo I decided the best bet would be to drop in a new system board. I went against all my usual practices and bought an Intel. Further research showed the stock board was made by MSI. I’ve never had good luck with MSI boards, although I know they’re popular. This one lasted five years, which is five years longer than the other two MSI boards I’ve seen. I was able to find an exact replacement, but the $70 price scared me off. Especially without knowing whether it was the board or CPU that was bad. With an Award BIOS, beep codes generally mean bad memory (a memory tester vindicated that), a bad CPU, or bad motherboard. Not very specific.

I wanted something reliable, cheap, and no slower than what she had. With an unlimited budget, I’d buy an Asus board, since I have a 6-year-old Asus board in the basement that’s still humming like new. Gatermann ran an Asus P55T2P4 for 10 years before it died, and I’ve seen lots of other Asus boards reach old age. Unfortunately, I couldn’t find an Asus motherboard/CPU combo for less than $100.

So I went with Intel’s desktop dual-core Atom board by default. Intel motherboards are as unexciting as they come, and I hate monopolies, but the board has a 3-year warranty and I know from my experience supporting Micron desktop PCs with Intel boards in them that it’ll last at least that long.

I had to change the ATX backplate, but I was glad to find the Compaq front-panel connector had the same pinout as this Intel board. Removing the old backplate was the hardest part of the installation, as the board mounts with just four screws.

I entered the BIOS on powerup and was disappointed to see I couldn’t disable the onboard video. I really wanted to plug a video card into the lone PCI slot and disable the onboard video to save some memory and bandwidth. I also found enabling USB boot was clunky, but other than that, the BIOS was predictable.

The board itself runs extremely cool. The power supply fan doesn’t blow out hot air or even warm air–it’s cool.

You have to slipstream SP2 or SP3 to install Windows XP on this board. I haven’t done that yet, so I don’t know yet how well it runs XP. But being a dual-core, 1.6 GHz CPU, it should be OK. When XP was introduced, 1.6 GHz single-core CPUs were mainstream. It may not keep up with the old 2.1 GHz AMD Athlon XP the system came with, but without all the crapware Compaq loads at the factory, I’ll bet the system will be faster than it ever was even if the new CPU isn’t quite as fast as the old one.

Cheap upgrades

Yesterday, during my weekly garage sale adventures, I bought some computer equipment. Among the haul: a Biostar Socket A motherboard with an AMD Sempron 2200+ CPU and 512MB of RAM. It’s not state of the art, but can hold its own against some of the stuff still on the market, and it’s a big upgrade over the 450 MHz Pentium II that’s been powering this web site since July 2002.I swapped the board into my 266 MHz Pentium II. That first-generation P2 was a useful machine for me for a while, but mostly it’s just been taking up space. I had to do some slight modifications to get the newer board to bolt in, but it fit without too much trouble and now some of the 11-year-old hardware is useful again. It reminded me a lot of my college days, when I used to drop 486 and Pentium boards into IBM PC/ATs.

Debian installed on the upgraded system with no complaints, but I quickly found my Linux command line skills are rusty. And there have been enough changes in the last six years that I can’t just copy over /var/www and /var/lib/mysql and expect it to run like it used to.

So I’ll apply my 15 minutes per day principle. My chances of finding a block of 2-3 hours to get it all done are near zero, but I should be able to find a few minutes each day. So one day I can move the databases, then I can move the HTML and PHP another day, convert to WordPress still another day, and maybe, just maybe, have a vastly improved site in about a week if it all goes well.

Buffer overflows explained

Buffer overflows are a common topic on a Security+ exam. The textbook explanation of them is confusing, perhaps even wrong. I’ve never seen buffer overflows explained well.

So I’m going to give a simplified example and explanation of a buffer overflow, similar to the one I gave to the instructor, and then to the class.

Read more