MonthOctober 2007

Steve Jobs does what Moriarty couldn’t: kills Sherlock

Professor Moriarty almost did it at Reichenbach Falls, but it took Steve Jobs and his Leopard to finally kill off Sherlock. Apple’s new operating system deletes the abandoned search utility during the installation process.

Sherlock was introduced with System 8.5, but has been dying a lingering death for years, as Apple replaced its functionality with Dashboard Widgets and web utilities became more ubiquitous. Most of its tools had ceased functioning already. I haven’t even launched it in years. In fact, the only way I knew it was gone is that it’s deletion left a question mark behind in my wife’s dock after I installed Leopard.

Leopard can’t see printers shared from old Macs

I keep my main home Mac in my family room, so in order to avoid (OK, reduce) computer clutter, I keep my printers in the basement. For us, it makes a lot of sense. We don’t actually print things that often, and besides the room they take up, printers are noisy — especially our black and white laser printer.

The printers are shared from an old beige G3 PowerMac tower, which doesn’t support Mac OS X past 10.2. The G3 also hosts a personal FTP and website, and has an external FireWire drive attached for backups.

This arrangement has worked great for years — the G3 is rock-solid and the monitor is usually kept off, so the whole system doesn’t draw much power.

After upgrading our main Mac (a dual-2GHz G5 PowerMac) to Leopard over the weekend, though, I was surprised to find that it could not see the shared printers, even though it could see the G3 itself just fine. I fired up an old iBook that was still running Tiger and confirmed that it could see the printers, so it definitely seemed like a Leopard issue.

Doing a lot of searching turned up some posts on Apple’s Support Discussion boards about the issue. Apparently, Leopard drops the CUPS protocol and uses only Rendezvous. The older Macs, obviously, share printers via CUPS, making them invisible to Leopard. The answer, provided by several posters, was to edit the configuration file used by Leopard’s built-in CUPS server, to look for printers using all protocols, not just Rendezvous.

It’s a pretty geeky solution, but it worked for both of my Leopard-upgraded Macs. Although it’s probably not an issue for many users, it’s impact could be pretty major for those who are affected. The way the Mac community not only found, but came up with a way to address the issue so quickly, is very impressive.

Life can be so sweet

On a side note, my “office” this morning is Manhattan’s Bryant Park, where I’m watching ice skaters on the “pond” and listening to Louis Armstrong sing “On The Sunny Side Of The Street” on the park’s PA system. The WiFi is slow, but usable and the weather is brisk but comfortable. Pretty good working conditions, if you can get them.

Leopard 2; Gremlins 1

On the three machines on which I’ve installed Leopard so far, two went off without a hitch: a G5 iMac and a dual G5 PowerMac. The third, a MacBook Pro — ironic perhaps, in that it was the only Intel-based machine I’ve upgraded so far — not so much.

For reasons I won’t get into, I run FileVault on the MacBook Pro. I’ve gotten to used to seeing (and for the most part ignoring) messages that tell me FileVault is taking up more space than it needs and that I can fix it. I usually ignore it because 1) Space is not really at a premium on this particular laptop; and 2) It takes way too much time to do and doesn’t seem to help for very long.

So when I got this message when my MacBook was shutting down in preparation for the Leopard install, I ignored it. It think that’s what bit me. The install itself went without a hitch, but when I tried to log back into my main account, I got a message telling me my FileVault-protected Home directory couldn’t be opened. I accepted the offer to fix it, but was greeted with an “unknown error.” My main account was hosed.

Luckily, all important data had already been backed up, and the alternate account on the machine opened just fine. I wound up deleting the original account and recreating it with the same settings. So far, everything’s working fine.

Lesson learned: If you’re offered the opportunity to “fix” FileVault before installing Leopard, take it.

John Gruber made $5,800 in five minutes

Valleywag picked up on on a Silicon Alley post that calculates Daring Fireball’s publisher made almost $6,000 from Amazon affiliate links on the site to Leopard orders.

Two things. One: Gruber’s no fanboy; when Apple does something stupid he calls them on it. Two: Good for him. If I could make that much money on the traffic flowing through my site, I’d do it too.

(via Shawn King)

Best Buy faces steep penalty for pre-embargo Leopard sales

A manager at Best Buy told me the company’s Point of Sale systems (we used to call them cash registers) are being monitored for any sales of Apple’s Leopard operating system in advance of the official 6 p.m. local time release.

“We’ll be fined $130,000 for each copy we sell before six,” he told me.

That seems like a pretty steep fine. I think he might be mistaken about the per-sale part, though. I don’t know why Best Buy would agree to something with such a high potential cost in comparison to the potential return. Even if they make $40 on each copy, they’d have to sell over 3,000 copies to make up the profit lost from each one that went out early.

© 2017 RandomMaccess

Theme by Anders NorénUp ↑