Thoughts

Here’s to the simple solutions

For the past couple of days, Mail had stopped working. It couldn’t connect to the email servers for some reasons and kept taking my accounts offline. I knew I hadn’t changed any of its settings. In all my years of using a Mac (since 1994), I’d never run into a situation where Mail settings had gotten corrupted, but I was now willing to look into it. I kept looking at all sorts of scenarios and guides online — things such as these (1, 2, 3, 4) — but nothing helped.

Then it occurred to me that three days ago, as I worked late, past midnight, I got the bright idea to switch the firewall level to High from Medium. “Oh, let’s get some extra protection, shall we?” My router is one of these gizmos handed to me by my ISP, it’s a ZTE that came with no printed documentation and barely any online documentation beyond “this is ON button, this is internet port”. So how was I to know that switching it to High would mean all traffic other than port 25 and 80 would be closed off? But that’s what happened. I did it, forgot about it, and when my email stopped working, it took me a couple of days to connect the dots.

I’m writing this down for you because it’s a great reminder that sometimes the simple solutions are the best (and possibly the only) ones. That, plus writing down changes to the internet configs, especially when I’m working late… Sure, I could have taken a dive into deep-level Mail documentation and email servers and the intricacies of setting up IMAP and opened up ports on my firewall and deleted my Mail settings and set up everything again, but all it took was me logging onto the ISP router and switching the firewall back down to Medium. Less than a minute vs. hours and hours of needless work.

Screen Shot 2016-07-21 at 13.53.34

Good to know, right?

Standard
Reviews

Initial thoughts after installing OS X Lion

I thought I’d jot down a few thoughts about OS X Lion, having just installed it on my MacBook Pro. I looked forward to getting it for months, and as luck would have it, I happened to be out of town with little internet access when it was released on the 20th.

  • The upgrade was painless. I bought it from the App Store, it began to download, and when it was done, it ran and finished without any bugs.
  • Without a media disc of some sort, or at least an image file, I am somewhat concerned about a re-install of the OS, should I need to do a fresh install. I hear there’s going to be a Lion Flash Drive available for sale in a month or so, but short of paying for that as well, is there some way for me to burn Lion on a DVD or make a bootable flash drive?
  • Overall, I like it. The design is more refined. It feels like a more mature OS.
  • I like the full-screen functionality of the apps.
  • The login screen is interesting. It’s a departure from what we’ve seen thus far. I like it, but I’m not sure what to think about the round thumbnails for the accounts yet. I’m used to square thumbnails. Photos are rectangular. Square photos? They used to be en vogue in the late 1800s. But who knows, maybe those round thumbnails will grow on me.
  • I do wish iCloud were launched at the same time as OS X Lion. For example, I don’t know if I did something to cause this, but every time I start up Safari, it wants to log me into MobileMe, where I don’t have an account. (I only have a .Mac email address.) If iCloud had been available right now, this glitch wouldn’t have occurred, because .Mac and MobileMe would have been unified already. And I think more people are going to run into it as they poke around in the new OS.
  • The hidden scrollbars are great, but they’ve changed the direction of the scrolling, haven’t they? It’s counter-intuitive… and yet it’s not. You now push up with two fingers on the trackpad to scroll down, and pull down to scroll up. If you think about it, it makes sense, but it’s been the other way around until now, so it’ll take a while to get used to it.
  • I like Launchpad. I think it’s a visually appealing way to present a list of all the Apps on my Mac, and to allow me to easily choose which one I want to run.

A couple of pieces of advice before you upgrade:

  • Run Software Update to make sure you’ve got the very latest version of Snow Leopard and whatever other updates you need.
  • Run Time Machine to make sure all your stuff’s backed up, just in case something goes wrong.

For those who like this sort of thing (I do), I’ve included a couple of before and after screenshots of my “About This Mac” window.

Before the upgrade to OS X Lion

After the upgrade to OS X Lion

That’s it for now.

Standard
Thoughts

What Microsoft Can Learn From Mac OS X Lion

This article makes a point which has been on the mind of Windows and Mac users for quite some time: namely, that Microsoft ought to stop selling so many versions of its OS. It’s confusing, it’s expensive, and from my point of view, underhanded.

What Microsoft Can Learn From Mac OS X Lion

They should take a cue from Apple, which has only two versions of its OS: its consumer version (for desktops and laptops), and its server version.

With OS X Lion, it looks like they’ll simplify things even more. It may ship with only one version, allowing those who want the server version to activate the server components as an add-on. Cheers for that!

Another point of contention for me is the ridiculous price difference between Windows and OS X. Windows can cost upwards of $300-500, depending on the version you choose, while OS X is just $129. Windows OS upgrades can cost anywhere from $200-300 dollars or more, while OS X upgrades are just $29.

The price difference is incredible, and I can’t help feeling cheated whenever I need to shell out that much money for a Windows license. What am I really getting in return, when I compare their OS with the Mac experience?

Standard
Thoughts

File corruption rears its ugly head

During the last few weeks, I’ve seen the following error in Adobe Lightroom 3.

There I am, editing photos, minding my own business, and when I try to view a photo for editing, I get the error message you see above: “The file appears to be unsupported or damaged.”

When I try to view the file in the finder, I get the same error message, this time directly from the OS: “The file […] could not be opened. It may be damaged…”

Here’s my workflow:

  1. Shoot RAW
  2. Import RAW files as DNG into Lightroom (LR converts them on the fly)
  3. Process in LR
  4. Export as JPG or as needed
  5. Back up the catalog and check its integrity weekly

It’s pretty straightforward, and that’s the way I like it. I currently have about 85,000 photos in my LR library, whose catalog is stored locally on my MBP, with the files (DNG, RAW, JPG and TIF) residing on a Firewire Drobo.

Fortunately, the file corruption is only temporary, meaning there’s an error somewhere along the way:

  • It could be Lightroom
  • It could be the DNG file format (because I haven’t gotten the error with RAW or JPG files)
  • It could be OS X: I wonder how much testing Apple did for 10.6.5 with volumes greater than 4TB
  • It could be the Drobo: it’s a big volume (4.4TB) with lots of data that’s constantly being updated, lots of I/O traffic

I don’t know, and I hope someone reading this has an answer.

What fixes the error every time is quitting LR, ejecting the Drobo, cycling its power, mounting it, and starting LR. I’ve also tried just restarting LR, or just ejecting the Drobo, but those methods didn’t work.

Standard