- Skip over Dan Benjamin’s “Interference” when it pops up in your newsreader on the 23rd; you’ve never had any AirPort trouble, and aren’t even sure what software version it is that you’re running. Besides, these software update problems only happen to other people.
- Wait three to four days for the word association between “airport update” and “trouble” to dissipate.
- Run Software Update.
- Note the appearance of AirPort and Bluetooth updates and install them.
- Note that nothing particularly noteworthy occurs.
- Next morning, note that signal strength is actually sitting on zero bars when you’re in the kitchen or at the dinner table, as opposed to the usual two bars.
- When you get to UWA, note incredible difficulty at getting online with the University Wi–Fi.
- Remember skipping over something about that AirPort update a few days ago.
- Pop open NetNewsWire and search for “airport”
- Scowl at NNW’s search function —lacking live searching and lacking a ‘Next’ button— for returning only the first result it finds… not what you were looking for.
- Search for “airport software 3.4” instead.
- Bingo.
- Realize that since you’re at Uni (and can’t get a connection right now) you can’t visit HiveLogic to read Dan’s article… and the excerpt isn’t particularly helpful.
- Go home.
- Read Dan’s piece, and the two linked pieces, at home on your own Wi–Fi; which still works despite the weak signal.
- Roll your AirPort software back to 3.31 with the help of the aforementioned article(s).
- Scowl at Apple for whatever “improvements” were made during this update.
- Get back to work.
- …
- …
- …
- Run Software Update.
- Note the appearance of AirPort Software 3.4.1 …a quietly revised update that, since installed, has caused none of the same problems as 3.4.
- Consider the fact that you should’ve checked for updates before the rollback rigmarole.
- Scowl at self.
Posted by Chris Clark on April 27, 2004 at 1:34 PM