reesesWeb

Along with the rest of the world, I am frequently amazed at the incredible and awe-inspiring incompetence when it comes to Apple QA'ing their software updates.

Earlier this week, the Apple Airport 3.4 update came up on SU. Hey, it'll improve output control! I installed it, and discovered the reception meter dropped by a little bit. No big deal, it all still worked.

When I got home today, everything worked fine for about an hour, then pfft. The signal meter registered a signal, but I couldn't obtain a DHCP lease. I configured the host/gw addresses, to no avail.

Normally, I'd suspect the AP, a first-rev WRT54G with a custom firmware installation, because it seems like the weak link. However, we have over half a dozen wireless devices working fine, and one wired device (the Vonage box) running without a hitch. In addition, thanks to RSS aggregation and increased blog scanning ability, I was somewhat aware of problems with the 3.4 update, and that someone had written directions on downgrading to 3.3.1, the last version that worked swimmingly.

An hour later, everything is up and hunky dory. Maybe later I'll talk about how I scared a couple guys at the airport who made the mistake of asking how I liked the Treo 600. Hint -- it sucks ass, and I believe I used that exact phrase before starting off on a long list of its tremendous shortcomings.

Bookmark/Search this post with:

delicious | digg | reddit | technorati