Houshold DSL speed: 5.5 mbps down, .75 mbps upiPhone WiFi: 5.8 mpbs down, 0.71 mpbs upiPhone 3G: 2 mpbs down, 0.08 mpbs up
Monday, March 15, 2010
FCC iPhone speed tester: very slow upload in MSP
Sunday, March 14, 2010
OS X Backup: Apple's Backup 3.x
- Time Machine, Time Capsule and offsite backup
- Online backup – the security problem (it’s not the encryption)
- CrashPlan (or JungleDisk) instead of Retrospect 8?
- Freeing up Time Capsule space – and documentation for Time Machine and Time Capsule
Can't mount sparsebundle disk images over an AFP network
Saturday, March 13, 2010
Two Problems with SuperDuper backup
- Time Machine, Time Capsule and offsite backup
- Online backup – the security problem (it’s not the encryption)
- OS X Backup: Apple's Backup 3.x
- CrashPlan (or JungleDisk) instead of Retrospect 8?
- Retrospect 8 - no user guide?
- Freeing up Time Capsule space – and documentation for Time Machine and Time Capsule
- Airport Extreme: Firmware update, Time Capsule bugs, tips and fixes
Thursday, March 11, 2010
The OS X Snow Leopard "Connected As" MobileMe bug
OS 10.6 - how to change "connected as" default name - Mac-Forums.com
I have an imac & a macbook on my network. when I'm on my imac & i click on the sidebar to connect to my macbook, the same "connected as" name always comes up. i don't remember where this name came from (it's actually my mobileme email address) it's not a name i have listed under users who can share on my macbook. after connecting i have do disconnect then quickly click connect so i can enter in the username i want to use, if i don't then it automatically connects back under the name i don't want. i just want to reset the default "connect as" i guess I'm trying to say. i don't have this problem when connecting from my MacBookIt's a Snow Leopard bug. If you enable MobileMe Snow Leopard tries to authenticate with a remote machine using the MobileMe name instead of a username. I think it's some version of a directory service; in theory it probably lets you easily connect to a remote account with the same MobileMe credentials -- even if has a different username and password. It fails, however, if you try to connect to a share with a different associated MobileMe account.
Why you shouldn't use OS X ACLs
The somewhat less decayed alternative is to use OS X Access Control Lists (ACLs). They are not widely used, though some geeks use them to share media collections among multiple machine accounts. (This kind of file sharing is not otherwise possible [1] without hacks that remind us that OS X is a dying desktop solution).
This, however, is not necessarily wise. This warning is embedded in Retrospect Professional 7.7 Mac OS Client preferences for ACL backup ...
Allow the Retrospect Client to examine Access Control Lists (ACLs) on Intel Macintoshes. This may cause Retrospect to freeze due to a defect in Apple's implementation of ACLs.
[1] Last April Tidbits claimed iPhoto '09 does enable multi-user sharing. It is, however, still undocumented by Apple and thus risky. Even so, I might give it a cautious try once I happy with my 10.6 backup solutions. I'm not happy yet.
Sunday, March 07, 2010
Using an HDTV as a low vision monitor - initial test
Saturday, March 06, 2010
iPhone Voice Memos.app - the missing manual

The Voice Memos.app behaves differently if you're wearing an Apple headset. From a previous post of mine ...
Gordon's Tech: iPhone Voice Memos.app - the secret feature
I wasn't that impressed with Voice Memos.app when if first appeared with OS 3. I joined the chorus complaining about the audio levels -- or lack thereof. It only works if you talk directly into the phone or headset mike. The record button should be huge, instead the UI is given over to a pointless graphic. It takes too many taps to close a recording. And so on.
There was, I thought, only one good feature of Voice Memos.app. It's fast. iTalk Lite had great features, but it was too damned slow to launch and record (I'd have paid for the pro version if it were five times faster).
That was before I discovered the secret feature.
If you're wearing Apple's earset and you have Voice Memos running, one click of the microphone switch starts recording, a second click stops and saves.
So if I'm driving with my right earset in, I can click dictate and click again. No distraction, no multi-taps, no delays. This is a great feature. Now I love Voice Memos.
So, where the #$$!$ is this documented? My Google searching can't find mention of this feature. Heck, I can't find any documentation on Voice Memos.app...
... PS. There is Apple documentation on some of the microphone switch's features. You can use it, for example, to decline an incoming call (hold 2 seconds) or to switch and hold (click once) or switch and kill (hold 2 seconds). No mention of Voice Memos.app though.
Friday, March 05, 2010
Little Snitch exposes network killing MobileMe behavior
It wasn't just the lights -- the network performance sucked. Sometimes things would rush down, but at other times they'd just hang. Crazy.
Naturally I blamed Videotron. Nice people, but last time we had a problem they had to replace her router twice. As usual I got an agreeable support person. Everything tested out for him, but I couldn't run the Videotron speed test - it took ages to load. He wanted to test further, but I thanked him and told him I'd check things out internally.
You see, I'd lied to him about not having a router installed. Yeah, that's bad. I felt guilty because once he'd confirmed their network was ok I had a hunch where the problem was.
I turned my suspicions to the other machines on the WLAN, including my MacBook. Sure enough, when I shut the MacBook the modem lights slowed down and the Videotron speed test showed 1mbps downlink and 128K uplink - just what Mom pays for.
...Little Snitch has a free, built-in demo mode that provides the same protection and functionality as the full version. The demo runs for three hours, and it can be restarted as often as you like...
So I was wrong, I did have malware. Apple malware.
--
My Google Reader Shared items (feed)
The Mac Mini drive clunk (knock) problem
- Apple - Support - Discussions - Hard drive "clunk": From 2005. The clunk behavior probably shortens drive lifespan. No fix.
- Mac Mini drive click [Archive] - The macosxhints Forums: Recommends smartreporter for diagnostics
- ClunKiller - Kill your Hard Drive *Clunk* noises! and Is your Hard Drive making *Clunk* noises?
- XdN » Clicking Hard Drives and Possibly Shortened Hard Drive Life (not clear this is a clunk problem though - PC Only)
- Set Automatic Acoustic Management level on hard drives - Mac OS X Hints (open firmware hacking -- too risky for me)
- Advanced hard drive power management via AppleScript - Mac OS X Hints - obsolete, but an interesting reference
My Google Reader Shared items (feed)
Thursday, March 04, 2010
Subsite filtering - harder than it looks
- Gordon's Notes: Parental controls - not an Apple thing
- Gordon's Tech: Parental Controls - Remote Access and other tips
- Gordon's Tech: Parental Controls - The wikipedia problem solved
- Gordon's Tech: OS X parental controls still broken in 10.5.7 (this bug now fixed I think)
- Gordon's Tech: OS X 10.5: Apple engineers need more children
- Be the Best You can Be: OS X 10.5: time limited computer access
- Gordon's Tech: Can't select Jabber or Google Talk for iChat? Here's one reason.
- Gordon's Notes: The software Apple can't do
- Gordon's Tech: LEGO Digital Designer is pure evil on OS X
Tuesday, March 02, 2010
Where did my Access 2007 object descriptions go? SP2 killed them.
Sometimes I have to use Access 2007. It’s always painful, but one of the worst agony comes because there are no object descriptions anymore. It’s hard enough to manage Access entities with object descriptions, but with Access 2007 all of my Access 2003 table and query descriptions are gone.
It’s weird because I swear I used to see them buried away in Access 2007 when I used it a year or two ago. Not in a useful place mind you, but at least they existed.
Turns out Office SP2 killed ‘em off:
After you apply 2007 Office system Service Pack 2, the description of an object does not appear in the Navigation Pane in Access 2007. This problem occurs when the Navigation Pane is viewed by Details.
There’s an August 2009 hotfix for this and sundry other Access 2007 bugs, unlike some hotfixes it is downloadable. I assume it will be included in Office 2007 SP3 when that comes out.
Wicked bug.
Sunday, February 28, 2010
MobileMe vs. DropBox
Saturday, February 27, 2010
My 10.6 iMac is crashing - a debugging exercise
My now flicker-free fairly new 27" quad core iMac is crashing.
There are two common failure modes. One is that it locks up when displaying photos in the screensaver. The clue is that the same images display repeatedly. The second mode is that iTunes becomes unresponsive, and then the Finder as well. I get the SBOD/SPOD/spinning beachball of death.
If I kill both I can restart iTunes, but not the Finder. I've tried several fixes. First I ran Safe Boot (shift restart). Then I installed the latest version of Onyx and ran the usual clean, check, maintenance, etc. Everything passed but the problems have persisted.
So I've begun uninstalling anything invasive. First I removed CrashPlan, and today I uninstalled 1Password (a quite involved uninstall, see OS X defect: The missing uninstaller).
I've been suspicious of 1Password for a while. I'm also monitoring Console.app, which is full of "missing bundle identifier" Office 2008 related messages. I've found mention of this problem in association with kernel panics last November, with a more recent responses. For example:
... 2/27/10 8:10:35 PM [0x0-0x28028].com.vmware.fusionDaemon[296] 2010-02-27 20:10:35.581 pkgutil[299:60f] PackageKit: *** Missing bundle identifier: /Library/Receipts/Office2008_en_proofing_brazilian.pkg...
Tonight I'll run the Apple hardware test that came with my machine in loop mode. (I think you need to attach a physical kb to get this to work -- holding 'D' on my bluetooth kb didn't seem to do anything.) If the problem persists, VMWare will be the next to go (For example). I want it to run my XP VM, but if need be I can move that VM to a MacBook running 10.5 and Fusion 2. If I figure this one out, I'll update this post.
PS. Bundle Identifier via Apple Dev:
The bundle identifier string identifies your application to the system. This string must be a uniform type identifier (UTI) that contains only alphanumeric (A-Z,a-z,0-9), hyphen (-), and period (.) characters. The string should also be in reverse-DNS format. For example, if your company’s domain is Ajax.com and you create an application named Hello, you could assign the string com.Ajax.Hello as your application’s bundle identifier.
- I moved the suspicious Office 2008 .pkg files to another drive. I'll see if I can reduce the Console messages.
- I realized that when I drag things to the trash they're being deleted immediately, rather than put in the trash. I found an old article on this that's being cited by 10.6 users recently. Naturally it's a permissions problem. I wonder if it's related to the odd way my account was created when I used migration assistant (long story). I'll try some of those fixes.
Ok, this is interesting. As described by the X Lab document I was getting the "will be deleted immediately" trash message because I had lost read/write privileges to my home directory. On inspection my User directory folders all refer to an user "_unknown". I think this was a side-effect of how I set up my account, which was:
- I setup an account called "jfaughnan" on my new machine.
- After a while I deleted it an migrated the "jfaughnan" account from my old machine.
- The new account was given the home folder name "jfaughnan 1". On inspection I found that deleting the user "jfaughnan" failed to remove the original home directory.
Update 2/28/2010: Went through 18 loops without a problem, so hardware seems good. I'll keep hitting on the software issues - esp. VMWare.
Update 3/2/2010: I thought I was getting somewhere, but today it was unresponsive with a faint glowing blue screen. I tried putting it to sleep by pressing the power button, but nothing happened. Then, on a hunch, I turned off an attached firewire 400 drive. The system responded, then went to sleep. It woke up normally.
On resumption there was an iTunes complaint about loss of Apple Store connectivity. Meanwhile my console showed many instances of this message:
3/2/10 3:45:14 PM com.apple.launchd.peruser.502[155] (com.apple.AddressBook.abd[13839]) Exited with exit code: 1
Update 3/11/10: It's still locking up, sometimes with awake from sleep and sometimes with switching users. It might be less frequent - maybe once a week. I'm suspicious of VMWare 3.02 on 10.6.2. I don't see any useful Console messages. I will try restarting the machine every few days as a prophylactic measure. Maybe 10.6.3 will help, it should be out soon.
Update 3/12/10: Got the faint blue screen, and again turning off the external drive did the trick. The screensaver slideshow uses that Firewire 400 drive. I ran Disk Utility and cleaned up permissions on the drive. It's set to ignore ownership. Looks like yet another OS/firewire problem.
Update 3/13/10: Found iTunes was not responding. Time Machine backup not working. When I tried to add a share got spinning beachball (noted, however, a share reference to a user account that was deleted - bug there). Console said slide show found a corrupted jpeg. Unable to shutdown -- until I turned off external firewire drive. I think 10.6 and new iMacs have serious problems with Firewire 400 enclosures. Errors seem to cause the OS to blow up - perhaps some kind of memory overow issue.
Update 3/13/10c: Apple just truncated the massive firewire complaint thread. Really, it didn't have anything to do with me. I guess they took care of that problem. I've switched to USB for now, I'll try firewire again with 10.6.3.
Update 3/29/2010: Same crash - locked up screen saver - but this time I was using a USB drive. Turning the drive off then on again cleared the problem. So this isn't a firewire problem after all! It's a screensaver and external drive bug. The console is showing "corrupt JPEG data", but that might just be from power cycling the drive.
Update 5/12/2010: I think this was fixed by 10.6.3. I haven't seen it since. I only have a USB drive attached however, so I can't rule out a Firewire bug. The "corrupt JPEG" console message was a red herring caused by loss of the drive when trying to display in the screensaver.
Update 10/27/2010: Things have been pretty stable since 10.6.3.
Friday, February 26, 2010
OS X 10.6 bug: persistent reconnection
My Google Reader Shared items (feed)