Safari 4 Beta Destroyed My Finder

I don't know about anyone else, but after installing the new Beta of Safari 4 my Finder kept dying. Poor beast would lock up. I'd force quit her and she'd never come back to life. The only way I could get her back was to either A) hard reboot with the metal button on the front of my tower (a PPC G5, mind you), or B) SSH in and: sudo killall loginwindow

Safari 4 Beta: The Finder Killer

Bummer.

Since uninstalling it, using the included uninstaller (which also hung after the "Restart" prompt, forcing a hard reboot), the problem has cleared up.

Anyway, this is just my experience, but word to the wise people. Beta means beta.

Oh well. Moving on.

Extending an Airport Network

UPDATE: It looks like there's actually a better way to extend an Airport network than the one I've outlined in this article. A few people have written in to tell me that they've had great success using the configuration "wizard" available in the Airport Express Utility. I haven't tried using this myself, but it does look exceedingly easy. So, definitely the thing to try first before you go into the twelve page set of instructions below.

Thanks to all who sent this in. I'll leave the detailed instructions below for anyone who's interested.

Man, I wish I'd known about this sooner.

Airport Utility Wizard: Quite Possibly A Better Way

A while back I got a second Airport Express in the hopes of using it to extend my existing wireless network. Doing so was fairly tricky and not anything like I'd expected.

I had initially believed — perhaps naively — that the process would essentially be a matter of joining the new Airport to the existing network the same way you'd add a new computer. This is decidedly not the case. It turns out that, in order to extend an wireless network across multiple Airports, you must set up what is known as a WDS network. Let's take a look at the process, which for me anyway, was fraught with difficulties that this article will hopefully help me (and you) avoid in the future.

Set Up the "Main"

The "Main" WDS Airport is the unit that will host the wireless network. It's the one that's connected to your cable modem, or your router, with an Ethernet cable. You'll connect the "Remote" Airports to the Main wirelessly, allowing them to extend the network. It's important to remember, as you continue with this process, that each new wireless node must be added to the main node in order for it to be seen by the WDS network. Ready? Here we go!

Wired Connection

  1. The easiest (and Apple-recommended) way to do all this is with a direct, wired connection, so grab yourself an Ethernet cable and connect your computer to the Airport that you want to be the Main unit. This is not absolutely necessary, but it will help to mitigate any problems you might have as you go making changes, since you won't be dependent on a wireless connection. You can skip this if it's easier.

Base Station Settings

  1. Once connected, open Airport Utility. You should see the Main at the very least.

    Extend Airport: Main Window

  2. Double-click the unit to open its configuration window. Begin in the Base Station tab by setting the name and password of the unit.
  3. The name will be the name of the base station itself, and the password is the one used to log in to and change the unit's settings. I recommend naming it something like "Airport-BS-Main" for easy identification. As always, make the password memorable and secure.

Extend Airport: Main Base Station Settings

Wireless Settings

  1. Under the Wireless tab, set the Wireless Mode to "Participate in a WDS Network." This is the key, really, to the whole shebang.
  2. It's also important to check the "Allow this network to be extended" checkbox.
  3. Here you'll also want to give the network a name. This is the name you'll use when joining the wireless network from your computer, so choose wisely and for the ages. I like clear nomenclature, so I went with "SystemsBoy-Wireless." Clever, huh?
  4. Set your encryption method. The Airport recommends WPA/WPA2 Personal, which I like too. Secure and compatible.
  5. Choose a channel, or use the default. It's all good unless you're in a super-crowded area, in which case trial and error is your friend.
  6. Finally, be sure to set your wireless network's password. This is the one used for joining the network from your computer. Two names, two passwords. I know it's confusing. But you're smart. You'll figure it out.

Extend Airport: Main Wireless Settings

WDS Settings

  1. Under the WDS Settings tab the Main WDS Airport's WDS Mode should be set to "WDS main."
  2. "Allow wireless clients" should be checked.
  3. You'll add your WDS Remotes later, once we've plugged in the other Airport in the next section.

Extend Airport: Main WDS Settings

