Skip to main content

Airport Extreme Powerbook, poor range

**USE AT OWN RISK, IF YOU DO THIS AND FRY SOMETHING, NOT MY FAULT, and DON'T ASK ME FOR HELP, I WROTE THE INSTRUCTIONS FOR YOU**

I have a 15" Powerbook, 1.67 Ghz. (not the HD screen model, the one before it). The Airport Extreme range really really sucks in it. I can't go to the other side of my house, and have it work.

I am also currently in a hotel where, apparently, the WAP is really far away from me or something, because I have one bar. So, I googled solutions.

I saw a bit about reset-ing my PRAM, so I did that. (Turn off computer, hold down Command + Option + P + R, and turn computer on, hold buttons until the Apple boot sound, and release). This will reset your NVRAM/PRAM and may help. I did that. I don't know if it helped at all, but I still only had one bar.

I saw a bit about reset-ing my PMU, so I did that. (Turn off computer, unplug, remove battery, and then press and hold the power key for 5 seconds -- i did it for 10.) This will reset your PMU. I did that. I don't know if it helped at all, but I still only had one bar.

So I googled some more. I found a solution online, that I am willing to share:

Hold down the Option key, and click on the AirPort icon in the menu bar.
select About AirPort...
The Apple Framework version is what you are looking for, mine was 421.13.0

However, the current Intel Framework is 426.1.0
That's quite a difference, so I thought to myself, where can I get the 426.1.0 Intel framework. OSX is universal binary, so that shouldn't matter... right? So this is what I did.

I went to Apple.com -> Support -> downloads, and I downloaded the 10.4.5 INTEL update. Now, after you download it, Apple is going to automount and run this thing, which, obviously, since your on a PPC, it can't do. Right click on the package and select "Show Package Contents".
You will see a file called "Archive.pax.gz".
Double click on it. It will untar/gz itself onto your desktop.

Shut off your airport, by clicking the icon in the menubar, and click "Turn Airport Off"

Open Terminal, type:
mkdir backup-framework
cd /System/Library/PrivateFrameworks
sudo mv Apple80211.framework ~/backup-framework/
sudo mv ~/Desktop/Archive/System/Library/PrivateFrameworks/Airport80211.framework/ .
(notice the period at the end, for move to current directory)

This will move the Intel 426.1.0 version that you just downloaded to your Airport80211.framework folder.
Now type:
open /Applications/Utilities/Disk\ Utility.app/

This will lauch Disk Utility (or you can go to finder, Applications -> Utilities -> Disk Utility) and click on "Repair Permissions on Disk" or whatever it says. So it will set all that stuff you just put there, as root. (As well as correct whatever else is wrong with your system).

Restart System.

Turn Airport back on.

Now, I noticed a couple things:
1. My computer booted in like, 2 seconds.
2. My Airport now had 4 bars, sitting in the exact same spot where I had 1.

Driver? Don't know. But it worked for me.

Comments

Popular posts from this blog

Offset, Depth, Distance, and Within

Without going off the deep-end here and discussing every single Snort rule keyword, I just wanted to touch on a few modifiers that people sometimes misunderstand.  They aren't difficult, and hopefully after this explanation and a few examples, I can clear some of the air around these five modifiers.

The five modifiers that I am talking about are
OffsetDepthDistanceWithinnocaseThese five modifiers are not keywords of themselves, but rather they apply as modifiers to another keyword.  That keyword is "content". The content keyword is one of the easiest pieces of the Snort rules language as all it does is look for a particular string.  So for instance if I wanted to look for the word "joel" within a packet.  A simple:
content:"joel";Would allow me to do that.  The interesting part comes into play when you want to specify where inside of a particular packet you want the string "joel" to be looked for.  If you are running just a plain content ma…

Writing Snort Rules Correctly

Let me start off by saying I'm not bashing the writer of this article, and I'm trying not to be super critical.  I don't want to discourage this person from writing articles about Snort rules.  It's great when people in the Snort community step up and explain some simple things out there.  There are mistakes, it comes with the territory.  If you choose to be one of the people that tries to write Snort rules, you also choose to be someone who wants to learn how to do it better.  That's why I write this blog post, not to bash the writer, but to teach.

I noticed this post today over at the "Tao of Signature Writing" blog, and to be honest I glanced over most of it figuring it was a rehash of things I've already read or things that have already been written from countless people about "Here's how you write Snort rules!".  I scrolled down quickly skimming, not reading at all really, and noticed this part:
Now, let us look at the second questio…

Safari 5.1.4 now available

Safari 5.1.4 now available, fixes issues and improves performance | TUAW - The Unofficial Apple Weblog:


Improve JavaScript performanceImprove responsiveness when typing into the search field after changing network configurations or with an intermittent network connectionAddress an issue that could cause webpages to flash white when switching between Safari windowsAddress issues that prevented printing U.S. Postal Service shipping labels and embedded PDFsPreserve links in PDFs saved from webpagesFix an issue that could make Flash content appear incomplete after using gesture zoomingFix an issue that could cause the screen to dim while watching HTML5 videoImprove stability, compatibility and startup time when using extensionsAllow cookies set during regular browsing to be available after using Private BrowsingFix an issue that could cause some data to be left behind after pressing the "Remove All Website Data" button