Some Snow Leopard users have suffered from AirPort problems since 10.6 was released. In this client update, which requires 10.6.2, Apple says it has fixed three major bugs. First, it repairs some systems that, when upgraded from Leopard to Snow Leopard, could not turn AirPort on or off. Second, the update eliminates what Apple calls an "occasional" problem when using Wake on Demand, where network access would be unavailable. (Wake on Demand, new in Snow Leopard, lets a computer connected to an AirPort Extreme or Time Capsule base station be woken over either Ethernet or Wi-Fi for network access to advertised Bonjour services.) Finally, this update restores the capability to create software base station (look in the Sharing preference pane) or computer-to-computer networks to some MacBook, MacBook Pro, and Mac mini systems that previously had trouble.
Disinfect Your Keyboard
Keyboards, particularly those shared by multiple people, harbor huge quantities of bacteria. If you want to reduce the chances of picking up your co-worker's cold, you can disinfect your keyboard with disinfecting wipes. To avoid damage to the keyboard, be sure to:
- Unplug the keyboard before disinfecting it.
- Squeeze out any excess liquids from the cloth to avoid liquid dripping into the keyboard.
- Don't let any liquid from the wipe sit for long periods of time on the keyboard.
- Don't scrub the keyboard, just lightly wipe down. Rubbing too hard leaves behind more lint.
- Avoid cleansing cloths that contain bleach.
Visit Das Keyboard
AirPort Client Update 2009-002
Put your company and products in front of tens of thousands of
savvy, committed Apple users who actually buy stuff.
More information: <http://tidbits.com/advertising.html>
As a workaround I use the drop box feature now.
Could you describe your failure in a bit more detail? Is the AirPort loosing commection? Is the AirPort staying connected, but the file transfer stalls out?
If the transfer is just stalling out, you can try this command to see if it helps:
sudo sysctl -w net.inet.tcp.delayed_ack=0
It still stinks when you're one of the few with problems.