Update and Test

  1. Once all this is set up, hit the "Update" button.
  2. The Airport will go and make the settings you just configured, which will require it to reboot.
  3. After the reboot, remove the Ethernet cable connect between the Airport and your computer, and (re)connect the Airport to the network/router.
  4. If all went well, you should see the classic green light on flashing on the Airport unit. You should also be able to connect to the Airport network wirelessly. If you don't or can't, reboot the unit again for good measure. Make sure you give it enough time before trying to connect to it. Five minutes should be more than enough.
  5. If, after all this, you still don't see the green light, you'll need to troubleshoot your connection in Airport Utility, which is beyond the scope of this article. But it's important to get the Main unit working as a wireless base station before proceeding. Everything depends on it. So get it working using the above settings.

Troubleshooting Tips

  1. Occasionally, after a reboot, the Airport will not be visible in Airport Utility. Simply restarting Airport Utility will sometimes fix this, so be sure to try it if you can't get connected.
  2. For whatever reason, this process took a few tries for me. So remember, a direct, wired Ethernet connection will aid in troubleshooting. This is recommended by Apple, and I concur.
  3. Don't forget, if need be, you can completely reset the Airport back to factory defaults and start from scratch using the super-secret reset button on the top of the device.

Set Up the "Remote(s)"

The Airport(s) you use to extend your wireless network are referred to, in WDS parlance, as "Remotes." With WDS Remotes you'll be able to join your wireless network — the same one you set up on the Main, with the same network name and password — from well beyond the reach of the Main. Remotes should, obviously, be placed within signal reach of the main, but far enough away to actually extend the reach of the network.

Wired Connection

  1. As before, this will all be a lot easier if you connect to the WDS Remote Base Station using an Ethernet cable. Be sure you're Remote has power, then connect with Airport Utility.

Base Station Settings

  1. With Airport Utility opened, you should still see Main, as well as the newly added, unconfigured Remote.
  2. Double-click the Remote unit to open its configuration window. Begin in the Base Station tab by setting the name and password of the unit.
  3. As before, the name will be the name of the base station itself, and the password is the one used to log in to and change the unit's settings. I called this one "Airport-BS-Remote" for easy identification.

Airport Utility: Airport Remote

Wireless Settings

  1. Under the Wireless tab, as before, set the Wireless Mode to "Participate in a WDS Network."
  2. Here too, check the "Allow this network to be extended" checkbox.
  3. For the Network Name you should enter the same name you entered for your Main — in my case, "SystemsBoy-Wireless." Remember: different Base Station; same wireless network.
  4. Your encryption method for the Remote should also match that of the Main.
  5. The channel can be whatever you want it to be.
  6. And, finally, the wireless network's password should match that of the Main Base Station.

Extend Airport: Remote Wireless Settings

WDS Settings

  1. Under the WDS Settings tab the Remote WDS Airport's WDS Mode should, not surprisingly, be set to "WDS remote."
  2. "Allow wireless clients" should be checked.
  3. And in the last box, labeled "WDS Main," you should the MAC (hardware) address of your WDS Main Airport. This can be found under the Summary tab of the configuration window. Each Base Station has two MAC addresses, actually: an "AirPort ID" and an "Ethernet ID." You want the Airport ID.

Extend Airport: Remote WDS Settings

Add the Remote to the Main

  1. Now here's where it gets a bit tricky. Both the Remote and the Main need to be aware of each other. So, now that your Main is configured, you should be able to see it in Airport Utility and open its configuration window. Open it so that both the Main and Remote configuration windows are open.
  2. Go to the Remote's summary window and copy its Airport ID to the clipboard.

    Extend Airport: Remote Airport ID

  3. Now go to the Main's WDS tab and hit the little plus sign to add a remote and paste the Airport ID number into the field.

    Extend Airport: Adding Remotes to Main

Finish

  1. With both Airports' roles now configured, and with each aware of the other, you should be good to go. Hit the "Update" button on the Main, wait a minute, and then hit on the Remote (so that the Main reboots first)
  2. Wait for them to reboot.
  3. Once rebooted the Remote should have a green light under the Status field of its Summary tab and should have no errors. If it complains about something, make sure the Main is working well over wireless, then give the Remote another reboot. If this still doesn't work, move on to troubleshooting.
  4. Once everything seems to be functioning without error, place the Remote Base Station in its intended physical location.
  5. Pat yourself on the back! You've just extended your Airport wireless network!

Make no mistake, extending your Airport network is a big, fat, sloppy pain in the booty. It's also extraordinarily handy in many cases where a single Airport just isn't cutting it.

