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.
Copy Existing Filename to 'Save As' Field
While many utilities provide file naming automation, they're mostly overkill for those cases when you need to make small variations in file content while ensuring the documents group together in a "by name" list.
In the Save As dialog, the default name is the current document name. You can quickly change this to match any existing file.
1. Make the list of files the active element.
2. Click on a grayed-out filename, which momentarily turns black.
3. The Save As field now contains the filename you just clicked.
You can modify the name (adding, say, "version 3") or overwrite that existing file you clicked.
AirPort Client Update 2009-002
Set up short abbreviations which expand to larger bits of text,
such as "Tx" for "TextExpander". With the new custom keyboard,
you can expand abbreviations in any app, including Safari and
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.