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.
Manage Multiple ChronoSync Documents
If you have multiple ChronoSync documents and need to run your syncs or backups manually, you may find it taxing to open each ChronoSync document and execute it manually. There are two easy methods to simplify managing multiple ChronoSync documents.
- You can add the ChronoSync documents to a Container document. A Container holds multiple ChronoSync documents and enables you to control several ChronoSync documents as if they were one document.
- You can make use of the Scheduled Documents Manager window to collect and organize commonly used ChronoSync documents without scheduling them.
Both methods allow you to schedule or manually run your syncs and backups.
Visit ChronoSync Tips
AirPort Client Update 2009-002
scanning solutions for companies of any size. Make your life more
productive, mobile, paperless, and efficient with a ScanSnap
scanner. To learn more, visit: <http://www.ez.com/sstb>
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.