Firefox Bookmarks

It just took me all freakin' day to discover where Firefox now stores its bookmarks. I thought I'd share.

All user-centric data — that is, all your preferences, cookies, bookmarks, etc — for Firefox are stored in:

~/Library/Application\ Support/Firefox/Profiles

Inside this folder is a folder that just uses a big long string as its name. Something like:

dswa56xw.default

Inside here is where are the goodies are stored. In particular, Firefox now stores your bookmarks in an SQL database called:

places.sqlite

Firefox Bookmarks" "Places?" WTF?

It actually makes sense when you realize that the Firefox folks are starting to move toward the "places" language to replace the idea of bookmarks, but like I said, all freakin' day I was looking for this.

So there you have it. From my process of elimination straight to your browser.

And don't forget to bookmark this page.

Google's Select All Conversations

In my ongoing adventures to move all my mail to Gmail there have been a few snags. One of them is the fact that Gmail only sucks down POP mail, which one of my many numerous email hosts does not support. The other problem has been one of management.

Gmail is becoming the de facto mail sorter for many folks. It has superior spam filtering, virtually unlimited — or at least more than you'll probably ever need — capacity, it can be searched using Google's legendary algorithms, and it can get mail from from any email account that supports POP, which most do. Aggregating your mail through Gmail has the additional advantage of keeping all your mail online and centrally located, so it can be read from any computer with a browser and an internet connection, and it's always in sync.

I've also come to prefer the Gmail approach to mail management. This basically boils down to one idea: tags instead of filters. So, in Gmail, instead of filing your mail in folders, you use what Google calls "labels," which are just tags, which are in fact text descriptors used to describe an email. The nice thing about labels is that an email can belong to more than one label at a time, giving you all kinds of sorting and viewing options. Good luck trying to do that with folders.

My approach to local mail management of late has been to keep all my mail in my Inbox — or once it's old enough, in an Archive box — and then to sort that mail into various views using Mail.app's Smart Folders. This is basically what Google recommends doing over the folder approach: Don't file, just search. This approach, however, no longer scales well on the Desktop, primarily because my computer is much slower than Google's server at this point, but also because Spotlight's algorithms are not quite as good as Google's.

Aside from the POP limitation, the only thing keeping me from moving entirely to Gmail was the plain fact that there was no way for me to Archive my 2000+ email conversations (which is what Google calls threads) in one fell swoop. So my Inbox sat there, completely full of mail. Unread messages might remain unread long enough that new read mail would pile up and bump them off the main screen and into obscurity. The only solution I could find to this was to go through what would have been hundreds of screens full of emails, hit "Select All" and then "Archive," and then to Archive everything as it came in ever after. Clearly what was needed — and this is true in a lot of online editors, including Wordpress' — was a "Select All" button that allowed you to select every message in the Inbox.

Recently, that option finally appeared. To see it, hit "Select All" in the Inbox view. After doing so, a subtle line of text will appear just below the selection bar:

Hit that and you suddenly, magically, amazingly have access to all your Gmail. Now you can archive it, label it, mark it with a tee — whatever you want. Finally I can keep my Inbox uncluttered. To see the Archived stuff, I just hit "All Mail" and there it is.

With this I think I may be moving entirely to Gmail at long last.

Aaaand... We're Back!

So if you've been obsessively checking the site tonight — and you really should have been — you may have noticed a bit of unscheduled downtime. This was just me trying to be clever and failing miserably. See, I've moved to a new web hosting provider, and I wanted desperately to make the transistion seamlessly. Obviously, no such luck. I borked the whole thing up. Majorly. Oh well, I wasn't down too long, and, hey, now I know better.

And, if you're wondering, I'm leaving my old web hosting provider, Web Hosting Buzz. Seems they have a rule that essentially forbids putting "downloadable files" greater than 500 kb. Yeah, that's right. Web Hosting Buzz gives you 1200 GB of storage and then limits you to files 500 kb in size. Sound scammy? I thought so too.

So, The Adventures of Systems Boy! is now living on a Media Temple Grid-Service account. We'll see how it goes. But my initial tests have shown the service to be quite reliable thus far, and I can't find anything that even hints at file size limits. But then, why would I?

Anyway, we're back in business again. Thanks for your patience.